Wednesday, March 21, 2018

Author: Doug Goldberg

As the process of capturing and documenting business requirements matures, there is often a watershed moment when an organization must decide whether to perform traceability of requirements as part of that process. Most companies involved with a formal methodology for software development utilize some degree of traceability; but those not familiar with it could be put off by the overhead of requirements management (RM), of which traceability is a component. Therefore, it helps to understand some of the value aspects of instituting traceability.

The International Institute of Business Analysis’ (IIBA) defines requirements traceability:
The ability to identify and document the lineage of each requirement, including its derivation (backward traceability), its allocation (forward traceability), and its relationship to other requirements.

[Read More...]

Post Rating


There are currently no comments, be the first to post one.

Post Comment

Only registered users may post comments.
Copyright 2009-2014 by Modern Analyst Media LLC