Traceability
Traceability is the ability to establish and maintain relationships between software work products throughout the development and testing lifecycle.
“The ability to establish explicit relationships between related work products or items within work products.”
(Definition reproduced from the ISTQB Glossary. Copyright belongs to ISTQB.)
View the complete ISTQB GlossaryWhat is Traceability?
Traceability links requirements, design, code, test cases, defects, and results, making it easier to verify coverage and assess the impact of changes.
Relationship mapping: Connects related development artifacts.
Coverage verification: Ensures all requirements are tested.
Impact analysis: Helps identify affected artifacts after changes.
Real World Example
A regulated product team is preparing a release where Traceability appears in reviews, test design conversations, or defect triage rather than as an isolated glossary word.
The risk is that the team treats Traceability as interchangeable with nearby ISTQB terms. That makes test scope blurry and can lead to weak evidence for the release decision.
The tester anchors the discussion in the official definition, asks where the concept appears in the product, and designs examples that show the difference between Traceability and similar ideas.
The page becomes useful in practice because Traceability is connected to a specific testing decision, not memorized as a detached definition.
Practice Questions
Question 1
Which statement BEST describes Traceability in the context of ISTQB terminology?
Question 2
A tester needs to explain Traceability to a non‑technical stakeholder. Which approach is MOST appropriate?
Test your knowledge with real ISTQB-style questions
You’ve learned Traceability. Test your understanding with topic-specific questions in our Mock Exams.