Requirements Development (RD)
An Engineering Process Area at Maturity Level 3
The purpose of Requirements Development (RD) is to produce and analyze customer, product, and product component requirements.
This process area describes three types of requirements: customer requirements, product requirements, and product component requirements. Taken together,these requirements address the needs of relevant stakeholders, including those pertinent to various product lifecycle phases (e.g., acceptance testing criteria) and product attributes (e.g., safety, reliability, and maintainability). Requirements also address constraints caused by the selection of design solutions (e.g., integration of commercial off-the-shelf products).
All developmentprojects have requirements. In the case of a project that is focused on maintenance activities, the changes to the product or product components are based on changes to the existing requirements, design, or implementation. The requirements changes, if any, might be documented in change requests from the customer or users, or they might take the form of new requirements received from the requirementsdevelopment process. Regardless of their source or form, the maintenance activities that are driven by changes to requirements are managed accordingly.
Requirements are the basis for design. The development of requirements includes the following activities:
• Elicitation, analysis, validation, and communication of customer needs, expectations, and constraints to obtain customer requirementsthat constitute an understanding of what will satisfy stakeholders
• Collection and coordination of stakeholder needs
• Development of the lifecycle requirements of the product
• Establishment of the customer requirements
• Establishment of initial product and product component requirements consistent with customer requirements
This process area addresses all customer requirements ratherthan only product-level requirements because the customer may also provide specific design requirements.
Customer requirements are further refined into product and product component requirements. In addition to customer requirements, product and product component requirements are derived from the selected design solutions. Throughout the process areas, where we use the terms product and productcomponent, their intended meanings also encompass services and their components.
Requirements are identified and refined throughout the phases of the product lifecycle. Design decisions, subsequent corrective actions, and feedback during each phase of the product’s lifecycle are analyzed for impact on derived and allocated requirements.
The Requirements Development process area includesthree specific goals. The Develop Customer Requirements specific goal addresses defining a set of customer requirements to use in the development of product requirements. The Develop Product Requirements specific goal addresses defining a set of product or product component requirements to use in the design of products and product components. The Analyze and Validate Requirements specific goaladdresses the necessary analysis of customer, product, and product component requirements to define, derive, and understand the requirements. The specific practices of the third specific goal are intended to assist the specific practices in the first two specific goals. The processes associated with the Requirements Development process area and those associated with the Technical Solution process areamay interact recursively with one another.
Analyses are used to understand, define, and select the requirements at all levels from competing alternatives. These analyses include the following:
• Analysis of needs and requirements for each product lifecycle phase, including needs of relevant stakeholders, the operational environment, and factors that reflect overall customer and end-user...
Leer documento completo
Regístrate para leer el documento completo.