CCBA Requirements Elicitation & Documentation 3 — Questions and Answers
Question 1: Which documentation format is MOST appropriate for capturing a system interaction from the perspective of an actor achieving a specific goal?
- Business Requirements Document (BRD)
- Use case specification (Correct answer)
- Data flow diagram
- RACI matrix
Correct 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.
Question 2: A user story follows the format 'As a [role], I want [feature], so that [benefit].' What component does the 'so that' clause provide?
- The acceptance criteria
- The business justification and value (Correct answer)
- The technical implementation approach
- The priority ranking
Correct 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.
Question 3: What is the PURPOSE of a requirements traceability matrix (RTM)?
- To assign ownership of each requirement to a specific developer
- To link requirements to their source, design components, and test cases to ensure full coverage (Correct answer)
- To prioritize requirements by business value and implementation cost
- To document the history of requirement changes over the project lifecycle
Correct 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.
Question 4: When should a BA use a context diagram?
- To show the internal processes within a system
- To illustrate the system boundary and external entities that interact with it (Correct answer)
- To document the data structure of the database schema
- To map stakeholder roles to project tasks
Correct 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.
Question 5: What distinguishes a Business Requirements Document (BRD) from a Software Requirements Specification (SRS)?
- A BRD is written in technical language; an SRS uses business language
- A BRD captures business needs and objectives; an SRS details specific functional and technical requirements for the system (Correct answer)
- A BRD is produced after development; an SRS is produced before
- A BRD is maintained by developers; an SRS is maintained by the BA
Correct 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.
Question 6: A BA is documenting acceptance criteria for a requirement. Which characteristic is MOST critical for well-written acceptance criteria?
- They should describe the technical implementation approach
- They should be testable and unambiguous so pass/fail can be objectively determined (Correct answer)
- They should be written in formal legal language to prevent disputes
- They should be approved only by the development team lead
Correct 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.
Question 7: In requirements documentation, what is meant by the term 'requirement atomicity'?
- Requirements must be approved unanimously by all stakeholders
- Each requirement should express a single, discrete need that cannot be broken down further without losing meaning (Correct answer)
- Requirements must be documented using formal mathematical notation
- Requirements must be traceable to a single business goal
Correct 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.
CCBA Requirements Elicitation & Documentation 3
Which documentation format is MOST appropriate for capturing a system interaction from the perspective of an actor achieving a specific goal?