Documentation On Bank Management System
Documentation On Bank Management System
ACKNOWLEDGEMENT
SUBMISSION
A
Project report on “Banking Management System”
Submitted of the computer practical
2013
Of
Class BSCS-I
For the practical fulfillment of the
requirement for the syllabus.
CERTIFICATE
Introduction:
In today’s world , the way of functioning and managing the system has been
totally changed. There is a sudden and adrupt changes in the structure,
maintenance and modification, handling, leveling inside every system. Without
managing system through computer applications and programming, the
development of infrastructures are unfinished. There are many errors and
drawbacks without use of computer programming and applications.
All transactional details and accounts are stored in files on stable storage.
Customers can view their own account details and can use them as
necessary
Faster performance.
Proposed System And Objectives:
Following are the major objectives behind the new proposed system:
Module description:
module description
Create File Selecting this create a new file for the
user by accepting input such as
account number, name and amount
Input Specification:
Struct Information
File Specification:
Screen Design:
Output screen design:
OBJECTIVES:
When the data is entered it will check for its validity. Data can be entered with
the help of screens. Appropriate messages are provided as when needed so that
the user will not be in a maize of instant. Thus the objective of input design is to
create an input layout that is easy to follow.
A quality output is one, which meets the requirements of the end user and
presents the information clearly. In output design it is determined how the
information is to be displaced for immediate need and also the hard copy
output. It is the most important and direct source information to the user.
Efficient and intelligent output design improves the system’s relationship to help
user decision-making. Designing computer output should proceed in an
organized, well thought out manner; the right output must be developed while
ensuring that each output element is designed so that people will find the system
can use easily and effectively.
DATABASE DESIGN:
A database is an organized mechanism that has the capability of storing
information through which a user can retrieve stored information in an effective
and efficient manner. The data is the purpose of any database and must be
protected. The database design is a two level process. In the first step, user
requirements are gathered together and a database is designed which will meet
these requirements as clearly as possible. This step is called Information Level
Design and it is taken independent of any individual DBMS. In the second step,
this Information level design is transferred into a design for the specific DBMS
that will be used to implement the system in question. This step is called Physical
Level Design, concerned with the characteristics of the specific DBMS that will
be used. A database design runs parallel with the system design. The
organization of the data in the database is aimed to achieve the following two
major objectives.
Data Integrity
Data independence
Normalization is the process of decomposing the attributes in an application,
which results in a set of tables with very simple structure. The purpose of
normalization is to make tables as simple as possible. Normalization is carried
out in this system for the following reasons.
To structure the data so that there is no repetition of data , this helps in
saving.
To permit simple retrieval of data in response to query and report request.
To simplify the maintenance of the data through updates, insertions,
deletions.
To reduce the need to restructure or reorganize data which new application
requirements arise.
Screen Shots:
Welcome screen
Creating account
Logging in as existing customer
Depositing Amount
Withdrawing Amount
Viewing Details
Converting Currency
Processing and validation:
Main menu:
There are number of options regarding users to creating a new account
or logging in as existing customer to access the facilities system providing or exit
the system after accessing the user requirements.
Converting currency:
This required a number of money user want to convert and also
required the name of currency user wish to convert in.
Uniqueness:
Each account number should be unique throughout all the existing
records. Name should be of character type and account number should be of
digit. Character and digits are not allowed.
Checking of size:
Account number cannot be greater than 2 of size.
Test Case 1
Test Case 2
Test Objective To check if the program menu displays all menu options
or not.
Test Case 4
Test Case 6
Test Objective To check if ‘view detail’ option shows the info or not.
Test Case 8
Test Objective To check if currency converter works properly or not.
Test Data Enter currency.
Expected Result Amount must be converted according to desired currency.
Test Case 10
Test Case 12
Results:
It does not need any additional hardware or software to operate the program,
but the following requirements should be strongly maintained:
Requirements for hardware:
CONCLUSION:
Program Weakness:
Program Strength:
TURBO C++
ROBERT LOFFORE
LET US C
YASHWANT KANETKAR