(→What is Traceability?) |
|||
| Line 1: | Line 1: | ||
== Traceability Body of Knowledge == | == Traceability Body of Knowledge == | ||
To contribute to this BoK you need to be a registered member of CoEST. You may register by clicking on the CoEST icon and then following instructions to register as a member. Consult the [http://meta.wikimedia.org/wiki/Help:Contents User's Guide] for information on using the wiki software. | To contribute to this BoK you need to be a registered member of CoEST. You may register by clicking on the CoEST icon and then following instructions to register as a member. Consult the [http://meta.wikimedia.org/wiki/Help:Contents User's Guide] for information on using the wiki software. | ||
| + | |||
== What is Traceability? == | == What is Traceability? == | ||
To contribute to this BoK you need to be a registered member of CoEST. You may register by clicking on the CoEST icon and then following instructions to register as a member. Consult the User's Guide for information on using the wiki software.
Traceability has been defined by Gotel et al, as "the ability to follow the life of a requirement in both a forward and backward direction"[1].
Jarke et al identified four types of traceability that they referred to as (i) backwards from requirements, (ii) forwards to requirements, (iii) backwards to requirements, and (iv) forward from requirements.