Please enable JavaScript.
Coggle requires JavaScript to display documents.
Requirements Life Cycle Management - Coggle Diagram
Requirements Life Cycle Management
5.1. Trace Requirements
2. Inputs
Requirements
Designs
3. Elements
2. Relationships
2. Depends
use when a requirement depends on another requirement
Necessity
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
3. Satisfy
relationship between an implementation element and the requirements it is satisfying
1. Derive
use when a requirement is derived from another requirement
4. Validate
relationship between a requirement and a test case or other element that can determine whether a solution fulfills the requirements
3. Traceability Repository
1. Level of Formality
1. Purpose
Ensure that requirements and designs at different level are aligned to one another,
To manage the effects of change to one level on related requirements
4. Outputs
Requirements (traced)
Designs (traced)
5.2. Maintain Requirements
2. Inputs
Requirements
Designs
3. Elements
2. Maintain Attributes
While eliciting requirements, BA elicit requirement attributes
requirement's source, priority, and complexity aid in managing each requirement throughout the requirement life cycle
3. Reusing Requirements
Requirements are identified, clearly named, defined, and stored in manner that makes them easily retrievable by other stakeholders
Requirements can be reused
within similar initiatives
within similar departments
within the current initiative
throughout the entire organization
1. Maintain Requirements
Requirements are maintained so that they remain correct and current after an approved change.
The requirements must be clearly named and defined, and easily available to stakeholders
1. Purpose
retain requirement accuracy and consistency throughout and beyond the change during the entire requirements life cycle
support reuse of requirements in other solutions
4. Outputs
Requirements (maintained)
Designs (maintained)
5.4. Assess Requirement Changes
2. Inputs
Requirements
Designs
Proposed Changes
3. Elements
2. Impact Analysis
3. Impact
Number of customer or business processes affected
4. Schedule
Impact to existing delivery commitments
2. Cost
Total costs to implement the change
5. Urgency
Level of importance of the change
1. Benefit
Benefit to be gained by accepting the change
3. Impact Resolution
1. Assessment Formality
1. Purpose
To evaluate the implications of proposed changes to requirements and designs
4. Outputs
Requirement Changes Assessment
Consider Proposed Changes
affects value delivered to business or stakeholder groups
impacts the time to deliver or the resources required to deliver the value
aligns with the overall strategy
alters any risks, opportunities, or constraints associated with the overall initiative
5.5. Approve Requirements
2. Inputs
Requirement (verified)
Designs
3. Elements
2. Conflict and Issue Management
3. Gain Consensus
1. Understand Stakeholder Roles
4. Track and Communicate Approval
1. Purpose
Obtain agreement on and approval of requirements and designs for business analysis work to continue and/or solution construction to proceed
4. Outputs
Requirements (approved)
Designs (approved)
5.3. Prioritize Requirements
2. Inputs
Requirements
Designs
3. Elements
2. Challenges of Prioritization
Considering challenges of prioritization.
May be need to make trade-offs in prioritization
3. Continual Prioritization
Address continual prioritization
1. Basis for Prioritization
4. Risk
Spend time early on risky or difficult components to make sure the solution can be delivered
5. Dependencies
Implement requirements that depend upon one another at the same time
3. Cost
Force stakeholder awareness of the implementation cost of requirements
6. Time Sensitivity
Yield quick or certain successes ralative to adding value to the business
2. Penalty
Minimize the negative consequences of not implementing a specific requirement
7. Stability
Avoid implementing unstable requirements until they are better defined and understood
1. Benefit
Provide the most business value and meet business goals and objectives
8. Regulatory or Policy Compliance
Address regulatory or policy requirements
1. Purpose
To rank requirements in the order of relative importance
4. Outputs
Requirements (prioritized)
Designs (prioritized)