Instructor Contact Information
Name:
Office:
John Petlicki
CTI 429, 4:30 - 5:30 p.m. (or by arrangement)
Phone:
E-mail:
URL:
(847) 679-4169 jpetlick@condor.depaul.edu
http://www.depaul.edu/~jpetlick/430_301
COURSE DESCRIPTION:
The course objective is to produce analysis and design documents that can be used to develop object-oriented software systems.
This course will cover

Object-oriented analysis/design concepts

UML notation

Approaches to transforming a problem into an object oriented analysis model and object oriented design
TEXTS:
Book Title Author(s) ISBN
Applying UML and Patterns Craig Larman (L) 0-13-748880-7
Fundamentals of Object-
Oriented Design in UML
Meilir Page-Jones (P) 0-201-69946-X
1

Session
Date
Topic(s)
1) 4/4 Syllabus,
Software Development,
Software Models
2) 4/11 Communicating Design,
Use Cases,
Problem Statement
3) 4/18 Requirements,
Business Rules,
Essential Use Cases,
Use Case Diagrams,
Use Case Prioritization
4) 4/25 Associations,
Attributes,
Conceptual Model,
System Glossary
5) 5/2 System Sequence
Diagrams
Real Use Cases
Connascence
Reading Student Deliverables
(L) 1-5
(P) 1-2
(L) 6
(P) 3
(L) 7-9
(P) 4

Class Exercise

Start team formation (4-5) members

Start formulating project statement
Assignment (5 points)

Identify Team (team name)
 list team members
 give a short description of the team project
Assignment (5 points)
 requirements of the project

Business rules

Essential Use Case Descriptions

Use Case Diagram (all use cases)
(L) 10-12
(P) 5
Assignment (5 points)

Conceptual Model with associations & attributes
6) 5/9 Assigning
Responsibilities,
Robustness Analysis
CRC Cards,
7) 5/16 Contracts
Collaboration Diagrams
Interaction Diagrams
8) 5/23 Design Class Diagrams,
Patterns
9) 5/30 Design Class Diagrams,
Patterns, Recap
10) 6/6 Student Presentations
Final Project Due
(L) 13-14
(P) 6
Assignment (5 points)
Pick 1 or more of your more interesting use cases and for each use case,
 expand the use case to show typical and alternate courses of action

Create System Sequence Diagrams

Design the User Interface

Create a Real Use Case
Assignment (5 points)
Pick 1 or more of your more interesting use cases and for each use case,

Create a robustness diagram

Create CRC cards
(L) 18-20
(P) 9-10
Assignment (5 points)


Ideal Object Diagrams

Collaboration Diagrams
Object Diagrams for starting and ending configuration of two use cases
(L) 21-22
(P) 11-12
Assignment (5 points)

Interaction diagrams (sequence or collaboration) of use cases

Design Class Diagrams
(P) 13-14 
Preview assessment of All Project Material to Date
Assignment (20 points)

Team Presentations of Project Work
Assignment (50 points)
 Project Material
 Team Member Participation Survey
2

GRADING:
Grades will be determined by the percentage of maximum possible points earned.
5 point penalty for any missed assignment
Assignments earning points: Maximum Point
Value
30
20
Weekly group assignments (6 X 5)
Final Presentation
Members of a team must give a portion of the presentation to earn points
Project Documentation
Maximum Points
Bonus points
50
100
TBD
Grading Policy
Final letter grades represent the total points earned as a percentage of the maximum possible (200).
Total
Points
Letter
Grade
94-100 A
90-93.9 A-
87-89.9 B+
83-86.9 B
80-82.9 B-
77-79.9 C+
73-76.9 C
70-72.9 C-
60-69.9 D
0 -59.9 F
3

Every member of the class session must be a member of a project team (4 to 5 people).
The team is responsible for the project and team members should review all materials prior to submission for a team grade.
Each team member is expected to participate in all team activities in such a way that the other team members perceive the work as evenly distributed.
Team member ratings will be handed in at the end of the term.
Evaluations should be prepared individually without consultation of other team members.
Team members who do not participate fully WILL NOT receive full credit for the team project.
NO ASSIGNMENTS WILL BE ACCEPTED AFTER 6 / 6 / 2001
4