UML Deliverables - Team Project

UML for the capstone will consist of three things:

• Use Case Descriptions
• Class Diagrams (analysis level)
• Sequence Diagrams

Use Case Descriptions

Due: 9/26; 10/24

For the new functionality in the release, generate one Use Case Description/Flow of Events. Use the format from the Bruegge & Dutoit book, page 45 (don't worry about the flow of events indentation if Word doesn't cooperate).

If would be advisable to run the list of use cases by the client prior to submission so you don't miss something critical!

Class Diagrams and Sequence Diagrams

Due: 10/8; 11/7

For the class diagram, you will need to include the following:

• All new classes needed for your updates, including their attributes and methods (with the exception of get and set methods).
• All SEURAT classes that your classes will interact with. Do not give attributes and methods that are in the original version of SEURAT but if you need to add new attributes or methods provide those on your diagram.

For the Sequence diagram, for the first release, give the sequence diagram to print the traceability matrix. Assume that at the start of the use case the user is looking at the SEURAT Rationale Explorer.