The process is institutionalized as a defined process.
Commitment to Perform
GP 2.1 (CO 1) Establish an Organizational Policy
Establish and maintain an organizational policy for planning and performing the requirements development process.
Elaboration:
This policy establishes organizational expectations for collecting stakeholder needs, formulating product and product-component requirements, and analyzing and validating those requirements.
Ability to Perform
GP 3.1 (AB 1) Establish a Defined Process
Establish and maintain the description of a defined requirements development process.
GP 2.2 (AB 2) Plan the Process
Establish and maintain the plan for performing the requirements development process.
Elaboration:
Typically, this plan for performing the requirements development process is a part of the project plan as described in the Project Planning process area.
GP 2.3 (AB 3) Provide Resources
Provide adequate resources for performing the requirements development process, developing the work products, and providing the services of the process.
Elaboration:
Special expertise in the application domain, methods for eliciting stakeholder needs, and methods and tools for specifying and analyzing customer, product, and product-component requirements may be
required.
Examples of other resources provided include the following tools:
· Requirements specification tools
· Simulators and modeling tools
· Prototyping tools
· Scenario definition and management tools
· Requirements tracking tools
GP 2.4 (AB 4) Assign Responsibility
Assign responsibility and authority for performing the process, developing the work products, and providing the services of the requirements development process.
GP 2.5 (AB 5) Train People
Train the people performing or supporting the requirements development process as needed.
Elaboration:
Examples of training topics include the following: [PA157.EL105]
· Application domain
· Requirements definition and analysis
· Requirements elicitation
· Requirements specification and modeling
· Requirements tracking
Directing Implementation
GP 2.6 (DI 1) Manage Configurations
Place designated work products of the requirements development process under appropriate levels of configuration management.
Elaboration:
Examples of work products placed under configuration management include the following:
· Customer requirements
· Functional architecture
· Product and product-component requirements
· Interface requirements
GP 2.7 (DI 2) Identify and Involve Relevant Stakeholders
Identify and involve the relevant stakeholders of the requirements development process as planned.
Elaboration:
Select relevant stakeholders from customers, end users, developers, producers, testers, suppliers, marketers, maintainers, disposal personnel, and others who may be affected by, or may affect, the product as well as the process.
Examples of activities for stakeholder involvement include the following:
· Reviewing the adequacy of requirements in meeting needs, expectations, constraints, and interfaces
· Establishing operational concepts and scenarios
· Assessing the adequacy of requirements
· Establishing product and product-component requirements
· Assessing product cost, schedule, and risk
GP 2.8 (DI 3) Monitor and Control the Process
Monitor and control the requirements development process against the plan for performing the process and take appropriate corrective action.
Elaboration:
Examples of measures used in monitoring and controlling include the following:
· Cost, schedule, and effort expended for rework
· Defect density of requirements specifications
GP 3.2 (DI 4) Collect Improvement Information
Collect work products, measures, measurement results, and improvement information derived from planning and performing the requirements development process to support the future use and improvement of the organization’s processes and process assets.
Verifying Implementation
GP 2.9 (VE 1) Objectively Evaluate Adherence
Objectively evaluate adherence of the requirements development process against its process description, standards, and procedures, and address noncompliance.
Elaboration:
Examples of activities reviewed include the following:
· Collecting stakeholder needs
· Formulating product and product-component requirements
· Analyzing and validating product and product-component requirements
Examples of work products reviewed include the following:
· Product requirements
· Product-component requirements
· Interface requirements
· Functional architecture
GP 2.10 (VE 2) Review Status with Higher Level Management
Review the activities, status, and results of the requirements development process with higher level management and resolve issues.
