WESCO Logo

Design

The project design phase is dependent upon adequate completion of requirements engineering. The focus of this phase is to develop a best-fit, cost-effective design that incorporates all defined functionality. The high-level design document is developed first to lay out system concepts, for example:

  • the number and type of user
  • processing load, system genre (stand-alone, client/server ext.)
  • communications medium
  • high-level system architecture
As the process progresses, detail is added to the design document. The final iteration of the complete system design includes a database design, program specifications (often including pseudo code logical algorithms), and an external interface design.

Acceptance of these design documents is a prerequisite for development of the functional system prototype.

A prototype includes screen layouts that contain adequate detail to permit the user to review core system functionality, and to provide an overall look and feel. Feedback from testing is incorporated into the system requirements specifications document if the risk of doing so is deemed acceptable. Risk analysis must confirm that the project scope does not expand with the addition of user feedback. If user feedback causes the scope to be modified, the project is redefined and the requirements engineering effort repeated.

   Deliverables
   Quality