ATM Interface

Computer Programming Project Report

CSL-113

Semester BSCS

Fall 2019

Submitted to: Faiza Khan

Date: 24-12-2019

Page 1 of 6
Abstract:

We have designed sample software that runs on an ATM machine

throughout the world. Our software is basically the demonstration of
how the ATM interfaces runs. We have used different loops and
conditions to provide outputs on the screen as per the desire of user.
We used multiple conditional statements that would prevent any sort
of errors and wrong outputs.

Introduction:
Asynchronous Transfer Mode (ATM) is a network protocol designed to
facilitate the simultaneous handling of various types of traffic streams
(voice, data, and video) at very high speeds over the same physical
connection. By always using 53-byte cells, ATM simplifies the design of
hardware, enabling it to quickly determine the destination address of each
cell. This allows simple switching of network traffic at much higher speeds
than are easily accomplished using protocols with variable sizes of transfer
units, such as Frame Relay and Transmission Control Protocol/Internet
Protocol (TCP/IP).

It is an electronic device which is used by only bank customers to process

account transactions. The users access their account through special type
of plastic card that is encoded with user information on a magnetic strip.
The strip contains an identification code that is transmitted to the bank’s
central computer by modem. The users insert the card into ATMs to access
the account and process their account transactions. The automated teller
machine was invented by john shepherd-Barron in year of 1960.

Related Work:
Although ATM was designed to operate without the requirement of any
other networking protocol, other protocols are frequently segmented and
encapsulated across multiple, smaller ATM cells. This makes ATM a

Page 2 of 6
transport mechanism for preexisting technologies such as Frame Relay
and the TCP/IP family of protocols.
ATM relies on the concepts of virtual paths and virtual circuits. A virtual
path, represented by a specific virtual path identifier (VPI), establishes a
route between two devices in a network. Each VPI can contain multiple
virtual circuits, each represented by a virtual circuit identifier (VCI).
VPIs and VCIs are local to the router, which means that only the two
devices connected by the VCI or VPI need know the details of the
connection. In a typical ATM network, user data might traverse multiple
connections, using many different VPI and VCI connections. Each end
device, just like each device in the network, needs to know only the VCI
and VPI information for the path to the next device.

Detail Design and Solution:

 Project Functionality Description:

o How it will work( you can show this by flow diagram as well)

o What are the modules in your system (like admin, user etc.

describe all functionalities of them that what they can do)

o Hardware and software specifications

(example: Hardware requirement :

 OS:Window XP or above

 Hard Drive: Minimum 10 MB

 RAM: 256 MB

Page 3 of 6
Results:

Some screen shots of your working system will go here with little

description.

Testing and Validation:

1)PIN Code authentication:

The program will ask the user to enter the correct PIN code which is
“1500”. If the user enters the wrong PIN, the error message will be
displayed and the user will be given 4 more chances to enter the
correct PIN. If the user enters the wrong code for the 4 times in a row,
then the program will be terminated !

Page 4 of 6
2)

Lesson Learnt:

The Evaluation is very important. What lessons were learnt during the
course of the project? Evaluate

(with hindsight) both the product and the process of its production.
Don’t forget to sell your work! Tell

the reader what was good, what was achieved. Be honest about
limitations – these can be suggestions

for future work. (yaha aap limitations ki heading me discuss krege k ye

ye kam mera system abho nahi
Page 5 of 6
krskta h. future work me btaskte h k ye ye behtri improvement askti h
kaam me.)

References

https://www.juniper.net/documentation/en_US/junos/topics/concept/
interfaces-atm-interfaces-overview.html

Page 6 of 6