Project Report on Banking Management System

Submitted In Partial Fulfillment Of the Requirement Of Bachelor of Business Administration

Submitted To: Ms.Padma Chahal

Submitted By: Vipul Kumar(07110601710) Nishant Baghel(11510601710) Rajinder Singh(10410601710) Shubham Jain (08410601710)

Submitted To: Ansal Institute of Technology Sector-55, Gurgaon (Affiliated to Guru Gobind Singh Indraprastha University)

CERTIFICATE
To the best of knowledge and belief, this work which embodies the work of students themselves, has been duly completed, fulfills the requirement of the ordinance relating to the fifth semester Degree of the University and is up to standard in respect of content, presentation and language for being referred to the examiner.

Faculty PADMA CHAHAL

ACKNOWLEDGEMENT

We would like to express our gratitude to all those who gave us the possibility to complete this project. we deeply indebted to our supervisor Ms. Padma Chahal, faculty in Ansal Institute of Technology, Gurgaon whose help, stimulating suggestions and encouragement helped us for writing of this report. We would like to express our gratitude to all those who gave us the possibility to complete this project.

VIPUL KUMAR NISHANT BAGHEL RAJINDER SINGH SHUBHAM JAIN

SYNOPSIS

The project entitled Banking Soft which keep the day by day tally record as a complete banking system. It can keep the information of bank employee, transactions, loan solution, ATM information and account information. The exciting part of this project is; it displays the employee details, payment details, loan details and transaction details.

Function:
1. Login
Login module is used to check whether the user is an authorized person to use the system or not. For this the user should give the correct user name and password

2. Maintain customer details

The customer detail Form is designed to provide customer details like name, a/c no., address, contact no. etc.

3. Maintain staff details

The staff detail Form is designed to provide Staff details like name, id, name of department, designation, contact no date of joining etc.

4. Maintain transaction details

The transaction detail Form is designed to provide transaction details of customers like date of deposition, date of withdrawal, total amount etc.

5. Maintain interest and loan details

The interest and loan detail Form is designed to provide Staff details like name, id, name of department, designation, contact no date of joining etc.

Types of Feasibility Study

Economic feasibility
Economic analysis is the most frequently used method for evaluating the effectiveness of a new system. More commonly known as cost analysis. The procedure is to determine the benefits and savings that are expected from a candidate system and compare them with costs. If benefits outweigh costs, then the decision is made to design and implement the system. It is done on two basis: cost and time.

Legal feasibility
Determines whether the proposed system conflicts with legal requirements, e.g. a data processing system must comply with the local Data Protection Acts.

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.[4]

Schedule feasibility
It estimates how long the system will take to develop, and can be completed in a given time period.

SDLC STUDY
SDLC (Software Development Life Cycle) is the process of developing software through business needs, analysis, design, implementation and maintenance. Software has to go through various phases before it is born which are as follows:

SDLC MODEL :Planning SR&S

Design

Implementation

Testing Installasation &Ooperation Maintenance

(i)Planning A concept comes from the users of the software. For example, a DOMINO,S may need software to sell pizza. An Indian store may need software to sell its newly arrived movies or grocery. The owner of the company feels that he needs software that would help him in tracking his expenses and income as well as enhance the selling process. This is how the concept is generated. The owner will specifically tell the software company what kind of software he would need. In other words, he will specify his requirements.

(ii) Requirements analysis After the owner (user) knows his requirements, then it is given to a software team (company) who will analyze the requirement and prepare requirement document that will explain every functionality that are needed by the owner. The requirement document will be the main document for developers, testers and database administrators. In other words, this is the main document that will be referred by everyone. After the requirement documents, other detailed documents many be needed. For example, the architectural design which is a blueprint for the design with the necessary specifications for the hardware, software, people and data resources.

(iii) Design: After the detailed requirement documents (some companies have design documents instead of requirement documents), the developers start writing their code (program) for their modules. On the other hand, the testers in the QA (Quality Assurance) Department start writing Test Plans (one module=1 test plan), test cases and get ready for testing.

(iv) Testing: Once the code (programs) are ready, they are compiled together and to make a build. This build is now tested by the software testers (QA Testers)

(v) Implementation: After testing, the application (software) goes into production (meaning, it will be handed over to the owner).

(vi) Maintenance: And one day, the owner will have say bye to the software either because the business grows and this software does not meet the demand or for some reason, the he does not need the software. Thats the end of it.

There is many kinds of SDLC models are as following:

waterfall Incremental Prototyping

Spiral

Various software development life cycle models are suitable for specific project related conditions which include organization, requirements stability, risks, budget, duration of project. One life cycle model theoretical may suite particular conditions and at the same time other model may also looks fitting into the requirements but one should consider trade-off while deciding which model to choose. Here I am summarizing here waterfall life cycle models:-

Waterfall:
The waterfall model is a model which was developed for software development; that is to create software. It is called as such because the model develops systematically from one phase to other in a downward fashion, like a waterfall. The most probable phases through which it progresses downwards are Definition Study/Analysis Basic Design Technical Design/Detailed Design Construction Testing Integration Management and Maintenance.

Before the advent of this method, the software development in the computer companies suffered from a haphazard integrated software network like cluttered knitting. However with this method they hoped to bring clarity in their projects. Waterfall Model :-

SR&S

Design

Implementation

Testing

Installasation &Ooperation Maintenance

(i) Requirements analysis After the owner (user) knows his requirements, then it is given to a software team (company) who will analyze the requirement and prepare requirement document that will explain every functionality that are needed by the owner. The requirement document will be the main document for developers, testers and database administrators. In other words, this is the main document that will be referred by everyone. After the requirement documents, other detailed documents many be needed. For example, the architectural design which is a blueprint for the design with the necessary specifications for the hardware, software, people and data resources.

(ii) Design: After the detailed requirement documents (some companies have design documents instead of requirement documents), the developers start writing their code (program) for their modules. On the other hand, the testers in the QA (Quality Assurance) Department start writing Test Plans (one module=1 test plan), test cases and get ready for testing.

(iii) Testing: Once the code (programs) are ready, they are compiled together and to make a build. This build is now tested by the software testers (QA Testers)

(iv) Implementation: After testing, the application (software) goes into production (meaning, it will be handed over to the owner).

(v) Maintenance: And one day, the owner will have say bye to the software either because the business grows and this software does not meet the demand or for some reason, the he does not need the software. Thats the end of it.

ADVANTAGES

Waterfall model is a very simple model for our project because there is lot of advantages behind that:

Simple goal. Simple to understand and use. Clearly defined stages. Well understood milestones. Easy to arrange tasks. Process and results are Well documented. Easy to manage. Each phase has specific deliverable and a review. Works well for projects where requirements are well understood. Works well when quality is more important then cost/schedule. Customers/End users already know about it.

SYSTEM REQUIREMENT ANALYSIS

SYSTEM ANALYSIS System analysis may be understood as a process of collecting and interpreting facts, identifying problems and using the information to recommend improvements in the system. System analysis is carried out with the following two objectives: To know how a system currently operates, and To identify the users requirements in the proposed system.

REQUIREMENT DETERMINATION Requirement determination, which is also termed as a part of software requirement specification is the starting point of the system development activity. This activity is considered as the most difficult and also the most error- prone activity because the usually does not understand software and the developer often does not understand the users, problem and application area.

STRATEGIES FOR REQUIREMENT DETERMINATION OR SQUIRO In order to collect information so as to study the existing system and to determine information requirement, there are different strategies, which could be used for the purpose. These strategies are:

1.

SAMPLING

Sampling is the first method of SQUIRO in which S acronyms sampling, which is used to collect the required data. In this method, a person collects the samples related to system and use it as a data which helps him to understand the system in proper way. The sampling is the oldest and the most often used device for gathering information about an existing system.

2.

QUESTIONNAIRE

A questionnaire is a term used for almost any tool that has questions to which individuals respond. The use of questionnaire allows analysts to collect information about various aspects of a system from a large number of persons. The questionnaire may contain structured or unstructured questions. The use of standardized questionnaire may give more reliable data than other fact- finding techniques. Also the wide distribution ensures greater anonymity for respondents, which can lead to more honest responses. The questionnaire survey also helps in saving time as compared to interview. However, this method does not allow analysts to observe

the expression or reactions of respondents as is possible during interviewing and also, it is difficult to design exhaustive questionnaire. The analysts should know the advantages and disadvantages of structured as well as unstructured questionnaire. Questionnaire must be tested and modified as per the background and experience of the respondents.

3.

INTERVIEW

The interview is a face to face method used for collecting the required data. In this method, a person asks question from the other person being interviewed. The interview may be formal or informal and the questions asked may be structured or unstructured. The interview is the oldest and the most often used device for gathering information about an existing system. The respondents are generally current users of the existing system or potential users of the proposed system. Although it is one of the preferred techniques, interviewing is not always the best source of application data. Because of the time required for interviewing and the inability of the users to explain the system in detail, other methods are also used to gather information. However, this method is helpful for gathering information from individuals who do not communicate effectively in writing or who may not have the time to answer questionnaire. Interviews allow analysts to discover areas of misunderstanding. The analysts must plan the interviews and must know clearly in advance regarding the following issues: Whom to interview? When to interview? What to ask? Where to hold the interview? How to begin the interview? How to conclude the interview?

Interviewing is regarded as an art and it is important that analysts must be trained in the art of successful interviewing.

4.

RECORD REVIEW

Record review is also known as review of documentation. Its main purpose is to establish quantitative information regarding volumes, frequencies, trends, ratios, etc. in record review, analysts examine information that has been recorded about the system and its users. Record may include written policy manuals, regulations and standard operating procedures used by the organization as a guide for managers and other employees. Procedures, manuals and forms are

useful sources for the analysts to study the existing system. The main limitation of this approach is that the documentation on the existing system may not be complete and up to date. It may be noted hare that there are two different views regarding the study of the existing system, one learns about its shortcomings and may use this knowledge to avoid committing the same mistakes again. Whereas the view which is against such a study, argues that it inhibits the generation of the new ideas and may bias the developer towards the same logic which is contained in the old system.

5.

OBSERVATION

Another information gathering tool used in system studies is observation. It is the process of recognizing and noticing people, objects and occurrences to obtain information. Observation allows analysts to get information, which is difficult to obtain by any other fact finding method. This approach is most useful when analysts need to actually observe the way documents are handled, processes are carried out and whether specified steps are actually followed. As an observer, the analyst follows a set of rules. While making observations, he is more likely to listen than talk. The exercise is time consuming and costly. Also the observer may not be able to get all the required information, especially about some intricacies of the system. Now a days, electronic observation and monitoring methods are being used widely as information gathering tools because of their speed and efficiency.

2.4

DATA FLOW DIAGRAM ( DFD)

Data flow diagram (DFD) is a graphical representation of the logical flow of data. It helps in expressing the systems requirements in a simple and understandable form. It is also known as a bubble chart. Its aim is to clarify the system requirements and identify major transformations that will become programs in system design. It decomposes the requirement specifications down to the lowest level of details. A DFD consists of a series of bubbles joined by lines representing data flow in the system. Ther are four main symbols used in a DFD, which are depicted below. 1) Square: it represents source of system data

2)

Arrow: it identifies data flow; it is a pipeline through which the data flow.

3)

Cicle/ Bubble: it represents a process that transforms incoming data flow into outgoing data Flow. A process can be represented by a circle or an oval bubble.

4)

Open Rectangle: it represents a data store.

A number of rules are to be followed in drawing a DFD: 1. 2. 3. 4. Processes should be named and numbered. Name should represent the process. The direction of flow is from top to bottom and from left to right. When a process is exploded into lower levels, they are numbered properly. The name of data stores, sources and destinations are written in capital letters. Process and data flow names have the first letter capitalized.

A DFD should not have more than 10-12 process, as having even 12 will take a DFD complex and difficult to understand. A DFD shows the minimum contents of a data store. Each data store should contain all the elements that flow in and out of it. DFD is very effective, when the required design is not clear and the user and the analyst require some symbolic representation for communication. The main advantages of a DFD is that a large number of iterations are often required to arrive at an accurate and complete solution.

SYSTEM DESIGN

SYSTEM DESIGN

System design is another important step in the system development process. This phase starts after the system analysis phase is over. The output of the system analysis phase, that is requirement specification become an input in the design phase. Data requirement are worked out on the basis of user requirement estimates. The identification of data requirements includes identifying data sources, the nature and type of data that is available and data gaps.

3.2

DESIGN OBJECTIVES

A system is designed with the following main objectives: Practically The system should be designed in such a way that it may be learnt and operated with ease by the users. Thus, the design should be user oriented. Flexibility The business organizations are dynamic in nature. Therefore, a system must be responsive to the change inevitably requested by its users. Efficiency A system must be efficient, that is it should perform jobs within their specified time. The efficiency of a system may be measured in terms of the following parameters. Security This aspect relates to hardware reliability, physical security of data and the detection and prevention of fraud and abuse of data.

3.3

DESIGN METHOD

There are a number of method for designing information system. Some methods are listed below:

Problem partitioning The method is based on the principle of divide and conquer. In this method, instead of solving the entire problem at once, the problem is divided into small manageable parts that can be solved separately. This problem partitioning method aims at reducing complexity because each module

can be developed, coded and tested relatively independently of the others. Also, maintenance is minimized if each module can be modified saparately. Structured design In this method, a structured chart is created, which can be used to implement the system. The chart depicts modules defining each module by the specific function. The aim is to produce a structure where the modules have minimum dependence on each other; and have a high level of cohesion, meaning all the statements within a module are functionally related. Various tools like flow charting, data flow diagram, structure charts, structured English, etc., are used in a structured design. Top down design The top down design is based on the concept of a system which suggests that a system consists of sub- system, which have sub- system of their own. A system may be termed as a hierarchy of sub system, the highest level sub- system corresponding to the total system. Accordingly, this method involves the identification of the main components of the system, decomposing them into their lower level components and iterating until the desired level of detail is reached.

SYSTEM DEVELOPMENT

System development is regarded as another form of problem solving in software which consists of activities like Understanding the problem Deciding a plan for a solution Coding the planned solution, and Testing the coded program

4.1

SYSTEM DEVELOPMENT STAGES

In order to develop a system successfully, it is managed by breaking the total development process into smaller basic activities or phases. Any system development process, in general, is understood to have the following phases:

I. II. III. IV. V. VI.

Investigation Analysis Design Construction Implementation Maintenance

4.2

SYSTEM DEVELOPMENT APPROACHES

In order to make sure that the system are analysed and designed efficiently and effectively, it is essential to adopt a suitable model, for which a basic understanding of various system development models currently in use, is a must. In a system development effort, the goal is to produce high quality software. The development process consists of activities, namely, I. II. III. IV. Investigation Analysis Design A system development model specifies how these activities are organized in the total system development efforts.

4.2.1

WATERFALL MODEL

Waterfall model, which follows the SDLC approach became popular in 1970s. the model states that the phases are organized in a linear order. The output of one phase becomes the input for the next phase. Various phases have already been under a general model of system development. In SDLC approach, the system is visualized as a living organism. The system takes birth, reaches the maturity stage through adolescence and ultimately dies its natural death.

4.2.2

PROTOTYPING MODEL

In the prototyping model, a prototype of the system is developed, instead of the complete system. A prototype is a comprehensive system and does not include all the requirement of the user. This model is based on the evolutionary method of system development. Prototyping is used in those system, in which identification of requirement is difficult and requirement may change during the development process. This model advocates the development of a throw away prototype to be given to the user to help understand his requirement. Start

4.2.3

Stop ITERATIVE ENHANCEMENT MODEL

In an iterative enhancement model, the system is developed in increments and each increments adds some functional capabilities to the full system is developed. Additions and modifications can be done at each step. To begin with, only a subset of the overall problem is considered in developing the system. The selected subset may be one of the important subsets, which may

contain some of the key aspects of the problem. The iterative enhancement process model is understood to have only three phases, namely, analysis, implementation and design.

Design1 Implement1 Analysis1

design2 implement2 analysis2

design3 implement3 analysis3

design4 implement4 analysis4

4.2.4

SPIRAL MODEL

The spiral model is the most recent system development model, which has been proposed by Boehm. This model suggests that the various activities involved in system development should be organized like a spiral. This model provides a framework for developing a process, which is guided by the risk level of the project. This model, as the name indicates, is cyclic in nature. Each circle of the spiral consists of four stages represented by one quadrant each. The angular dimension represents the progress in the development process, whereas the radius of the spiral represents the cost involved. Planning risk analysis

User evaluation

engineering

CONCLUSION

Thus we can conclude that we have successfully developed the BANK MANAGEMENT SYSTEM. It has got the following advantages over Manual System: Manual work takes more time and cost due to staff and other materials such as papers and registers. Data retrieval process becomes easy when it is needed, if we use computer management instead of manually. Storage capacity of the computer is also excellent. Generating the invoice by printer using computer is also useful feature. Updating of data is easy in computerized system. Data consistency is required for neat and proper management that is achieved by computer easily. With the help of software, data redundancy reduces as compared to manual. Time is precious and speed is the order of today. Our software supports this statement