CS-489 Phase 1 Final Report

Version 1.2 (11/3/1998)

The phase 1 final report 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 number, and names of team members.
2. Table of contents.
3. Project (phase 1 and phase 2) requirements (updated from analysis report)
4. Analysis use cases (updated from analysis report):
   • High-level use cases for project (phase 1 and phase 2) requirements.
   • Expanded essential use cases for phase 1 requirements.
5. Conceptual model (updated from analysis report):
   • Include concepts, attributes, and associations.
   • Document in one or more Rose class diagrams.
6. System behavior (updated from analysis report):
   • System sequence diagrams (Rose), with use case references or text.
   • Contracts for system operations (Word).
7. Real use cases for phase 1 (updated from design document).
8. Collaboration diagrams (updated from design document).
9. Design class diagrams (updated from design document).
10. Code review report(s), with a copy of reviewed code for the first (in-class) review only.
11. Test plan:
    • Unit test
      • List of tests and results for each test.
      • Scaffold code (drivers, stubs), if any.
      • Test data files, if any.
    • System test
      • List of tests and results for each test.
      • Test scripts or other test procedure documentation.
      • Test data files, if any.
12. Program source code (preferably in a ZIP file, optionally in a UNIX tar file).
13. 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.
14. 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.
15. 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.
    • Defect data summary.
    • Team comments on development process and suggestions for improvements.
16. Additional project documentation (optional):
    • User documentation draft (user documentation will be required in phase 2).
    • Code review checklist.
    • Reference material (e.g., Rose or MFC) developed by team members (e.g., development or support managers).
    • Any other material that is relevant to understanding the project or process.

This page was last updated on November 03, 1998. Send comments to Mark Sebern.