SE/CS343, CS543 Object Oriented Analysis and Design

Fall 2009

Instructor: Mike Rowe

Office: 215 Ullrich Hall

Phone: 342-1511

Email: rowemi@uwplatt.edu

Office Hours: see web site http://www.uwplatt.edu/~rowemi/



Course Description:

Requirements engineering, analysis, and specification using the object-oriented paradigm. Object-oriented architectural and detailed design. Use of an OOA&D modeling language such as UML. Investigation of OOA&D patterns. Moderate size, group project. (Fall) Components: Lecture Cross Offering: COMPUTER 3430; Prereqs/Coreqs: P: SOFTWARE 2730.

Course Outcomes:

Upon completion of this course, students should be able to:
  1. Understand the role of requirements engineering in software development
  2. Research a domain to obtain information sufficient to specify a software system
  3. Specify a software system using requirements and use cases
  4. Understand and practice at least one method for developing a good object-oriented design
  5. Understand the role of and develop an introductory competency in the following software engineering modeling tools or methods:
    1. Use Case diagrams and flows
    2. Class diagrams
    3. Sequence diagrams
    4. State diagrams
    5. Executional Architecture generation from a Class model
  6. Understand the benefit of patterns in analysis and design
  7. Become familiar with roles and contribute in a professional manner to a software engineering team.

SE Department: Goals, Objectives, Outcomes

Important Dates:

  • Classes Begin: 1-Sep-2009
  • No Classes: 7-Sep-2009
  • Fall miniBreak No Classes: 16-Oct-2009
  • Last day to drop/withdraw from classes: 27-Oct-2009
  • Thanksgiving: (26-27)-Nov-2009
  • Last day of classes: 11-Dec-2009
  • Final Test: Group 10, Tuesday, 15-Dec-2009 7:00pm in (probably in Velzy Commons
  • Fall 2009 Exam Schedule (all classes)

Preliminary Schedule for Assignments / Deliverables / Quizzes / Tests

Time Reporting Ground Rules See Time Reporting RequirementsUpdated 7/20/2009 for details.

Proj 0: Select team members
Each group SHALL have at no more than one graduate students. Minimum team size shall be five (5) and maximum six (6). Email me no later than Noon 4-Sept. with your team roster. See specific details at: Project 00 Requirements Updated 8/23/2009 for details.

Deliverable 001: Concepts Document
Template / Example of a Project Report
A project report will be required for each deliverable (except for deliverable 0). Below is a link to a template for a project report.
Example Project Report Updated 20-Jul-2009 (in MS Word Format)


QUIZ 01: Tuesday, 22-Sept-2009

Proj 2: Requirements Document Due 21, 28-Sept 12:05 pm

QUIZ 02: Thursday, 1-Oct-2009


QUIZ 03: Tuesday, 13-Oct-2009

Proj 3: Preliminary Use Case DevelopmentDue: 08, 13 Oct.
Proj 4: Use Case Scenarios and Data Requirements Due xx, xx Oct.
Mid Term Test: Oct 20 (all topics from beginning of semester)


QUIZ 04: Thursday, 5-Nov-2009

Proj 5: Analysis Level Class Diagram Due 04,11 Nov. -->
Proj 6: Design Level Class Diagram Due xx, xx Nov .
Proj 7: Interaction Diagrams Due xx Nov,
Proj 8: State Diagrams Due xx DEC,
Test 2:xx Dec
Proj 9: Executable Architecture Due xx DEC
Proj 10: Design Patterns Due xx DEC
Peer Evaluation Assignment Due xx DEC
Proj 04 . . . Quiz 04

Class Notes/Handouts

Syllabus
Syllabus Updated 27-Aug-2009 (in MS Word DOC Format)

Introduction
Notes001: Introduction to OOA&D Updated 15-Aug-2009 / (in MS Word Format)

Notes001: 2004 Chaos Report paper Updated 3-Sep-2009 / (in MS Word Format)

Requirements
Notes002: Requirements Updated 5-Sep-2009 / (in MS Word Format)
Good Specifications and Requirements Updated 5-Sep-2009 / (in MS Word Format)
See notes # 12:
  • Section 4.1: Distribution of Control Patterns
  • Section 4.2: Safety and Reliability Patterns
  • Section 5.3.2: Observer a.k.a. Publisher-Subscriber Pattern
  • Security Example, Four Eyes Security, San Fransico IT Manager
Analysis, Design, and Process
Notes003: Analysis, Design, and Process Updated 23-Sept-2009/ (in MS Word Format)

Use Case Centric Analysis Approach
Notes004: Use Case Centric Analysis Approach Updated23-Sept-2009/(in MS Word Format)

Notes004a: Use Case Language Updated23-Sept-2009/(in MS Word Format)
Class Diagrams
Notes005: Class Diagrams Updated 11-Oct-2009/(in MS Word Format)

Interaction Diagrams
Notes006: Interaction Diagrams Updated 11-Oct-2009/(in MS Word Format)

Rose MDL Message example Updated 11-Oct-2009/(in Rose MDL file)

Rose MDL Elevator Example Updated 11-Oct-2009/(in Rose MDL file)

Class Associations
Notes007: Class Associations Updated 28-Oct-2009/(in MS Word Format)

MDL file to Flight/Plane and Account Example
Special Classes
Notes008: Special Classes Updated 3-Nov-2009/(in MS Word Format)

Unit Testing Design
Notes009: Unit Testing Updated 14-Oct-2009/(in MS Word Format)

Class V and V
State Diagrams
Executable Architecture
Patterns
Notes012: Patterns Updated 5-Sept-2009(in MS Word Format)

<------------------------------------------>

Other SE and CS Classes