BABOK_Guide_v3_member_copy

Requirements Life Cycle Management
Trace Requirements
Figure 5.1.3: Trace Requirements Input/Output Diagram
Input
Guidelines and Tools
Domain Knowledge
Requirements
Designs
5.1.4 Elements
Information Management
Approach
Legal/Regulatory
Information
Requirements Management
Tools/Repository
.1 Level of Formality
5.1
Requirements
(traced)
5.1
Trace Requirements
Output
Tasks Using This Output
7.5
Define Design
Options
5.1
Designs
(traced)
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.
The effort to trace requirements grows significantly when the number of
requirements or level of formality increases.
Complimentary IIBA® Member Copy. Not for Distribution or Resale.
.2 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. This type of relationship is appropriate
to link the requirements on different levels of abstraction. For example, a
solution requirement derived from a business or a stakeholder requirement.
81