Checklist for final submission
==============================

As part of the final submission for the project, teams should submit
the final versions of alla of their deliverables, including the final release.

An important part of the final submission is the close-out document,
which acts as a reflection and summary of the project. The team is expected
to submit one close-out document between them. The close-out document
does not need to be an overview of your entire project, but rather just
a brief reflection.

As part of the submission, please make a directory in your team directory
called 'delivered' with  everything that was delivered to the client inside,
as well as all other deliverables, including the final SRS, SDD, test plans,
test scripts, and source code, and the close-out document.

The following is a checklist of deliverables that should be in the
final submission:

1. SRS.

2. SDD(s).

3. Test plans.

4. Source code.

5. Test scripts, drivers, stubs, etc.

6. The final release.

7. A README describing how to build and run the system.

The following is a checklist for items that should appear in your close-out
document:

1. Lessons learnt (the big things, not "svn ci commits my work").

2. What you would have done differently.

3. What is still left to for completion of the product and why it has
not been done.

4. Where the project could go from here if you had more time.

5. Any other comments reflecting on the project as whole.