Requirements Elicitation & Documentation Flashcards
7 cards from real CCBA practice questions. Tap to flip, then mark Knew It or Still Learning — missed cards come back until you master them.
Read the first 7 Requirements Elicitation & Documentation flashcards as text
Which documentation format is MOST appropriate for capturing a system interaction from the perspective of an actor achieving a specific goal?
Answer: Use case specification
A use case specification documents the interaction between an actor and a system to achieve a goal, making it the standard format for this purpose.
A user story follows the format 'As a [role], I want [feature], so that [benefit].' What component does the 'so that' clause provide?
Answer: The business justification and value
The 'so that' clause articulates the business value or benefit, ensuring the team understands WHY the feature is needed.
What is the PURPOSE of a requirements traceability matrix (RTM)?
Answer: To link requirements to their source, design components, and test cases to ensure full coverage
An RTM traces requirements forward to design and test cases and backward to their source, ensuring no requirement is missed or untested.
When should a BA use a context diagram?
Answer: To illustrate the system boundary and external entities that interact with it
A context diagram depicts the system as a single process and shows all external entities (actors, systems) and their data flows at a high level.
What distinguishes a Business Requirements Document (BRD) from a Software Requirements Specification (SRS)?
Answer: A BRD captures business needs and objectives; an SRS details specific functional and technical requirements for the system
The BRD articulates high-level business needs and goals, while the SRS provides detailed functional and non-functional requirements for the development team.
A BA is documenting acceptance criteria for a requirement. Which characteristic is MOST critical for well-written acceptance criteria?
Answer: They should be testable and unambiguous so pass/fail can be objectively determined
Acceptance criteria must be testable and unambiguous so that testers and stakeholders can objectively verify whether the requirement has been met.
In requirements documentation, what is meant by the term 'requirement atomicity'?
Answer: Each requirement should express a single, discrete need that cannot be broken down further without losing meaning
Atomicity means each requirement states exactly one need, making it testable, unambiguous, and independently implementable.
How this page was made: written with AI tools and published by Nathan Beja, founder of Practice Test Geeks, who is responsible for its content. Exam facts are checked against the official sources listed below. Not reviewed by a subject-matter expert. Editorial policy
Sources & references
Exam facts on this page (fees, format, dates, passing scores) are checked against these official sources; the date is our last check. Editorial policy
- iiba.org — Eligibility, retake policy, score release, test delivery, fees, exam format, time limit, score validity, renewal, passing score · verified Oct 2026