Document: uc-deposit-money.htm

Date: 30 May, 2001; Author: Shane Sendall (LGL-DI-EPFL)


BAT System

Use Case: Deposit Money

 

Scope: Bank Accounts and Transactions System

Level: User Goal

Intention in Context: The intention of the Client is to deposit a sum of money on an account. Clients do not interact with the System directly; instead, for this use case, a client interacts via a Teller.

Primary Actor: Client

Main Success Scenario:

1. Client requests Teller to deposit money on an account, providing sum of money.

2. Teller requests System to perform the deposit, providing deposit transaction details*.

3. System validates the deposit,
credits the account for the amount,
records the details of the transaction,
and informs Teller.

Extensions:

2a. Client requests Teller to cancel the deposit: use case ends in failure.

3a. System ascertains that it was given incorrect information:

3a.1. System informs Teller; use case continues at step 2.

3b. System ascertains that it was given insufficient information to make the deposit:

3b.1. System informs Teller; use case continues at step 2.

3c. System is not capable of depositing (e.g. transaction monitor of System is down)**:

3c.1. System informs Teller; use case ends in failure.

Notes:

* a hyperlink to the document that contains data details and formats.

** this is an example of an IT infrastructure failure, we only write it in a use case if there is a corresponding project constraint that states a physical separation, e.g., the transaction section depends on a legacy system which is located somewhere else. 

 


BAT Use Cases | BAT Description