Sample - Bank Management System PDF

Your project MUST have these modules
1. Properly documented code use comments
2. Properly prompt statements
3. Data type should have valid justification
4. User menu
5. Use Data Structure Array.
6. Searching facility
7. Store user data (File handling)

DEPARTMENT OF COMPUTER SCIENCE
Computer programming Lab
PROJECT PROPOSAL FORM
SEMESTER FALL Bs (cs) 1 A / B 2018

TITLE OF PROJECT
BANK MANAGEMENT SYSTEM

Group Members
S# Student(s) Name Registration Number
1
email:
email:
email:
EXECUTIVE SUMMARY OF PROJECT PROPOSAL (MAXIMUM 300 WORDS)

Our project has two Modules.
1. One Module for Customers illustrating the implementation of basic functions like those carried out by
an ATM for an Account Holder within a Bank.
2. Second Module illustrating the role of Bank Employees managing the system as Administrators. The
role and design of Administration Module is assumption based and not taken from real world
example like the Customer Module is based upon ATM features and functions.
PROJECT PURPOSE, SCOPE AND OBJECTIVES (MAXIMUM 1000 WORDS)

• PURPOSE
Purpose of the project is to get basic know how and workings involved in the designing and
developing of Bank Management System Softwares which includes:
1. Understanding the services provided by Banking System.
2. Analyzing the workings and dynamics of mechanisms involved in services provided by Banking
System.
3. Understanding and analysis of prerequisites required for providing services delivered by
Banking System.
4. Designing and developing computational model and structure based system for Banking
System Model.
5. Implementing developed computational model and structure based system in a programming
language.
• SCOPE
The scope of this project is focused around 2-Main Role Players involved in the workings of the
system and each having a portal designed for carrying out their relevant functions. The role players
along with their scopes are:
1. CUSTOMER (ACCOUNT HOLDER WITHIN A BANK):
Customers will be able to perform the following functions:
1. Balance Inquiry
2. Transactions History
3. Cash Withdrawal
4. Cash Transfer
5. Change Pin
Page 2 of 6
2. BANK ADMINISTRATORS (ACCOUNTS MANAGEMENT EMPLOYEES):

Bank Administrators will be able to perform the following functions:
1. Add New Account (Customer)
2. Remove Existing Account (Customer)
3. Modify Existing Account (Customer)
4. Lock/Unlock Account (Customer)
3. COMMON FUNCTIONS
The function of logging into and out of the system will be common for both customers and
Administrators with the following differences in their parameters:
1. Customers: Login via Account Number and Pin.
2. Administrators: Login via Username and Password.
• OBJECTIVES
To implement each of the functions in a concise and efficient manner with proper understanding in
Java Programming Language.
PROJECT DESCRIPTION (most important part)

The System Will Have the following Structure:
Page 3 of 6
• CLASSES:
o Class to build Account type for Customers
o Class to build Login_Info type for Administrators
o Calss to build Account_Info type for Customers
o Class to build Transactions_Info and Log Types
All of these Classes will have Arrays i.e Arrays of their Objects and the information of these
objects will be stored in files as well although we also propose that information be stored on a
proper Database technology integrated with the system like MS Access database or SQL Server
Database.
• MAIN CLASS and Function:
The main function will only contain the Data type declarations and initializations and calls to Main
Menu methods and Display prompts.
• STATIC CLASs FOR OPERATIONS:
Most of the operations performed by and on the two main roles interacting by the system will be
Page 4 of 6
placed in a static Class Named “Operations” for better organizing of Code and reuse in future
development of this type of System.
• SEARCHING FACILITIES:
The searching Facilities to be used in the system are as follows:
o String & No.Matching with in the records of Customers for Successful Login and Information
Rertrieval after Login.
o Same as above for Successful Login of Administrators with the difference being file used will
be Administraor_Info_Login
o Account Number Searching with in the Array of Customers (Most probably Sequential Search
and if possible Binary Search)
Above mentioned Searching will be used by the Administrator Methods as well as Customer
Methods.
• RECORDS MAINTAINING FACILITY:
Records of each Customer’s and Administrator’s information will be stored in files and Updated,
Modified or removed as per needs of the Methods Performed.
If possible, we will try to Use some proper Database technology integrated in the system for proper
manipulation and handling of Records and data.
TEAM PROFILE
< Individual qualifications and strengths (such as: programming, design, presentation, documentation,
management and organization)
Note: It is expected that every team member shall be involved in all project activities; this only indicates
individual strengths, not their sole responsibilities >
ASSUMPTIONS AND CONSTRAINTS

We have assumed that the Administrators information present for logging in to the system will be added by
the developers of the system and given to the bank employees via email. Also, the method of Cash transfer is
within the same bank and the system is for one branch only and not for multiple branches. Further we will
bound the system to be synchronized with the time stamps and clocks of the hardware systems on which it is
deployed and running. Also, we are constraining that the CNIC and Account Numbers of the Customers will be
unique and their Duplication will not be Allowed for one particular type of account i.e. A Customer may have
more than one account only if the accounts are of different type.
PROJECT DELIVERABLES NOT CHANGEABLE
Deliverables include
• Software Project Proposal.
• Project progress
• Project report (template will be uploaded)
• Team members work, as per their contribution, you should have to be honest with your
future.
Team Profile
Filled by your self
SCHEDULE AND BUDGET SUMMARY
Page 5 of 6
ITEM DATE SIGNATURE

Project Proposal
Proposal Presentation
Software Project Management Plan
<other project deliverables>
Project I Presentation
Progress Report
Exposition paper
EXPECTED RESULT(S)/OUTCOME(S) (MAXIMUM 300 WORDS)
For Teacher Use Only
REMARKS
Course Teacher Fasiha Ikram Signature Date
Name Talha Alam Signature Date
Page 6 of 6

Sample - Bank Management System PDF

Uploaded by

Copyright:

Available Formats

Sample - Bank Management System PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Sample - Bank Management System PDF

Uploaded by

Copyright:

Available Formats

Your project MUST have these modules

1. Properly documented code use comments

2. Properly prompt statements

3. Data type should have valid justification

5. Use Data Structure Array.

7. Store user data (File handling)

SEMESTER FALL Bs (cs) 1 A / B 2018

BANK MANAGEMENT SYSTEM

EXECUTIVE SUMMARY OF PROJECT PROPOSAL (MAXIMUM 300 WORDS)

PROJECT PURPOSE, SCOPE AND OBJECTIVES (MAXIMUM 1000 WORDS)

2. BANK ADMINISTRATORS (ACCOUNTS MANAGEMENT EMPLOYEES):

PROJECT DESCRIPTION (most important part)

ASSUMPTIONS AND CONSTRAINTS

Filled by your self

SCHEDULE AND BUDGET SUMMARY

ITEM DATE SIGNATURE

EXPECTED RESULT(S)/OUTCOME(S) (MAXIMUM 300 WORDS)

For Teacher Use Only

Course Teacher Fasiha Ikram Signature Date

Name Talha Alam Signature Date

You might also like