Please enable JavaScript.
Coggle requires JavaScript to display documents.
Requirements Life Cycle (Trace Requirements (Purpose To ensure that…
Requirements Life Cycle
Trace Requirements
Purpose To ensure that requirements and designs are aligned to one another and to manage the effects of change
Traceability identifies and documents the lineage of each requirement including backward traceability, forward traceability and its relationship to other requirements. It is also used to help ensure that the solution adheres to requirements and assist in scope, change risk time, cost and communication management. Traceability enables:
- faster and simpler impact analysis
- more reliable discovery of inconsistencies and gaps
- deeper insights into the scope and complexity of a change
- reliable assessment of which requirements have been addresses
-
-
-
Maintain Requirements
Purpose To retain requirement accuracy and consistency throughout and beyond the change during the entire requirements life cycle and to support reuse of requirement in other solutions
A requirement that represents an ongoing need must be maintained to ensure that it remains valid over time. In order to maximize the benefits of maintaining and reusing requirements they should be:
- consistently represented
- reviewed and approved for maintenance using a standardized process that defines proper access rights and ensures quality
- easily accessible
-
-
-
-
-
Approve Requirements
Purpose To obtain agreement on and approval of requirements and designs for business analysis work to continue and solution construction to proceed
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.
Approval of requirements and designs may be formal or informal. Predictive approaches typically perform approvals at the end of the phase or during planned change control meetings. Adaptive approaches typically approve requirements only when construction and implementation of a solution meeting the requirements can begin. BA's work with key stakeholders to gain consensus on new and changed requirements, communicate the outcome of discussions and track and manage the approval
-
-
-
-
Trace Requirements
- Business Rules Analysis
- Functional Decomposition
- Process Modelling
- Scope Modelling
Maintain Requirements
- Business Rules Analysis
- Functional Decomposition
- Process Modelling
- Use Cases and Scenarios
- User Stories
Prioritize Requirements
- Backlog Management
- Business Cases
- Decision Analysis
- Estimation
- Financial Analysis
- Interviews
- Item Tracking
- Prioritization
- Risk Analysis and Management
- Workshops
Assess Requirements
- Business Cases
- Business Rules Analysis
- Decision Analysis
- Document Analysis
- Estimation
- Financial Analysis
- Interviews
- Item Tracking
- Risk Analysis
- Workshops
Approve Requirements
- Acceptance and Evaluation Criteria
- Decision Analysis
- Item Tracking
- Reviews
- Workshops