Type the formal use case template, filled in for BorrowBox. Keep the field labels aligned — the shape is what you are learning.

Answer

Use case: Collect a reserved tool Primary actor: Member Goal: leave with the copy, unaided Secondary: Locker Controller, Payments Gateway Precondition: reservation held, hold not expired Trigger: member arrives at the locker bank Scenario: 1 request code 2 present code 3 door opens 4 take tool 5 reservation -> checked out Exceptions: expired hold | locker jam | already collected

The template is the answer to "how do I start?" under exam conditions. Fill the fields top to bottom and the content follows: naming the primary actor forces you to state a goal, stating a goal forces a precondition, and the numbered scenario then writes itself. Exceptions come last on purpose — each one has to survive the rationalisation rule (the software must be able to detect it AND handle it) before it earns a line.

Pressman 9e ch7 §7.4, §7.6–§7.8