OBJECT ORIENTED

SOFTWARE ENGINEERING
ATM MANAGEMENT
SYSTEM

Submitted by:
Submitted to:
Vaibhav Sharma 2K17/EC/180 Mr Carlos
Wasim Jafar 2K17/EC/195
Tushant 2K17/EC/177
 Experiment 1
Aim: - Write a problem statement for ATM Management System.
Theory: -
A problem statement is a clear concise description of the issues that needs to be addressed
by a problem solving team. It is used to centre and focus the team at beginning, keep the
team on track during the effort, and it is used to validate that the effort delivered an
outcome that solves the problem statement.

Problem Statement: -
State Bank of India is planning to introduce Automated Teller Machine (ATM system for its
customers to provide convenient withdrawal service in everywhere, even if customer
doesn't come to a bank. A software is to be designed that will control ARM having a
magnetic stripe reader for reading an ATM card, a customer console keyboard and display
for interaction with the customer, a shot for deporting envelopes, a dispenser for cash) and
a printer for printing customer receipts. The bank provides computer to maintain its own
accounts and process transactions against them The ATM will service one customer at a
time. A customer will be required to insert an ATM card and enter a personal identification
number PIN-both of which would be sent to the bank for validation as part of each
transaction. The customer will then be able to perform one or more transactions. The card
will be retained in the machine until the customer indicates that he/she desires no further
transactions, at which point it will be returned.
The ATM will communicate each transaction to the bank and obtain verification that it was
allowed by the bank. If the bank determines that the customer's PIN is invalid, the customer
will be required to re-enter the PIN before a transaction can proceed. If the customer is
unable to successfully enter the PIN after three tries, the card will be permanently retained
by the machine, and the customer will have to contact the bank to get it back. If a
transaction fails for any reason other than an invalid PIN, the ATM will display an
explanation of the problem, and will then ask the customer whether he/she wants to do
another transaction
The ATM will also maintain an internal log of transactions facilitate resolving ambiguities
arising from a hardware failure in the middle of a transaction entries will be made in the log
when the ATM is started up and shut down, for each message sent to the Bank along with
the response back, if one is expected for the dispensing of cash, and for the receiving of an
envelope. Log entries may contain card numbers and amounts, but for security will never
contain a PIN.
To avail ATM facility, a customer is required to open/have an account in the bank and apply
for the ATM card. A customer can have one or more accounts and for each account, only
one ATM card will be provided. The bank also provides SMS updates for every transaction of
customer's account. To obtain SMS updates, customer is required to register his/her mobile
number against account in the bank.
The ATM will also inform the customer about the number of available bank notes of each
value so that customer can decide how much money he can withdraw. This will also reduce
the number of failed transactions due to unavailability of certain bank notes. As the number
of free ATM transactions is now limited, this feature would be really useful for customers
and banks, both.

Result: - The problem statement of the system assigned is properly understood and laid
out in front of the students. Also, the functionality of the system is described, which will
make the further steps in project easier.

Conclusion: - The problem statement is produced which contains all the consolidated
requirements of the software to be produced.
 Experiment 2
Aim: - Write the initial requirement document of ATM Management System.
Theory: -
Information Requirement Document (IRD) is the most basic paperwork produced during the
software development. It is written during the inception of the software development
process.
The IRD is used to consolidate and compile all the initial requirements of the user/customer.
The IRD also consists of other important information about the software, such as Title of
Project, Stakeholders Involved, Techniques used to capture requirements, Development
Team Members, and the Version of the Software being produced.
Development of IRD has many advantages, such as it specifies all the initial requirements for
the software and it also acts as an input to create Use-Case Diagram, which is also an
important document produced during software development.
STEPS TO BE FOLLOWED:
● The specified format of writing the IRD is looked up.
● The format of the IRD is written on the word file.
● The various sections of IRD are filled accordingly, such as Version, Stakeholders
Involved etc.
● The requirements are consolidated and are written under the ‘Consolidated
Requirements’ section.

RESULT:

INITIAL REQUIREMENT DOCUMENT

TITLE Course Management System

Students, faculty members, data

STAKEHOLDERS INVOLVED administrator.

TECHNIQUES USED IN CAPTURING REQUIREMENTS Interviews, Brainstorming, Use Cases.

Mayank Bajaj
DEVELOPERS
Navendu Gupta
DATE 24.08.2017
VERSION 1.0
CONSOLIDATED INITIAL REQUIREMENTS :
● There should be login id for each student, faculty member and data administrator.
● The student should be able to fill a registration form and choose courses at the beginning of the
semester.
● There should be a print facility for printing the registration form.
● There should be a feature to update phone no, address and email id.
● The students should be able to view and print their attendance.
● Students should be able to download and print their report cards.
● The faculty should be able to add and delete courses.
● The faculty should be able to view and mark attendance of every student.
● Faculty will be provided with the feature of entering marks of students, print report card, upload
course material, lectures and assignments.
● There should be a forum facility for discussion.

DISCUSSION: The Initial Requirement Document of the system has made a picture of the
system under consideration, which will help in smooth passage into the next segments of
the project.

CONCLUSION: The Initial Requirement Document is produced which contains all the
consolidated requirements of the software to be produced.