In a use case specification, what are guarantees?

In a use case specification, what are guarantees?

• A. Postconditions, the conditions that must be true at the end of the use case
• B. The main success scenario
• C. The event that gets the use case started
• D. Alternative sequences branching from the main success scenario

Answer: (A)

Guarantees in a use case specification are the postconditions—the conditions that must be true at the end of the use case. They describe the final state the system guarantees after the use case completes, regardless of the path taken (as long as the flow doesn’t fail). For example, after submitting an order, the guarantees might include that an order record exists with a unique identifier, the inventory is updated, and a confirmation is sent. This focus on the final state distinguishes guarantees from the main success scenario, which outlines the typical steps to reach a successful outcome, as well as from the initiating event that starts the use case and from alternative or extension flows that describe other possible paths.

Guarantees in a use case specification are the postconditions—the conditions that must be true at the end of the use case. They describe the final state the system guarantees after the use case completes, regardless of the path taken (as long as the flow doesn’t fail). For example, after submitting an order, the guarantees might include that an order record exists with a unique identifier, the inventory is updated, and a confirmation is sent. This focus on the final state distinguishes guarantees from the main success scenario, which outlines the typical steps to reach a successful outcome, as well as from the initiating event that starts the use case and from alternative or extension flows that describe other possible paths.