Document: uc-identify-client.htm

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


BAT System

Use Case: Identify Client

 

Scope: Bank Accounts and Transactions System

Level: Sub-Function

Intention in Context: The intention of the Client is to identify him/herself to the System. Clients identify themselves with a Mediator (which can be a Teller, ATM, or a Web Client). Non-Teller Mediator can be an ATM, or a Web Client.

Primary Actor: Client

Main Success Scenario:

1. Client identifies him/herself with Mediator in reference to an account*.

2. Teller validates identification with respect to account information.

Extensions:

2a. Teller fails to identify Client as an owner of the account: use case ends in failure.

2b. Non-Teller Mediator requests System to identify Client, providing identification details*.

Notes:

*How the Client identifies him/herself depends on the kind of Mediator (Identification details required by Teller, ATM, or a Web Client)

 


BAT Use Cases | BAT Description