Ensure the product is sustainable by IT Bureau Ensure the product’s usability by the stakeholders Ensure the product meets current and future DC achievement goals. 4.2.2 4.2.2.1 [System Specification Requirements] The SSR will be written with Deliverable Acceptance Criteria - Comprehensive detailed requirements so that all understanding by team members. team members will have a Standards for Content and Format - As outlined in the SSR and comprehensive understanding of SDD templates. what is to be designed. An initial Quality Review - The documents will be reviewed by the Project System Design Documents will be Manager for coherency and content. developed. 4.2.2.2 [Test Plan] Description A detailed test plan Deliverable Acceptance Criteria Comprehensive – – will be written which will feature understanding by team members. all phases of testing, including unit, Standards for Content and Format As defined by the IEEE – alpha, and beta. 829-2008 documentation. The documents will be reviewed by the Quality Review - Project Manager for coherency and content. 4.2.2.3 [Development of Code Modules] Description Utilizing MS Visual Deliverable Acceptance Criteria Code modules have passed – – Studio 2010, code modules will be unit testing. Application is functioning as initially expected. written and have passed unit Standards for Content and Format Code reviews and – testing. utilization of the content and format features provided by TFS. As documented in the Test Plan (see Quality Review – above). 4.2.2.4 [Quality Assurance] Description Based on the Test Deliverable Acceptance Criteria Acceptance testing (both – – Plan, all testing phases will be alpha and beta) will have occurred and the application will be conducted and have passed. approved for deployment. Modifications will have been made Standards for Content and Format As defined in the test – based on alpha and beta testing. plan (above).
Ensure the product is sustainable by IT Bureau Ensure the product’s usability by the stakeholders Ensure the product meets current and future DC achievement goals. 4.2.2 4.2.2.1 [System Specification Requirements] The SSR will be written with detailed requirements so that all team members will have a comprehensive understanding of what is to be designed. An initial System Design Documents will be developed. Deliverable Acceptance Criteria - Comprehensive understanding by team members. Standards for Content and Format - As outlined in the SSR and SDD templates. Quality Review - The documents will be reviewed by the Project Manager for coherency and content. 4.2.2.2 [Test Plan] Description – A detailed test plan will be written which will feature all phases of testing, including unit, alpha, and beta. Deliverable Acceptance Criteria – Comprehensive understanding by team members. Standards for Content and Format – As defined by the IEEE 829-2008 documentation. Quality Review - The documents will be reviewed by the Project Manager for coherency and content. 4.2.2.3 [Development of Code Modules] Description – Utilizing MS Visual Studio 2010, code modules will be written and have passed unit testing. Deliverable Acceptance Criteria – Code modules have passed unit testing. Application is functioning as initially expected. Standards for Content and Format – Code reviews and utilization of the content and format features provided by TFS. Quality Review – As documented in the Test Plan (see above). 4.2.2.4 [Quality Assurance] Description – Based on the Test Plan, all testing phases will be conducted and have passed. Modifications will have been made based on alpha and beta testing. Deliverable Acceptance Criteria – Acceptance testing (both alpha and beta) will have occurred and the application will be approved for deployment. Standards for Content and Format – As defined in the test plan (above).
DC_PMP_10-31-12.docx