Please enable JavaScript.
Coggle requires JavaScript to display documents.
5.Requirements Life Cycle Management - Coggle Diagram
5.Requirements Life Cycle Management
Trace Requirements
Inputs:
Requirements
Designs
Outputs:
Requirements (traced)
Designs (traced)
Purpose:
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.
Elements
Relationships
There are several types of relationships that the business analyst considers when defining the traceability approach:
Derive
: relationship between two requirements, used when a requirement is derived from another requirement.
Depends
: relationship between two requirements, used when a requirement depends on another requirement. two types:
--
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 or other element that can determine whether a solution fulfills the requirement.
Traceability Repository
Requirements traceability is documented and maintained in accordance with the methods identified by the business analysis approach.
Level of Formality
When tracing requirements, business analysts consider the value that each link is supposed to deliver, as well as the nature and use of the specific relationships that are being created.
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, and
reliable assessment of which requirements have been addressed and which have not.
Maintain Requirements
Inputs:
Requirements
Designs
Outputs:
Requirements (maintained)
Designs (maintained)
Purpose:
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.
Elements
Maintain Attributes
While eliciting requirements, business analysts elicit requirement attributes. Information such as the requirement’s source, priority, and complexity aid in managing each requirement throughout the life cycle.
Reusing Requirements
Depending on the level of abstraction and intended need being addressed, requirements can be reused:
within the current initiative,
within similar initiatives,
within similar departments, and
throughout the entire organization.
Maintain Requirements
Requirements are maintained so that they remain correct and current after an approved change. Business analysts are responsible for conducting maintenance to ensure this level of accuracy is retained.
In order to maximize the benefits of maintaining and reusing requirements, the requirements should be:
consistently represented,
reviewed and approved for maintenance using a standardized process that defines proper access rights and ensures quality, and
easily accessible and understandable.
Assess Requirements Changes
When assessing changes, business analysts consider if each proposed change:
aligns with the overall strategy,
affects value delivered to the business or stakeholder groups,
impacts the time to deliver or the resources required to deliver the value, and
alters any risks, opportunities, or constraints associated with the overall initiative.
Outputs:
Requirements Change Assessment
Designs Change Assessment
Inputs:
Proposed Change
Requirements
Designs
Elements
Impact Analysis
When considering changes or additions to existing requirements, business analysts assess the impact of the proposed change by considering:
Benefit
Cost
Impact
Schedule
Urgency
Impact Resolution
Depending on the planned approach, various stakeholders (including the business analyst) may be authorized to approve, deny, or defer the proposed change. All impacts and resolutions resulting from the change analysis are to be documented and communicated to all stakeholders.
Assessment Formality
Business analysts will determine the formality of the assessment process based on the information available, the apparent importance of the change, and the governance process.
Purpose:
The purpose of Assess Requirements Changes is to evaluate the implications of proposed changes to requirements and designs.
Approve Requirements
Business analysts are responsible for ensuring clear communication of requirements, designs, and other business analysis information to the key stakeholders responsible for approving that information.
Outputs:
Requirements (approved)
Designs (approved)
Inputs:
Requirements (verified)
Designs
Elements
Gain Consensus
Business analysts are responsible for ensuring that the stakeholders with approval authority understand and accept the requirements.
Track and Communicate Approval
The business analyst records approval decisions, possibly in requirements maintenance and tracking tools. In order to communicate the status of requirements, it is necessary to keep accurate records of current approval status.
Conflict and Issue Management
To maintain stakeholder support for the solution, consensus among stakeholders is usually sought prior to requesting approval of requirements.
Understand Stakeholder Roles
The approval process is defined by the task Plan Business Analysis Governance. Part of defining the approval process is understanding stakeholder roles and authority levels.
Purpose:
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.
Prioritize Requirements
Prioritization is the act of ranking requirements to determine their relative importance to stakeholders. When a requirement is prioritized, it is given greater or lesser priority.
Outputs:
Requirements (prioritized)
Designs (prioritized)
Inputs:
Requirements
Designs
: any designs in the form of text, prototypes, or diagrams that are ready to prioritize.
Elements
Challenges of Prioritization
Prioritization is an assessment of relative value. Each stakeholder may value something different. When this occurs, there may be conflict amongst stakeholders.
Continual Prioritization
Priorities may shift as the context evolves and as more information becomes available. Initially, prioritization is done at a higher level of abstraction.
Basis for Prioritization
Typical factors that influence prioritization include:
• Benefit
• Penalty
• Cost
• Risk
• Dependencies
• Time Sensitivity
• Stability
• Regulatory or Policy Compliance
Purpose:
The purpose of Prioritize Requirements is to rank requirements in the order of relative importance.
Inputs
Requirements
Designs
Proposed Change
Requirements (verified)
Outputs
Requirements (approved)
Designs (approved)
Requirements Change Assessment
Designs Change Assessment
Requirements (prioritized)
Designs (prioritized)
Requirements (maintained)
Designs (maintained)
Requirements (traced)
Designs (traced)