Development System This is the initial version of the application, created in the development environment, and tested by the developers in that environment. All changes are made and tested in this environment first.
System Documentation System documentation can include job, program, object, operations, and overall system documentation, and should be created for programs, stored procedures, functions, and other objects. These documents should be created in Word (see the documentation group for standards).
Migration/Installation Procedures These procedures are for either migrating the system to the test region, or installing the system in the test environment. The procedures must be written before testing can begin in the QA test environment, so that the migration/installation procedures can be tested with the application.
User Documentation (hardcopy &/or online help) User documentation explains how to use the system to accomplish business functions. It should consist of online help and paper documents, which can include user manuals, reference manuals, and quick reference cards, as determined during the analysis stage of the project. The online help is created using RoboHelp, and the documents are created in Word. Templates are available from the documentation group.
Training Materials (courseware) These materials are the courseware for user training. They would include student workbooks, workshop instructions and training database, and instructor's manuals. At this time, there are no templates or samples available.
Finalized Test Scripts The test scripts are updated as needed based on any changes made during the construction phase. The expected results of each test should be included in the script.
Finalized Test Plan The test plan is modified as needed, based on any changes or additions identified during the construction phase.
QA Test System This is the system that will be used for QA testing, and is created from a frozen development system. Any problems identified during QA testing will be corrected and unit tested in the development system, which will then be used to recreate the QA test system.
QA Test Installation Procedures These are the procedures that will be used to install the system in the QA test environment (including client workstations, as needed). As much as possible, this procedure should be the same as the procedure that will be used for production installation, so that the procedure can be adequately tested.
QA Evaluation Sign-off This is a form, signed by the QA representative, that indicates that the system, documentation, and training materials have passed all tests within acceptable margins. There is no sample available for this form at this time.
User Acceptance Test System This is the system that will be used for User Acceptance testing, and is created from a frozen development system. Any problems identified during User Acceptance testing will be corrected and unit tested in the development system, which will then be used to recreate the User Acceptance test system.
User Acceptance Test Installation Procedures These are the procedures that will be used to install the system in the User Acceptance test environment (including client workstations, as needed). As much as possible, this procedure should be the same as the procedure that will be used for production installation, so that the procedure can be adequately tested.
Updated Project Plan The project plan is updated as needed, and a phase section containing the work breakdown structure and schedule for the next phase is added. At this time, no sample is available.
Methodology Compliance Form This form is initialized by the project team, and completed by a methodology representative who has reviewed the project documentation and found it acceptable. It is completed in Word. At this time, no sample is available.

Steps

1. Create all application code, following University standards, and using the internal and external specifications developed in the Design stage. Best practices suggest that code walkthroughs be conducted throughout this process.
2. Create online help based on the external specifications and validated against the actual system. Connect the help topics to the system as required.
3. Unit test each object, and its interactions with related objects, using appropriate test data.
4. Document all jobs, programs, objects, operations, and stored procedures, including a high-level description of the overall system. This documentation is referred to as system documentation, and includes both specific documents created in Word, and liberal comments throughout the code (programs, scripts, stored procedures, objects, and other executables). See the documentation group for templates.
5. Create and document procedures for installing or migrating the development system into the QA testing environment.
6. Create user documentation (user manuals, handbooks, reference manuals, quick reference cards, etc.), based on the external specifications as determined in the Design stage, and validated against the actual system. Schedule documentation reviews by the developers, to ensure accuracy.
7. Create materials to be used in training users, help desk personnel, and production support staff in the application functionality. This includes student and instructor workbooks, training exercises and workshops, training databases and files.
8. Update the test scripts and the test plan with final changes for QA and User Acceptance testing. QA and user acceptance tests should include both system and integration testing, as well as testing of documentation, especially online help. Scripts can be developed once, and used for both QA and User Acceptance testing.
9. Build installation procedure and document it.
10. Deliver complete system, with documentation and test plan, to the QA (Quality Assurance) representative, who will run all tests detailed in the test plans, including tests of the installation, and the online help. The QA representative should also review any hardcopy user documentation.
11. The QA representative documents the results of each test, and provides error reports and correction requests to the appropriate developer (or writer).
12. The developer(s) and writer(s) correct the system, installation procedures, and online help, as required.
13. Repeat steps 10-12 as often as needed, until the system and documentation pass all the tests within acceptable margins.
14. The test team or project team completes the Testing Checklist for application transition deliverables.
15. The QA representative signs-off using the QA Evaluation Sign-Off template.
16. The developer(s) and writer(s) create the User Acceptance Test system and installation procedures, using the frozen development system containing all the corrections discovered during QA testing.
17. The team gathers all the project documentation together, including all of the deliverables for the Construction phase, and forwards them, with the project plan, to the methodology representative for review.
18. The methodology representative reviews the project packet and completes the compliance form before returning the materials to the project team.
19. The core team reviews the project plan, and updates the schedules and resources, if necessary.