CS-489 Cycle 2 Analysis/Design Report

The Cycle 2 analysis/design document should contain the following items (items from previous reports should be updated to reflect the current state of the project):

1. Title page, including project name, team designation, and names of team members.
2. Table of contents.
3. Project (Cycle 1 and Cycle 2) requirements:
4. Analysis use cases:
• Expanded essential use cases for project (Cycle 1 and Cycle 2) requirements.
5. Domain model (updated and corrected from previous reports):
• Include concepts, attributes, and associations.
• Document in one or more UML class diagrams drawn using a CASE tool.
6. System behavior:
• System sequence diagrams (CASE Tool), with use case references or text.
• Contracts for system operations (e.g., Word).
7. Real use cases for project (Cycle 1 and Cycle 2).
8. Interaction (Sequence or Collaboration) diagrams, including relevant presentation layer behavior.
9. Design class diagrams
10. Glossary of terms (updated from previous reports):
11. Issue list:
• Risks and contingency plans:
• Identified risks and status (potential, actual, resolved, etc. - include relevant dates)
• Contingency plans for identified risks.
• Possible enhancements and other issues
12. Project management information (see process details):
• Time spent on the project to date, by team member and phase. (It is likely that all the effort to date will be in the "planning" phase of Cycle 1 of the project.) Include summary totals by team member, by phase, and for the entire project.
• Copies of the time tracking sheets (or other form of recording) of all team members.
13. Your CASE tool model file.