Table 5.3: 'Fully dressed' use case template. Use case: Functional goal (= use case title) (stated as an active verb phrase, e.g. 'Navigate to destination'); Primary and other roles (called 'Actors' in UML); Main/normal/happy day scenario: Step 1 Step 2, etc; Variation scenarios (maybe branching off from and maybe returning to the main scenario; similarly narrated in steps): Variation 1: Variation Scenario 1 . Variation 2, etc; Exceptions, i.e. exception events and their exception-handling scenarios (branching off from any scenarios in the use case and, if possible, returning to them, or else ending with failure; again narrated in steps): Exception event 1: Exception scenario 1 Exception event 2, etc; Preconditions, including the trigger condition that causes the use case to start; Guarantees (postconditions) (what must be true when the use case ends): the success guarantee(s) what must be true for the use case to end with success - minimal or failure guarantee(s) - what must be true, however the use case ends; Stakeholders and interests: people/organisations who have valid interests, briefly stated here, in this use case; Local qualities and constraints (nonfunctional requirements) that apply specifi- cally to this use case (rather than 'globally' to the whole product; shared information should be held in a central place and linked to the use cases that need it to avoid duplication.)