Please enable JavaScript.
Coggle requires JavaScript to display documents.
Requirement Life Cycle Management - Coggle Diagram
Requirement Life Cycle Management
Input
:
Requirements
Designs
Proposed Change
Requirements (verified)
Output
Requirements (traced)
Designs (traced)
Requirements (maintained)
Designs (maintained)
Requirements (prioritized)
Designs (prioritized)
Requirements Change Assessment
Designs Change Assessment
Requirements (approved)
Designs (approved)
Trace Requirements
Purpose
: 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.
Input
:
Requirements
Design
Traceability enables:
Faster and simpler impact analysis.
More reliable discovery of inconsistencies and gaps in requirements.
Deeper insights into the scope and complexity of a change.
Reliable assessment of which requirements have been addressed and which have not.
Output
:
Requirements (traced)
Designs (traced)
Elements
Level of Formality
:
When tracing requirement, BA consider the value and nature and use of the specific relationships.
Relationships
:
Derive
: a requirement is derived from another requirement, appropriate to link the requirements on different levels of abstraction.
Depends
Necessity
: when it only makes sense to implement a particular requirement if a related requirement is also implemented
Effort
: when a requirement is easier to implement if a related requirement is also implemented
Satisfy
: relationship between an implementation element and the requirements it is satisfying.
Validate
: relationship between a requirement and a test case determine whether a solution fulfills the requirement.
Traceability Repository
:
Requirement traceability is documented and maintained manually or requirement management tools (as identified in BA approach).
Maintain Requirements
Purpose
: to retain requirement accuracy and consistency throughout and beyond the change during the entire requirement life cycle, and to support reuse of requirements in other solutions.
Input
:
Requirements
Designs
A requirement that represents an ongoing need must be maintained to ensure that it remains valid over time.
Output
:
Requirements (maintained)
Designs (maintained)
Elements
Maintain Requirements
BA conduct maintenance to ensure requirements remain correct and current after an approved change.
Requirements must be clearly named and defined, easily available for stakeholders.
BA also maintain the relationships among requirements.
Maintain Attributes:
Requirement's source, priority and complexity aid in managing requirement through life cycle.
Reusing Requirements
:
For reuse, requirement need to be identified, clearly named, defined and stored easily retrievable.
Requirements can be reused:
:check:within current initiative
:check:within similar initiative
:check:within similar departments
:check:throughout the entire organization
Requirements are intended for reuse reflect the current state of the organization.
Prioritize Requirements
Purpose
: to rank requirements in the order of relative importance.
Input
:
Requirements: ready to prioritize
Designs: ready to prioritize
Prioritization is a critical exercise that seeks to ensure the maximum value is achieved.
Output
: ensure the highest value requirements/designs are addressed first
Requirements (prioritized)
Designs (prioritized)
Elements
Basis for Prioritization
Benefit
Penalty
Cost
Risk
Dependencies
Time Sensitivity
Stability
Regulatory or Policy Compliance
Challenges of Prioritization
Sometimes appear conflicts between stakeholders.
Stakeholders need to make trade-offs in prioritization.
Continual Prioritization
Priorities may shift as the context evolves and as more information becomes available.
Assess Requirements Changes
Purpose
: to evaluate the implications of proposed changes to requirements and designs.
Input
:
Proposed Change
Requirements
Designs
BA assess the potential effect of the change to solution value, and whether proposed changes introduce conflicts with other requirements or increase the level of risk.
Output
: the recommendation to approve/modify or deny a proposed change
Requirements Change Assessment
Designs Change Assessment
Elements
Assessment Formality
:
Predictive approach may indicate more formal assessment.
Adaptive approach may require less formality in the assessment.
Impact Analysis
:
Traceability is a useful tool for performing impact analysis.
When perform impact analysis, BA consider:
:check: Benefit
:check: Cost
:check: Impact
:check: Schedule
:check: Urgency
Impact Resolution
:
All impacts and resolutions resulting from the change analysis are to be documented and communicated to all stakeholders.
Approve Requirements
Purpose:
to obtain agreement on and approval of requirements and designs for business analysis work to continue and/or solution construction to proceed.
Input
:
Requirements (verified)
Designs
Once requirement has been approved, it is a finalized BA work product, and is implemented.
Approval can be formal or informal.
Output
: requirements/designs are agreed to by stakeholders and are ready for use.
Requirements (approved)
Designs (approved)
Elements
Understand Stakeholder Roles
BA is required to understand who holds decision-making responsibility and who possesses authority for sign-off across the initiative.
BA also consider influencers.
Conflict and Issue Management
BA facilitates communication between stakeholders in areas of conflict.
Gain consensus
BA need to ensure that stakeholders with approval authority understand and accept the requirements.
Lack of agreement is the associated risks are to be identified and managed accordingly.
Track and Communicate Approval
BA records approval decision.
May create audit history of changes