Use Case
Write the refund request end to end: how the customer starts, how the system responds, and what failure looks like.
Write the refund request end to end: how the customer starts, how the system responds, and what failure looks like.
Center on one actor goal: Name who is trying to achieve what and what triggers the interaction.
Alternate actions and responses: State what the actor does and what the system displays or changes at every step.
Include important exceptions: Explain how expired, incomplete, or duplicate requests end or return to a recoverable state.
Using only the refund rules I provide, write the “customer requests a refund” use case with its actor, trigger, preconditions, customer actions, system responses, successful result, and important exceptions. List missing rules as questions instead of inventing a refund window, and do not expand into controllers, APIs, or database design. Then check that every ending is visible and understandable to the customer.
Build in 3D. Put your computer to work.