A business analyst is tasked with documenting requirements for a complex system involving multiple user interactions to achieve specific goals. The stakeholders prefer detailed descriptions of user-system interactions in a sequential manner. Which requirements gathering tool should the business analyst use?
Use cases are appropriate when detailed descriptions of user-system interactions are needed. They provide step-by-step sequences of actions that define how users interact with the system to achieve specific goals, aligning with the stakeholders' preference for detailed sequential descriptions. User stories are high-level, brief statements of user needs and lack the detailed interactions required in this scenario. Prototypes are preliminary models used to visualize the system's design but do not document interactions in a sequential narrative. Context diagrams illustrate the system's boundaries and relationships with external entities but do not capture user interactions in detail.
Ask Bash
Bash is our AI bot, trained to help you pass your exam. AI Generated Content may display inaccurate information, always double-check anything important.
What are use cases?
Open an interactive chat with Bash
Why are user stories considered insufficient for complex systems?
Open an interactive chat with Bash
How do prototypes differ from use cases in terms of requirements gathering?
Open an interactive chat with Bash
CAPM
Business Analysis Frameworks
Your Score:
Report Issue
Bash, the Crucial Exams Chat Bot
AI Bot
Loading...
Loading...
Loading...
Project Management Package Join Premium for Full Access