Iteration 5 should include the following at a minimum:
Also called a QA Plan, this document should include details on how you intend to test (verify and validate) your system, and it should include acceptance tests for your highest priority SRS use-cases and system tests for your highest priority functional requirements. A validation plan document template is provided in PolyLearn. Include plans for continuous integration and automated testing. Ideally, set this up with a proof of concept.
You should have a vertical prototype complete in this iteration. A vertical prototype implements one small slice of functionality using all key architectural technologies. A link to the vertical prototype should be posted in an email to Dr. Janzen. Because your vertical prototype environment may go away at some point, static screenshots should be posted in a document to Dr. Janzen.
The architecture document should be complete. All technologies and components should be identified and described. The system organization and behavior should be clearly described to the degree that detailed designs could be generated.
Ensure that your SRS is as complete as possible. Address customer concerns with your SRS.
Create a traceability matrix that maps SRS elements to Design artifacts and QA artifacts. You may choose the tool and format for your matrix. A simple table may be sufficient. Keep the matrix as concise and simple as possible. For example, use identifiers (e.g. UC-4) and keywords (e.g. Add Curve) rather than sentences.
Present all final artifacts to your customer on November 30. Discuss plans for transitioning to software construction iterations in January.
Post all artifacts on https://sites.google.com/site/secapstone1213/. Get access from Dr. Janzen by sending him your gmail address (or whatever email you want to use to access Google Sites).