Which statement describes when it is a good time to apply a "use case"?

Question

Options

• AYou must identify how many transactions should be included in a system test cycle.
• BYou must understand the major process steps a customer wants for collaboration among
• CYou must identify the network capacity required by a new Cisco TelePresence system.
• DYou must estimate a company's cash flow impacts from upgrading security software to the

• A
  4% (2)
• B
  94% (49)
• C
  2% (1)

Explanation

Option B is correct because a use case is a tool for capturing how a user or customer interacts with a system to achieve a goal - it documents the sequence of steps (process flow) involved in that interaction, making it ideal when you need to understand what a customer wants a system to do and how collaboration should work. Use cases answer "what does the user need the system to do, and how?" from a functional, process-oriented perspective.

• A is wrong - counting transactions for a test cycle is a testing metrics concern, not a process-flow description; you'd use test planning documents for that.
• C is wrong - determining network capacity for a TelePresence system is an infrastructure/capacity planning task, requiring traffic analysis and bandwidth calculations, not a use case.
• D is wrong - estimating cash flow from a software upgrade is a financial/business case analysis, not a use case.

Memory tip: Think of "use case" as the customer's story - who does what, and in what order. If the answer involves steps a person takes to accomplish a goal with a system, that's your use case signal. Anything involving numbers (bandwidth, transactions, cash flow) points away from use cases toward technical or financial analysis tools.

No community discussion yet for this question.