Requirements Life Cycle

Management
EEPTM of International Institute of Business Analysis [IIBA], Canada
REP of International Requirements Engineering Board [IREB], Germany

Presenter
Mohan Kumar Subramani, B.E, MBA, CBAP
Business Analysis Faculty

Download Fhyzics app from

www.fhyzics.com | cs@fhyzics.com | 900-304-9000 | 900-305-9000 | 900-306-9000 Google Play or App Store
 Requirements Life Cycle Management

The Requirements Life Cycle Management knowledge area

describes the tasks that business analysts perform in order
to manage and maintain requirements and design
information from inception to retirement

These tasks describe establishing meaningful relationships

between related requirements and designs, assessing
changes to requirements and designs when changes are
proposed, and analyzing and gaining consensus on
changes
 Purpose of RMC

To create a common shared understanding

To communicate to broad and diverse audience
To seek approval of requirements
To baseline requirements
Requirements Life Cycle Management

Trace Requirements

Maintain Requirements

Prioritize Requirements

Assess Requirements Changes

Approve Requirements
Requirements Life
Cycle Management
 Trace Requirements

The purpose of Trace Requirements is to ensure that

requirements and designs at different levels are aligned to
one another, and to manage the effects of change to one
level on related requirements

Requirements traceability identifies and documents the

lineage of each requirement, including its backward
traceability, its forward traceability, and its relationship to
other requirements
 Trace Requirements

Inputs
Requirements
Designs

Elements
Level of Formality
Relationships
Traceability Repository
 Trace Requirements

Guidelines and Tools

Domain Knowledge
Information Management Approach
Legal/Regulatory Information
Requirements Management Tools/Repository
 Trace Requirements

Techniques
Business Rules Analysis
Functional Decomposition
Process Modelling
Scope Modelling

Stakeholders
Customers
Domain Subject Matter Expert
End User
 Trace Requirements

Implementation Subject Matter Expert

Operational Support
Project Manager
Sponsor
Suppliers
Tester

Outputs
Requirements (traced)
Designs (traced)
 Trace
Requirements
 Maintain Requirements

The purpose of Maintain Requirements is to retain

requirement accuracy and consistency throughout and
beyond the change during the entire requirements life cycle,
and to support reuse of requirements in other solutions

A requirement that represents an ongoing need must be

maintained to ensure that it remains valid over time
 Maintain Requirements

Inputs
Requirements
Designs

Elements
Maintain Requirements
Maintain Attributes
Reusing Requirements
 Maintain Requirements

Guidelines and Tools

Information Management Approach

Techniques
Business Rules Analysis
Data Flow Diagrams
Data Modelling
Document Analysis
Functional Decomposition
Process Modelling
 Maintain Requirements

Use Cases and Scenarios

User Stories

Stakeholders
Domain Subject Matter Expert
Implementation Subject Matter Expert
Operational Support
Regulator
 Maintain Requirements

Outputs
Requirements (maintained)
Designs (maintained)
Maintain Requirements
 Prioritize Requirements

The purpose of Prioritize Requirements is to rank

requirements in the order of relative importance

Prioritization is the act of ranking requirements to determine

their relative importance to stakeholders
 Prioritize Requirements

Inputs
Requirements
Designs

Elements
Basis for Prioritization
Challenges of Prioritization
Continual Prioritization
 Prioritize Requirements

Guidelines and Tools

Business Constraints
Change Strategy
Domain Knowledge
Governance Approach
Requirements Architecture
Requirements Management Tools/Repository
Solution Scope
 Prioritize Requirements

Techniques
Backlog Management
Business Cases
Decision Analysis
Estimation
Financial Analysis
Interviews
Item Tracking
Prioritization
Risk Analysis and Management
Workshops
 Prioritize Requirements

Stakeholders
Customer
End User
Implementation Subject Matter Expert
Project Manager
Regulator
Sponsor
Outputs
Requirements (prioritized)
Designs (prioritized)
 Prioritize
Requirements
 Assess Requirements Changes

The purpose of Assess Requirements Changes is to

evaluate the implications of proposed changes to
requirements and designs

The Assess Requirements Changes task is performed as

new needs or possible solutions are identified. These may or
may not align to the change strategy and/ or solution scope
 Assess Requirements Changes

Inputs
Proposed Change
Requirements
Designs

Elements
Assessment Formality
Impact Analysis
Impact Resolution
 Assess Requirements Changes

Guidelines and Tools

Change Strategy
Domain Knowledge
Governance Approach
Legal/Regulatory Information
Requirements Architecture
Solution Scope
 Assess Requirements Changes

Techniques
Business Cases
Business Rules Analysis
Decision Analysis
Document Analysis
Estimation
Financial Analysis
Interface Analysis
Interviews
 Assess Requirements Changes

Item Tracking
Risk Analysis and Management
Workshops

Stakeholders
Customer
Domain Subject Matter Expert
End User:
Operational Support
Project Manager
 Assess Requirements Changes

Regulator
Sponsor
Tester

Outputs
Requirements Change Assessment
Designs Change Assessment
Assess Requirements Changes
 Approve Requirements

The purpose of Approve Requirements is to obtain

agreement on and approval of requirements and designs for
business analysis work to continue and/or solution
construction to proceed

Inputs
Requirements (verified)
Designs
 Approve Requirements

Elements
Understand Stakeholder Roles
Conflict and Issue Management
Gain Consensus
Track and Communicate Approval
 Approve Requirements

Guidelines and Tools

Change Strategy
Governance Approach
Legal/Regulatory Information
Requirement Management Tools/Repository
Solution Scope
 Approve Requirements

Techniques
Acceptance and Evaluation Criteria
Decision Analysis
Item Tracking
Reviews
Workshops
 Approve Requirements

Stakeholders
Customer
Domain Subject Matter Expert
End User
Operational Support
Project Manager
Regulator
Sponsor
Tester
 Approve Requirements

Outputs
Requirements (approved)
Designs (approved)
Approve Requirements
 Thank You

www.fhyzics.com | cs@fhyzics.com | 900-304-9000 | 900-305-9000 | 900-306-9000