MTE project

Modulation and simulation

By – 2K19/SE/137 TARUN WILSON KERKETTA

Partner – 2K19/SE/127 SIDDHARTH YADAV

 Topic
Bank Customer simulation model

 Introduction
The BANK CUSTOMER SIMULATION SYSTEM undertaken as a project is
based on object-oriented programming. The main aim of the project is
to develop software for bank management system using the features
present in C++ that focus on objects rather than procedural
programming. This project has been developed to carry out the
processes easily and quickly, which is not possible with the manual
systems, which are overcome by this software.

The bank system is working for accounts information, service bias and
also has VIP status facility. The model simulates the efficiency of the
service provided by the bank counters, service type & quality and
fulfilling the customer’s demand. It shows live function of the bank with
no. of customers arriving, waiting and obtaining service.

This project is to prepare a software or application which could maintain

data & provide a user-friendly interface for retrieving customer related
details just in few seconds, with 100% accuracy. Software is completely
computerised, so it will not be a Time - consuming process. No paper
work required and can be implemented further.

The bank customer simulation system is based on Object oriented

programming, the program follows bottom up approach:
 Encapsulation is done via wrapping up of data and information under a
single class.
Abstraction is done via displaying only essential information and hiding
the details by the class functions present in the program, the user only
calls the appropriate functions and does not interfere with the objects
directly.

 Objectives
1. To allow only authorised user to access various function and
processed available in the system.
2. Locate any account wanted by the user.
3. Reduced clerical work as most of the work would be done by the
computer.
4. Provide greater speed and reduced time consumption.
5. Software will be user-friendly and easy to use so that even a
beginner could operate the program and thus maintain the status
of account.
6. This will reduce the manual workload and give information easily.
The software will maintain the list of accounts and customer
record.
7. The model gives shows the queuing system between the customer
and bank counters and how to minimize idle time of counter and
wait time of customers.

 Features of the bank model

The main objective of the system is to automate all the banking process
with improved performance an realize the vision of paperless banking.
Salient features of the proposed bank management system is given
below.

Using this bank management system any information can be easily

searched. User can view all the details of the customer.

Using this system user can create new customer account and maintain
its data efficiently and effectively. All records of account and customer
are stored in separate files. Which are maintained constantly update by
system.
 Manage large number of customer details with ease. Particular A/c
information can be modified A particular customer record can be
modified for one or more field’s customer name, address by providing
A/c number.

Create a statistical report to facilitate the finance department work.

Activities like updating, modification, deletion of records should be
easier. A customer record can be easily deleted by authorize user by
providing A/c number.

The proposed system provides faster data access, data entry and
retrieval.

The proposed system is more efficient, fast, reliable, user friendly. Over
and above the proposed system does not have any possibility of data
loss during processing.

 Brief
The bank works 5 days per week. It has 4 counters which are exclusively
for service information. The bank opens at 9:15a.m. and closes its
entrance door at 4:30 p.m., but still operates until all the customers in
the bank are served. Once a customer enters the bank, she/he takes a
number from the ticket machine based on the required service. The
bank offers
five different types of services including:
A: Deposit/ Withdraw/ Loan payment/Account info
B: VIP account
C: Customer Service Information
D: Service bias

Customers are categorized into three groups based on the type of

service chosen:
• Customer type 1: A
• Customer type 2: B,D
• Customer type 3: C
 The number taken represents the position of the customer in the waiting
line. The customers will be called according to their numbers based on
the queue discipline. Two queues have been considered in the system:
• Q1: the queue for getting a ticket number
• Q2: the queue in which the customers will be served
by one of the four counters

The customers arrive at the bank and join Q1 to take a number from the
ticket machine. Customer type 1 will be placed in Q2 and will wait to be
called based on the first-in first-served discipline by one of the four
counters. Customer type 2 has a priority over other customers and will
also be served by one of the four counters. However, the situation is
different for customer type 3. When a type 3 customer arrives in the
system and takes a number, she would have to wait in waiting area for
his turn; otherwise she/he will join Q2 and will be treated as a type 1
customer in the system. It should be noted that, in the real situation
there is a common waiting area in the bank where all types of customers
wait together to be served based on their numbers, that is, the
mentioned queues are all virtual.

 Assumptions of simulation model

The following assumptions were considered when the simulation model
was constructed:
 The customers remain in the system until they receive the required
service.

 The interval between the time a customer is called by a server and the
time when a service starts can be neglected.

 There is no interruption in service at the counters.

 Based on the operating conditions of the bank described in the previous

section, one of the working counters works after 4:30 p.m. until all
customers in the system are served; it is assumed that there is no
customer in the system by 7:15 p.m. (i.e. the run length of the system is
considered 600 minutes).
 Waiting time is the time when a customer takes a number until she/he is
called to be served.

 Breakdown time of 12 minutes and time between failures of 180

minutes have been considered for counter 2.

 Languages and tools used

 C++ with classes

 Hardware requirements

Minimum
 Computer with a 1.6 Ghz or faster processor
 384 MB of RAM or more
 2.2 GB of available hard disk space
 5400 RPM hard drive
Recommended
 2.4 Ghz or higher CPU
 1024 MB or more RAM
 7200 RPM or higher hard disk

 Software requirement
 Windows OS : 2000 or above
 C++ IDE compiler

 Proposed methodology
To review and improve the bank servers and operation systems, as
there are two important areas through which the productivity of
banking operations can be improved.
 The servers should not be less idle and their time should be
properly used.
  A customer waiting for a long period of time will result in
customer dissatisfaction.
 A speculation for the banks to monitor their service time given
to each customer and to minimise waiting time for the
customer and idle time taken by the counters to be more
improved and efficient.

 References
 Object- Oriented programming with C++ by E balagurusamy
 C++ by Sumita arora
 Simulation modelling and analysis Averil M Law