ATM

SYSTEM

[Link]: ATM SYSTEM

DATE:

ABSTRACT:

The expansion of ATM is Automated Teller Machine. ATM is used for money
transferring purpose. The client should have account in ATM system as well as in bank.

The process is as follows first insert ATM card into ATM machine.

After inserting the ATM card enters the pin number, card reader reads the pin
number, and machine asks their corresponding password(pin code) to the client.

The pin code must be within four digits. If the pin code is valid, the client can
perform their corresponding operations on his account, otherwise appropriate message will
be displayed to the client.

After that client entered the password and choose the options that are displayed in
the moniter. The options are enquiry,withdraw, transaction and exit.

Once the client chooses their required option, the details regarding that particular
options are entered. Client details will be displayed on the screen.

REQUIREMENT ANALYSIS:
 In this requirement analysis , the ATM system’s requirement specification is described in
detail . The clint details and account details are the basic requirements of this project.

There are three operations to be performed here,

[Link]
[Link] of money
3. Transaction history
ABOUT REQUISTE PRO:

Rational requiste pro stores the requirement documented under dynamically linked
[Link] user can communicate , collaborate and provide updates on the same project.

There can be several requiste project with one requiste pro database , each one associated
with a separate Rational [Link] there can be only one relational project associated with
each requiste pro project.

Analysing requirements with different views:

After crating the package and Requirement types the user can analyse the requirements in
a View.

[Link] MATRIX:

It provides the precise visualization of requirements , priorities ,cost,status and unique id

created for each of these.

[Link] MATRIX:

It is a two dimensional with rows and columns for requirement type [Link] is a
pictorial view of hierarchy in which the users analyse.

[Link] INTO:

This is an extension of traceability matrix where only the requirements that is traced to
their [Link] is viwed in the form of tree.

[Link] OUT OF:

This is another extension of traceability tree in which only the requirements that trace
their child are depicted.
ATTRIBUTE MATRIX - ATM SYSTEM

TRACEABILITY MATRIX - ATM SYSTEM

TRACEABILITY TREE ( TRACED INTO )

TRACEABILITY TREE ( TRACED OUT OF )
DESIGN:

Design has a great impact on the overall success of the software development project. A
large pay off is associated with creating a good design “ upfront “, before writing a single line of
[Link] this is true of all programming classes and objects underscore the approach even
more good design usually simplifies the implementation and maintenance of a project.

During design phase , we must evaluate the model into actual objects that can perform the
required task. Ther is a shift in emphasis from the application domain to [Link]
classes are identified during analysis provide as a framework for the design phase.

ABOUT RATIONAL ROSE:

Rational Rose enables visual modeling of architecture components and data using
Unified Modeling Language ( UML ). It is a graphical representation of a software [Link]
automatically implements the framework of our code in a popular language and [Link]
process of maintaining consistency between a software model and its implementation.

A Rose model can be associated with more than one relational project and multiple Rose
models can be associated to same rational project.

It shares visual model for business process software components , classes and objects.

The user can model the following five basic diagrams in logical view.

[Link] case Diagram

[Link] Diagram

[Link] Diagram

[Link] Diagram

[Link] Diagram

The user can also model the other diagrams

1. State chart diagram

2. Component diagram

3. Deployment diagram

ATM SYSTEM
USE CASE DIAGRAM
[Link] and drop the actors and use cases from the browser window into the diagram
window.

[Link] the use cases and actors.

PinValidation

User
CommenceTransaction CardInsertion

CardRemoval
ATM machine CurrencyFormat
Specification

CurrencyDispension

PrintTransactionDetails
DisplayBalance

TerminateTransaction
CLASS DIAGRAM

[Link] diagram gives an overview of a system by showing its classes and relationship
among them.

[Link] class diagram are [Link] display what they interact.

ATM m/c
Client
PinNo
PinNo
PinStatus
Amount W/d
AmountDispensed
CurrencyFormat
CurrentBalance
CurrentBalance
ValidatePin() * *
InsertCard()
SetPinStatus()
SpecifyPin()
GetCurrencyFormat()
SpecifyAmt()
GetAmountDispensed()
RetrieveCash()
GetCurrentBalance()
RemoveCard()
PrintTransactionDetails()
SEQUENCE DIAGRAM
[Link] a new package from the data base and name it as sequence diagram.

[Link] the tool bar select the required tools and make corresponding connections.

SEQUENCE DIAGRAM: ATM MACHINE

: ATM Pin Receive Balance Currency Currency Bill

machine Validation Amount Check Format Dispense Transactio...
1: Validate the pin

2: Get the amount to be withdrawn

3: Check Balance with amount

4: Receive the money split

5: Dispense the amount

6: Print the Transaction information

SEQUENCE DIAGRAM: USER

Card Insertion Pin Amount MoneySplit-up Cash Card Removal

Specification Specification Specification Collection
: User

1: Insert the code

2: Specify the pin

3: Specify the amount

4: Specify the split up

5: Collect the cash

6: Remove the card

COLLABORATION DIAGRAM
[Link] F5 on the sequence diagram then collaboration diagram is obtained.

[Link] the diagram.

ATM MACHINE
Pin
Validation
1: Validate the pin
Receive
2: Get the amount to be withdrawn Amount

3: Check Balance with amount

Balance
: ATM machine Check
4: Receive the money split

5: Dispense the amount Currency

Format

6: Print the Transaction information

Currency
Dispense
Bill
TransactionInfo

USER
Card
Insertion
1: Insert the code Pin
2: Specify the pin Specification

3: Specify the amount Amount

Specification
4: Specify the split up
: User
MoneySplit-up
5: Collect the cash
Specification

6: Remove the card

Cash
Collection
Card
Removal

ACTIVITY DIAGRAM
[Link] activity diagram describes the sequence of activities with support for both
conditional and parallel.
[Link] various controls are placed in the diagram window to create activity diagram.

Commence transaction after

card insertion

Get the pin

number

Is valid? Get the amount to be Check for

Yes withdrawn balance

Get the format for

currency dispension

Dispense the
currency

Update the
account

Print the transaction

details

Remove card and

terminate transaction

IMPLEMENTATION:
CODING:

FORM 1:

Private Sub Command1_Click()

[Link] = True

[Link] = True

[Link] = True

End Sub

Private Sub Command2_Click()

If [Link] = 1234 Then

[Link]

Else

MsgBox ("enter correct password")

End If

End Sub

Private Sub Timer1_Timer()

[Link] = Time

[Link] = Date

End Sub

FORM 2:

Private Sub Command2_Click()

[Link] = False

[Link] = False
MsgBox "YOUR BALANCE IS 15685.89"

End Sub

Private Sub Command3_Click()

[Link] = False

[Link] = False

[Link] = True

[Link] = True

End Sub

Private Sub Command4_Click()

[Link] = True

[Link] = True

[Link] = True

[Link] = False

[Link] = False

End Sub

Private Sub Command6_Click()

MsgBox "COLLECT UR CASH AND RECEIPT"

End

End Sub

Private Sub Timer1_Timer()

[Link] = Time

[Link] = Date

End Sub

OUTPUT:
CONCLUSION:

Thus the program is analysed, designed, implemented and tested for an ATM. This
project provides efficient money transition between the customer and the bank.

Further ATM also allows only the authenticated users. Thus the security level is
very high. It also ensures the user reliability.

As the project is implemented using object oriented concept, further changes can be
made easily and more utilities can be added.

Finally there is no doubt that as the modifications are updated immediately, this
project will exist in the future, with many more additional facilities.