Atm Project Book

[ANTI THEFT PROTECTION FOR ATM USING IOT]
ANTI THEFT PROTECTION FOR ATM USING IOT

A Project report submitted in partial fulfillment
For the Award of degree of
BACHELOR OF TECHNOLOGY
IN
COMPUTER SCIENCE AND ENGINEERING

[2016-2020]
Submitted by
V.V Suma(16A51A05G6) S.Balaraju(16A51A05E1)
S.Vineetha(16A51A05E4) R.Sunil(16A51A05d3)
Under the esteemed Guidance of

Sri D.Sreenu Babu, M. Tech.
Assistant. Professor, Department of CSE
DEPARTMENT OF COMPUTER SCIENCE AND ENGINEERING
ADITYA INSTITUTE OF TECHNOLOGY AND MANAGEMENT

[Autonomous]
Approved by AICTE,Permanently A liated to JNTU,Kakinada,Accredited by NBA&NACC
K.Kotturu, Tekkali-532201,Srikakulam dist.(A.P )
[Department of C.S.E] Page 1

ADITYA INSTITUTE OF TECHNOLOGY AND MANAGEMENT

(Approved by AICTE, Permanently Aliated to JNTU, Kakinada)
(Accredited by NBA&NACC)
K.Kotturu, Tekkali-532201, Srikakulam dist.(A.P)
DEPARTMENT OF COMPUTER SCIENCE AND

ENGINEERING
CERTIFICATE
This is to Certify that the project work entitled as ANTI THEFT PROTECTION FOR ATM USING IOT is Carried
outbyV.V.Suma(16A51A05G6),S.Balaraju(16A51A05E1),S.Vineetha(16A51A05E4),R.Sunil(16A51A05D3)
Submitted in partial ful-fillment for the award of Bachelor of Technology in COMPUTER SCIENCE AND ENGI-
NEERING during the year 2016-2020 to the Jawaharlal Nehru Technological University is a record of bonafide work
carried out by them under my guidance and supervision.
Signature of Project Guide Signature of the Head of the Department
Sri D.Sreenu Babu, M. Tech, Dr. G.S.N Murthy, M. Tech, Ph. D,
Assistant. Professor, Head of the Department,
Department of CSE. Department of CSE.

ACKNOWLEDGEMENTS
We have great pleasure to acknowledge our sincere gratitude to our project guide Sri
D.Sreenu Babu, Assoc. Professor, Department of Computer Science and Engineering,
AITAM, Tekkali for his help and Guidance during the project. His valuable suggestions and
encouragement helped us a lot in carrying out this project work as well as in bringing this
project to this form.
We take this opportunity to express our sincere gratitude to our Director Prof.V. V.
Nageswara Rao
We take the privilege to thank our principal Dr.A.S.Srinivasa rao for his encouragement
and support.
We are also very much thankful to,Dr.G.S.N Murthy Head of Computer Science &
Engineering for his help and valuable support in completing the project.
We are also thankful to all staff members in the Department of Computer Science and
Engineering, for their feedback in the reviews and kind help throughout our project.
Last but not the least, we thank all our classmates for their encouragement and their help
in making this project a success. There are many others who have contributed towards the
project in some manner or the other whose names could not be mentioned.
Project Team

DECLARATION
We hereby declare that the project titled “ANTI THEFT PROTECTION FOR ATM SUSING
IOT” is a bonafide work done by us at AITAM, Tekkali Affiliated to JNTU Kakinada,
towards the partial fulfillment for the award of degree of Bachelor of Technology in
Computer Science and Engineering during the period 2016-2020.
Project Associates
V.V.Suma(16A51A05G6)
S.Balaraju(16A51A05E1),
S.Vineetha(16A51A05E4),
R.Sunil(16A51A05D3),

ABSTRACT
In this era of digitalization, everyone needs money without interaction with bank at
any time. So the ATM (Automotive Teller Machines) are installed everywhere in the
localities. As the number of ATMs increased, prevention of theft and security of
customer is the prime objective. At present, security systems are not highly secured
as they are provided with alarm system. This project deals with design and
implementation of ATM security system using pizeo electric sensor , GSM and GPS
module..
Keywords: GPS, vibration sensor, IOT, ATM theft, ATM Security.

Contents
ABSTRACT
LIST OF TABLES
LIST OF FIGURES
1 INTRODUCTION
1.1 Motivation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2 LITERATURE SURVEY
3 REQUIREMENTS AND TECHNICAL DESCRIPTION
4 SYSTEM DESIGN
5 IMPLEMENTATION
6 TESTING
7 CONCLUSION AND FUTURE SCOPE

Chapter 1
INTRODUCTION
We belong to the edge of digitized and smart world. People are getting smarter day
by day with the help of new technology, new innovations. Main reason behind the
up-gradation of new technologies is nothing but to overcome the existing problems.
Economic growth of world makes the life smarter and better as compared to previous
lifestyle.
The Internet of Things (IoT) is that the network of physical objects or "things"
embedded with electronics, software, sensors, and network property, that permits
these objects to gather and exchange information. IoT permits objects to be detected
and controlled remotely across existing network infrastructure, making opportunities
for additional direct integration between the physical world and computer-based
systems, and leading to improved efficiency, accuracy and economic profit. "Things,"
(ATMs) were 1st introduced in 1939. Nowadays, concerning three million units area
unit put in worldwide. Because the variety of ATM units increase, the machines area
unit susceptible to hacker attacks, fraud, robberies and security breaches. Within the
past, the ATM machines main purpose was to deliver cash of bank notes and to debit
a corresponding checking account. However, ATM machines have become additional
difficult, and that they serve varied functions, so changing into a high priority target
to robbers and hackers. Trendy ATM machines are enforced with high security
protection measures. They work beneath advanced systems and networks to perform
transactions. The information processed by ATMs area unit sometimes encrypted,
however hackers will use discreet hacking devices to hack accounts and withdraw the
account's balance. As an alternate, unskilled robbers threaten bank patrons with a
weapon to loot their withdrawn cash or account.
A smart step towards economy is the introduction of Automated teller machine

(ATM), for faster and easier money transfer. But a group of people do malpractices
over this ATM system to put people, organization or bank into a millions pounds of
loses. This system proposed in our project, maintain the entry of a single card holder
at a time with the help of auto sensor detection. Follows by the vibration detection
and GPS technology used in the ATM machine. If any types of unexpected events
occurred, nearest police station and the authority will be informed automatically.

Chapter 2
LITERATURE SURVEY
2.1 INTRODUCTION:
ATM center are now a day’s increasing large in number, which will be comfortable
for people to do easy transaction at any point of time. Though many procedures
which are indispensable to be followed inside a centre people fail to do this paves
way to crimes like ATM thefts, manhandling prevails inside the centre. There are
several DO’S and DONT’S inside an ATM center which are captioned outside the
center but people in their busy schedule even fail to have a notice at the boards. Small
faults can lead to unplayable consequences. As stated in an English proverb “LOOK
BEFORE YOU LEAP” precaution measures must be taken before you step in danger
zone. The classic scenario which falls in this category is smoking which will lead to
dangerous fire accidents causing damage both to life and property. So, smoking
inside ATM is strictly prohibited shows in.
It also depicts prohibition to the usage of cell phone, which makes use of
electromagnetic waves for communication. It is observed from basic physics that two
electromagnetic waves can undergo constructive or destructive interference which
deteriorate the performance of a machine. ATM is also an electronic machine uses
EM waves. For high degree of transaction and resolving EM interference usage of
cell phone is forbidden. The CCTV camera are provided at the door step to identify
the people entering the centre but then when the customer enter with the helmet there
is no use in providing CCTV When the crime occurs inside the centre, legal
evidences can’t be gathered and the criminal cannot be traced even if they are
arrested they will escape from the hands of law.

Existing system:
 The Idea of Designing and Implementation of Security Based ATM theft
project is born with the observation in our real life incidents happening around
us.
 Those project deals with image processing techniques
 They capture the live defined pre objects
Proposed System:
 To design and implement a framework for securing ATM's using IOT.
 To integrate the system with police for quick response and action.
 To evaluate the system with respect to consequences and possible
misconceptions from the two departments such as banking and police.
 To investigate inter-disciplinary techniques or mechanisms that contributes to
the fully functional security of ATM system.
 Formal step towards smart city.
Advantages
 Highly secured.
 Multi level robust data security system.
 This system can monitor remote area ATM machines from theft.
 Provides ATM anti-theft security.
 Geological location will always be traced of an ATM machine.

A.PERFORMANCE AND SCALABILITY: How fast does the system return

results? How much will this performance change with higher workloads?
B. PORTABILITY AND COMPATIBILITY. Which hardware, operating systems,
browsers, and their versions does the software run on Does it conflict with other
applications and processes within these environments Reliability, availability,
maintainability. How often does the system experience critical failures and how much
time is it available to users against downtimes.
C. SECURITY: How are the system and its data protected against attacks?
D.LOCALIZATION: Does the system match local specifics?
E. USABILITY: How easy is it for a customer to use the system?
2.2 FEASIBILITY STUDY:
A feasibility study is an assessment of the practicality of a proposed project or
system. A feasibility study aims to objectively and rationally uncover the strengths
and weaknesses of an existing business or proposed venture, opportunities and threats
present in the natural environment, the resources required to carry through, and
ultimately the prospects for success. In its simplest terms, the two criteria to judge
feasibility are cost required and value to be attained.
2.2.1 TECHNICAL FEASIBILITY:
Assessing technical feasibility includes evaluating the ability of computer hardware
and software to handle workloads adequately. Figure below shows the steps the
systems analyst takes in ascertaining hardware and software needs. First, all current
computer hardware the organization owns must be inventoried to discover what is on
hand and what is usable.
2.2.2 OPERATIONAL FEASIBILITY:
Operational feasibility is the measure of how well a proposed system solves the
problems, and takes advantage of the opportunities identified during scope definition
and how it satisfies the requirements identified in the requirements analysis phase of
system development.

2.2.3 ECONOMIC FEASIBILITY:

Economic feasibility is the cost and logistical outlook for a business project or
Endeavour. Prior to embarking on a new venture, most businesses conduct an
economic feasibility study, which is a study that analyze data to determine whether
the cost of the prospective new venture will ultimately be profitable to the company.
Economic feasibility is sometimes determined within an organization, while other
times companies hire an external company that specializes in conducting economic
feasibility studies for them.
2.2.4 SCHEDULE FEASIBILITY:
The process of assessing the degree to which the potential time frame and completion
dates for all major activities within a project meet organizational deadlines and
constraints for affecting change.

Chapter 3
REQUIREMENTS AND TECHNICAL DESCRIPTION
3.1 SOFTWARE REQUIREMENTS:
These software’s are required for this project
1. Arduino
2. windows Operating System
There are two types of requirement specifications
3.1.1 FUNCTIONAL REQUIREMENTS:
Software engineering and systems engineering, a functional requirement defines a
function of a system or its component, where a function is described as a
specification of behavior between outputs and inputs. Functional requirements may
involve calculations, technical details, data manipulation and processing, and other
specific functionality that define what a system is supposed to accomplish.
Behavioral requirements describe all the cases where the system uses the functional
requirements, these are captured in use cases. Functional requirements are supported
by non-functional requirements (also known as "quality requirements"), which
impose constraints on the design or implementation (such as performance
requirements, security, or reliability). Generally, functional requirements are
expressed in the form "system must do <requirement>," while non-functional
requirements take the form "system shall be <requirement>.
The plan for implementing functional requirements is detailed in the system design,
whereas non-functional requirements are detailed in the system architecture. As
defined in requirements engineering, functional requirements specify particular
results of a system. This should be contrasted with non-functional requirements,
which specify overall characteristics such as cost and reliability. Functional
requirements drive the application architecture of a system, while non-functional
requirements drive the technical architecture of a system.

3.1.2 NON-FUNCTIONAL REQUIREMENTS:

In systems engineering and requirements engineering, a non-functional requirement
(NFR) is a requirement that specifies criteria that can be used to judge the operation
of a system, rather than specific behaviors. The plan for implementing non-functional
requirements is detailed in the system architecture, because they are usually
architecturally significant requirements. Broadly, functional requirements define what
a system is supposed to do and non-functional requirements define how a system is
supposed to be. Functional requirements are usually in the form of "system shall do
<requirement>", an individual action or part of the system, perhaps explicitly in the
sense of a mathematical function, a black box description input, output, process and
control functional model or IPO Model. In contrast, non-functional requirements are
in the form of "system shall be <requirement>", an overall property of the system as a
whole or of a particular aspect and not a specific function. The system's overall
properties commonly mark the difference between whether the development project
has succeeded or failed. Non-functional requirements are often called "quality
attributes" of a system. Other terms for non-functional requirements are "qualities",
"quality goals", "quality of service requirements", "constraints", "non-behavioural
requirements", or "technical requirements". Informally these are sometimes called the
"ilities", from attributes like stability and portability. Qualities—that is non-
functional requirements—can be divided into two main categories: Execution
qualities, such as safety, security and usability, which are observable during operation
(at run time).Evolution qualities, such as testability, maintainability, extensibility and
scalability, which are embodied in the static structure of the system
3.2 HARDWARE REQUIREMENTS:

1. Arduino
2. GSM module
3. Pizeo electric sensor
4. GPS

3.3 ARDUINO
Arduino is an open-source hardware and software company, project and user
community that designs and manufactures single-board microcontrollers and
microcontroller kits for building digital devices. Its products are licensed under the
GNU Lesser General Public License (LGPL) or the GNU General Public License
(GPL),permitting the manufacture of Arduino boards and software distribution by
anyone. Arduino boards are available commercially in preassembled form or as do-it-
yourself (DIY) kits.
Arduino board designs use a variety of microprocessors and controllers. The boards
are equipped with sets of digital and analog input/output (I/O) pins that may be
interfaced to various expansion boards ('shields') or breadboards (For prototyping)
and other circuits. The boards feature serial communications interfaces, including
Universal Serial Bus (USB) on some models, which are also used for loading
programs from personal computers. The microcontrollers can be programmed using
C and C++ programming languages. In addition to using traditional compiler tool
chains, the Arduino project provides an integrated development environment (IDE)
based on the Processing language project.

Working of Arduino

3.3.1 GSM
GSM (Global System for Mobile Communications):
The GSM which is one of the representative wireless networks which has low-power,
low-cost and convenience to use .Global System for Mobile Communications
originally from Group Special Mobile is the most popular standard for mobile
telephony systems in the world. The GSM Association, its promoting industry trade
organization of mobile phone carriers and manufacturers, estimates that 80% of the
global mobile market uses the standard. GSM is used by over 1.5 billion people
across more than 212 countries and territories. A GSM modem is a specialized type
of modem which accepts a SIM card, and operates over a subscription to a mobile
operator, just like a mobile phone. From the mobile operator perspective, a GSM
modem looks just like a mobile phone. When a GSM modem is connected to a
computer, this allows the computer to use the GSM modem to communicate over the
mobile network. While these GSM modems are most frequently used to provide
mobile internet connectivity, many of them can also be used for sending and
receiving SMS and MMS messages. A GSM modem can be a dedicated modem
device with a serial, USB or Bluetooth connection, or it can be a mobile phone that
provides GSM modem capabilities.

Pin Description:
(i) Technical details:

Most GSM networks operate in the 900 MHz or 1800 MHz bands. Some countries in
the Americas (including the United States and Canada) use the 850 MHz and 1900
MHz bands because the 900 and 1800 MHz frequency bands were already allocated.
The rarer 400 and 450 MHz frequency bands are assigned in some countries, notably
Scandinavia, where these frequencies were In the 900 MHz band the uplink frequency
band is 890-915 MHz, and the downlink frequency band is 935-960 MHz this 25 MHz
bandwidth is subdivided into 124 carrier frequency channels, each spaced 200 kHz
apart.
(ii) Using GSM Modem in the ATM System:
In the system we will be using a GSM Modem to send and receive SMS. When the
robbery occurs, it will send send the message to corresponding banks and police
station.

Working of GPS
● Any instant of time, there are at least 4 GPS satellites in line of sight to a
receiver on the earth.
● Each of these GPS satellites sends information about its position and the
current time to the GPS receiver at fixed regular instants of time.
● This information is transmitted to the receiver in the form of signal which is
then intercepted by the receiver devices. These signals are radio signals that
travel with the speed of light.
● A GPS requires at least 3 satellites to calculate 2-D position(latitude and
longitude on a map).
Technical details:
Most GSM networks operate in the 900 MHz or 1800 MHz bands. Some countries in
the Americas (including the United States and Canada) use the 850 MHz and 1900
MHz bands because the 900 and 1800 MHz frequency bands were already allocated.
The rarer 400 and 450 MHz frequency bands are assigned in some countries, notably
Scandinavia, where these frequencies were In the 900 MHz band the uplink
frequency band is 890-915 MHz, and the downlink frequency band is 935-960 MHz
this 25 MHz bandwidth is subdivided into 124 carrier frequency channels, each
spaced 200 kHz apart.

Using GSM Modem in the ATM System:

In the system we will be using a GSM Modem to send and receive SMS. When the
robbery occurs, it will send the message to corresponding banks and near police
station (PS) according to the controller response
3.4 PIZEO Electric sensor
Piezoelectric sensors measure dynamic pressure. Dynamic pressure measurements
including turbulence, blast, ballistics, and engine combustion require sensors with
special capabilities
Sensor Working:
The commonly measured physical quantities by a piezoelectric sensor are
Acceleration and Pressure. In the pressure sensor, a thin membrane is placed on a
massive base to transfer the applied force to the piezoelectric element. Upon
application of pressure on this thin membrane, the piezoelectric material gets loaded
and starts generating electrical voltages. The produced voltage is proportional to the
amount of pressure applied. The ability of a piezoelectric material to convert a
mechanical stress into electrical charge is called a Piezoelectric Effect. The word
Piezoelectric derived from the Greek word ‘piezein’ which means to push, press and
squeeze. Piezoelectric effect is reversible effect means when we applied mechanical
stress to the piezoelectric material we get some electrical charge at output. Same as
when we feed electrical charge to the sensor it gets stretch or compresses.
Applications
Production and detection of sound
Generation of high voltage
Electronic Frequency generation
Microbalances
Ultra-fine focusing of optical assemblies

Chapter 4
SYSTEM DESIGN
4.1 METHODOLOGY
The Project ‘Anti theft security for ATM using IOT system using gsm and PIZEO
sensor is designed using IOT technology. According to this technology the
communication takes place between two devices PIZEO and micro controller. The
PIZEO is a sensor device which identifies the tilt produced by the atm machine due to
the irregular movement that occur during theft. This project makes best use of PIZEO
as a sensor device which identifies the tilt produced by the atm machine due to the
irregular movement that occur. The project basically consists of a PIZEO sensor
which identifies the tilt by the machine and activates the microcontroller to start the
following sequence in which shutting the door using stepper motor and sending sms
to vigilance system using gsm is involved
4.2 Block Diagram

UML Diagrams:
The Unified Modeling Language (UML) is a general-purpose, developmental,

modeling language in the field of software engineering that is intended to provide a
standard way to visualize the design of a system.
The creation of UML was originally motivated by the desire to standardize the
disparate notational systems and approaches to software design. It was developed by
Grady Booch, Ivar Jacobson and James Rumbaugh at Rational Software in 1994–
1995, with further development led by them through 1996.
In 1997, UML was adopted as a standard by the Object Management Group (OMG),
and has been managed by this organization ever since. In 2005, UML was also
published by the International Organization for Standardization (ISO) as an approved
ISO standard. Since then the standard has been periodically revised to cover the latest
revision of UML
In software engineering, a class diagram in the Unified Modeling Language (UML) is

a type of static structure diagram that describes the structure of a system by showing
the system's classes, their attributes, operations (or methods), and the relationships
among objects.
These diagrams are

1.Class Diagrams
2.Sequence Diagrams
3.Activity Diagrams
4.Collobaration Diagrams
5.USE Case Diagrams

CLASS Diagrams:
The class diagram is the main building block of object-oriented modeling. It is used
for general conceptual modeling of the structure of the application, and for detailed
modeling translating the models into programming code. Class diagrams can also be
used for data modeling. The classes in a class diagram represent both the main
elements, interactions in the application, and the classes to be programmed.
In the diagram, classes are represented with boxes that contain three compartments:
The top compartment contains the name of the class. It is printed in bold and
centered, and the first letter is capitalized.
The middle compartment contains the attributes of the class. They are left-aligned
and the first letter is lowercase. The bottom compartment contains the operations the
class can execute. They are also left-aligned and the first letter is lowercase.
A class with three compartments.

In the design of a system, a number of classes are
identified and grouped together in a class diagram that
helps to determine the static relations between them.
With detailed modeling, the classes of the conceptual design are often split into a
number of subclasses.
In order to further describe the behavior of systems, these class diagrams can be
complemented by a state diagram or UML state machine.
UML provides mechanisms to represent class members, such as attributes and

methods, and additional information about them like constructors.
Visibility
To specify the visibility of a class member (i.e. any attribute or method), these
notations must be placed before the member's name:
+ Public
- Private
# Protected
~ Package
Activity diagrams
These are graphical representations of workflows of stepwise activities and actions
with support for choice, iteration and concurrency. In the Unified Modeling
Language, activity diagrams are intended to model both computational and
organizational processes (i.e., workflows), as well as the data flows intersecting with
the related activities. Although activity diagrams primarily show the overall flow of
control, they can also include elements showing the flow of data between activities
through one or more data stores.
Activity diagrams are constructed from a limited number of shapes, connected with
arrows.
The most important shape types:
ellipses represent actions;
diamonds represent decisions;
bars represent the start (split) or end (join) of concurrent activities;
a black circle represents the start (initial node) of the workflow;
an encircled black circle represents the end (final node).
Arrows run from the start towards the end and represent the order in which activities
happen.
Activity diagrams can be regarded as a form of a structured flowchart combined with

a traditional data flow diagram. Typical flowchart techniques lack constructs for
expressing concurrency. However, the join and split symbols in activity diagrams
only resolve this for simple cases; the meaning of the model is not clear when they
are arbitrarily combined with decisions or loops.
While in UML 1.x, activity diagrams were a specialized form of state diagrams, in
UML 2.x, the activity diagrams were renormalized to be based on Petri net-like
semantics, increasing the scope of situations that can be modeled using activity
diagrams. These changes cause many UML 1.x activity diagrams to be interpreted
differently in UML 2

SEQUENCE Diagram:
A sequence diagram shows object interactions arranged in time sequence. It depicts
the objects and classes involved in the scenario and the sequence of messages
exchanged between the objects needed to carry out the functionality of the scenario.
Sequence diagrams are typically associated with use case realizations in the Logical
View of the system under development. Sequence diagrams are sometimes
called event diagrams or event scenarios.
A sequence diagram shows, as parallel vertical lines (lifelines), different processes or
objects that live simultaneously, and, as horizontal arrows, the messages exchanged
between them, in the order in which they occur. This allows the specification of
simple runtime scenarios in a graphical manner.
Diagram building blocks
If the lifeline is that of an object, it demonstrates a role. Leaving the instance name
blank can represent anonymous and unnamed instances.
Messages, written with horizontal arrows with the message name written above them,
display interaction. Solid arrow heads represent synchronous calls, open arrow heads
represent asynchronous messages, and dashed lines represent reply messages. [1] If a
caller sends a synchronous message, it must wait until the message is done, such as
invoking a subroutine. If a caller sends an asynchronous message, it can continue
processing and doesn’t have to wait for a response. Asynchronous calls are present in
multithreaded applications, event-driven applications and in message-oriented
middleware. Activation boxes, or method-call boxes, are opaque rectangles drawn on
top of lifelines to represent that processes are being performed in response to the
message (Execution Specifications in UML).
Objects calling methods on themselves use messages and add new activation boxes
on top of any others to indicate a further level of processing. If an object
is destroyed (removed from memory), an X is drawn on bottom of the lifeline, and
the dashed line ceases to be drawn below it. It should be the result of a message,
either from the object itself, or another.
A message sent from outside the diagram can be represented by a message
originating from a filled-in circle (found message in UML) or from a border of the
sequence diagram (gate in UML).
UML has introduced significant improvements to the capabilities of sequence
diagrams. Most of these improvements are based on the idea of interaction
fragments which represent smaller pieces of an enclosing interaction. Multiple
interaction fragments are combined to create a variety of combined fragments, which
are then used to model interactions that include parallelism, conditional branches,
optional interactions.

Collaboration Diagrams
Collaboration diagrams (known as Communication Diagram in UML 2.x) are used to

show how objects interact to perform the behavior of a particular use case, or a part
of a use case. Along with sequence diagrams, collaboration are used by designers to
define and clarify the roles of the objects that perform a particular flow of events of a
use case. They are the primary source of information used to determining class
responsibilities and interfaces
 Model collaborations between objects or roles that deliver the functionalities of

use cases and operations
 Model mechanisms within the architectural design of the system
 Capture interactions that show the messages passing between objects and roles
within the collaboration
 Model alternative scenarios within use cases or operations that involve the
collaboration of different objects and interactions
 Support the identification of objects (hence classes) that participate in use cases
 Each message in a collaboration diagram has a sequence number.
 The top-level message is numbered 1. Messages sent during the same call have
the same decimal prefix but suffixes of 1, 2, etc. according to when they occur.
 Each object in the collaboration is named and has its class specified
 Not all classes need to appear
 There may be more than one object of a class
 An object’s class can be unspecified. Normally you create a collaboration

diagram with objects first and specify their classes later.
 The objects can be unnamed, but you should name them if you want to
discriminate different objects of the same class.

Actors
Normally an actor instance occurs in the collaboration diagram, as the invoker of the
interaction. If you have several actor instances in the same diagram, try keeping in
the periphery of the diagram.
Each Actor is named and has a role

One actor will be the initiator of the use case
Links
Links connect objects and actors and are instances of associations and each link
corresponds to an association in the class diagram
Links are defined as follows:

A link is a relationship among objects across which messages can be sent. In
collaboration diagrams, a link is shown as a solid line between two objects.
An object interacts with, or navigates to, other objects through its links to these
objects.
A link can be an instance of an association, or it can be anonymous, meaning that its
association is unspecified.
Message flows are attached to links, see Messages.
Messages
A message is a communication between objects that conveys information with the
expectation that activity will ensue. In collaboration diagrams, a message is shown as
a labeled arrow placed near a link.
The message is directed from sender to receiver

The receiver must understand the message
The association must be navigable in that direction

USE Case Diagram:

A use case diagram at its simplest is a representation of a user's interaction with the
system that shows the relationship between the user and the different use cases in
which the user is involved. A use case diagram can identify the different types of
users of a system and the different use cases and will often be accompanied by other
types of diagrams as well.
The use cases are represented by either circles or ellipses.

While a use case itself might drill into a lot of detail about every possibility, a use-
case diagram can help provide a higher-level view of the system. It has been said
before that "Use case diagrams are the blueprints for your system". They provide the
simplified and graphical representation of what the system must actually do.
Due to their simplistic nature, use case diagrams can be a good communication tool
for stakeholders. The drawings attempt to mimic the real world and provide a view
for the stakeholder to understand how the system is going to be designed. Siau and
Lee conducted research to determine if there was a valid situation for use case
diagrams at all or if they were unnecessary.
What was found was that the use case diagrams conveyed the intent of the system in
a more simplified manner to stakeholders and that they were "interpreted more
completely than class diagrams".

4.3 System Flowchart

Start
Sense the ATM

Vibration
Vibration Voltage
>
YES Threshold Voltage
>
YES
GSM Module
Asks for Security Pin
Alert to Server Match

NO
Allows For Transaction
Stop

4.4 Use case

4.5 Sequence Diagram

Chapter 5
IMPLEMENTATION
Programming language and Coding tools
Arduino programs are written in the Arduino Integrated Development Environment

(IDE). Arduino IDE is a special software running on your system that allows you to
write sketches (synonym for program in Arduino language) for different Arduino
boards. The Arduino programming language is based on a very simple hardware
programming language called processing, which is similar to the C language. After
the sketch is written in the Arduino IDE, it should be uploaded on the Arduino board
for execution.
The first step in programming the Arduino board is downloading and installing the
Arduino IDE. The open source Arduino IDE runs on Windows, Mac OS X, and
Linux. Download the Arduino software (depending on your OS) from the official
website and follow the instructions to install.
The structure of Arduino program is pretty simple. Arduino programs have a

minimum of 2 blocks,
Preparation & Execution
Each block has a set of statements enclosed in curly braces:
#include<Software serial.h>
Pin define
void setup( )
{
statements-1;
.
.
.
statement-n;
}
void loop ( )
{
statement-1;
.
.
.
statement-n;
}

Here, setup ( ) is the preparation block and loop ( ) is an execution block.

The setup function is the first to execute when the program is executed, and this
function is called only once. The setup function is used to initialize the pin modes and
start serial communication. This function has to be included even if there are no
statements to execute.
void setup ( )
{
pinMode (pin-number, OUTPUT); // set the ‘pin-number’ as output
pinMode (pin-number, INPUT); // set the ‘pin-number’ as output
}
After the setup ( ) function is executed, the execution block runs next. The execution
block hosts statements like reading inputs, triggering outputs, checking conditions
etc..
In the above example loop ( ) function is a part of execution block. As the name
suggests, the loop( )
function executes the set of statements (enclosed in curly braces) repeatedly.
Void loop ( )
{
digitalWrite (pin-number,HIGH); // turns ON the component connected to ‘pin-
number’
delay (1000); // wait for 1 sec
digitalWrite (pin-number, LOW); // turns OFF the component connected to ‘pin-
number’
delay (1000); //wait for 1sec
}
Note: Arduino always measures the time duration in millisecond. Therefore,

whenever you mention the delay, keep it in milli seconds.
Now, let’s take a giant leap and do some experiments with Arduino
Blinking the LED
Fade-in and fade-out the LED

Coding
#include <SoftwareSerial.h>
static const int RXPin = 7, TXPin = 8;
SoftwareSerial gprsSerial(RXPin, TXPin);
int count=0;
int c;
float lati=18.565708;
float lon=84.196350;
void setup()
{
pinMode(A0,INPUT);
Serial.begin(9600);
gprsSerial.begin(9600);
Serial.println("1.0.2");
}
void loop()
{
int c=analogRead(A0);
Serial.println(c);
delay(1000);
if(c>1000){
Serial.println("Location found");
gprsSerial.println("AT+CMGF=1"); //Sets the GSM Module in Text Mode
delay(2000); // Delay of 1000 milli seconds or 1 second
gprsSerial.println("AT+CMGS=\"+919441085368\"\r"); // Replace x with mobile

number
delay(2000);
gprsSerial.print("Intruder Alert!:");
gprsSerial.print("www.google.com.ph/maps/place/");
gprsSerial.print(lati,6);
gprsSerial.print(",");
gprsSerial.print(lon,6);
gprsSerial.print("\r");
// The SMS text you want to send
delay(300);

gprsSerial.println((char)26);// ASCII code of CTRL+Z
delay(3000);
//SendGPRS();
}
}
void RecieveMessage()
{
gprsSerial.println("AT+CiNMI=2,2,0,0,0"); // AT Command to receive a live SMS
delay(1000);
}

Output: Receiving an Alert text SMS to registered mobile number with live google map location
with GSM Technology.

Navigated to Google maps

Theft Alert

TESTING
Software testing methodologies are the various strategies or approaches used to test
an application to ensure it behaves and looks as expected. These encompass
everything from front to back-end testing, including unit and system testing
Functional vs. Non-functional Testing
The goal of utilizing numerous testing methodologies in your development process is

to make sure your software can successfully operate in multiple environments and
across different platforms. These can typically be broken down between functional
and non-functional testing. Functional testing involves testing the application against
the business requirements. It incorporates all test types designed to guarantee each
part of a piece of software behaves as expected by using uses cases provided by the
design team or business analyst. These testing methods are usually conducted in order
and include:
 Unit testing
 Integration testing
 System testing
 Acceptance testing
Non-functional testing methods incorporate all test types focused on the operational
aspects of a piece of software. These include:
 Performance testing
 Security testing
 Usability testing
 Compatibility testing
The key to releasing high quality software that can be easily adopted by your end
users is to build a robust testing framework that implements both functional and non-
functional software testing methodologies.

Unit Testing
Unit testing is the first level of testing and is often performed by the developers
themselves. It is the process of ensuring individual components of a piece of software
at the code level are functional and work as they were designed to. Developers in a
test-driven environment will typically write and run the tests prior to the software or
feature being passed over to the test team. Unit testing can be conducted manually,
but automating the process will speed up delivery cycles and expand test coverage.
Unit testing will also make debugging easier because finding issues earlier means
they take less time to fix than if they were discovered later in the testing process.
TestLeft is a tool that allows advanced testers and developers to shift left with the
fastest test automation tool embedded in any IDE.
Integration Testing
After each unit is thoroughly tested, it is integrated with other units to create modules
or components that are designed to perform specific tasks or activities. These are then
tested as group through integration testing to ensure whole segments of an application
behave as expected (i.e, the interactions between units are seamless). These tests are
often framed by user scenarios, such as logging into an application or opening files.
Integrated tests can be conducted by either developers or independent testers and are
usually comprised of a combination of automated functional and manual tests.
System Testing
System testing is a black box testing method used to evaluate the completed and
integrated system, as a whole, to ensure it meets specified requirements. The
functionality of the software is tested from end-to-end and is typically conducted by a
separate testing team than the development team before the product is pushed into
production.
Acceptance Testing
Acceptance testing is the last phase of functional testing and is used to assess whether
or not the final piece of software is ready for delivery. It involves ensuring that the
product is in compliance with all of the original business criteria and that it meets the
end user’s needs. This requires the product be tested both internally and externally,
meaning you’ll need to get it into the hands of your end users for beta testing along
with those of your QA team. Beta testing is key to getting real feedback from
potential customers and can address any final usability concerns.

Performance Testing
Performance testing is a non-functional testing technique used to determine how an

application will behave under various conditions. The goal is to test its
responsiveness and stability in real user situations. Performance testing can be broken
down into four types:
Load testing is the process of putting increasing amounts of simulated demand on

your software, application, or website to verify whether or not it can handle what it’s
designed to handle.
 Stress testing takes this a step further and is used to gauge how your software
will respond at or beyond its peak load. The goal of stress testing is to overload the
application on purpose until it breaks by applying both realistic and unrealistic
load scenarios. With stress testing, you’ll be able to find the failure point of your
piece of software.
 Endurance testing, also known as soak testing, is used to analyze the behavior

of an application under a specific amount of simulated load over longer amounts
of time. The goal is to understand how your system will behave under sustained
use, making it a longer process than load or stress testing (which are designed to
end after a few hours). A critical piece of endurance testing is that it helps uncover
memory leaks.
 Spike testing is a type of load test used to determine how your software will
respond to substantially larger bursts of concurrent user or system activity over
varying amounts of time. Ideally, this will help you understand what will happen
when the load is suddenly and drastically increased.

Security Testing
With the rise of cloud-based testing platforms and cyber attacks, there is a growing
concern and need for the security of data being used and stored in software. Security
testing is a non-functional software testing technique used to determine if the
information and data in a system is protected. The goal is to purposefully find
loopholes and security risks in the system that could result in unauthorized access to
or the loss of information by probing the application for weaknesses. There are
multiple types of this testing method, each of which aimed at verifying six basic
principles of security:
1. Integrity
2. Confidentiality
3. Authentication
4. Authorization
5. Availability
6. Non-repudiation
Usability Testing
Usability testing is a testing method that measures an application’s ease-of-use from

the end-user perspective and is often performed during the system or acceptance
testing stages. The goal is to determine whether or not the visible design and
aesthetics of an application meet the intended workflow for various processes, such
as logging into an application. Usability testing is a great way for teams to review
separate functions, or the system as a whole, is intuitive to use.
Compatibility Testing
Compatibility testing is used to gauge how an application or piece of software will

work in different environments. It is used to check that your product is compatible
with multiple operating systems, platforms, browsers, or resolution configurations.
The goal is to ensure that your software’s functionality is consistently supported
across any environment you expect your end users to be using.
Testing With Test Complete
Test Complete is our robust automated GUI testing tool that excels in compatibility
and integration testing. It helps QA teams create and run tests across desktop, mobile,
and web applications – enabling testing professionals to speed up delivery cycles and
improve software quality. Test complete comes with built-in support for various test
environments, integrations to performance testing tools, as well as support for
developer friendly SCMs, allowing you to seamlessness integrate it into your
development process. Using Test Complete will enable you to build a robust testing
framework that utilizes the broad spectrum of available software testing
methodologies.

Chapter-7
CONCLUSION AND FUTURE SCOPE
The proposed system ensures to develop advanced ATM anti theft system. Proposed
system is distinctive in many ways from existing ATM intrusion and theft control
systems. It is reliable, inexpensive and appropriate design.
As we all know, these days most of the ATM has been attacked by the robberies.
Also gradual increases the theft of ATM after the year by year. This project
demonstrates how an automation of “ATM THEFT SECURITY SYSTEM USING
IOT” prevention from robbery (or) thief can be implemented using GSM Technology
,vibrating sensor, arduino micro processor At-Mega 328-p can be implemented in
ATM Machines center. By implementing this project we can catch thief and robberies
in ATM itself and also we can save our precious time. In future the system can be
implemented using ARM CORTEX A8.Beagle bone as well as updates to processors
with high frequencies. We can provide more Security to data by using encryption
,decryption techniques.

Bibliography
[1]. Sakr, Sharif. "ARM co-founder John Biggs". Engadget. Retrieved December
23, 2011. "[...] the ARM7-TDMI was licensed by Texas Instruments and designed
into the Nokia 6110, which was the first ARM-powered GSM phone."
[2]. electricmotors.machinedesign.com
[3]. Kim, Bo-Ra, “Domestic ATM status and meanings”, Payment and Settlement,
and IT, Vol. 44, pp. 76,2011.
[4]. Karki, James (September 2000). "Signal Conditioning Piezoelectric Sensors"
(PDF). Texas Instruments Retrieved 2007-12-02.
[5]. "GSM UMTS 3GPP Numbering Cross Reference". ETSI. Retrieved 30
December 2009.
[6]. "Gsmd – Openmoko". Wiki.openmoko.org. 8 February 2010. Retrieved 22
April 2010.
[7]. "The Hacker's Choice Wiki". Retrieved 30 August 2010.
[8]. Liptak, Bela G. (2005). Instrument Engineers' Handbook: Process Control and
Optimization. CRC Press.p. 2464. ISBN 978-0-8493-1081-2.
[9]. Herman, Stephen. Industrial Motor Control. 6th ed. Delmar, Cengage
Learning, 2010.
Page 251.
[10]. Laughton M.A. and Warne D.F., Editors. Electrical engineer's reference
book. 16th ed. Newnes, 2003
[11]. William H. Yeadon, Alan W. Yeadon. Handbook of small electric motors.
McGraw-Hill Professional,2001
[12]. "BC548 − NPN Epitaxial Silicon Transistor". Retrieved 28 June 2013.
[13]. World's Transistor Comparison Tables, Tech/ECA, 1993, ISBN 981-214-
444-7


Atm Project Book

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Atm Project Book

Uploaded by

Copyright:

Available Formats

[ANTI THEFT PROTECTION FOR ATM USING IOT]

ANTI THEFT PROTECTION FOR ATM USING IOT

COMPUTER SCIENCE AND ENGINEERING

Under the esteemed Guidance of

DEPARTMENT OF COMPUTER SCIENCE AND ENGINEERING

ADITYA INSTITUTE OF TECHNOLOGY AND MANAGEMENT

Approved by AICTE,Permanently A liated to JNTU,Kakinada,Accredited by NBA&NACC

K.Kotturu, Tekkali-532201,Srikakulam dist.(A.P )

[Department of C.S.E] Page 1

ADITYA INSTITUTE OF TECHNOLOGY AND MANAGEMENT

DEPARTMENT OF COMPUTER SCIENCE AND

Signature of Project Guide Signature of the Head of the Department

Sri D.Sreenu Babu, M. Tech, Dr. G.S.N Murthy, M. Tech, Ph. D,

Assistant. Professor, Head of the Department,

Department of CSE. Department of CSE.

[Department of C.S.E] Page 2

D.Sreenu Babu, Assoc. Professor, Department of Computer Science and Engineering,

project to this form.

[Department of C.S.E] Page 3

IOT” is a bonafide work done by us at AITAM, Tekkali Affiliated to JNTU Kakinada,

Computer Science and Engineering during the period 2016-2020.

[Department of C.S.E] Page 4

[Department of C.S.E] Page 5

3 REQUIREMENTS AND TECHNICAL DESCRIPTION

7 CONCLUSION AND FUTURE SCOPE

[Department of C.S.E] Page 6

A smart step towards economy is the introduction of Automated teller machine

[Department of C.S.E] Page 7

[Department of C.S.E] Page 8

[Department of C.S.E] Page 9

A.PERFORMANCE AND SCALABILITY: How fast does the system return

[Department of C.S.E] Page 10

2.2.3 ECONOMIC FEASIBILITY:

[Department of C.S.E] Page 11

[Department of C.S.E] Page 12

3.1.2 NON-FUNCTIONAL REQUIREMENTS:

3.2 HARDWARE REQUIREMENTS:

[Department of C.S.E] Page 13

[Department of C.S.E] Page 14

[Department of C.S.E] Page 15

[Department of C.S.E] Page 16

(i) Technical details:

[Department of C.S.E] Page 17

[Department of C.S.E] Page 18

Using GSM Modem in the ATM System:

[Department of C.S.E] Page 19

[Department of C.S.E] Page 20

The Unified Modeling Language (UML) is a general-purpose, developmental,

In software engineering, a class diagram in the Unified Modeling Language (UML) is

These diagrams are

[Department of C.S.E] Page 21

A class with three compartments.

UML provides mechanisms to represent class members, such as attributes and

Activity diagrams can be regarded as a form of a structured flowchart combined with

[Department of C.S.E] Page 23

[Department of C.S.E] Page 24

Collaboration diagrams (known as Communication Diagram in UML 2.x) are used to

 Model collaborations between objects or roles that deliver the functionalities of

 Model mechanisms within the architectural design of the system

 Each message in a collaboration diagram has a sequence number.

 Not all classes need to appear

 There may be more than one object of a class