Process Models in Design and Development
Read this article. It provides an overview of planning models. Pay particular attention to Figure 1 as it visually provides a global view of planning models. Then review Figures 2 -17 for more in-depth visual planning processes.
Meso-level models
Macro-level models
This section completes the review by discussing the third and outermost of the three levels of the organising framework shown in Fig. 1. Many of these macro-level models concentrate on the large-scale organisation and management of design and development. Some consider interactions between the design and development process and the context into which the design will be delivered. Considering the first of these two situations, the primary difficulty companies face is arguably the integration of systems, disciplines, tools, processes, and personnel. Research addressing this is often known as Concurrent Engineering (CE) or Integrated Product Development (IPD). According to Prasad, CE emphasises approaches "to elicit the product developers, from the outset, to consider the 'total job' (including company's support functions)". Some of the key facets of this philosophy are to use advanced collaboration tools including approaches such as Quality Function Deployment, appropriate team structures, and Design for X methods to increase concurrency and information exchange between coupled tasks, teams, and design considerations. Overall, CE/IPD is thought to compress lead time and support integration by reducing the mistakes and oversights that can cause late design changes.
Stage-Gate model emphasises the need to ensure that a design is sufficiently mature to exit each stage of the development process, to prevent costly loop-backs.
Fig. 13
Vee model of the systems engineering process emphasises management of decomposition and integration to avoid rework.