MANAGEMENT

6 - REQUIREMENTS ANALYSIS
6.2.2.2 Select the Requirements Models
A component of analysis is the development of graphical or text models, which are helpful in finding gaps in
information and identifying extraneous information. Requirements are modeled and refined to provide greater insight
and correctness and to elicit additional information to define the details necessary to build the product, service, or result.
As some models are better suited for certain environments, it is important to select requirements models based
on specific characteristics, type of project, methodology, timing, purpose, and level of abstraction.
Requirements models are constructed at various levels of detail. There are a number of categories and modeling
notations available to assist in model development, which is described in Section 6.3.2 of this practice guide and
in Section 4.10.3 of Business Analysis for Practitioners: A Practice Guide. Consistent language and syntax should
be used in the models to minimize confusion and increase comprehension of requirements.
6
6.2.2.3 Prioritize Requirements
Requirements prioritization is an important step in managing product scope and is used to rank requirements
in the order of importance. It is used to assist key stakeholders in making tradeoffs between requirements and
to analyze the relative value of requirements against one another. Since it may not be feasible to implement all
requirements within the project constraints, prioritization helps to focus the stakeholders on the most critical
requirements based on the prioritization criteria. It is essential to define the criteria that will be used in prioritization,
and this is typically accomplished during requirements management planning. Common types of criteria include:
• Value,
• Risk level,
• Complexity,
• Cost, and
• Regulatory constraints.
These criteria provide the foundation for continual prioritization as requirements evolve and change over the
project life cycle. Several techniques exist that can be used to drive prioritization. Some commonly used techniques
include MoSCoW, voting, and timeboxing, which are further described in Section 6.3.1.
6.2.2.4 Allocate and Derive Requirements
Requirements allocation is the process of assigning requirements to functions, solution components, and
organizational entities. Requirements are subsequently allocated to specific releases or iterations. This activity
occurs in the analysis process until in-scope requirements have been apportioned across the solution. Allocation
helps assure that the proposed solution will be delivered in a manner and order that maximize value to the
business. How requirements are allocated can change the amount of value delivered by the solution.
Deriving requirements is the process of analyzing requirements into more detail to extrapolate more granular
discrete requirements and remove ambiguity. When requirements are broadly defined, they should be progressively
©2016 Project Management Institute. Requirements Management: A Practice Guide
35