You are on page 1of 34

BANKING MANAGEMENT

SYSTEM

PROJECT PRESENTATION
SOFTWARE DEVELOPERS

 TEAM MEMBERS
FAROOQ
YOUSUF
ANIKET
UMAR
JANARDHAN-R
CONTENTS

 AIM OF THE SYSTEM.


 LITRATURE SURVEY
 SYSTEM ANALYISS
 SOFTWARE REQUIREMENT SPECIFICATION
 SYSTEM DESIGN
AIM

 To develop a software for solving financial


application of a customer in banking environment in
order to nurture the needs of an end banking user by
providing various ways to perform banking tasks .
Also to enable the user’s workspace to have
additional functionalities which are not provided
under a conventional banking software.
LITREATURE SURVEY

SOFTWARE INTRODUCTION
 INTRODUCTION VISUAL BASICS
 INTRODUCTION TO ORACLE
INTRODUCTION TO VISUAL BASICS

 Visual Basics is a 3rd generation event driven


programming language .
 Integrated Development Environment (IDE).
 Graphical User Interface (GUI).
 Rapid Application Development (RAD).
 Creation of ActiveX controls and object.
 Microsoft Windows Programming Language.
 Visual Basic uses Win32 and MFC libraries
to implement its functionality.
• Objected oriented
INTRODUCTION TO ORACLE

 Oracle is a 4th generation Relational Database


Management System(RDBMS).
 Manages Data efficiently.
 User to perform multiple task with ease.
 A DBMS store ,organize and manage a large amount of
information with a single software application.
 Oracle is both online transaction and batch processing
application
 Require ODBC connection .
 ADODB and ADODC are Microsoft ActiveX Data control
SYSTEM ANALYSIS

 EXISTING SYSTEM
 PROPOSED SYSTEM
 SYSTEM ANALYSIS
 FESIBILITY STUDY
 OPERATIONAL FESIBILITY
 TECHINICAL FESIBILITY
 ECONOMICAL FESIBILITY
EXISTING SYSTEM

 Transaction done manually but not in proposed


system.
 Lack of security of data.
 More man power.
 Time consuming.
 Needs manual calculations
 Damage of machine due to lack of attention.
Disadvantage

 No user friendly.
 Difficult in report generation .
 Manual control.
 Lots of paper work.
 Time consuming
PROPOSED SYSTEM

 To over come all the limitation of existing system.


 Security of data.
 Minimize manual data entry.
 User friendliness and interactive,
 Reduce the damage of machine.
 greater efficency.
 Better service.
 Minimum time required.
Advantage

 User friendly.
 Reports are easy to generate.
 Very less paper work.
 Computer operator control.
 No redundancy.
 Protected.
SYSTEM ANALYSIS

 Gathering and interpreting the facts .


 Diagnosing the problem and the information to
recommend improvements on the system.
 Intensive communication between system user an
system developers.
 The system is studied and analyzed.
 The system analysis checks everything in existing
system to improve or update to be added to the new
system.
FEASIBILITY STUDY

 Feasibility study is made to see if the project on


completion will serve the purpose of the
organization for the amount of work ,effort and the
time that spent to develop the system.
 Ability to meet the users needs and effective use of
resources
 A new application is proposed in normally goes
through a feasibility study before it is approves for
development.
OPERATIONAL FEASIBILITY

 No doubt the proposed system is fully GUI based


that every user friendly and all inputs to be taken all
self explanatory even to a layman . as far our
concerned the clients are comfortable and happy as
well the system has cut down their load and doing.
 It requires any one operator to operate it instead
many,
 No special course requires for an operator to operate
the system .
 Easy data retrieval can be done by this system .
TECHNICAL FESIBILITY

 The system must be evaluated from the technical


point of view first.
 The assessment of this feasibility must be based on
an outline design of the system requirement in the
terms of input ,output and procedure.
 Technical issues raised during the investigation are:
 Does the existing technology sufficient for the
suggested one.
 Can the system expand if develop.
ECONOMIC FESIBILITY

 The benefit must be justified by cost and benefits.


 One of the factors , which affect the development of a
new system ,is the cost it would require.
 Important financial questions asked during preliminary
investigation are:
 the cost conduct a full system investigation.
 The cost of the hardware and software.
 The benefits in the form of reduced costs or fewer costly
errors.
 It gives an indication of the system is economically
possible to development.
SOFTWARE REQUIREMENT

 The purpose of the software requirement specification


(SRS) is to bridge the communication gap between the
client and the user.
 SRS document is a contact between the developer and
the customer.
 Once the SRS document is approved by the customer
any subsequent contravention are settled by referring the
SRS document.
 The purpose of this document is to describe the function
and design of the project designed by the group.
 Developer use this as reference if any of the requirement
undergo any change in the future.
FUNCTIONAL REQUIREMENT

 Describes the capabilities and functions that is expected


to performed at the output screen .
 Satisfaction user: the system is such that it stands up to
user expectation .
 Response time :the response of all operation are good.
 Error handling : to ensure that the system is operates
without halting.
 Safety and robustness : the system is able to avoid or
tackle disastrous actions
 Portable: the software is easily transferred to other
platform if need.
NON–FUNCTIONAL REQUIREMENT

 Product requirement
 Organization requirement
 External requirement
 The system provides security, managing the item list.
 It is easy due to centralized management.
DOMAIN RQUIREMENT :

 Domain requirement reflects the environment in


which the system operates
 Domain requirement may be expressed using
specialized domain technology.
 Because this requirement are specialized ,software
engineer’s often to find it very difficult to
understand how they are related to other system
requirements.
SYSTEM REQUIREMENT

 SOFTWARE REQUIREMENT
OS :Windows98,XP,windows7 and above.
Front end : Visual Basics.
Back end : Oracle 10g or 11g.
 Hardware requirements
processor :PIV and above.
RAM :4gb and above.
Hard disk: 20gb and above.
SYSTEM DESIGN

 Design various block for overall system process.


 Design smaller ,compact and workable modules in
each block.
 Design various database structure.
 Specify details programs to achieve desired
functionality.
 Design the form of inputs and outputs of the system
 Perform documentation of the design.
 System reviews
MOUDALS

 CUSTUMER ACCOUNT
 EMPLOYEE ACCOUNT
 ACCOUNTS MANAGEMENT
 FIXED DEPOSIT MANAGEMENT
 SAVINGS ACCOUNT
 CURRENT ACCOUNT
ZERO LEVEL DFD-DIDGRAM
LEVEL1-DFD
LEVEL2-DFD
ENTITY RELATIONDHIP DISGRAM
NORMALIZATION
FIRST NORMAL FORM(1NF)
SECOND NORMAL FORM(2NF)
SCHEMA TABLES
SCHEMA TABLE
THANK YOU

THANK YOU

You might also like