CS-489 Phase 2 Analysis/Design Report
The phase 2 analysis/design report should contain the following items (items from
previous reports should be updated to reflect the current state of the project):
- Title page, including project name, team number, and names of team members.
- Table of contents.
- Project (phase 1 and phase 2) requirements.
- Analysis use cases:
- Expanded essential use cases for project (phase 1 and phase 2) requirements.
- Conceptual model (updated from previous reports):
- Include concepts, attributes, and associations.
- Document in one or more Rose class diagrams.
- System behavior:
- System sequence diagrams (Rose), with use case references or text.
- Contracts for system operations (Word).
- Real use cases for project (phase 1 and phase 2).
- Collaboration diagrams, including relevant presentation layer behavior.
- Design class diagrams.
- Glossary of terms (updated from previous reports).
- This should include a report of all the documentation in the Rose design model,
including:
- Operation specifications (arguments, preconditions, postconditions, semantics, etc.)
- Attribute specifications (types, description)
- Association specifications
- You may use Rose's "print specifications" and documentation report features to
generate most of this information.
- Issue list (updated from previous reports):
- Risks and contingency plans:
- Identified risks and status (potential, actual, resolved, etc.)
- Contingency plans for identified risks.
- Development problems and issues:
- Pending problems.
- Possible enhancements.
- Other issues.
- Project management information (see process details):
- Time spent on the project to date, by team member and phase.
- Copies of the time tracking sheets (or other form of recording) of all team members.
- Team comments on development process and suggestions for improvements.
This page was last updated on November 01, 1998. Send comments to Mark Sebern.