What are Use Cases?

• A. Describe how users will use the program
• B. Describe the internal data structures of the program
• C. Provide a list of test cases
• D. Explain the hardware requirements

Answer: (A)

Use cases describe how people will interact with the system to achieve their goals, focusing on the sequence of actions a user takes and how the system responds. They capture goals from the user’s perspective and lay out typical steps—the main flow—plus any variations if things don’t go as planned. This helps you see what features are needed and how the system should behave in real-world use.

That’s why describing how users will use the program is the best fit. The other options delve into things like internal implementation details (data structures), testing artifacts (test cases), or non-functional constraints (hardware requirements), which aren’t about how users interact with the program to achieve their goals. For example, a use case for an online store might be “Purchase an item,” detailing steps like selecting an item, adding it to the cart, entering shipping information, processing payment, and receiving a confirmation.