Scribd
Upload
322 views

Software Design Checklist 01

This software design checklist provides guidance for system owners, project managers, and other IT professionals to identify and plan software design activities throughout the IT lifecycle. The checklist outlines a process for translating system requirements into a functional design, finalizing this design with stakeholders, and using it as the basis for more technical system design. It includes activities such as selecting a design methodology, identifying necessary resources, designing interfaces, creating documentation, and conducting reviews.

Uploaded by

Uzair Ghafoor Mughal
Copyright
© Attribution Non-Commercial (BY-NC)
Available Formats
Download as PDF, TXT or read online on Scribd
322 views

Software Design Checklist 01

This software design checklist provides guidance for system owners, project managers, and other IT professionals to identify and plan software design activities throughout the IT lifecycle. The checklist outlines a process for translating system requirements into a functional design, finalizing this design with stakeholders, and using it as the basis for more technical system design. It includes activities such as selecting a design methodology, identifying necessary resources, designing interfaces, creating documentation, and conducting reviews.

Uploaded by

Uzair Ghafoor Mughal
Copyright
© Attribution Non-Commercial (BY-NC)
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 3

Software Design Checklist

Overview The following checklist is intended to provide system owners, project managers, configuration managers, and other information system development and maintenance professionals with guidance in identifying and planning software design activities. The checklist reflects recognized design activities to be performed throughout the information technology (IT) life cycle. Software design starts as a process for translating documented system requirements into a customer-oriented functional design. The system owner, customers, and project team finalize this design and use it as a basis for the more technical system design. Note: The degree to which the following design activities are applied may vary with the nature, scope, size and complexity of a project.

This checklist is utilized in Section 4, Planning Phase, Section 6, Functional Design Phase, Section 7, Systems Design Phase, Appendix D, In-Phase Assessment, and Appendix E, Phase Exit. Contents of Checklist Documented system requirements are used as the basis for selecting a design methodology. Resources necessary to perform software design activities on the project (i.e., estimated staff, development tools) are identified. Using a documented design methodology identifies a software structure. System design entities, inputs, and outputs are derived from the software structure. Customer interfaces are designed in consultation with the system owner. A logical data model that describes the systems data control flow is constructed. A Functional Design Document is created and distributed to the project team members and the system owner. A Functional Design Review is performed. At least one In-Phase Assessment is performed before the Functional Design Phase Exit. A system architecture including hardware, software, database, and data communications structures is specified. An Analysis of Benefits and Costs (ABC) is conducted on several system architecture alternatives and is used as the basis for an architecture recommendation. Functional Design entities are used as the basis for creating system modules, procedures, and objects.

Rev Oct. 2002-1

Page 1of 3

Software Design Checklist


A physical data model, based on the logical data model, is developed. A system design is approved and baselined. Changes to the system design baseline are managed and controlled. A System Design Document is created. A Critical Design Review is conducted. At least one In-Phase Exit is performed before the System Design phase exit. System design activities are reviewed with the project manager/leader both periodically and as needed. Software Quality Assurance/Improvement periodically reviews and/or audits software design activities and deliverables and reports the results. Documented system requirements are used as the basis for selecting a design methodology. Resources necessary to perform software design activities on the project (i.e., estimated staff, development tools) are identified. Using a documented design methodology identifies a software structure. System design entities, inputs, and outputs are derived from the software structure. Customer interfaces are designed in consultation with the system owner. A logical data model that describes the systems data control flow is constructed. A Functional Design Document is created and distributed to the project team members and the system owner. A Functional Design Review is performed. At least one In-Phase Assessment is performed before the Functional Design Phase Exit. A system architecture including hardware, software, database, and data communications structures is specified. An Analysis of Benefits and Costs (ABC) is conducted on several system architecture alternatives and is used as the basis for an architecture recommendation. Functional Design entities are used as the basis for creating system modules, procedures, and objects.
Page 2of 3

Rev Oct. 2002-1

Software Design Checklist


A physical data model, based on the logical data model, is developed. A system design is approved and baselined. Changes to the system design baseline are managed and controlled. A System Design Document is created. A Critical Design Review is conducted. At least one In-Phase Exit is performed before the System Design phase exit. System design activities are reviewed with the project manager/leader both periodically and as needed. Software Quality Assurance/Improvement periodically reviews and/or audits software design activities and deliverables and reports the results.

Signature: ____________________________________ Date: _______________

Rev Oct. 2002-1

Page 3of 3

You might also like