Please enable JavaScript.
Coggle requires JavaScript to display documents.
5 Requirements Life Cycle Management, 5.1 Trace Requirements - Coggle…
5 Requirements Life Cycle Management
Define
The Requirements Life Cycle Management knowledge area describes
the tasks that business analysts
perform i
n order to manage
and
maintain requirements and design information
from inception to retirement.
These tasks describe establishing meaningful relationships between related requirements and designs, assessing changes to requirements and designs when changes are proposed, and analyzing and gaining consensus on changes.
The purpose of requirements life cycle management is to ensure that business, stakeholder, and solution requirements and designs are aligned to one another and that the solution implements them.
The requirements life cycle:
continues through the development of a solution, and
ends when a solution and the requirements that represent it are retired.
begins with the representation of a business need as a requirement
The Requirements Life Cycle Management knowledge area includes the following
tasks:
Trace Requirements:
analyzes and maintains the relationships between requirements, designs, solution components, and other work products for impact analysis, coverage, and allocation.
Maintain Requirements:
ensures that requirements and designs are accurate and current throughout the life cycle and facilitates reuse where appropriate.
Prioritize Requirements:
assesses the value, urgency, and risks associated with particular requirements and designs to ensure that analysis and/or delivery work is done on the most important ones at any given time.
Assess Requirements Changes:
evaluates new and changing stakeholder requirements to determine if they need to be acted on within the scope of a change.
Approve Requirements:
works with stakeholders involved in the governance process to reach approval and agreement on requirements and designs.
5.1 Trace Requirements
1/Purpose
ensure that requirements and designs at
different levels are aligned to one another
manage the effects of change
to one level on related requirements
2/ Description
Traceability enables:
more reliable discovery of inconsistencies and gaps in requirements
deeper insights into the scope and complexity of a change
faster and simpler impact analysis
reliable assessment of which requirements have been addressed and which
have not
3/Inputs
Requirements
may be traced to other requirements (including goals, objectives, business requirements, stakeholder requirements, solution
requirements, and transition requirements), solution components, visuals, business rules, and other work products.
Designs
may be traced to other requirements, solution components, and other
work products.
4/Elements
1/Level of Formality (Mức độ trang trọng)
2/Relationships
3/Traceability Repository (kho lưu trữ xác định nguồn gốc)
5/ Outputs
Requirements (traced)
have clearly defined relationships to other requirements, solution components, or releases, phases, or iterations, within a solution scope, such that coverage and the effects of change are clearly identifiable.
Designs (traced)
clearly defined relationships to other requirements, solution components, or releases, phases, or iterations, within a solution scope, such that coverage and the effects of change are clearly identifiable.