Purpose:

Stakeholder needs, expectations, constraints, and interfaces are collected and translated into customer requirements.

Objective:

To gather Customer Requirements form the Requirements Providers, Analyze the gathered requirements and document detailed and traceable requirements.

Description:

The needs of stakeholders (e.g., customers, end users, suppliers, builders, testers, manufacturers, logistics support staff) are the basis for determining customer requirements. The stakeholder needs, expectations, constraints, interfaces, operational concepts, and product concepts are analyzed, harmonized, refined, and elaborated for translation into a set of customer requirements.

Frequently, stakeholder needs, expectations, constraints, and interfaces are poorly identified or conflicting. Since stakeholder needs, expectations, constraints, and limitations should be clearly identified and understood, an iterative process is used throughout the life of the project to accomplish this objective. To facilitate the required interaction, a surrogate for the end user or customer is frequently involved to represent their needs and help resolve conflicts. The customer relations or marketing part of the organization as well as members of the development team from disciplines such as human engineering or support can be used as surrogates. Environmental, legal, and other constraints should be considered when creating and resolving the set of customer requirements.

Inputs:

  • Draft Project Charter
  • Baseline Project Charter
  • Process Design Summary
  • Requirements Traceability Matrix Template

Outputs:

  • Customer Requirements Document
  • Requirements Traceability Metrics
  • Meeting Minutes
  • Updated Project Issue Log

Controls:

Task Instructions:

Inputs:

  • Draft Project Charter
  • Baseline Project Charter
  • Process Design Summary
  • Requirements Traceability Matrix Template

Outputs:

  • Customer Requirements Document
  • Requirements Traceability Metrics
  • Meeting Minutes
  • Updated Project Issue Log

Controls:

Task Instructions:

Elicit Stakeholder Needs

    1. Using the Draft Project Charter and [methods?], [the Business Analyst] with support from Business Relationship Manager and identified list of Requirements Providers is responsible for engaging  relevant stakeholders for eliciting needs, expectations, constraints, and external interfaces.

Develop and Prioritize Customer Requirements

    1. Using the Draft Project Charter, and the Customer Requirements Document Template, [the Business Analyst] with support from identified list of Requirements Providers is responsible for translating stakeholder needs, expectations, constraints and interfaces into documented customer requirements.
    2. Using the System Requirements Specifications Template, [the Business Analyst] with support from identified list of Requirements Providers is responsible for updating the consolidating the elicited information into Functional and non-functional.
    3. Using the System Requirements Specifications Template, the [Business Analyst] with support from identified list of Requirements Providers is responsible for prioritizing the requirements.
    4. Using the System Requirements Specifications Template, [the Business Analyst] with support from identified list of Requirements Providers is responsible for proposing acceptance criteria for each User Requirement.
    5.  Using the System Requirements Specification Template [the Business Analyst] with support from identified list of Requirements Providers is responsible for developing operational concepts through User Stories, Data Models and/or Screen Shots.
    6. Using User Stories, Data Models and/or Screenshots [the Business Analyst] with support from Requirements Providers is responsible for gathering additional requirements.
  1.