13. Conduct a Development Department Notification / Review. This is to ensure other projects are aware of any impact that may occur due to this project.
14. Begin building the Training Program.
15. Begin building the Quality Assurance Plan.
16. Begin building the lntegration Test Plan.
17. Start User and Internal Documentation.
18. Create a Modular Detail Design Document.
19. Build the Unit Test Plan.
20. Conduct Unit Testing by following the Unit Test Plan.
21. Conduct a code walk-thru / Design review with Project team.
22. Conduct a Development Department Notification / Review. This will ensure any project impact.
23. Finish the Integration Test Plan.
24. Conduct Integration Testing (internal and w/ other products) by following the Integration Test Plan.
25. This step is optional. Release an Alpha version of the product for a specific client.
26. Complete the Quality Assurance Plan.
27. Create the product distribution plan by following current distribution guidelines
28. Complete User and Internal Documentation.
29. Complete the Beta Plan.
30. Sign up Clients for the Beta Plan.
31. Verify the project requirements were met. (Use a check list type of form to ensure the product is under source control, the distribution is secure, all documentation is complete, the build process is verified, etc.)
32. Begin the Internal Training by following the Internal Training Plan.
33. Begin the Quality Assurance Process - The main goal is to verify the project has met its requirements by testing each module and documentation. The QA team will follow a Quality Assurance Plan to identify defects as follows:
a. Defect tracking
b. Risk assessment of defects
c. Defect resolution
Quality Assurance Goals:
· Product Verification. Does the product meet the specifications?
· Verify User Requirements Verify Performance Risk Assessment:
· Testing assessment Defect assessment
· Product Feedback: Non-impacting comments about look, feel, and performance
· Verify ease-of-use
· Verify Documentation is correct, complete, and useful Verify Distribution Method is effective, safe, and the package contains the right components.
• Verify Installation Instructions - verify they work.
• Update the Defect Database. Currently, a single database is being developed for all products.
· Test reliability and serviceability aids (logs, reports, messages, etc.)
· Follow the QA Plan.
· Follow the product documentation.
· Perform random testing and test all probabilities.
34. Complete the Quality Assurance Process.
35. Release the product in beta form by following the Beta Plan. The QA team will track and maintain the Beta Plan under the guide of the Project Manager.
POLICY: This Life Cycle will be followed for all projects and enhancements. It will not be deviated from for any reason.
Go To Page: 1 2
