01-03-2013, 11:34 AM
ATM SYSTEM
[attachment=52273]
Aim:
To create a system to perform Bank ATM transaction
Problem statement:
This system is build for the bank client and the manager.
The bank client must be able to deposit and withdraw amount from his/her accounts using the ATM machine. Each transaction must be recorded and the client must be able to review all transactions performed in his/her account. Recorded transactions must include the date, time, transaction type, amount and account balance after the transaction.
The bank manager must be able to view the ATM machine status that is the total balance of the ATM machine, today’s withdrawal, today’s balance and the limitations of the machine.
The bank client is provided by login verification. If it is valid he/she will access their account otherwise an appropriate message is displayed to the client.
USE-CASE name: Withdraw
The user tries to withdraw an amount from his or her checking account. The amount is less than or equal to the checking account’s balance, the transaction is performed and the available information is displayed. The system creates a record of the transaction and the display confirmation message is displayed to the client.
USE-CASE name: Mini statement
The bank user requests a history of transactions for a checking account. The system displays the transaction history for the checking account. The transaction history consists of amount, date, transaction type and balance of the particular account.
USE-CASE name: ATM machine status
The bank manager enters a username and password. If it is valid, the bank manager accesses the machine status. If it is invalid, an appropriate message is displayed to the user.
USE-CASE name: Deposit
The bank user requests the system to deposit money to an account. The user accesses the account for which a deposit is going to be made and enters the amount. The system creates a record of the transaction and an appropriate confirmation message (display confirmation) is displayed to the client. The transaction must include the date, type, amount and account balance after the transaction.
Class diagram
The class diagram, also referred to as object modeling is the main static analysis diagram. The main task of object modeling is to graphically show what each object will do in the problem domain. The problem domain describes the structure and the relationships among objects.
The ATM system class diagram consists of four classes:
1. User class
2. ATM machine status
3. Account
4. Transaction
Sequence diagram:
A sequence diagram represents the sequence and interactions of a given USE-CASE or scenario. Sequence diagrams can capture most of the information about the system. Most object to object interactions and operations are considered events and events include signals, inputs, decisions, interrupts, transitions and actions to or from users or external devices.
An event also is considered to be any action by an object that sends information. The event line represents a message sent from one object to another, in which the “form” object is requesting an operation be performed by the “to” object. The “to” object performs the operation using a method that the class contains.
It is also represented by the order in which things occur and how the objects in the system send message to one another.
The sequence diagram for each USE-CASE that exists when a user withdraws, deposits, needs information about ATM machine status and account are drowned.
[attachment=52273]
Aim:
To create a system to perform Bank ATM transaction
Problem statement:
This system is build for the bank client and the manager.
The bank client must be able to deposit and withdraw amount from his/her accounts using the ATM machine. Each transaction must be recorded and the client must be able to review all transactions performed in his/her account. Recorded transactions must include the date, time, transaction type, amount and account balance after the transaction.
The bank manager must be able to view the ATM machine status that is the total balance of the ATM machine, today’s withdrawal, today’s balance and the limitations of the machine.
The bank client is provided by login verification. If it is valid he/she will access their account otherwise an appropriate message is displayed to the client.
USE-CASE name: Withdraw
The user tries to withdraw an amount from his or her checking account. The amount is less than or equal to the checking account’s balance, the transaction is performed and the available information is displayed. The system creates a record of the transaction and the display confirmation message is displayed to the client.
USE-CASE name: Mini statement
The bank user requests a history of transactions for a checking account. The system displays the transaction history for the checking account. The transaction history consists of amount, date, transaction type and balance of the particular account.
USE-CASE name: ATM machine status
The bank manager enters a username and password. If it is valid, the bank manager accesses the machine status. If it is invalid, an appropriate message is displayed to the user.
USE-CASE name: Deposit
The bank user requests the system to deposit money to an account. The user accesses the account for which a deposit is going to be made and enters the amount. The system creates a record of the transaction and an appropriate confirmation message (display confirmation) is displayed to the client. The transaction must include the date, type, amount and account balance after the transaction.
Class diagram
The class diagram, also referred to as object modeling is the main static analysis diagram. The main task of object modeling is to graphically show what each object will do in the problem domain. The problem domain describes the structure and the relationships among objects.
The ATM system class diagram consists of four classes:
1. User class
2. ATM machine status
3. Account
4. Transaction
Sequence diagram:
A sequence diagram represents the sequence and interactions of a given USE-CASE or scenario. Sequence diagrams can capture most of the information about the system. Most object to object interactions and operations are considered events and events include signals, inputs, decisions, interrupts, transitions and actions to or from users or external devices.
An event also is considered to be any action by an object that sends information. The event line represents a message sent from one object to another, in which the “form” object is requesting an operation be performed by the “to” object. The “to” object performs the operation using a method that the class contains.
It is also represented by the order in which things occur and how the objects in the system send message to one another.
The sequence diagram for each USE-CASE that exists when a user withdraws, deposits, needs information about ATM machine status and account are drowned.