Author: Hayden Smith 2021
Why?
What?
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.
When a customer tells you what they want, try and express it in the form As a < type of user >, I want < some goal > so that < some reason >
E.G. They say:
User stories:
Why do we care?
Building a to-do list
As a user, I want to use a search field to type a city, name, or street, so that I can find matching hotel options.
As a user, I can log in through a social media account, because I always forget my passwords
As a user, I want to be able to recover the password to my account, so that I will be able to access my account in case I forgot the password.
Scenario: Forgot password
Given: The user has navigated to the login page
When: The user selected forgot password option
And: Entered a valid email to receive a link for password recovery
Then: The system sent the link to the entered email
Given: The user received the link via the email
When: The user navigated through the link received in the email
Then: The system enables the user to set a new password
Generally you can represent use cases as:
There is a range of different approaches that can be taken too, e.g. Cockburn style (not required reading)
MAIN SUCCESS SCENARIO
Step 1. ATM asks customer for pin
Step 2. Customer enters pin
Step 3. ATM asks bank to verify pin and account
Step 4. Bank informs ATM of validity and balance of account
Step 5. ATM asks customer what action they wish to take
Step 6. Customer asks to withdraw an amount of money
Step 7. ATM Dispenses money to customer
Step 8. ATM informs bank of withdrawal
Let's take the opportunity to build our requirements for a UNSW monorail. Ensure some of the requirements are expressed in terms of user stories and/or use cases.
https://tharunka.arc.unsw.edu.au/src-approves-plans-for-monorail/