MET CS 682 Systems Analysis and Design

Last updated December 28, 2005: Last few changes often in red font

Description:

This course describes object-oriented methods of information systems analysis and design for organizations with data-processing resources.  It covers the discovery process for system feasibility, and describes stakeholder analysis and information requirements analysis. The course explains use cases and the manner in which they are applied to requirements analysis.  It covers project management, control, and risk analysis.  Hardware/software trade-offs are discussed.  The Unified Modeling Language (UML) for describing system designs is defined and described.  Database utilization is included in the course, as are software designs with UML models.  Data flow and state models are integrated with the design coverage.  The course covers implementation management, system-level testing, and system installation. 4cr

Prerequisite:

MET CS 579 or MET CS 669.

Learning Objectives

Learning Goals for CS 682

• Distinguish among types of business systems
• Describe a proposed systems analysis project
• Examine the issues of working in a team
• Distinguish high- from low-level requirements
• Examine the goals of good system design

Course Learning Outcomes for CS 682

• Deal with risks
• Develop a project schedule
• Write functional and non-functional requirements
• Write use cases
• Use classes in Object-Orientation
• Relate classes to each other
• Create sequence and other UML diagrams
• Construct system architectures

Textbook and Materials

System Analysis and Design Methods by Jeffrey L. Whitten, Lonnie D. Bentley.  Publisher: McGraw-Hill/Irwin;

Evaluation of Students

Absorbing and synthesizing system analysis techniques will be expected of all students.  To attain excellence, students will be expected to create original analyses and comparisons.

The course grade will be computed from the following

Weekly assignments: 45%

Weekly quizzes: 20%

Final: 35%

Students may be given a number of pass/fail assignments throughout the semester.  A “Pass” grade is required on all of these.  A grade of A or A+ may be given for a pass/fail homework when the student has gone well beyond the requirements of the problem and has performed exceptionally.

Late homework will not be accepted unless there is a reason why it was impossible to perform the work in time given work and emergency conditions.  In that case, e-mail the written reason should be attached to the homework, which will be graded on a pass/fail basis if the reason is accepted by me.

Warning concerning plagiarism

Please cite all references and uses of the work of other.  All instances of plagiarism must be reported to the College for action.  e-mail, see or call me if you have any doubts about the proper use of others’ material. In any case, clearly acknowledge all sources in the context they are used, including code, of course.  See plagiarism policies for examples and a fuller explanation.

Syllabus

9/8 and 9/22(note): Introduction and Process

• Types of business systems
• Participants in systems analysis
• A systems analysis example
• Introduction to system process

Readings: Notes + pages 4 through 29 in the textbook

9/29 and 10/6: System Project Management

• System development processes
• Team interfaces
• Team inter-personnel issues
• Risk management
• Project scheduling

Readings: Notes + pages 80 through 179 in the textbook

10/13 and 10/20: System and Requirements Analysis

• The meaning of “Requirements”
• High-level requirements
• Detailed requirements
• Functional requirements
• Non-functional requirements

Readings: Notes + pages 184 through 267 in the textbook

10/27 and 11/3: Modeling with UML

• Classes
• Class relationships
• Use cases
• Sequence diagrams
• Data Flow diagrams
• State diagrams
• Activity Diagrams

Readings: Notes + pages 270-289, 342-397, 428-465 in the textbook

11/10 and 11/17: System Architectures

• Design Purposes
• Software Frameworks
• Trading off Architecture Alternatives
• The Façade Design pattern
• Categorizing system architectures
• Component technology

Readings: Notes + pages 470 through 545 in the textbook

12/1 and 12/8 Object-Oriented Designs

• Relating Use Cases, Architecture, and Detailed Design
• Sequence and Data Flow Diagrams for Detailed Design
• Detailed Data Flow Diagrams
• Specifying classes and functions
• Standards for Detailed Design

Readings: Notes + pages 684 through 716 in the textbook

12/15: Final

Forums — past and present

Fall 2004