Building the picture

• Identify dependencies, conflicts, risks
• Establish relative priorities
• Usually done through: User stories Use cases

1. Use Cases

• Represent a dialogue between the user and the system, with the aim of helping the user achieve a business goal.
• The user initiates actions and the system responds with reactions.
• They consider the system a black box.

1.1 Initial template

1.2 ATM Example

Use Case: Withdraw Money Goal in Context: Customers need to withdraw money from their accounts without entering the bank Scope: ATM, banking infrastructure Level: Primary Task Preconditions: The customer has an account with the bank Success End Condition: The customer has the money they needed to withdraw Failed End Condition: The customer has no money Primary Actor: Customer Trigger: Customer puts card into ATM

2. User Stories & UAT

2.1 Overview

User Stories are a method of requirements engineering used to inform the development process and what features to build with the user at the centre.

2.2 Structure

Example: