Acceptence criteria:

• acceptance criteria are a way to capture assumptions and details
• accepance criteria allow us to factor in different business situations and user behaviours that result in different outcomes
• SMART framework

What did these criteria reflect?

• reflects assumptions about the user
• reflects assumptions about the business env
• generalisations about the user or business environment

We understand that the customer and the developer need to agree on the acceptable outcomes when the user interacts with the system in a given business environment. Acceptance criteria do the following:

• capture specific details
• capture assumptions

Happy Path:

we call scenarios that lead to the most optimistic outcome, the "happy path".

So what the acceptance criteria helps us do is prove that under given conditions, when the user performs an action (or a set of actions) with the system, a favourable outcome is reached.

Reinforce Happy Path concept by reviewing ATM example of withdrawing cash.

The user story: As an account holder I would like to withdraw cash from an ATM so that I have money to spend

For a favourable outcome what business conditions need to be met?
Account Holder enters valid pin
Account Holder has a balance matching or exceeding requested amount
ATM has cash matching or exceeding requested amount

So what should happen when the Account Holder tries to withdraw cash?
ATM dispenses requested cash immediately
Account Holder's balance is reduced
ATM cash balance is reduced