Improving Product Reliability and Software Quality, 2nd Edition
by Mark A. Levin, Ted T. Kalal, Jonathan Rodin
19Design Concept Phase
Previously, in the product concept phase, the product requirements are defined on the basis of market‐driven product features – cost, forecasted demand, target customers, and business fit. This is where we produce a set of design requirements, and possibly, high‐level system architecture. Once these product requirements have been defined, a design concept must be developed to meet these needs. The design concept phase uses the product requirements to develop lower‐level design architecture. Upon completion of the design concept phase, the specifications for the outline dimensions, weight, input and output (I/O), power, cooling, and so on is determined.
19.1 Reliability Activities in the Design Concept Phase
Decisions made in the design concept designate what type of components, materials, and technologies are required to design the product. These decisions have a significant impact on the product cost, development time, design complexity, manufacturability, testability, serviceability, and reliability of the product. At the completion of the design concept phase, about half of the product cost is defined (see Figure 19.1). Product cost is a significant factor in profitability. This is where the design concept phase is used to ensure that the product cost goals are obtainable.
Figure 19.1 Opportunity to affect product cost.
Five reliability activities ...