- Course Title and Number
- ITC 255 Systems Analysis
- Credits
- 5
- Times
- TTH 1:00 PM- 3:10 PM
- Prerequisites
- ITC 110
- Course Overview
- This course uses scenarios to intruduce the student to techniques for approaching, analysing and developing Complex systems and programming problems. It focuses on the use of Unified Modeling Language (UML) and object oriented concepts to describe requirements. and procedures.
- ADA
- If you need course adaption or accomodation because of a disability, if you have emergancy medical information, or if you need special arrangements if the building must be evacuated, please make an appointment with your instructor as soon as possible
- Instructor
- Steve Conger
- Office Location
- BE3168A
- Office Phone
- 206.587.5458
- Office Hours
- See Schedule
- sconge@sccd.ctc.edu
- Web page
- http://seattlecentral.edu/faculty/sconge
- Educational Philosophy
- The pre-Socratic Philosopher Heraklitos said, "it rests by changing." By this he meant that the normal state of things is constant change. This has never been more true than today. Though, the course focuses on particular software, it has a broader purpose: Software changes constantly. The most important skills to learn, are the techniques for learning new skills, new software, and learning how to generalize the skills you've learned in order to apply them to new situations. These are the skills that will keep you afloat in stream of constantly changing technology
- Student Outcomes and competencies
- Understand Systems Analysis Concepts and terms
- understand and use object oriented concepts
- Gather information about project requirements and users
- Create use cases to diagram project requirements (using Visio)
- Determine alternative solutions and analyse their feasibilities
- Create Class diagrams for the problem domain
- Create Activity and Sequence diagrams to describe procedures and methods
- Create a prototype of some aspect of a project
- Work with others effectively in groups
- Present materials effectively
- Methods of Instruction
- There will be some lecture on concepts, but much of the class will be hands on. We will do examples together and then I will provide practice time.
- Textbook
- The Object Oriented Approach Second Edition, John W. Statxinger and Tore Oruck, Course Technology
- Other Resources
- Handouts. On-line notes
- Assignments and Schedule
- The large part of the class will be spent working in groups on designing systems in response to scenarios, but there will also be individual assignments, and lecture on various topics. Tuesdays will be mostly devoted to lectures and individual assignments; Thursdays will be mostly devoted to the scenarios.
| Week | Topic | Assignments |
|---|---|---|
| Week One | Overview of Systems and UML. The nature of "Objects" | Read chapters 1 and 2; Excercises for Chapter 2 |
| Week Two | More Objects | Read chapters 3 and 4; Excercises Chapter 4 |
| Week Three | Introduction to UML Use Cases, class diagrams; Life Cycle; Introduction to scenarios | Read chapter 5, chapter 8, Excersises chapter 5, Form Scenario groups and begin |
| Week Four | Determining Requirements; More object oriented Models requirements | Read chapter 6 and 7, Excercises chapter 6. Scenario work |
| Week Five | Determining Alternatives and Feasibility | Read chapter 9, Midterm, Scenario worl |
| Week Six | Object oriented Design, | Read chapter 10, Scanario group presentations of Alternatives |
| Week Seven | Domain Class Diagrams, Activity, State, and Sequence Diagrams | UML Excercises (handouts) Scenario groups |
| Week Eight | More Activity and Sequence diagrams, 3 tier approach, applying UML to Coding | Code assignment (handout); Scenario Work |
| Week Nine | Database Design and Development. Prototyping | Database Assignment (handout); Scenario work |
| Week Ten | Scenario Work and Midterm 2 | Midterm; Scenario work |
| Week Eleven | Presentations of scenario groups/td> | presentations |
- Grading and Attendance
- Attendence is critical. We will be covering material and doing labs most every day. If you know ahead of time you will not be able to attend, let me know as soon as possible. Otherwise contact me as soon after the abscence as you can.
