BANKING

INFO SYSTEM

SYNOPSIS
SUBMITTED TO- Mr. ROHIT KHOKHER
GROUP MEMBERS ;
PRATIK GUPTA ( TEAM LEADER )
POOJA SINGH
PRAVIN KUMAR
POOJA AWASTHI
PRADEEP BOHRA
PUNEET RAJAN
PRATIMA CHAUHAN
VEMPATI ANVESH
 Statement of
purpose
qWhat is this project all about?
qHow we are going to do this
project?
What is this project all about?
§ Bank is the place where customers feel the senseof safety
for their property. In the bank, customers deposit and
withdrawtheir money.

§ Nowto keep thebelief andtrust of customers, there is

the positive need for management of the bank. Smooth
and efficient management affects the satisfaction of the
customers and staff members, indirectly.
§ So, we are trying our best to develop a softwareprogram
for the Bank Management Systemwhere all the tasks to
manage the bank systemare performed easily and
efficiently.

§ It manages all the transactions like

ünewaccount entry
üdeposit as well as withdrawentry
ütransaction of money for various processes
üloan entry
ümanaging bills cashor cheque,
How we are going to do this
project?
§ This thefirst time wearemaking the project. For this we
have divided our work as per ability and interest of the
individual so that everyone makes use of his strength to
build a flawless program.

§ This project is to be made using Clanguage. Wewouldbe

using all the feature of C language learnt by as so far
including the loop statements, decision control
statement, arrays, functions, structures, file handling
etc.
1.Initial phase - it wouldrequire us to analyze the requirement of
the project

2.Then in this phasewewouldcollect information regarding

the various banking info system. For this purpose we
would ask each teammembers to search and collect as
much information as he/she can.

3.Nowwe will divide thework on the basis of the information

collected and interest of the individual. This would also
include forming the algorithmand flowchart required for
the project.
REQUIREMENT ANALYSIS
The requirement analysis of the proposed system are:-


 


qSPECIFIC REQUIREMENTS:
 


New account creation.

Withdrawal of cash
Deposits of cash or cheque
Checking of Account balances by account holders by
admin
Transaction records in the form of reports.
 

qSYSTEM REQUIREMENTS:
LANGUAGE: C
COMPILER: Turbo C 4.5
OPERATING SYSTEM: WINDOW PLATFORM
(XP, VISTA & 7), DOS


qHARDWARE REQUIRMENT:
PROCESSOR: INTEL (CELERON, DUAL CORE &
CORE 2 DUO etc)
HARD DISK: 40GB
RAM: 128MB

FEASIBILITY ANALYSIS

There are three key consideration involved in this



feasibility analysis each consideration has reviewed to

depict how it relates to the system effort.
They are as follows:-


Ø Economic feasibility
Ø Technical feasibility
Ø Operational feasibility

ECONOMIC FEASIBILITY
The manual efforts involved in maintaining the A/c and
customer information, the withdrawal, the deposit
and balance calculation, is tremendous.
With the help of this software it is very easy to maintain
the detail of accounts and transactions.
We would invest around 800 bucks on this project mainly in
the documentation part.



Technical Feasibility
This is concerned with specifying equipment and
software that will successfully satisfy the user
requirement. The technical needs of the system may
vary considerably, but might include:


ü The facility to produce outputs in a given time

ü Response time under certain conditions.
ü Ability to process a certain volume of transaction at a
Operational feasibility
Operational feasibility is a 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.
For example, in my project, records of the customer,
their transactions will be maintained which will be
helpful in the future as reference prior to dealings
well as evidence.
Also limitations can be overcome by better
technologies and system can be made more efficient.
Minutes of Meeting
Time Duration Topic of discussion Venue Members
(approx.) Present

12:00-1:00 1hr Bio data collection 108 - A ALL MEMBERS EXCEPT

23/1 PUNEET & PRATIMA

3:20-4:00 1hr 30min Synopsis development 109 B ALL MEMBERS , EXCEPT

11/2 distribution PUNEET