The ideal team size is about 4.
The work is assigned on a Thursday so you have more days to do it.
There will be time at the end of each Thursday class to
start each iteration.
The work is
timeboxed: Present what you have at the start of the class when it is due.
Give me the Deliverables then.
Exception -- the final version of the project is due at the start of
Project deliverables can be hard copy or a link plus access to
the information on the web. If you elect to put artifacts on the web
keep with the safer formats: .html, .txt, .pdf, .gif, .jpg.
You are building up a packet of artifacts, increment by increment.
In theory source code, tests, and executables would be a major part
of each iteration.... but we won't have time in this class to do this.
- Vision + Business case
- Use case Diagram
- Use cases: details on interesting scenarios.
- Supplementary specifications: desirable qualities.
- Architecture -- package diagram
- Domain model class diagram
- Business Rules
- System Sequence Diagrams for nearly all interesting scenarios.
- Interactions: sequence or communication diagrams for all interesting
messages in your SSD....
- Design classes (DCD) that support all your interactions.
|Due in Class#||Project Work(10 pts)
|03||W0 (Project Vison)
[ w0.html ]
|05||W1 (Inception: section 4.3)
[ w1.html ]
|07||W2(Use Case Model 1)
[ w2.html ]
|09||W3(Domain Model 1)
[ w3.html ]
|11||W4(transition to design: SSD+packages)
[ w4.html ]
|13||W5(Interaction + Class Diagrams)
[ w5.html ]
[ w6.html ]
|17||W7(Model 2: use cases, domain, objects, classes)
[ w7.html ]
|19||W8(Model 3: model 2 improved)
[ w8.html ]
|Final||W9(Model 4: model 3)
[ w9.html ]
Don't forget to read the web pages and the assigned part of the book,
and do the review questions.