|
Overview The Design Phase seeks to develop detailed specifications that emphasize the physical solution to the user's information technology needs. The system requirements and logical description of the entities, relationships, and attributes of the data that were documented during the Requirements Analysis Phase are further refined and allocated into system and database design specifications that are organized in a way suitable for implementation within the constraints of a physical environment (e.g., computer, database, facilities). A formal review of the high-level architectural design is conducted prior to detailed design of the automated system/application to achieve confidence that the design satisfies the system requirements, is in conformance with the enterprise architecture and prescribed design standards, to raise and resolve any critical technical and/or project-related issues, and to identify and mitigate project, technical, security, and/or business risks affecting continued detailed design and subsequent lifecycle activities. During the Design Phase, the initial strategy for any necessary training is also begun. Estimates of project expenses are updated to reflect actual costs and estimates for future phases. In addition, the work planned for future phases is redefined, if necessary, based on information acquired during the Design Phase. The Design Phase ends with a review to determine readiness to proceed to the Development Phase. Review A Preliminary Design Review (PDR) is performed by the Technical Review Board (TRB) early in the Design Phase to ensure that the proposed design conforms to the CMS Technical Reference Architecture (TRA), there is sufficient infrastructure to support the application and data needs; and determine if the risk impact upon the Enterprise Security Model is acceptable. A Detailed Design Review (DDR) is performed by the Technical Review Board (TRB) at the end of the Design Phase to ensure the design that will be implemented conforms to the Technical Reference Architecture (TRA) (see "IT Standards" under Related Links Inside CMS) and the infrastructure is sufficient to support the application and data needs. For specifics on these reviews, please refer to ILC Reviews (see Related Links Inside CMS). Artifacts A System Design Document, Interface Control Document, Physical Data Model, Computer Match Agreement, and Inter/Intra-Agency Agreement are developed. A Data Use Agreement, Database Design Document, Data Conversion Plan, Test Case Specification, Implementation Plan, User Manual, Operations & Maintenance Manual, and Contingency Plan are started. The Section 508 Product Assessment Package, Information Security Risk Assessment and System Security Plan are continued. A Release Plan, System of Records, and Test Plan are baselined. For specifics on these artifacts, please refer to the ILC Template Library (see Related Links Inside CMS).
Page Last Modified: 10/24/2011 7:43:07 AM
Help with File Formats and Plug-Ins
Submit Feedback
|
