Text Notation & Scenario of mobile bank

The following image shows how these three basic elements work together to form a use case diagram.

Text Notation

Behind each Use Case is a series of actions to achieve the proper functionality, as well as alternate paths for instances where validation fails, or errors occur. These actions can be further defined in a Use Case description. Because this is not addressed in UML 1.4, there are no standards for Use Case descriptions. However, there are some common templates you can follow, and whole books on the subject writing of Use Case descriptions . 

Scenario

name: Registration

Actors: User, Admin

Flow Of Control: 

1)      Fill the registration form

2)      User will check the availability for ID

3)      Enroll registration details with ID and Password.

Scenario name: Login

Actors: User, Admin

Flow Of Control:

1)      User enter ID and Password

2)      Admin will check for authentication

3)      Generates the page with inbox or with error

Scenario name: Browse for Mobile information

Actors: Viewer

Flow of Control:

1)      User can check balance amount

2)      User can add friends.

3)      User can view profile.

4)      User can do online money transfer.

5)      User can view friends.

Scenario name: Get paid to the user

Actors: Viewer, Admin

Flow of Control:

1)      User checks the account to get paid

2)      User will select to pay if the amount.

Scenario name: Update customer account

Actors: Admin

Flow of Control:

1)      Admin will subtract from the customer

2)      Admin will add the amount to the customer account