Structuring systems process requirements

Diagram it using a swim lane flowchart

Use Case Title: Balance Inquiry

Primary Actor: Customer

Level: Kite (Summary)

Stakeholders: Customer, Bank teller

Precondition: Customer must enter PIN, in order to view balance inquiry.

Minimal Guarantee: Uncompleted action

Success Guarantees: Customers balance inquiry is shown.

Trigger: The customer chooses balance inquiry from the menu of transaction types.

Main Success Scenario:

1. The customer enters their card into the ATM.
2. The customer enters the PIN to gain access.
3. The customer chooses the View Balance option.
4. The account balance is displayed on the ATM screen.
5. The customer chooses Complete Transaction
6. The ATM returns the customers card.
7. The customer takes the card.

Extensions:

1a. The customer enters an invalid card.

1a1. The ATM displays an error message.

1a2. The ATM ejects the card.

1a3. The customer takes the card.

1a4. The customer puts the card back to the ATM and continues

2a. The customer enters an invalid PIN.

2a1. The ATM displays that the wrong PIN has been entered.

2a2. The ATM asks the customer to enter their PIN again.

2a3. The customer enters the PIN again and continues.

4a. The account balance is not displayed on the screen.

4a1. The customer cancels the transaction to take the card out.

4a2. The customer calls the bank staff to inform the issue.

7a. The card stuck in the ATM

7a1. The ATM alerts the customer.

7a2. The ATM explains the machine malfunction to the user.

7a3. The ATM asks the customer to speak to the bank teller.