Information & Technology Management Standards
Quality Control Items List
This form is used to formally record the findings from the quality control review of a deliverable. This form may be used by non-IT client reviewers and by IT reviewers if a manual items management system is used on the project.
Template |
Contact |
||
| Quality Control Items List Template (DOC, 47KB) |  |
Portfolio Manager | |
Related Standards
| All deliverables must be approved and formal acceptance of the final product must be obtained from the project sponsor. |
| All deliveries should be made to the Project Delivery Office to be logged and distributed for review and acceptance. |
All project deliverables will be subject to a review and approval process and will be signed off by the project sponsor and stakeholders with a vested interest in the particular deliverable. Click on the hyperlink to view the Guidelines on QA turnaround timelines for ADE deliverables (PDF, 141KB). |
| Peer reviews will be held for business design and technical design documents, and code-walkthroughs for non-generated code. |
| Defining a test strategy has been scheduled in the Business Design phase. This strategy will include the development of test scenarios, test cases and a detailed test plan. |
| Five levels of project testing will take place: unit, integration, system, system integration, and user acceptance. At the end of system integration testing the system should be ready for user acceptance testing. |
| System Testing Process (PDF, 92KB). |
| Unit Testing Process (PDF, 101KB). |
| An acceptance test task is included in the workplan to enable the business area to test the final product in a production-like environment prior to implementation. The initial requirements for this acceptance test will be documented during the business design. |
| All system and application deliverables will be signed off prior to migration to production. |
