Analyze and Validate Requirements (User Story)

Purpose:

The requirements are analyzed and validated.

Objective:

Analyzing and validating the requirements with respect to the end user is intended environment.

Description:

The Analyze and Validate Requirements goal is to support the development of the requirements in both the Develop Customer Requirements and the Develop Product Requirements. The specific goal is to cover analyzing and validating the requirements with respect to the end user’s intended environment.

Analyses are performed to determine what impact the intended operational environment will have on the ability to satisfy the stakeholders’ needs, expectations, constraints, and interfaces. Considerations, such as feasibility, mission needs, cost constraints, potential market size, and acquisition strategy, should all be taken into account, depending on the product context. Architecturally significant quality attributes are identified based on mission and business drivers. A definition of required functionality and quality attributes is also established. All specified usage modes for the product are considered.

The objectives of the analyses are to determine candidate requirements for product concepts that will satisfy stakeholder needs, expectations, and constraints and then to translate these concepts into requirements. In parallel with this activity, the parameters that will be used to evaluate the effectiveness of the product are determined based on customer input and the preliminary product concept.

Requirements are validated to increase the probability that the resulting product will perform as intended in the use environment.

Inputs:

• Draft Customer Requirements Document
• Draft Product Requirements Document
• Draft System Requirements Document
• Process Design Summary

Outputs:

• Baseline Customer Requirements Document
• Baseline Product Requirements Document
• Baseline System Requirements Document

Controls:

• <?>

Task Instructions:

Establish Operational Concepts and Scenarios

1. 1. Using the <?>, [the ?] with support from <?> is responsible for developing operational concepts and scenarios that include operations, installation, maintenance, support, and disposal as appropriate.
      
   2. Using the <?>, [the ?] with support from <?> is responsible for defining the environment in which the product will operate, including boundaries and constraints.
   3. Using the <?>, [the ?] with support from <?> is responsible for reviewing operational concepts and scenarios to refine and discover requirements.
      
   4. Using the <?>, [the ?] with support from <?> is responsible for developing a detailed operational concept, as candidate solutions are identified and product and product component solutions are selected by the supplier, that defines the interaction of the product, the end user, and the environment, and that satisfies operational, maintenance, support, and disposal needs.

Analyze Requirements

1. 1. Using the <?>, [the ?] with support from <?> is responsible for analyzing stakeholder needs, expectations, constraints, and external interfaces to organize into related subjects and remove conflicts.
   2. Using the <?>, [the ?] with support from <?> is responsible for analyzing requirements to determine whether they satisfy higher level requirements.
   3. Using the <?>, [the ?] with support from <?> is responsible for analyzing requirements to ensure that they are complete, feasible, realizable, and verifiable.
   4. Using the <?>, [the ?] with support from <?> is responsible for analyzing and propose the allocation of requirements.
   5. Using the <?>, [the ?] with support from <?> is responsible for  identifying key requirements that have a strong influence on cost, schedule, performance, or risk.
   6. Using the <?>, [the ?] with support from <?> is responsible for identifying technical performance measures to be tracked during the acquisition. 
   7. Using the <?>, [the ?] with support from <?> is responsible for analyzing operational concepts and scenarios to refine customer needs, constraints, and interfaces and to discover new requirements.
   8. – – – 
   9. Using Process Design Summary, [the Business Analyst] with support from Requirements Providers is responsible for check for consistency with Process Design Summary.

Analyze Requirements to Achieve Balance

1. 1. Using the <?>, [the ?] with support from <?> is responsible for using proven models, simulations, and prototyping to analyze the balance of stakeholder needs and constraints.
      
   2. Using the <?>, [the ?] with support from <?> is responsible for performing a risk assessment on requirements and design constraints.
   3. Using the <?>, [the ?] with support from <?> is responsible for examining product lifecycle concepts for impacts of requirements on risks.
   4. Using the <?>, [the ?] with support from <?> is responsible for performing a cost benefit analysis to assess impact of the requirements on the overall acquisition strategy and acquisition project costs and risks.

Validate Requirements

1. 1. Using the <?>, [the ?] with support from <?> is responsible for analyzing the requirements to determine the risk that the resulting product will not perform appropriately in its intended-use environment.
   2. Using the <?>, [the ?] with support from <?> is exploring the adequacy and completeness of requirements by developing product representations (e.g., prototypes, simulations, models, scenarios, storyboards) and by obtaining feedback about them from relevant stakeholders.
   3. Using the <?>, [the ?] with support from <?> is assessing product and product component solutions as they are developed by the supplier in the context of the validation environment to identify issues and expose unstated needs and customer requirements.