CAPM Practice: Demonstrate an understanding of business analysis (BA) roles and responsibilities
Question 18 of 67 in Demonstrate an understanding of business analysis (BA) roles and responsibilities
Pick an answer below — you'll get the explanation instantly, no signup.
Show answer & explanation
Correct answer: A description of how an actor (user or system) interacts with the system to achieve a specific goal, used to capture functional requirements
Explanation
A use case describes a system's behavior from the user's perspective — a sequence of steps showing how an actor achieves a goal. Use cases are a classic BA tool for capturing and communicating functional requirements.
**Why not B:** A business case document used to justify a project is a separate artifact from a use case. Business cases evaluate project viability and ROI, while use cases describe specific user-system interactions. The similar terminology can be confusing, but they serve entirely different purposes in BA work.
**Why not C:** A legal precedent for resolving requirements disputes does not describe a use case. Use cases are modeling tools that capture functional requirements by describing how actors interact with a system to achieve goals, not legal frameworks for dispute resolution.
**Why not D:** A case study of a similar project used as a planning reference describes benchmarking or lessons learned, not a use case. Use cases focus on defining the specific interactions between users and the system being developed, not on reviewing past project experiences.
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