FIGURE 2-2 Flow diagram of product–process development. This diagram seeks to capture series and parallel activities at several levels of detail over time during the development of a product. Some of the required activities are listed along the arms of the V while others, not associated with particular phases of the process, are listed across the bottom. Software tools are not available (red) for many of the required product development activities. For other activities, software tools may be emerging (yellow) or common (green) but are not interoperable or are used inefficiently.

leads to uncertainties in materials properties and processes and can contribute to unexpected behavior. Prototypes may be needed to detect some of these uncertain events. Regulatory agencies often require safety tests prior to the production and sale of certain products (e.g., automobiles and aircraft). Microprocessors can be completely designed in software using design rules, once the production processes have been verified on test chips that have the required device sizes, materials, and line widths and spacing. Verification of these processes still requires hardware. In software development, prototypes are used to test the new software against customers' expectations. Thus, even if programming aids eliminate bugs, there will still be a need for prototypes.

In some industries, development of prototypes and computer simulations go hand in hand. In aircraft jet engine design, simulations are used to make conceptual, preliminary, and detailed designs of fans, compressors, combustors, and turbines. Each of these components is built in prototype form and tested, as is the final engine. These tests not only determine whether the engine meets its requirements but also provide essential information for updating the



The National Academies | 500 Fifth St. N.W. | Washington, D.C. 20001
Copyright © National Academy of Sciences. All rights reserved.
Terms of Use and Privacy Statement