CS-489 Cycle 1 Final Report

The Cycle 1 Final document should contain the following items (items from previous reports should be updated to reflect the current state of the project and the instructor's feedback):

1. Title page, including project name, team number, and names of team members.
2. Table of contents.
3. Project (Cycle 1 and Cycle 2) requirements (updated from analysis report)
4. Domain model (updated from analysis report):
• Include concepts, attributes, and associations.
• Document in one or more CASE Tool drawn class diagrams.
5. System behavior (updated from analysis report):
• System sequence diagrams (CASE Tool), with use case references or text.
• Contracts for system operations (Word).
6. Use cases (updated from analysis and design reports):
• High-level use case(s) for project Cycle 2 requirements.
• Final use case(s) for Cycle 1 requirements.
7. Interaction (Sequence or Collaboration) diagrams (updated from design document).
8. Design class diagrams (updated from design document).
9. Code review report(s), with a copy of reviewed code for the first (in-class) review only.
10. 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.
11. Program source code as an appendix and in a zip file with your other project files. Do not include files that I can recreate simply by building your project, with the exception that your executable file(s) should be in the zip.
12. Glossary of terms (updated from previous reports).
13. Issue list (updated from previous reports):
• Risks and contingency plans:
• Identified risks and status (potential, actual, resolved, etc. - include relevant dates)
• Contingency plans for identified risks.
• Development problems and issues:
• Pending problems.
• Possible enhancements.
• Other issues.
14. 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.
15. Additional project documentation (optional):
• User documentation draft (user documentation will be required in Cycle 2).
• Code review checklist.
• Reference material (e.g., CASE or Development Tool) developed by team members (e.g., development or support managers).
• Any other material that is relevant to understanding the project or process.
16. Your CASE tool model file.