1. Question Overview
This question focuses on the value of traceability in software testing. Traceability links work products such as requirements, risks, test conditions, test cases, and results, providing visibility and control.
Question:
Which of the following statements is a CORRECT example of the value of traceability?
- a) Traceability between the mitigated risks and test cases that passed provides a means of determining the level of residual risk
- b) Traceability between user requirements and test results provides a means of measuring project progress against business goals
- d) Traceability between the identified risks and written test conditions provides a means of determining which risks are worth testing
이 문제는 “트레이서빌리티(추적성)”이 실제로 어떤 가치를 제공하는지 묻고 있습니다. 트레이서빌리티는 요구사항 → 테스트 조건 → 테스트 케이스 → 테스트 결과까지 연결해 결함 위치 파악, 테스트 누락 방지, 위험 커버리지 확인 등에 활용됩니다.
✔ Correct Answer: a) Traceability between the mitigated risks and test cases that passed provides a means of determining the level of residual risk
2. Why Option (a) Is Correct
Traceability between risks and test cases/results helps determine:
- whether major risks were tested
- whether tests addressing those risks passed or failed
- what level of residual risk still exists after mitigation
This is one of the primary values of traceability: it provides visibility into risk coverage and supports decision-making about release readiness.
위험(risk)과 테스트 결과의 연결 관계를 보면 어떤 위험이 아직 남아 있는지(residual risk), 그리고 해당 위험을 완전히 커버했는지를 판단할 수 있습니다. 이는 ISTQB가 설명하는 트레이서빌리티의 전형적 가치입니다.
3. Why the Other Options Are Incorrect
Option (b)
b) Traceability between user requirements and test results provides a means of measuring project progress against business goals
Traceability here helps measure test coverage, not business goal progress. Project progress toward business goals involves product value, timelines, scope—not simply test results.
- 요구사항 ↔ 테스트 결과 연결은 커버리지 확인 용도이며 비즈니스 목표 달성 여부를 판단하는 지표는 아니다.
Option (c)
c) Traceability between testers and test cases that failed provides a means of determining the skill level of the testers
This incorrectly uses traceability for evaluating people. Tester skill level is not measured through failed test cases.
- 테스트 실패는 시스템 결함 때문이며 테스터 실력 평가와 관련이 없다.
Option (d)
d) Traceability between the identified risks and written test conditions provides a means of determining which risks are worth testing
Deciding which risks are worth testing is part of risk assessment, not traceability. Traceability verifies coverage, not prioritization.
- 트레이서빌리티는 위험 우선순위 결정에 대한 답이 아니라, “이미 정의된 위험이 테스트로 연결되었는가”를 확인하는 활동이다.
4. Key Study Notes
- Traceability links requirements, risks, test cases, and results
- It ensures coverage and detects missing or redundant tests
- Supports impact analysis and release decisions
- Helps evaluate residual risk after execution
- 트레이서빌리티는 누락 테스트를 방지하고 위험 커버리지를 확인하는 데 필수
- 위험 기반 테스트(RBT)와 함께 사용하면 잔여 위험 판단 가능
5. Conclusion & Call to Action
Traceability provides visibility into coverage, and option (a) demonstrates its value clearly by showing how it supports the evaluation of residual risk. refer to FL-1.4.4
Related: More ISTQB posts