Once your project has passed its final acceptance test, the software is considered complete. At this point, it is now possible to ensure the entire project notebook is internally consistent.
Specifically, the following elements of the final project notebook must be consistent with the final, accepted software:
Note that you must get approval from the TA before making any modifications to your requirements document. The software you produce in your project is intended to implement the functionality described in your requirements specification. If the code does not match the requirements, there is either a requirements error, or you must modify your code to match the requirements. Since the requirements are an agreement between your team, and your customer (the Professor and the TA), you cannot change this agreement without approval from both parties.
In addition to producing the final project notebook, you must also ensure that your project Web site is complete, with the most recent versions of all documents available on the Web site. Additionally, the Subversion repository must contain the version of the software used during the acceptance test.
Typically, groups will turn in their final project notebooks at the conclusion of a successful acceptance test.