Which of the following describes a use case?

• A. A document about organizational structure
• B. A technique for documenting potential requirements
• C. A method for training staff
• D. A description of software licensing terms

Answer: (B)

A use case is a narrative of how a user or external system interacts with the software to achieve a specific goal. It focuses on the sequence of steps, who is involved (the actors), and the expected outcomes, capturing how the system should behave in typical and alternative scenarios. This makes it a technique for documenting potential requirements because it translates stakeholder needs into concrete interactions and flows that the system must support.

For example, a use case might describe a clinician logging into a patient records system, selecting a patient, and updating a chart, including alternate paths like what happens if the patient record is locked or if data entry is incomplete. This kind of description helps elicit and validate functional requirements and informs design and testing.

The other options don’t fit this concept: a document about organizational structure describes governance or hierarchy, not user-system interactions; a method for training staff focuses on education rather than how the system will be used; and a description of software licensing terms covers contractual terms rather than user workflows and system behavior.