1. Page 1 TEST in the large RELEASE REWORK ASSESS packaged application documentation models and source code management documents requirement alloc. matrix potential roles during this phase: tested application documentation models requirement alloc. matrix project manager support manager operations manager training manager developer support engineer operations engineer trainer project auditor testing manager test engineer technical writer DELIVER PHASE The main goal here is to deploy the application, including the appropriate documentation, to the user community.

2. Page 2 TEST IN THE LARGE ACCEPT TEST PLAN packaged application master test quality assurance plan previous test results FUNCTION TEST OPERATIONS TEST STRESS TEST ALPHA/BETA TEST INSTALLATION TEST tested application test results PERFORM METRICS USER ACCEPTANCE TEST RECORD DEFECTS The goal here is to ensure that the application works on its entirety. This includes user testing in which the application is specifically tested by members of user community.

3. Page 3 Test in the large entrance conditions checklist  The application has been packaged for delivery  The master test/QA plan in available  Previous test results are available  Team members are trained

4. Page 4 Test in the large to be performed checklist  The master test/QA plan was accepted  Defects have been recorded  All particular tests were performed  Artifacts that are potentially reusable by this project team have been identified and used  Decisions, both made and forgone, have been documented in group memory  Metrics have been collected

5. Page 5 Test in the large exit conditions checklist  The application has passed testing  Test results were documented

6. Page 6 REWORK PRIORITIZE DEFECTS tested application tested results, documents models, source code requirement alloc. matrix organizational priorities REMODEL TEST IN THE SMALL UPDATE DOCUMENTA- TION PERFORM METRICS REPROGRAM reworked application models, source code documentation requirement alloc. matrix The focus of this process is to fix the critical defects discovered by the “test in the large” process to ensure the successful deployment of the application. It is like a miniature version of the “construct” process.

7. Page 7 Rework entrance conditions checklist  The test results are available  The organization priorities are known  The current version of software is able to be reworked  Team members are trained

8. Page 8 Rework to be performed checklist  Defects have been prioritized  The models have been reworked  The requirement allocation matrix has been reworked  The support documentation has been reworked  The user documentation has been reworked  The operations documentation has been reworked  The source code has been reworked  The application was tested in the small (system tests)  Reusable artifacts were used  Risk assessment document was updated  Decisions, both made and forgone, have been documented in group memory  Metrics have been collected

9. Page 9 Rework exit conditions checklist  The selected and prioritized defects have been reworked  The construct phase deliverables (code, doc, models) are consistent  The application has been repackaged for testing

10. Page 10 RELEASE ACCEPT TRAINING AND RELEASE PLANS release procedures training plans application package operations and support documentation ACCEPT USER SUPPORT AND OPERATIONS DOCUMENTS DEPLOY THE OPERATION PROCESS FINALIZE CONVERSION OF LEGACY DATA DEPLOY THE SUPPORT PROCESS TRAIN OPERATIONS STAFF ANNONCE ACTUAL RELEASE TO USERS TRAIN SUPPORT STAFF PACKAGE APPLICATION released application procedures documentation TRAIN USERS PERFORM METRICS DEPLOY THE APPLICATION The goal of this process is to deploy the application and its corresponding documentation successfully to the user community (end users and also operations department staff that will help the users work with the application effectively).

11. Page 11 Release entrance conditions checklist  The application has been packaged for release  Organization release procedures are available  The training plan for user, operations and support communities are available  The documentation is available to be deployed  Team members are trained

12. Page 12 Release to be performed checklist  The training and release plans have been accepted  The user, support and operations documentation has been accepted  The legacy data has been converted  The product baseline and version description has been finalized  The release notes have been finalized  The installation procedures have been finalized  The operation staff has been trained  The support staff has been trained  The release was announced  The user community was trained  The application was deployed to user community  Risk management document was updated  Decisions, both made and forgone, have been documented in group memory  Metrics have been collected

13. Page 13 Release exit conditions checklist  The user, support, and operations communities have been trained  The application has been deployed  The application and its documentation has been accepted  The support environment has been installed

14. Page 14 ASSESS project deliverables project metrics group knowledge base REVIEW PROJECT DELIVERA- BLES ASSESS TEAM MEMBER PERFORMANCE DEVELOP LEARNING HISTORY DEVELOP PROJECT ASSESSMENT learning history project and staff assessment process improvement plan ANALYZE METRICS DEVELOP STAFF ASSESSMENT ASSESS USER INVOLVEMENT DEVELOP SOFTWARE PROCESS IMPROV. PLAN This process has two goals: a) for the project team, to learn from its experiences developing the application b) to provide an opportunity to evaluate the members of the project team to support their personal growth

15. Page 15 Assess entrance conditions checklist  Management support exists  Project members and key user representatives are available  Project deliverables, including the group memory and collected metrics are available  Team members are trained

16. Page 16 Assess to be performed checklist  Project deliverables were reviewed  Metrics collected during the project were presented and analyzed  The performance of individual team members was assessed  The involvement of user community was assessed  The involvement of support community was assessed  The involvement of operations community was assessed  The project assessment was documented  The learning history was developed  The software process improvement plan was developed  Risk assessment document has been updated  Decisions, both made and forgone, have been documented in group memory  Metrics have been collected

17. Page 17 Assess exit conditions checklist  All staff assessments are complete  The project assessment has been presented to senior management  The software process improvement plan has been accepted