Professional Documents
Culture Documents
Manish Najkani(10BCA38)
Rahul Nath(10BCA40)
Nitish Xavier Tirkey(10BCA52)
Submitted to:
BCA DEPT.
Renu Kewalramani
Class: SY BCA Sem-IV
ACKNOWLEDGEMENT
I am thankful to all the faculty members, providing their valuable
time and guidance in elaborating view of studying the project
details and getting the right vision for its implementation.
I am also thankful to Mrs. Renu Kewalramani, who is having a
vast knowledge of DBMS, System Analysis and Design &
Programming concepts which are the building block of project.
I also thank Mr. Samir Thakkar, our H.O.D., and all other faculty
members who are directly or indirectly involved with our project. I
am also pleased with the support and co-operation of the lab in
charge in order to make use of the free lab slots.
Abstract
Requirements definition and management is recognized as a necessary step
in the delivery of successful systems and software projects, discipline is also
required by standards, regulations, and quality improvement initiatives.
Creating and managing requirements is a challenge of IT, systems and
product development projects or indeed for any activity where you have to
manage a contractual relationship. Organization need to effectively define
and manage requirements to ensure they are meeting needs of the customer,
while proving compliance and staying on the schedule and within budge.
The impact of a poorly expressed requirement can bring a business out of
compliance or even cause injury or death. Requirements definition and
management is an activity that can deliver a high, fast return on investment.
The BANK MANAGEMENT SYSTEM undertaken as a project is based on
relevant technologies. The main aim of this project is to develop software for
bank management system. This project is to develop software for bank
management system. This project has been developed to carry out the
processes easily and quickly, which is not possible with the manuals
systems, which are overcome by this software. This project is developed
using VB language and. Hence it provides the complete solution for the
current management system.
Table of Contents
1. Introduction of the Project
1.1. Project Objective
1.2. Project Benefit
1.3. Project Scope
1.4. Project Limitation
2. System Development Life Cycle
2.1. Preliminary Investigation
2.1.1. Request Clarification
2.1.2. Feasibility Study
2.1.2.1. Technical Feasibility
2.1.2.2. Economical Feasibility
2.1.2.3. Operational Feasibility
2.1.3. Request Approval
2.2. Determination of System Requirements
3. System Design
3.1. Interface Design
3.1.1. User Interface
3.1.2. Communication Interface
3.2. Detailed System Specification
3.2.1. Detailed System Design
3.2.1.1 Functional Flow of System
3.2.1.2 Data Flow of System
4. Testing & Debugging
5. Appendix
5.1. References
1.1.
Project Objective
To allow only authorized user to access various function and
processed available in the system.
Locate any A/C wanted by the user.
Reduced clerical work as most of the work done by computer.
Provide greater speed & reduced time consumption.
Implementation
System Testing
Development of
System
Preliminary
Investigation
Determination of
Requirements
Design of System
2.1.
Preliminary Investigation
For this, the need arises to understand the viewpoint of two important
entities
Top management and users.
After carrying out these interviews, I drew conclusion about the Top
Managements requirements and whether users are in support of the new
system.
This activity is consisting of three parts:-
2.1.2.
Feasibility Study
2.1.2.1.
Technical Feasibility
Issues to be studied are, whether the work for the project will be
done with current equipment, existing S/W technology and available
personnel? If the new technology is required, then what is the
likelihood that it can be developed?
Hardware Requirements
Server Machine:
Minimum p-3, 256 MB RAM, 20 GB Hard Disk
Client Machine:
Minimum p-3, 128 MB RAM, 8 GB Hard Disk
Printer:
132 columns High Speed Dot Matrix Printer with local
language support
Software Requirements
Microsoft for
Client
Visual Basic: Version 6.0 and above; Source: Microsoft
MS-Access:
2.1.2.2.
Economic Feasibility
2.1.2.3.
Operational Feasibility
2.1.3.
Request Approval
The Top Management reviewed the above factors and gave their
ascent. After the consent to request approval, the design was taken up.
2.2.1. Reviewing
Documents
Organization
Design of System
3.1. Interface Design
User Interface
Communication Interface
3.2.1.
Detailed Design
The design that we have formed for the new system are given
as under:3.2.1.2 Data Flow Diagram:
0-Level DFD
Account No
User
Account
Details
Bank
Transaction
System
Flow chart
ACC. NO.
ADDRESS
.
NAME
BALANCE.
START
BANK
TRANSACTION
DEBIT
h
a
s
CUSTOMER
Don
e by
CREDI
T
START
CUSTOMER
ha
s
ha
s
FIXED
DEPOSITE
ACCOUNT
AMOUNT
ID. NO.
DURATION
BALANCE
ACC. ID.
TRANSACTION
CUSTOMER
CURRENT
BALANCE
DEBIT
CREDI
T
UPDATE
BALANCE
UPDATE
BALANCE
BALANCE
Transaction Process
Unit Testing:
It is testing of individual module. Before initiating unit testing, it must be
ensured that the code is peer previewed.
Integration Testing:
Integration testing is performed after all the software units are combined
together. The objective here is to test the software interfaces. Project team
conducts the integration testing. Before entering integration testing, it
may be ensured that code review and unit testing have been performed on
the individual software modules.
I conducted the unit testing for finding errors and the results of the
unit testing are recorded and action initiated for rectification of the
errors/defects.
VALIDATION
i.e.
we
the
the
as
part
Testing Process
APPENDIX
5.1. References
Books:
(e-book)
(e-book)
Websites:
http://www.intranic.in
http://www.google.com