CAPM Practice: Demonstrate an understanding of business analysis (BA) roles and responsibilities
Question 7 of 67 in Demonstrate an understanding of business analysis (BA) roles and responsibilities
Show answer & explanation
Correct answer: Linking requirements to their origin (stakeholder need) and their implementation (test cases, design elements) to ensure completeness and manage changes
Explanation
Requirements traceability creates bidirectional links: requirements trace back to business needs (justifying why they exist) and forward to design, code, and tests (confirming they were implemented and verified). This supports impact analysis for changes.
**Why not A:** Requirements traceability is about linking requirements to their business origin and downstream artifacts, not about tracking individual authorship. Knowing which developer wrote a requirement does not help ensure completeness or manage the impact of changes across the project lifecycle.
**Why not C:** Counting the number of revisions is a version control concern, not traceability. Requirements traceability establishes bidirectional links — from stakeholder needs through to design, implementation, and test cases — so that every requirement can be verified as addressed and any change impact can be assessed.
**Why not D:** Recording submission dates is an administrative tracking activity, not traceability. True requirements traceability connects each requirement forward to its implementation and testing artifacts and backward to its originating stakeholder need, enabling completeness verification and change impact analysis.
Key Concept
This question covers Demonstrate an understanding of business analysis (BA) roles and responsibilities under Demonstrate an understanding of business analysis (BA) roles and responsibilities (Business Analysis Frameworks).
All 1,500+ CAPM questions are free
Sign up to track your progress, see detailed analytics, and get personalized study recommendations.
Sign Up Free