UML Diagram for Bank Management System – Part III

Continued from UML Diagram for Bank Management System – Part II

Flow of Events

8.2 Basic flow

1. Customer inserts card in ATM or Card reader

2. ATM or Card reader validates the card.

3. On success user can precede the transaction

8.3 Alternate Flow

If the card is invalid, ATM ejects the card or then it may be taken back from Card reader and gives a receipt indicating the error number.

8.4 Pre Conditions

The User must possess an ATM card or else a debit/credit card.

8.5 Post Conditions

None.

9. Invalid card – Use case specifications

9.1 Brief Description

The card inserted will be checked for validation. The card may not be inserted properly or it may be out of date or it can be an invalid for specific bank. In those situations it is requested for re-insert.

Flow of Events

9.2 Basic flow

1. Customer inserts card in ATM or swipes in Card reader.

2. ATM (Card reader) validates the card is invalid.

3. Customer must re-insert (swipe) the card again.

9.3 Alternate Flow

Even after reinserting the card, if the card is invalid ATM (Card reader) gives a receipt indicating that the card is invalid.

9.4 Pre Conditions

The User must possess an ATM card or a credit/debit card.

9.5 Post Conditions

None.

10. Pin validation – Use case specifications

10.1 Brief Description

After inserting the card and if it is checked for validation, the user is requested for pin. The pin is itself present on magnetic strip on back of card and it is checked with the entered one.

Flow of Events

10.2 Basic flow

1. Customer inserts card in ATM and enter his pin number.

2. ATM validates the pin.

3. On success user can precede the transaction

10.3 Alternate Flow

If the pin is invalid, ATM ejects the card and gives a receipt indicating

the error number.

10.4 Pre Conditions

The User must possess an ATM card.

10.5 Post Conditions

None.

11. Invalid Pin – Use case specifications

11.1 Brief Description

The pin entered may be wrong in that case transaction is cancelled. The customer is requested for re-inserting of card and re-entry of pin. The number of wrong trials may be limited according to bank’s specifications.

Flow of Events

11.2 Basic flow

1. Customer inserts card in ATM and enter his pin number.

2. ATM founds that pin is invalid.

3. The customer requested to reinsert card or reenter the pin.

4. In case the number of trials exceeded, ATM blocks the card temporarily.

11.3 Alternate Flow

If customer enters a correct pin transaction proceeds further.

11.4 Pre Conditions

The User must possess an ATM card.

11.5 Post Conditions

The user should not enter the pin number more than the number of trials.

Continued to UML Diagram for Bank Management System – Part IV

Subscribe to 4CAST

Enter your email address to subscribe to this blog and receive notifications of new posts by email.

Join 23 other subscribers