Certificate

S.V.P.M’S,

INSTITUTE OF TECHNOLOGY AND ENGG.MALEGAON BK. BARAMATI, DIST.PUNE.

(Affiliated to MSBTE MUMBAI)

2022-2023

This is to certify that the following group of students submitted Micro Project

Report Entitled “ATM Management System” Of Fourth Semester of

Diploma in INFORMATION TECHNOLOGY has Completed the Micro-Project

satisfactorily in course Software Engineering (Course code: 22413) for the

Academic Year 2022 to 2023 as prescribed in the curriculum . Submitted by

Name of Member1: Dinesh Anil Jagtap Enroll No:2100380100

Name of Member2: Viraj Suresh Khandekar Enroll No:2100380097

Name of Member3: Santosh Gorakh Jadhav Enroll No:2100380087

Prof. Dhame D.P. Prof. KADAM H.S. Prof. WABALE R.M.

Micro-Project Guide ( H.O.D.) Principal

 Shivnagar Vidya Prasarak Mandal’s
Institute of Technology and Engineering, Malegaon (Bk.)
Tal-Baramati; Dist-Pune PIN-413115. Telephone No. (02112)254214
__________________________________________________________________________

A
Report
On

MICROPROJECT
ACADEMIC YEAR 2022-23

TITLE OF PROJECT
ATM Management System
Guided By: Mr. Dhame D.P.

Program: SYIF Program Code : IF4I

Course: Software Engineering Course Code: 22413

Presented By:

Sr.No. Name of Student Sr.No./Roll No.

1. Dinesh Anil Jagtap 18

2. Viraj Suresh khandekar 15
3. Santosh Gorakh Jadhav 05

ANNEXURE II
EVALUATION SHEET FOR MICRO PROJECT
Academic Year: 2022-2023 Name of Faculty: Prof.D.P.Dhame
Course: Software Engineering Course Code:22413 Semester: IV
Title of the Project: .ATM Management System………………………………………..……….
CO’s addressed by the Micro Project.

a) …………………………………………………………………………………………………….…….………

b) …………………………………………………………………………………………………….…….……...

c) …………………………………………………………………………………………………….…….………

Major learning outcomes achieved by students by doing the project

a) Unit Outcomes (Cognitive Domain)
………………………………………………………………………………………………..
……………………………………………………………………………………………….
b) Practical Outcomes (in Psychomotor Domain)
………………………………………………………………………………………………
………………………………………………………………………………………………
c) Affective Domain Outcomes
……………………………………………………………………………………………...
………………………………………………………………………………………………
Comments/Suggestions about team work/leadership/inter-personal communication (if any)

……………………………………………………………………………………………...
Marks out of 6 for Marks out of 4 for
performance in performance in
Roll No./ Total out
Student Name group activity oral /
Sr.No of 10
(D5 Col. 8) presentation
(D5 Col. 9)
18 Dinesh Anil Jagtap
15 Santosh Gorakh Jadhav
05 Viraj Suresh Khandekar
………………………………………………………………………………………………

Name & Signature of faculty

Prof.D.P.Dhame

ATM MANAGEMENT SYSTEM

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 account.

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 register 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 user may withdraw as much as many amount as he wants
until his account 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 user friendly and
not confusing. Help manuals should be provided in case any customer has
problem working with the software.

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 account, 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. Login:
Here the user enters the card and the inputs his password to enter into the main
form. If the password 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 user specifies the
amount and may request for the printed output also.

iii. Maintaining Customer Information:

Here the administrator plays an important role, whose work is to add customer,
delete customer account, update customer account, etc.

2.2 Identified Actors

i Administrator:

Administrator plays an important role. He is the system designer. All the updating
works is done by him only like adding, deleting customer accounts.

ii Database:
All the transaction works-withdrawal and deposit are updated in the database.

iii Customer:
He is the external user the ATM system for taking money and depositing money
also.

2.3 Use Case Diagram

3. Design of ATM system

3.1 Design Documentation

1. Login

1.1 Brief description:

This use case describes how the user logs into the System.

1.2 Flow of events:

1.2.1 Basic flow:

This use case starts with the actor wishes to log in to the ATM System.
1. The system requests the user 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 user
into the system.

1.2.2 Alternative flow:

1. If the user 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 login at which point use
case ends.

1.3 Pre conditions:

None

1.4 Post conditions:

User will perform corresponding transaction.

3. Transaction

2.1 Brief description:

This describes the transaction that the user is doing.
2.2 Flow of events:

2.2.1 Basic flow:

This use case starts after the user has logged on to the system.
1. The system requests the user 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 user 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 administrator takes care of customer information.

3.2 Flow of events:

3.2.1 Basic flow:

This use case starts after the administrator has logged into the system.
1. The system asks the administrator whether he wants to add or delete customer
information.
2. The administrator then enters the type of maintenance.
3.2.2 Alternative flow:
None

3.3 Pre Condition:

The administrator logs on to the system before this use case begin.

3.4 Post Condition:

Administrator 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 administrator has chosen to add customer’s
information.
2. The system asks the administrator to enter customer information.
3. The administrator enters the customer information.
4. The system displays the updated information.

3.2.1.1.2 Alternative flow:

If the administrator 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 administrator has chosen to delete an existing
customer from the system.
2. The system asks the administrator to enter the customer information.
3. Administrator enters the corresponding user information.
4. The system then displays updated results.
3.2.1.2.2 Alternative flow:

If the administrator has entered any wrong information then the system displays
administrator error message.

3.2.1.3 Updating an existing Customer account

3.2.1.3.1 Basic flow:

1. This use case starts when the administrator has chosen to update the customer’s
information.
2. The system asks the administrator to enter the customer information.
3. The administrator enters the customer information.
4. The system displays the updated information.

3.2.1.3.2 Alternative flow:

If the administrator has entered any wrong information then the system displays
administrator error message.
SEQUENCE DIAGRAM

1. Login :
2. Maintenance:
3. Adding customer :
4. Deleting customer :

5. Updating customer :
6. Transaction :
COLLABORATION DIAGRAM :

1. Login:
2. Adding customer :

3. Deleting customer :
5. Updating customer :

6. Transaction :
STATE CHART DIAGRAM
CLASS DIAGRAM
COMPONENT DIAGRAM
 Conclusion

From this presentation, one can observe that an ATM system is associated
with the bank transactions of the consumers. Majorly, the ATM system is
utilized for the money associated transactions from the consumers.
Consumers make major use of ATM to withdraw money from their bank
account. It is a fast way to get money out of your account, especially
when on the go or during a trip .
 Reference

1. www.google.com
2. www.atmmanagementsystem.com
3. www.byjus.learn
4. www.unacademy.com