Design Phase
What is the requirements role in the Design Phase?

The design is based on the requirements established in the Analyze Phase and provides the basis on how the proposed system will be built. A functional design focuses on usability and reliability. Logical design includes outputs, inputs, presentation, processes, storage, and personnel.

The Design Phase could include the following activities:

• Establish the system environment
• Design the system
• Prototyping
• User documentation
• Preliminary design review
• User training
• User acceptance
• Critical design review
• Revise documentation from prior phases

Depending on the nature of the project, the design may come from a programmer, an architect, a graphic designer, or a quality specialist, to name but a few.

Project parameters should remain as fluid as possible and allow for changes to costs, schedules and overall plans, while remaining in line with Business Requirements. Project feasibility continues to be addressed through the Design Phase.

Test plans are developed according to expectations derived from the design and implemented during the Test Phase.

By the end of the Design Phase, project deliverables should include System Design Document, Implementation Plan, Training Plan, and Maintenance, Operations and User Manuals.

Once design is complete, the Project Manager oversees production of a Project Status Review, which will be read and evaluated by Approvers and other Stakeholders.

Summary

The Design Phase involves the creation of the specific design of the product or service. The design may come from a programmer, an architect, a graphic designer, or a quality specialist. System architecture is finalized and test plans are developed. A functional design focuses on usability and reliability. Project parameters should remain as fluid as possible and allow for changes to costs, schedules and overall plans. Project deliverables include Maintenance, Operations and User Manuals employed in the Deploy Phase.

Requirementing Steps