Create a deployment package to be delivered to the customer. The package should include everything necessary for the customer to install your system at their site. Include installation instructions and a user guide.
Separate SRS into two documents: one that matches completed user stories, and one that identifies future development. Update user stories to reflect changes requested by customer in 405.
Create a traceability matrix that maps SRS elements to User Stories to Design artifacts and QA artifacts.
Complete/update/create a Quality Assurance Plan. The primary component is of a set of acceptance, functional, and non-functional tests. Tests should be created for as many attacks as appropriate.
Calculate product and process metrics based on system at end of 405. Formally document measures. Likely metrics tools to use include Emma/Cobertura, ckjm, and Eclipse Metrics. Metrics include but are not limited to the following:
Improve development environment in order to minimize manual installations and configuration for new developers. Document development environment and build setup so that a new developer joining the team could check-out source code, compile, build, and run automated tests with no assistance. Prepare system for external deployment by outside maintainers. Document all system requirements and installation steps including references to third-party installations and configurations. Prepare user-training documents and activities.
Improve quantity of unit tests resulting in improved code coverage.
Complete new user stories as jointly determined with customer. Update all artifacts for customer deployment. SQA/Consultants are charged with continuous quality activities including writing and executing functional, acceptance and regression tests, calculating quality metrics, and performing root cause analyses. They will work with functional team members to accomplish QA goals, but their primary objective is to ensure and improve product quality with minimal impact to the functional teams. They are also available for a limited amount of "consulting" for each team.
Same as previous iteration.
Same as previous iteration.
Due: On-going throughout quarter
Review, prioritize, assign, complete, integrate, and deploy defect corrections.
Each team will give a presentation showing the system and summarizing key activities and lessons learned. All team members will participate in the presentation. The SQA/Consultant team will also give a presentation with comparison defect information and process/product metrics.