Difference between revisions of "Requirements traceability"
(Created page with "Requirements traceability is the ability for tracking the relationships between sets of requirements and designs from the original stakeholder need to the actual implement...") |
|||
| Line 5: | Line 5: | ||
:[[Requirements traceability]]. The ability for tracking the relationships between sets of requirements and designs from the original stakeholder need to the actual implemented solution. Traceability supports change control by ensuring that the source of a requirement or design can be identified and other related requirements and designs potentially affected by a change are known. | :[[Requirements traceability]]. The ability for tracking the relationships between sets of requirements and designs from the original stakeholder need to the actual implemented solution. Traceability supports change control by ensuring that the source of a requirement or design can be identified and other related requirements and designs potentially affected by a change are known. | ||
| − | [[Category: Business Analysis]][[Category: | + | [[Category: Business Analysis]][[Category: Articles]] |
Latest revision as of 08:27, 7 July 2020
Requirements traceability is the ability for tracking the relationships between sets of requirements and designs from the original stakeholder need to the actual implemented solution. Traceability supports change control by ensuring that the source of a requirement or design can be identified and other related requirements and designs potentially affected by a change are known.
Definitions
According to the BABOK Guide (3rd edition),
- Requirements traceability. The ability for tracking the relationships between sets of requirements and designs from the original stakeholder need to the actual implemented solution. Traceability supports change control by ensuring that the source of a requirement or design can be identified and other related requirements and designs potentially affected by a change are known.
