Revision as of 03:06, 20 July 2011 (view source) Jhuang (Talk | contribs) (→What is Traceability?) ← Older edit		Revision as of 03:10, 20 July 2011 (view source) Jhuang (Talk | contribs) (→Another page here) Newer edit →
Line 6:		Line 6:
−	== Another page here ==	+	== References ==
−	testing	+	1. Orlena Gotel, Anthony Finkelstein: Contribution structures (Requirements artifacts). RE 1995: 100-107.
		+
		+	2. Matthias Jarke: Requirements Tracing - Introduction. Commun. ACM 41(12): 32-36 (1998)

---

Revision as of 03:10, 20 July 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].

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.

References

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

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