Atm System.pdf 1n3c1o
This document was ed by and they confirmed that they have the permission to share it. If you are author or own the copyright of this book, please report to us by using this report form. Report 3i3n4
Overview 26281t
& View Atm System.pdf as PDF for free.
More details 6y5l6z
- Words: 1,673
- Pages: 19
Ex.No:
ATM SYSTEMS Date: 1. Problem analysis and project planning 1.1 Introduction Banking is one of the common and day to day attribute of life. Nowadays it is totally different from that existed a few years ago banking has become completely computerized new facilities such as credit cards, debit cards & ATM has been introduced. ATM is automatic teller machine which is basically used to withdraw money from an .
1.2 Objectives The objective of this software is similar to ATM software installed in ATM center. It should first validate the pin in the ATM card. Then the type of transaction is enquired and the information from the customer is validated. If it is a withdrawal the amount is asked. After the money is delivered the transaction just made is updated in the database where the customer’s information is stored.
1.3 Scope The scope of the project is to design an ATM system that will help in completely automatic banking this software is going to be designed for withdrawal and deposit of money and the transaction in the database where the customer’s information is stored.
1.4 Problem Statement ATM is another type of banking where the most frequently type of transaction made is withdrawal. A may withdraw as much as many amount as he wants until his holds a sum greater than his withdrawal amount. ATM is completely automated and there is no necessity of the ATM center being placed at the bank itself. It can be placed in the shopping malls, airports, railway stations etc. This ATM system can use any kind of interface. But it should be friendly and not confusing. Help manuals should be provided in case any customer has problem working with the software.
http://www.vidyarthiplus.com/
The system will retain information on the entire customer who has necessity rights to access the service. It will contain the balance amount in the , rate of interest, any special allowance for that customer and most of all pin number of the customer. The ATM system should be compatible with any kind of database such as MS-ACCESS, DB2, ORACLE, SQL, SERVER etc. the emphasis here is on consistency. Some customer could have availed some special offers on his ATM cards. So this must be taken care of and the appropriate data should be dealt with. The ATM should provide easy access to the data for the customer. It should also have a highly secure interface so that one can take money one behalf of others. So the security is one of the main aspects in ATM.
2. Problem statement(Use case)analysis 2.1 Identified use cases i. : Here the enters the card and the inputs his to enter into the main form. If the is incorrect, the system will display an error message.
ii. Transaction: This is the important part of the ATM system, where there are two types of transaction-withdrawal and deposit. While withdrawing the specifies the amount and may request for the printed output also.
iii. Maintaining Customer Information: Here the plays an important role, whose work is to add customer, delete customer , update customer , etc.
http://www.vidyarthiplus.com/
2.2 Identified Actors i : plays an important role. He is the system designer. All the updating works is done by him only like adding, deleting customer s.
ii Database: All the transaction works-withdrawal and deposit are updated in the database.
iii Customer: He is the external the ATM system for taking money and depositing money also.
2.3 Use Case Diagram
customer
bank
ask id() display error message()
transaction (withdrawal) maintain customer information
atm system
http://www.vidyarthiplus.com/
database
3. Design of ATM system 3.1 Design Documentation 1. 1.1 Brief description: This use case describes how the logs into the System.
1.2 Flow of events: 1.2.1 Basic flow: This use case starts with the actor wishes to to the ATM System. 1. The system requests the to enter the name and PIN. 2. The actor enters the name and PIN. 3. The system validates the name and the PIN and logs the into the system.
1.2.2 Alternative flow: 1. If the enters the wrong name and the PIN then the system displays an error message. 2. The actor can either return to the basic flow or cancel at which point use case ends.
1.3 Pre conditions: None
1.4 Post conditions: will perform corresponding transaction.
2. Transaction 2.1 Brief description: This describes the transaction that the is doing. http://www.vidyarthiplus.com/
2.2 Flow of events: 2.2.1 Basic flow: This use case starts after the has logged on to the system. 1. The system requests the to enter the type of transaction of either withdrawal or deposit and asks for customer information. 2. The actor enters the type of transaction and the customer information. 3. The system displays the corresponding transaction screen.
2.2.2 Alternative flow: If the customer enters any wrong information then the system displays an error message.
2.3 Pre Condition: The logs on to the system.
2.4 Post Condition: Based on the transaction he gets the transaction screen.
3. Maintain Information about Customer 3.1 Brief description: This describes how takes care of customer information.
3.2 Flow of events: 3.2.1 Basic flow: This use case starts after the has logged into the system. 1. The system asks the whether he wants to add or delete customer information. 2. The then enters the type of maintenance. http://www.vidyarthiplus.com/
3.2.2 Alternative flow: None
3.3 Pre Condition: The logs on to the system before this use case begin.
3.4 Post Condition: gets the corresponding maintenance screen according to his choice.
3.2.1.1 Adding Customer 3.2.1.1.1 Basic flow: 1. This use case starts when the has chosen to add customer’s information. 2. The system asks the to enter customer information. 3. The enters the customer information. 4. The system displays the updated information.
3.2.1.1.2 Alternative flow: If the enters any wrong information the system displays an error message.
3.2.1.2 Deleting Customer 3.2.1.2.1 Basic flow: 1. This use case starts when the has chosen to delete an existing customer from the system. 2. The system asks the to enter the customer information. 3. enters the corresponding information. 4. The system then displays updated results.
http://www.vidyarthiplus.com/
3.2.1.2.2 Alternative flow: If the has entered any wrong information then the system displays error message.
3.2.1.3 Updating an existing Customer 3.2.1.3.1 Basic flow: 1. This use case starts when the has chosen to update the customer’s information. 2. The system asks the to enter the customer information. 3. The enters the customer information. 4. The system displays the updated information.
3.2.1.3.2 Alternative flow: If the has entered any wrong information then the system displays error message.
http://www.vidyarthiplus.com/
SEQUENCE DIAGRAM 1. :
: customer
main window
window
controller
welcome screen
error message
1: run atm()
2: ask id() 3: provide id() 4: verification() 5: successful()
6: un successfull()
7: display error message()
http://www.vidyarthiplus.com/
2. Maintenance:
:
main window
maintanance window
1: ask type of maintanence
2: provide information
3: add
4: delete sequence diagram 5: updete customer information sequence diagram
sequence diagram
http://www.vidyarthiplus.com/
3. Adding customer:
:
add customer information
add customer
error message form
1: request customer information
2: provide customer information
3: verification 4: valid information
5: display error message 6: re-enter
http://www.vidyarthiplus.com/
: database
4. Deleting customer:
:
maintenance window
delete
error message
customer
1: ask customer details
2: provide information
3: valid details
4: remove form database
5: invalid details
6: display error message
5. Updating customer:
:
maintain window
update database
1: ask customer details
2: enter customer details
3: correct details
4: incorrect details
5: display error message
http://www.vidyarthiplus.com/
error message
updete database
6. Transaction:
: customer
transaction screen
update database
1: initiate transaction
2: provide information
3: correct
4: incorrect
5: display error message
http://www.vidyarthiplus.com/
error message
COLLABORATION DIAGRAM: 1. : main window
welcome screen
1: run atm() 5: successful() 3: provide id()
4: verification() window
controller
2: ask id() : customer 6: un successfull()
error message 7: display error message()
2. Maintenance: 2: provide information
1: ask type of maintanence :
main window 3: add 4: delete 5: updete customer information
maintanance window
http://www.vidyarthiplus.com/
3. Adding customer:
error message form
: 2: provide customer informat... 6: re-enter
5: display error message 1: request customer information 3: verification add customer information
add customer 4: valid information
: database
4. Deleting customer: 2: provide information maintenance window 1: ask customer details :
3: valid details delete customer
4: remove form database 6: display error message
updete database
error message 5: invalid details
http://www.vidyarthiplus.com/
5. Updating customer: 2: enter customer details maintain window 1: ask customer details : 3: correct details 4: incorrect details
5: display error message update database
error message
6. Transaction: 3: correct
1: initiate transaction transaction screen 2: provide information : customer
4: incorrect
error message 5: display error message
http://www.vidyarthiplus.com/
update database
STATE CHART DIAGRAM
initilisation
event(add record)[fullfill bank req]/rec is added to the datab... event(delete record)[bank balance less than request]/ record is dele...
add
delete
update
http://www.vidyarthiplus.com/
CLASS DIAGRAM 1.
customer
ask id() display error message()
main window
<< >> error message. window welcome message
contooller
http://www.vidyarthiplus.com/
2. Transaction:
customer
ask id() display error message()
<< >> transaction screen initiate transaction() provide information() +1
+1
+1
+1...*
+0...*
+1
<< >>
<< >>
generate report
<< >>
update database
error message.
COMPONENT DIAGRAM
<< >>
<< >> transacti on
<< >> maintain customer information
http://www.vidyarthiplus.com/
SOURCE CODE: 1. Option Explicit Public NewProperty As _window Public NewProperty2 As welcome_message Public NewProperty3 As customer Public NewProperty4 As error_message
2. Transaction Option Explicit Public As error_message Public NewProperty As customer Public Sub initiate_transaction() End Sub Public Sub provide_information() End Sub
http://www.vidyarthiplus.com/
ATM SYSTEMS Date: 1. Problem analysis and project planning 1.1 Introduction Banking is one of the common and day to day attribute of life. Nowadays it is totally different from that existed a few years ago banking has become completely computerized new facilities such as credit cards, debit cards & ATM has been introduced. ATM is automatic teller machine which is basically used to withdraw money from an .
1.2 Objectives The objective of this software is similar to ATM software installed in ATM center. It should first validate the pin in the ATM card. Then the type of transaction is enquired and the information from the customer is validated. If it is a withdrawal the amount is asked. After the money is delivered the transaction just made is updated in the database where the customer’s information is stored.
1.3 Scope The scope of the project is to design an ATM system that will help in completely automatic banking this software is going to be designed for withdrawal and deposit of money and the transaction in the database where the customer’s information is stored.
1.4 Problem Statement ATM is another type of banking where the most frequently type of transaction made is withdrawal. A may withdraw as much as many amount as he wants until his holds a sum greater than his withdrawal amount. ATM is completely automated and there is no necessity of the ATM center being placed at the bank itself. It can be placed in the shopping malls, airports, railway stations etc. This ATM system can use any kind of interface. But it should be friendly and not confusing. Help manuals should be provided in case any customer has problem working with the software.
http://www.vidyarthiplus.com/
The system will retain information on the entire customer who has necessity rights to access the service. It will contain the balance amount in the , rate of interest, any special allowance for that customer and most of all pin number of the customer. The ATM system should be compatible with any kind of database such as MS-ACCESS, DB2, ORACLE, SQL, SERVER etc. the emphasis here is on consistency. Some customer could have availed some special offers on his ATM cards. So this must be taken care of and the appropriate data should be dealt with. The ATM should provide easy access to the data for the customer. It should also have a highly secure interface so that one can take money one behalf of others. So the security is one of the main aspects in ATM.
2. Problem statement(Use case)analysis 2.1 Identified use cases i. : Here the enters the card and the inputs his to enter into the main form. If the is incorrect, the system will display an error message.
ii. Transaction: This is the important part of the ATM system, where there are two types of transaction-withdrawal and deposit. While withdrawing the specifies the amount and may request for the printed output also.
iii. Maintaining Customer Information: Here the plays an important role, whose work is to add customer, delete customer , update customer , etc.
http://www.vidyarthiplus.com/
2.2 Identified Actors i : plays an important role. He is the system designer. All the updating works is done by him only like adding, deleting customer s.
ii Database: All the transaction works-withdrawal and deposit are updated in the database.
iii Customer: He is the external the ATM system for taking money and depositing money also.
2.3 Use Case Diagram
customer
bank
ask id() display error message()
transaction (withdrawal) maintain customer information
atm system
http://www.vidyarthiplus.com/
database
3. Design of ATM system 3.1 Design Documentation 1. 1.1 Brief description: This use case describes how the logs into the System.
1.2 Flow of events: 1.2.1 Basic flow: This use case starts with the actor wishes to to the ATM System. 1. The system requests the to enter the name and PIN. 2. The actor enters the name and PIN. 3. The system validates the name and the PIN and logs the into the system.
1.2.2 Alternative flow: 1. If the enters the wrong name and the PIN then the system displays an error message. 2. The actor can either return to the basic flow or cancel at which point use case ends.
1.3 Pre conditions: None
1.4 Post conditions: will perform corresponding transaction.
2. Transaction 2.1 Brief description: This describes the transaction that the is doing. http://www.vidyarthiplus.com/
2.2 Flow of events: 2.2.1 Basic flow: This use case starts after the has logged on to the system. 1. The system requests the to enter the type of transaction of either withdrawal or deposit and asks for customer information. 2. The actor enters the type of transaction and the customer information. 3. The system displays the corresponding transaction screen.
2.2.2 Alternative flow: If the customer enters any wrong information then the system displays an error message.
2.3 Pre Condition: The logs on to the system.
2.4 Post Condition: Based on the transaction he gets the transaction screen.
3. Maintain Information about Customer 3.1 Brief description: This describes how takes care of customer information.
3.2 Flow of events: 3.2.1 Basic flow: This use case starts after the has logged into the system. 1. The system asks the whether he wants to add or delete customer information. 2. The then enters the type of maintenance. http://www.vidyarthiplus.com/
3.2.2 Alternative flow: None
3.3 Pre Condition: The logs on to the system before this use case begin.
3.4 Post Condition: gets the corresponding maintenance screen according to his choice.
3.2.1.1 Adding Customer 3.2.1.1.1 Basic flow: 1. This use case starts when the has chosen to add customer’s information. 2. The system asks the to enter customer information. 3. The enters the customer information. 4. The system displays the updated information.
3.2.1.1.2 Alternative flow: If the enters any wrong information the system displays an error message.
3.2.1.2 Deleting Customer 3.2.1.2.1 Basic flow: 1. This use case starts when the has chosen to delete an existing customer from the system. 2. The system asks the to enter the customer information. 3. enters the corresponding information. 4. The system then displays updated results.
http://www.vidyarthiplus.com/
3.2.1.2.2 Alternative flow: If the has entered any wrong information then the system displays error message.
3.2.1.3 Updating an existing Customer 3.2.1.3.1 Basic flow: 1. This use case starts when the has chosen to update the customer’s information. 2. The system asks the to enter the customer information. 3. The enters the customer information. 4. The system displays the updated information.
3.2.1.3.2 Alternative flow: If the has entered any wrong information then the system displays error message.
http://www.vidyarthiplus.com/
SEQUENCE DIAGRAM 1. :
: customer
main window
window
controller
welcome screen
error message
1: run atm()
2: ask id() 3: provide id() 4: verification() 5: successful()
6: un successfull()
7: display error message()
http://www.vidyarthiplus.com/
2. Maintenance:
:
main window
maintanance window
1: ask type of maintanence
2: provide information
3: add
4: delete sequence diagram 5: updete customer information sequence diagram
sequence diagram
http://www.vidyarthiplus.com/
3. Adding customer:
:
add customer information
add customer
error message form
1: request customer information
2: provide customer information
3: verification 4: valid information
5: display error message 6: re-enter
http://www.vidyarthiplus.com/
: database
4. Deleting customer:
:
maintenance window
delete
error message
customer
1: ask customer details
2: provide information
3: valid details
4: remove form database
5: invalid details
6: display error message
5. Updating customer:
:
maintain window
update database
1: ask customer details
2: enter customer details
3: correct details
4: incorrect details
5: display error message
http://www.vidyarthiplus.com/
error message
updete database
6. Transaction:
: customer
transaction screen
update database
1: initiate transaction
2: provide information
3: correct
4: incorrect
5: display error message
http://www.vidyarthiplus.com/
error message
COLLABORATION DIAGRAM: 1. : main window
welcome screen
1: run atm() 5: successful() 3: provide id()
4: verification() window
controller
2: ask id() : customer 6: un successfull()
error message 7: display error message()
2. Maintenance: 2: provide information
1: ask type of maintanence :
main window 3: add 4: delete 5: updete customer information
maintanance window
http://www.vidyarthiplus.com/
3. Adding customer:
error message form
: 2: provide customer informat... 6: re-enter
5: display error message 1: request customer information 3: verification add customer information
add customer 4: valid information
: database
4. Deleting customer: 2: provide information maintenance window 1: ask customer details :
3: valid details delete customer
4: remove form database 6: display error message
updete database
error message 5: invalid details
http://www.vidyarthiplus.com/
5. Updating customer: 2: enter customer details maintain window 1: ask customer details : 3: correct details 4: incorrect details
5: display error message update database
error message
6. Transaction: 3: correct
1: initiate transaction transaction screen 2: provide information : customer
4: incorrect
error message 5: display error message
http://www.vidyarthiplus.com/
update database
STATE CHART DIAGRAM
initilisation
event(add record)[fullfill bank req]/rec is added to the datab... event(delete record)[bank balance less than request]/ record is dele...
add
delete
update
http://www.vidyarthiplus.com/
CLASS DIAGRAM 1.
customer
ask id() display error message()
main window
<< >> error message. window welcome message
contooller
http://www.vidyarthiplus.com/
2. Transaction:
customer
ask id() display error message()
<< >> transaction screen initiate transaction() provide information() +1
+1
+1
+1...*
+0...*
+1
<< >>
<< >>
generate report
<< >>
update database
error message.
COMPONENT DIAGRAM
<< >>
<< >> transacti on
<< >> maintain customer information
http://www.vidyarthiplus.com/
SOURCE CODE: 1. Option Explicit Public NewProperty As _window Public NewProperty2 As welcome_message Public NewProperty3 As customer Public NewProperty4 As error_message
2. Transaction Option Explicit Public As error_message Public NewProperty As customer Public Sub initiate_transaction() End Sub Public Sub provide_information() End Sub
http://www.vidyarthiplus.com/
Related Documents 3h463d
Atm 2a6i3a
April 2021 0
Atm 2a6i3a
March 2021 0
Atm 2a6i3a
December 2022 0
Atm 2a6i3a
April 2020 26
Atm 2a6i3a
April 2020 37
Atm And Atm Ima 6u3dk
December 2019 53More Documents from "mani" 3k6c3j
Calibration Of Single Phase Energy Meter 102t6a
October 2019 72
Mrunal Ignou Sociology Ba Ma Without Registration 5c414e
November 2019 79
Auditorium Design.pdf 2m2o72
December 2019 89
Load Test On Dc Shunt Generator u352m
December 2019 76
Flare Recovery System 695l3h
November 2019 69