Google Search

Friday, April 1, 2011

ATM SYSTEM


ATM SYSTEM

1.Problem Statement

To develop an ATM System for ICICI Bank The System developed should contain
the following features
1.The Customer login into the system using Credit Card No or Debit Card no and Pin Number. The system checks for validation.
2.The System queries the customer for the type of account either S.B Account or Credit. After getting the type of account the system shows the amount left.
3.The System then queries the customer for required amount. The user enters the amount and gets the money.


2. LOGIN

2.1Brief Description

The use case describes how a User logs into the ATM System

2.2 Flow of Events

2.2.1 Basic Flow

This use case starts when the actor wishes to Login to the ATM System.
1.The System requests that the actor enter his/her name and password
2.The actor enters his/her name and password
3.The System validates the entered name and password and logs the actor into the System

2.2.2 Alternative Flows

Invalid Name/Password
If, in the Basic flow, the actor enters an invalid name and/or password, the system displays an error message. The actor choose to either return to the beginning of the Basic flow or cancel the login, at which point the use case ends.

2.3Special Requirements

None

2.4Pre-Conditions

None

2.5Post-Conditions

If the use case was successful, the actor is now logged into the system. If not, the
system State is unchanged.

2.6Extension Points

None

3.Maintain Customer Information

3.1Brief Description

This use case starts when administrator wants to add, delete or modify Customer
Information

3.2 Flow of Events

3.2.1 Basic Flow

This use case starts when the Administrator wishes to add, change, and/or delete Customer information in the system.
1. The system requests that the Administrator specify the function he/she would like to perform.
2. Once the Administrator provides the requested information, one of the sub flows is executed.
If the Administrator selected “Add a Customer”, the Add a Customer sub flow is executed.
If the Administrator selected “Update a Customer”, the Update a Customer sub flow is executed.
If the Administrator selected “Delete a Administrator”, the Delete a Customer sub flow is executed.

3.2.1.1 Add a Customer

The System requests that the Administrator enter the Customer information. This includes
-name
-Credit Card Number
- Pin Number
-Account Type
-Amount
- Address

3.2.1.2 Update a Customer

1.The System request that the Administrator enter the Credit Card Number.
2.The Administrator enters the Credit Card Number. The System retrieves and displays the Customer information.
3.The Administrator makes the desired changes to the Customer information. This includes any of the information specified in the Add a Customer sub flow.
4.Once the Administrator updates the necessary information, the system updates the Customer record.

 3.2.1.3 Delete a Customer

1.The System request that the Administrator enter the Credit Card Number
2.The Administrator enters the Credit Card Number. The System retrieves and displays the Customer information.
3.The System prompts the Administrator to confirm the deletion of the customer.
4.The Administrator verifies the deletion
5.The System deletes the Customer from the system.

3.3 Alternative Flow

If administrator gives invalid information i.e.trying to search for a person who does not have account then error occurs.

3.4 Special Requirements

None

3.5 Pre Condition

The Administrator must logged into the system

3.6 Post Condition

If the use case was successful, the administrator can do modification

3.7 Extension Point

None

4.Transaction

4.1Brief Description

This use case starts when the customer wants withdraw amount from Account.

4.2 Flow of Events

4.2.1 Basic Flow

1.The Actor enters into the system by entering Credit card no followed by Pin Number. The System validates and gives access to the system if credit card no and pin number is valid
2.The System shows the customer about the amount left in his account and queries the customer the amount he/she needed.
3.The Customer enters the amount and waits for money.
4.The System checks for the minimum balance and returns the money.

4.3Alternative Flow

If Customer wants to take amount more than minimum amount left in his Account error message will be displayed.

4.4Special Requirements

None

4.5 Pre-Condition

The Actor must logged into the System

4.6 Post-Condition

If the use case was successful, the customer will receive the amount.

0 comments:

Post a Comment