The final project report is a summary of the your work over the semester. This document should be something that an interested party (e.g. a prospective employer) can read to gain a thorough understanding of your course project. For example, it should include the following:

• Introduction and motivation (revised from Assignment 2)
• Group overview (roles, responsibilites, credit assignment)
• A few paragraphs explaining group dynamics, how the plan differs from the result, difficulties encountered, and how the group managed these difficulties
• The group's approach to each phase of the development cycle (analysis, design, implementation/testing, and delivery)
• The group's "story" through each iteration - how the project progressed through each of the 3 iterations.
• Conclusion and future work
• Source code

It should also include the following artifacts:

• Complete list of requirements, along with priority, and an indication of whether it was completed (revised from Assignments 3, 7)
• Use Case Diagram (revised from Assignment 3)
• Final UML Class Diagram (revised from Assignments 5, 7)
• Sequence Diagrams to illustrate complex behavior (from Assignment 4)
• Test cases
• Any other design artifacts you deem relevant, especially E-R diagrams!

Submission

Submit on blackboard (the actual content), and make the content available on your group website as well.

Submit your test plan, and the code running your sets of test cases. Remember, each test case consists of the chosen input value, the expected output value, the code to run the test, and some indication of what component you are testing.

Since blackboard does not let you upload .zip files, you may email the instructor a zip/tarball containing the code. Other documents should be submitted on blackboard and posted to your website.

Giving Credit

Grading

• 50% - The final resulting software: quality and completeness
• 50% - This Final Project Report: quality, completeness, and correctness (including the revised diagrams)