Please enable JavaScript.
Coggle requires JavaScript to display documents.
Requirement Life Cycle, 5.1. Trace Requirements, 5.2. Maintain…
- Definition: manage & maintain requirements and design info from the start to the end.
- Purpose: ensure that business, SH and solution RQMs and designs are aligned to one another and that the solution implements them
- Begin with needs > continues through the development of solution > end when solution and requirements end
- The management of RQMs doesn't end when a solution is implemented >< RQMs continue to provide value when they're managed properly througout the life of solution
RQM Life Cycle knowledge area:
- Trace RQM
- Maintain RQM
- Prioritize RQM
- Assess RQM changes
- Approve RQM
Inputs:
- RQM
- Designs
- Proposed changes
- RQM (verified)
5.1. Trace Requirements
.1. Purpose:
- Ensure that RQMs & designs at different levels are aligned to one another
- Manage the effects of change to 1 level on related RQMs
.2. Description
- Identify and document the lineage of each RQM: its backward & forward tracibility, its relationship to other RQMs
- Ensure that the solution conforms to (~obey) RQMs and to assist in scope, change, risk, time, cost & communication management
- Detect missing functionality/identify if there's implemented functionality not supported by any RQM
-
.4. Elements
.1. Level of formality: BA consider the value that each link is suppose to deliver + the nature & use of the specific relationships that are being created
-
.3. Traceability Repository: is documented and maintained in accordance with the methods identified by the BA approach
-
-
5.3. Prioritize RQMs
.2. Description
- rank RQMs to determine their relative importance to SHs
Priority refer to:
- the relative value of a RQM or
- the sequence in which it will be implemented
- ongoing process: priority change when context change
-
-
-
-
5.4. Assess RQM changes
-
.2. Description
- is performed as new needs or possible solutions are identified => determine whether a proposed change will increase the value of the solution and if so, what action should be taken
BA:
- assess the potential effect of the change to solution value
- assess if proposed change conflicts with other RQMs or increase the risk level
- ensure each proposed change can be traced back to a need
BA consider if each proposed change:
- aligns with overall strategy
- affects value delivered to business or SH groups
- impact the time to deliver or resources required to deliver value
- alter any risk, opportunites, constraints associated with overall initiative
-
-
.4. Elements
-
.4.2. Impact Analysis
- is performed to assess/evaluate the effect of a change
- useful tool: traceability
- when a RQM changes, its relationships to other RQM/solution components can be reviewed => each relelated RQM/component may require a change to support new RQM
BA assess the impact of proposed change by considering:
- Benefit: gained benefit by accepting the change
- Cost: total cost to implement the change (cost to make change, cost to rework, opportunity cost)
- Impact: customers or business processes affected if the change is accepted
- Schedule: the impact to the existing delivery commitments
- Urgency: importance level
.4.3. Impact Resolution
- Based on the planned approach, various SHs may be authorized to approve, deny or defer the proposed change
- All impacts and resolutions resulting from the change analysis are documented and communicated to all SHs (How? - check Plan BA Governance)
-
5.5. Approve RQMs
.4. Elements
.4.1. Understand SH role
BA is responsible for:
- obtaining SH approvals
- understanding who holds decision-making responsibility & who owns approval for initiative
-
-
-
-
.2. Description
- BA is responsible for ensuring clear communication of RQMs, designs and other BA info to the key SHs responsible for approving that info
Approval can be formal or informal:
- Predictive approach: perform approvals at the end of the phase/during planned change control meetings
- Adaptive approach: approve RQMs only when construction and implementation of a solution meeting the RQM can begin
BA work with key SHs to:
- gain agreement on new and changed RQMs
- communicate the outcome of discussion
- track & manage the approval
-
-
.1. Purpose: obtain agreement on and approval of RQMs and designs for BA work to continue &/or solution construction to proceed