CS-489 Cycle 2 Final Report

This 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 designation, and names of team members.
2. Table of contents.
3. Executive summary, briefly describing project, including benefits and total project development cost.
4. Project (Cycle 1 and Cycle 2) requirements
5. Domain model (updated and corrected from previous reports):
• Include concepts, attributes, and associations; be sure to explain the attributes.
• 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. Use cases for project (Cycle 1 and Cycle 2).
8. Interaction (Sequence or Collaboration) diagrams, including relevant presentation layer behavior.
9. Design class diagrams, with supporting diagrams (e.g., state charts) as appropriate.
10. Glossary of terms (updated from previous reports):
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. User documentation with the following content, as applicable:
    1. Instructions for executing the software.
    2. Screen displays and user prompts (you may refer to screen displays from design documentation if you wish).
    3. Expected input.
    4. Error messages and recovery procedures.
    5. Output report formats and/or examples.
    6. Input and output data file formats.
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.
• Possible enhancements and other issues
14. Project management information (see process details):
• Time spent on the project, by team member and phase. Include summary totals by team member, by phase, and for the entire project.
• Weekly time log summary for all eight weeks of the project broken down by team member.
• Total project development cost, using a reasonable hourly rate.
• 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.
• Listing of claimed extra credit (e.g., optional features).
15. Additional project documentation (optional):
• 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. Program source code as an appendix and in the 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.
17. Your CASE tool model file (in the zip file).