Main Page

From Coest Body of Knowledge
(Difference between revisions)
Jump to: navigation, search
(Another page here)
(9 intermediate revisions by 2 users not shown)
Line 1: Line 1:
 
== What is Traceability? ==
 
== What is Traceability? ==
  
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].  
+
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]. Each traceability link follows a basic [[life cycle]].
  
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.
+
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 [2].
 +
 
 +
Traceability links can be established either manually or dynamically.  Dynamic methods involve rule-based approaches or [[trace retrieval methods]].
  
  
 
== References ==
 
== References ==
1. Orlena Gotel, Anthony Finkelstein: Contribution structures (Requirements artifacts). RE 1995: 100-107.
+
1. Olly Gotel, Anthony Finkelstein: Contribution structures (Requirements artifacts). RE 1995: 100-107.
  
 
2. Matthias Jarke: Requirements Tracing - Introduction. Commun. ACM 41(12): 32-36 (1998)
 
2. Matthias Jarke: Requirements Tracing - Introduction. Commun. ACM 41(12): 32-36 (1998)

Revision as of 19:52, 4 August 2011

What is Traceability?

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]. Each traceability link follows a basic life cycle.

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 [2].

Traceability links can be established either manually or dynamically. Dynamic methods involve rule-based approaches or trace retrieval methods.


References

1. Olly Gotel, Anthony Finkelstein: Contribution structures (Requirements artifacts). RE 1995: 100-107.

2. Matthias Jarke: Requirements Tracing - Introduction. Commun. ACM 41(12): 32-36 (1998)

© Center of Excellence for Software Traceability