nehaproject 2pages

8/7/2019 nehaproject 2pages

1/57

BANK MANAGEMENT SYSTEM

SUBMITTED BY :Neha

Agrawal557099


2/57

TITLE OF THEPROJECT

BANK MANAGEMENT SYSTEMDOEACC A LEVEL

SUBMITTED BYNEHA AGRAWAL

557099H.No. 4, NAVJYOTI COLONEY, HAPUR-245101(U.P.)

DATE OF SUBMISSION

UNDER GUIDANCE OFMiss. SMRITI AGARWAL (M.C.A.)

NAME & ADDRESS OF ACCREDITED INSTITUTE :

ADVANCE COMPTER EDUCATION INSTITUTE RAILWAY ROAD

BULANDSHAHR- 203001(U.P.)


3/57

To,The Executive Director,DOEACC SOCIETYElectronics Niketan6,CGO Complex,New Delhi 110003

March, 2011

Subject : Submission of DOEACC A LEVEL Project.Respected Sir,

I am submitting my A Level project for evaluation.Details of my registration & postal address, etc are as under :

REGN : 557099

LEVEL : A

NAME : NEHA AGRAWAL

FATHERS NAME : MR. RAJENDRA KUMAR AGRAWAL

ADDRESS : W/o NITIN GUPTAH. No. 4, NAV JYOTI COLONEY,MEENAKSHI ROAD, HAPUR(U.P.)

PIN- 245101PH.NO. : 09410269847

E- MAIL : [email protected]


4/57

ACKNOWLEGMENT

This BANK MANAGEMENT SYSTEMPROJECT is entirely created by Neha Agrawal,

student of A Level. I am grateful to Mr. SanjeevBansal ( Head ofAdvance Computer EducationInstitute ) for his timely help, support and

encouragement. I am also grateful to Mrs. AnshuBansal for their valuable comments, suggestions andmany innovative ideas in carrying out this project.

I would like to thank faculty ofAdvanceComputer Education Institute for their technicalguidance and mutual support. I had tried my best to

make this software error free software.

Thanking you

( Neha Agrawal )


5/57

SOFTWARE DEVELOPMENT PROCESS

PROJECT IDENTIFICATION AND SELECTION

PROJECT INITITION AND PLANNING

ANALYSIS

LOGICAL DESIGN

PHYSICAL DESIGN

1. E-R DIAGRAM

2. DATA FLOW DIAGRAM

IMPLEMENNTATION

1. DIRECT CONVERSION

2. PILOT CONVERSION

3. PARALLEL CONVERSION

4. PHASED CONVERSION

MAINTENANCE

1. CORRECTIVE MAINTENANCE

2. ADAPTIVE MAINTENANCE

3. PERFECTIVE MAINTENANCE

4. PREVENTIVE MAINTENANCE

CASE STUDY OF THE PROJECT

REFRENCES

ABSTRACT

CONCLUSION OF THE PROJECT


6/57

CODING

OUTPUT

OBJECTIVE & SCOPE OF THE PROJECT

There is always remain a room for improvement in any

software package however good or efficient it may be. The important

thing is that the system developed be flexible to accommodate any

further enhancement.

The scope of software package BANK MANAGEMENT

SYSTEM can be further extended for any Organization. In

future we can modify this package by providing this facility on the

basis of programming.


7/57

DEFINITION OF THE PROBLEM

This project gives a perfect user interface with menus at a

beginning providing an introduction to the software and it features

with copyright. A form of multiple choices gives to choose either to

add a new record or find or delete the specified record. We can

also update the existing record.

The application consists of major eight sections:

1. Introduction

2. Open New Account

3. List of Accounts

4. See Individual Account

5. Daily Transaction

6. Monthly Report

7. Edit Account(Modify Account, Close Account)

8. Exit


8/57

This application gives total information about a Detail, which helps

to add, update and find any record.

USER REQUIREMENT

For users the Hardwares Specification for this BANK

Management Project is as follows:

SPECIFICATIOIN :

Space taken : This project can hardly take 100 Kilo

Bytes on your disk.

MINIMUM SYSTEM REQUIREMENT :

DISPLAY : 256 Colors

Hard Disk : 1.2 Giga Byte

RAM : 16 Mega Byte

Monitor : Color

Operating System Support :

Platforms : Window 98/2000/XP.


9/57

DETAILS OF HARDWARE & SOFTWARE USED

For the execution of the project there are two types of

requirement, we need : -

1. Hardware Requirement.

2. Software Requirement.

HARDWARE REQUIREMENT -

Our project requires the following hardware:

Personal computer based on Pentium processor.

Installed & functioning network.

128 MB RAM for standard database.

Hard disk space-The amount of hard disk space

required, depends on the installation & replication

option that you select.

SOFTWARE REQUIREMENT-

Our project requires the following software:

Window 98/2000/XP.

Ms-office


10/57

C++

FEATURES OF C++

Some of the important features of C++ have been discussed below:

Building a useful user interface.

Writing C++ code in clear constructs to mark the code run smoothly.

Mastering the art of getting the errors out of a C++ program.

Software complexity decreases.

In C++ we can built program from the standard working modules that

communicates with each other rather than having to start writing the

code from search. This leads to saving of development time and higher

productivity.

Complex project can be easily divided into simple code functions, to

mark a user understand easily.

Object oriented system can be easily upgraded from one platform to

another.

Objects communicate with each other through message exchange.

OOP provides an elegant facility called polymorphism to handle this

situation.

Object oriented programs are built from reusable software

components.

Mapping objects is possible.


11/57

Cost And Benefit Analysis

In Bank Management System the Cost and benefit analysis is a procedure,that gives a picture of various costs, benefits, rules associated with the system.

The determination of Cost and benefit entails the following steps:

Identify the Cost and benefit pertaining to given project.

Categorized various Cost and benefit for analysis.

Select a method for evolution.

Interpret the result of analysis.

Take necessary actions.

Problems involved in Cost and benefit analysis:

(i) Valuation problem: Intangible cost and benefitsare difficult to

quantified.

(ii) Distortion problem: There are two ways of distorting theresult of cost and benefit analysis. The first one is the

international favoritism of alternative for political reason.

Other is when data are incomplete or missing from the

analysis.


12/57

(iii) Completeness problem: Occasionally and alternative isoverlooked forces us to that comprise about the quality of the final choice.

Classification of Cost and Benefit:

The next step in Cost and benefit determination is to categorized cost and

benefits. They may be tangible or intangible, direct or indirect, fixed or

variable. Let us review each category.

1) Tangible or Intangible Cost and benefits

2) Direct or Indirect Cost and benefits

3) Fixed or variable Cost and benefits

System

cost

Cost

Break Even

Point

TimePayback Period

System Benefit


13/57

Tangible or Intangible Cost and benefits:

Tangibility refers to ease with which costs or benefits can be

measured. An outlay of cash for a specific item or activity is referred to

astangible cost. They are usually shown as disbursement on the books.The purchase of hardware or software, software, personnel training and

employee salaries are example of tangible costs. They are readily identified

and measured.

Costs that are known to exist but whose financial value cannot

be accurately measured are referred to as intangible costs.

Probability


14/57

Direct or Indirect Cost and benefits :

From a cost accounting point of view, cost are handled differently

depending on whether they are direct or indirect.

Direct Costs are those with which a dollar figure can be directlyassociated in a project. They are applied directly to the operation for example,

the purchase of a box of diskettes for $35 is a direct cost because we canassociate the diskettes with the dollars expended.

Direct Benefitsalso can be specifically attributable to a giveproject. For Example, a new system that can handle 25% more transactions

per day is direct benefit.

Indirect Costare the results of operations that are not directlyassociated with a given system or activity. They are often referred to as

overhead. A system that reduces overhead realizes savings. If it increases

overhead it incurs an additional cost.

Indirect Benefitsare realized as a by-product of another activityor system. For example, our proposed safe deposit billing system that provides

profiles showing vacant boxes by size, location and price will help

management decide on how much advertising to do for box renal. Information

about vacant boxes becomes an indirect benefit of the billing even though it isdifficult to specify its value. Direct and indirect cost and benefits are readily

identified for tangible cost and benefits, respectively.


15/57

1. Corrective Maintenance :

In this type of maintenance, repairing is done if any problem occurs.

In spite of all these kind of maintenance, these constitute more then 60% of

total maintenance effort. Corrective maintenance is very much undesirable.

It does not do any value addition to software. Care should be taken to see that

normal business operations are not disturbed because of it.

2. Adaptive Maintenance

Changes are needed as a consequence of upgraded version or changes

in operation system, hardware, or DMBS. Adaptive maintenance is required

because business operates on a social environment and need of the

organization changes as organization ventures into new areas, or as

government regulation police changes, etc.

Maintenance of the software to adapt to this kind of changes is called

adaptive maintenance. Unlike corrective maintenance, this kind of activity

adds value to the information system and affects a small part of the

organization. This activity is not as urgent as corrective maintenance as these

changes are gradual and allow sufficient time to the system group to makechanges to the software.

3. Perfective Maintenance

This kind of maintenance activity involves adding new functionalities

and features to the software to make it more versatile and user oriented. Some

times, changes are made to improve performance of the software.


16/57

In some sense, this maintenance can be thought of as a new development

activity. This value to the information system and is required to say ahead ofthe competition.

4. Preventive Maintenance

Changes are made to software to make it easily maintenance and toprevent any kind of system failure in future. This reduces the need of

corrective maintenance. As corrective maintenance could lead hamper normal

functioning, prevent maintenance is done periodically to ensure that the

probability of system failure is minimized.

Preventive maintenance could increase the volume of transactions that can

be handled by the system. Preventive maintenance is done when the system is

least used or not at all. This does not add value to the system, but certainly

lowers the cost of corrective maintenance.

75%

25%Adaptive

Maintenance,

Perfective

Maintenance and

Preventive

maintenance

CorrectiveMaintenance

Comparative figures of Maintenance Efforts


17/57

Testingis also a part of maintenance. System testing is quite expensiveand time consuming process. The common view of testing help by user is

that it is performed to prove that program is error free.

The most useful and practical approach is with the understanding that

testing is the processing of executing a program with the explicit intention of

finding errors that is, making the program fail. A successful test, then, is the

one that finds errors.

No system can be perfect. Testing is of vital importance as a team of software

engineer designs all information system and end users have little or no

knowledge of system development. Testing is done to bridge the between the

perceived out come desired by the user to that of systems analysts and

program team. The design specification is requirements of the user and

translated to working software by the programmers.

Hence, it is the ability of the programmer to code exactly as per the design

specification that is to be judged by the testing the software module. The

objective of any testing mechanism is to discover and fix bugs before the

product is delivered to the customer.

A good testing scheme has a high probability of discovering an

undiscovered error. The objective of any good testing scheme is to find and fix

bugs with minimum time and resources.


18/57

Besides, bugs and errors system are testing for response time, volume of

transactions that can be handled, stress under which it can function, security

and usability. For an online transaction processing system, testing of the

software for response time could be quite vital.

System testing assumes that all parts of the system are correct and error-

free. Even though the system has been testing for individual components and

modules, there is no guarantee that the system after integration will work as

per the desire specification. System test involves a holistic approach for testingthe working o the application in totality.

The following are various type of system Testing:

1) Recovery Testing

2) Security Testing

3) Stress Testing

4) Performance Testing

5) Response Testing6) Alpha Testing

7) Beta Testing

Recovery Testing;

Test the ability of the system to recover from error. Error or any other

processing faults must not overall system to fail. The recovery time of thesystem after failure must be within a specific period and tolerance limits.

System failure are forced during this phase of testing by introducing

exceptions to see how the system responds to the case.


19/57

Security Testing:

System used for processing sensitive information is prone to highsecurity risks. Individual often tries to access unauthorized data for various

reasons. Threats could be external or internal. Hacking of passwords is a

common problem. Individual can use software to generate random passwords

to gain access of the system. Security testing takes care of these aspects of the

system security.

Stress Testing:

Stress test is designed to test the system as to how the system behave in

abnormal situation. The aim of the stress test is to find the limit of quantity or

frequency of input after which the system fail. Stress test cases are designed

which require maximum and other resources; in excess of what a normal

situation demands.

Performance Testing:

Performance testing is specifically important to embedded and real

time systems. It checks the run time performance of the system. It is often

coupled with stress testing.

Response Testing:

Testing of response time of special important in OLTP (online

Transaction Processing system like railway reservation system, point of sale,

etc). Testing is done to measure the response time. The same is compared with

desired maximum response time.


20/57

Although enough care is taken to test the system as per the documented

specification, it is almost always a confusion regarding how the user will use

the end product. In case there is one customer, a series of acceptance tests are

carried out to validate all the user requirements. But this is not possible if the

software is to be used by many customers. An alternate approach is

application of Alpha and Beta testing techniques.

Alpha Testing:

Alpha testing is carried out by the customer at developers site.

The customer uses the software and records the error\bugs and usage

problem. Alpha testing is carried out in a controlled environment.

Beta Testing:

Beta testing is carried out at one or more customers site by the endusers. It is live testing of software product and not controlled by the

developer.The customer tests the software using her\his own data records and reports

the bugs or problems in intervals to the developer.


21/57

The SDLC is a highly linked set of phases where output of one phase serves

as input to the subsequent phase. Throughout the system development life

cycle, the systems development project needs to be carefully planned and

managed. Therefore, the larger the project, the greater is the need for project

management.


22/57

Case Study of Bank Management System

The problem is to computerize management system of bank. In this

bank, the data entry and recovery procedures are all manual and this takes

a lot of time and energy to browse through the pages of the registers for

locating the relevant information.

This current manual system of the bank is very tough and time-

consuming and chances of getting errors get very high. This method is

not trustworthy. This problem can be solved in the following steps:

Project Initiation and planning

The main objective of this project is:

1. To provide the user with an easy and fast interface.

2. To see that information handling is very easy and fast.

3. Easy updating and modification of data.

4. The basic function is to automate the basic functions of the bank.


23/57

Fixed or variable costs and benefits

Some costs and benefits are constant; regardless of how well a

system is used fixed costs are sunk costs. They are constant and do not change.

Once encountered, they will not recur. Examples are straight-line

depreciation of hardware, exempt employee salaries and insurance.

I contrast, variable costs are incurred on a regular basis. Theyare usually proportional to work volume and continue as long as the system

is in operation. For example, the cost of computer form vary in proportion to

the amount of processing or the length of the reports required.

Fixed benefits are also constant and do not change. An example isa decrease in the number of personnel by 20 percent resulting from use of a

new computer. The benefit of personnel savings may recur every month.

Variable benefits, on the other hand are realized on the regularbasis. For example, consider a safe deposit tracking system that saves 20

minutes preparing customer notices compared with the manual system.

The amount of time saved varies with the number of notices produced.


24/57

SOFTWARE DEVELOPMENT PROCESS

In Bank Management System , first of all when user runs this programa main menu appears on the screen & it provides the introduction of the

project. After this some options will be displayed and you can choose a option

among these.

In the development of software, there are seven step which are as follows:

System analysis / Feasibility study

Software Analysis

Designing ( ERDs / DFDs )

Coding

Testing

Implementation

Maintenance

This interconnection of all seven step is shown in its figure. It is possible to

go back to any previous stage due to some unexpected results.


25/57

DEVELOPMENT OF SUCCESSFUL SYSTEM

Project initiation

and Planning

Project Identification

Analysis

Physical Design

Implementation

Maintenance

Logical Design


26/57


27/57


28/57

SYSTEM DEVELOPMENT LIFE CYCLE

Most organizations find it beneficial to use a set of step, called a system

development methodology , to develop and support their information system .

Like many processes, the development of information system often follows a

life cycle. The system development life cycle (SDLC) is common methodology

for system development in many organizations, featuring various phases that

mark the progress of the system analysis and design effort.

Although any life cycle appears at first glance to be a sequentially

ordered set of phases but actually it is not. The specific steps and their

sequence are meant to be adapted as required for a project, consistent with

management approach. For example, in any given SDLC phase, the project

can return to an earlier phase, if necessary. If a commercial product does not

perform well just after its introduction, it may be temporarily removed from

the market and improved before being re-introduced. In the system

development life cycle, it is also possible to complete some activities in one

phase in parallel with some other activities of another phase.

Sometimes, life cycle is iterative that is, phases are repeated as

required until a satisfactory and acceptable system is found. Such an iterative

approach is special characteristic of rapid application development methods,

such as prototyping. Some people consider life cycle is spiral, in which we

constantly cycle through the phases at different levels of detail. The life cycle

can also be thought of a circular process in which the end of the useful life of

one system leads to the beginning of another project that will develop a new

version or replace an existing system altogether. However, the system

development life cycle used in an organization is an orderly set of activities

conducted and planned for each development project? The skills of a systemanalyst are required to be applied to the entire life cycle.


29/57

PHASES OF SYSTEM DEVELOPMENT LIFE CYCLE

SDLC consists of mainly seven steps. These are:

1) Project identification and Selection

2) Project initiation and planning

3) Analysis

4) Logical Design

5) Physical Design

6) Implementation

7) Testing

Project Identification and Selection

The first phase in the SDLC is called project identification and

selection. In this phase, the user identifies the need for a new or improved

system. In large organization, this identification may be part of a system

planning process. Information requirements of the organization as a whole

are examined and project to meet these requirements are proactivelyidentified.

The organizations information system requirements may result

from requests to deal with in current systems procedures, from the desire

to perform additional tasks, or from the realization that information

technology could be used to capitalize on an existing opportunity.


30/57

These need can then be prioritized and translated into a plan for

the Information system department including a schedule for developingnew major system.

In smaller organizations, determination of which system to develop

may be affected by user request submitted as the need for new or enhanced

system arises as well as from a formal information planning process. In

either case, during project identification and selection, an organization

determines weather or not resources should be devoted to the development

or enhancement of each information system under consideration. The

outcome of the project identification and selection process is a determination

of which system development project should be undertaken by the

organization at least in terms of an initial study.

Project Initiation and Planning

The second phase is project initiation and planning. The problemsthat are identified should be investigated and a decision to implement the

information system or not for the organization should be taken. A critical

step at this point is determining the scope of the proposed system. The projectleader and initial team of system analysts also produce a specific plan for the

proposed project, which the team will follow using the remaining SDLC step.

Now, the baseline project plan customizes the standardized SDLC and

specifies the time and resources needed its execution.

The formal definition of a project is based on the likelihood that

the organizations information system department is able to develop a system

that will solve the problem or use the opportunity and determine whether the

costs of developing the system outweigh the benefit it could provide. The

project leader and other team members usually make the final presentation


31/57

with the subsequent project phases to someone in management or to

a special management committee with the job of deciding whichprojects the organization will undertake.

Analysis

Analysis is the next phase. During this phase, the analysis has

several sub-phases. The first requirements determination the expectations

of users from the proposed system. This sub phase usually involves a

careful study of users from the proposed systems; manual or computerizedthat might be replaced or enhanced as part of this project. Next, the

requirements are studied and structured in accordance with their inter-

relationships and eliminate any redundancies. Third, alternative initial

design is generated to match the requirement. Then, these alternatives

are compared to determine which alternative best meet the requirement

in terms of cost and labor to commit to development process.

In this phase, feasibility study of proposed system is also

performed. Various types of feasibility are:

Technical feasibility

Economic feasibility

Behavioral feasibility

Operational feasibility

Legal feasibility

Time feasibility

If the proposed system is not feasible to develop, it is rejected at this


32/57

very step. The output of the analysis phase is a description if ( but not

are detailed design for) the alternative solution recommended by theanalysis team. Once, the recommendation is accepted by those with

funding authority, you can begin to make plans to acquire any hardware

and system software necessary to build or operate the system proposed.

[ System design ]

After analysis phase is complete, design of the system begins. The design

consists of logical and physical design of the system. The fourth and fifth

phase are devoted to design of the new and enhanced system . During design,

you must design all aspects of the system from input and output screens to

reports, databases, and computer processes. Design occurs in two phases,

viz, Logical and Physical Design.

Logical Design

Logical design is not tied to any specific hardware and systems

software platform . Theoretically, the system could be implemented on any

hardware and system software. The idea is to mark sure that the system

functions as intended. Logical design concentrates on the business aspects

of the system.


33/57

Physical Design

In physical design, the logical design is turned into physical or

technical specification . For example, you must convert diagram that map

the origin, flow, and processing of data in system into a structured system

design that can be broken down into smaller unit, smaller unit known as

modules for conversion to instruction written in a programming language.

You design various parts of the system perform the physical operation

necessary to facilitate data capture, processing, and information output.

During the physical design, the analyst team decides the

programming language in which the computer instruction will written in,which database system and file structure will be used for the data, the

platform that will be used and the network environment under which the

system will be run. These decisions finalize the hardware and software plans

initiated at the end of the analysis phase. Now, proceedings can be made with

respect to acquisition of any new technology not already present into the

organizing. E-R diagrams and Data Flow Diagrams are also the part of

designing.

E-R DIAGRAMS

P.P. Chen introduced not only E-R model but also corresponding

diagramming technique. It uses three features to describe data.

These are the following:

Entities:

An entity is a person, place, thing or event of interest to the

organization and which data are captured, stored or processed.


34/57

Attributes:

Various types of data items that describe an entity are

known as attributes.

Relationship:

An association of several entities in Entity- Relationshipmodel is called relationship.

E-R DIAGRAM FOR BANKING ENTERPRISE

Rectangle

Oval

Diamond

Line

Represent

Entity Set

Represent

Attributes

Represent

Relationship among

entity set

Links attributes to

entity sets and entity

sets or relations

BRANCH CITY


35/57

DATA FLOW DIAGRAM

BRANCH

LOANBRANCH

CUSTOMERSREET

CUSTOMERCITY

LOAN-PAYMENTPAYMENTDATEPAYMENTDATE

PAYMENT

NUMBER

TYPE

ACCESS DATEA/C

NUMBER

IS

AWORK

SFOR

SAVING A/C

DEPOSITER

EMPLOYEE

NAME

MANAGER

WORKER

CUSTOMERNAME

CUSTOMER

ACCOUNT

OVERDRAFTAMOUNT

E SOCIALSECURITY

DEPENDENTNAME

TELEPHONENUMBER

START DATEEMPLOYEE

LENGTH

BRANCHNAME

ASSETS

LOAN

SOCIAL

SECURITY

PAYMENTBORROWER LOAN-

PAYMENT

PAYMENTAMOUNT

EMPLOYEE

CUURENT A/C

INTEREST

RATE

CUST.BANKER

BALANCE


36/57

When solving a problem, the entire problem can be tackled at once.

for solving large Problems, the basic principles the time-tested principle ofdivide and conquer. Clearly, dividing in such a manner that all the

divisions have to be conquered together is not the intent of the wisdom. This

principle, is elaborated, would mean, divide into smaller pieces, so that each

piece can be conquered separately.

Problem partitioning, which is essential for solving a complex problem,

leads to hierarchies in the design. That is, the design produced by using

problem partitioning can be represented as hierarchy of components. The

relationship between the elements in this hierarchy can very depending on the

method used. For example, the most common is the whole-part of

relationship. In this the system consists of some parts, each part consists of

sub parts, and so on. This relationship can be naturally represented ashierarchical it must easier to comprehend a complex system. Due to this, all

design methodologies aim to produce a design that has nice hierarchical

structures.

The DFD was first designed by Larry Constantine as way of expressing

system requirements in a graphical form; this led to a modular design. A

DFD, also known as Bubble chart, has the purpose of clarifying system

requirements and identifying major transformations that will become

programs in system design. Do it is the starting point of the design phase that

functionally decomposes the requirements specifications down to the lowest

level of detail. A DFD consists of series of bubbles joined by lines represent

data flows in the system.

DFD SYMBOLS

In the DFD, there are four Symbols.

1- A square defines a source (originator) or

destination of system data.

2- An arrow identifies data flow-data in motion. It is pipeline through

which information flows.

3- A circle or a bubble ( some people use an oval bubble ) represents a

process that transforms incoming data flow into outgoing data flow.


37/57

4- An open rectangle is a data store-data at rest, or a temporary repositoryof data.

[ SYMBOLS ] [ MEANING ]

The final product of the design phase is the physical system

specification in a form ready to turned over to programmers and other

system builders for constructions. The physical system specifications are

turned over to programmers as first part of the implementation phase.

Source may be one destination transaction

Data Flow

Process that transforms Data Flow

Data Store


38/57

Implementation

During implementation, you turn system specifications into

working system that is tested and put into use. Implementation includes

coding, testing and installation.

During coding, programmers write programs that make up the system.

During testing programmers and analysts tests the individual programs

and the entire system in order to find and correct errors. During

installation, the new system become a part of the new hardware and users

are introduced to new system and trained. The analysts begin planning for

testing and installation as early as the project initiation and planning

phase, since testing and installation require extensive analysts in order to

develop the right approach.

Installation of system can be done in the following three ways:

Direct conversion : This is abrupt approach. The old systemis shutdown and the new system starts. These kinds of conversion

although

economical, the users are at the mercy of the new system, hence direct

installation can be very risky. Some times due to procedural reasons where

two systems fail, there is no to start the old system as a backup as it has been

shutdown. This kind of conversion plan is often the least preferred for critical

business applications.

Pilot conversion : This is the middle path approach. Insteadof converting all at once throughout the organization, this kind of Pilotinstallation involves conversion/ installation of system at a single pre-


39/57

decided location. The location may be branch office of the organization.

Proper selection of the pilot site is important, as it should be able to performa true conversion process to test all functionalities of the new system. The

advantage of the pilot conversion is that the potential risk in case of failure of

the system is limited to a single location. Once the user is ascertained that the

implementation of the system has been successful in a particular location, it is

proposed to replicate the system in order locations.

Although this kind of pilot conversion plan is beneficial for the user, it

places a substantial burden on the implementation team, as it has to maintain

two system in parallel.

Parallel conversion : In this type of conversion, both the oldand new systems are run in parallel for some tome. After monitoring

the new system for a reasonable period of time and if it is performing

well, then, the new system is implemented replacing the old one. Errors

and bugs identified with the new system are not detrimental for normal

functions are resumed by the old system. Parallel conversion is costly

as two system are run in parallel, but the results of only one system are

used for business operation. It is least risk prone.

Phased conversion : In this type of conversion, the system isinstalled module. It is an incremental approach to switch over to the

new system. Different sub-system of the new system is used in

conjunction until the whole new system is converted. This kind of

approach for conversion limits the potential risk of failure of the new

system.

In a phased installation as a sub-system is made functional, actual result arevisible before the whole new system is made functional,


40/57

Implementation activities also include initial user support such as the

finalization ofdocumentation, training programs, and user assistance. Note

that documentation and training programs are finalized during

implementation. Document is produced through the life cycle. Implementation

can continue for as long as the system exists since ongoing is also part of

implementation. Despite the efforts of analysts, managers and programmers,

however, installation is not always a simple process. Many well-design system

can fail if implementation is not well managed. The management of

implementation is usually done by the project team.

Maintenance

The final phase is maintenance. When a system is an operating in an

organization, user sometimes find problem with how it works and often think

better ways to perform its functions. Also, the organizations requirement

with respect to the system changes with time. During maintenance,

programmers make the changes that user ask for and modify the system to

reflect and support changing business condition. These changes are necessary

to keep the system running and useful. Maintenance is not separate phase but

a repetition of the other life cycle phase required to study and implement the

needed changes, thus, maintenance is an overlay to the life cycle rather than a

separate phase. The amount of time and effort devoted to maintenance

depends a great deal on the performance of the previous phase of life cycle.


41/57

There comes a time, however, when an information is no longer performing

as desired, when maintenance cost becomes prohibitive, or when theorganizations needs has changes substantially.

Such problem are an indication that it is the time to being designing the

systems replacement, therefore, completing the loop and starting the life

cycle again. Often, the distinction between the major maintenance and new

development is not clear, which is another reason why maintenance often

resembles the life cycle itself.

Maintenance is of four types:

1) Corrective maintenance

2) Adaptive maintenance

3) Perfective maintenance4) Preventive maintenance

1. Corrective Maintenance :

This type of maintenance is to rectify design, coding and implementation

problems detected after the implementation of the system. This kind of

problem generally surface immediately after the system is implement. This

type of problem needs immediate attention as it hampers the day todaywork of the end user. Proper development process can minimize corrective

maintenance.


42/57

Analysis

Is it feasible to automate the system? The three major areas to

determine the Feasibility of project are given below :

Technical Feasibility : The current level of technology cansupport the proposed system. The proposed software is enabled to meet all

the objectives of the system and the output received would be more

efficient. So, the project is technical feasible.

Economic Feasibility : Theproposed system needs to gethardware and software installed. The short-term costs are

overshadowed by the long term gains. The management question can

invest in the system and is in condition to pay for the cost of systems

study, cost of employees time involved in the study and the cost of

development of software. Thus, project is economically feasible.

Operational Feasibility : The current system faces a lot ofproblems, which would be removed in the proposed system . The

employees of the system will be free from the burden of the paperwork and a lot of confusion. The employees are themselves interested

in getting the manual system replaced by the automated one. The

proposed system is user-friendly. So, even a layman can use it. Thus, it

is operationally feasible.

Design

Once it is found that the project developed is feasible, Design has to be

developed for the requirement listed in the analysis phase.

Data Dictionary

A data dictionary is catalogue of all elements in a system . It consists

of data about data.

It is documents that collect co-ordinates and confirms what specific

data terms mean to different people in the team.


43/57

The United Bank makes certain computerized facilities in their bank toimplement customer records and their daily transaction records. The

bank keeps certain information as follow:

INITIAL. dat:acc_no : Account number

name : Name of the Accountee

address : Address of the Accountee

balance : Initial balance of the account

When the any customer will be create an account, the bank will keep the

above fields in their INITIAL.dat file as master account holder.

BANKING.dat:acc_no : Account number

type : Transaction type by Cash/Cheque

dd,mm,yy : Date of transaction

tran : Transaction for Deposit or Withdraw

interest : Interest rate

amount : Transaction amount

balance : Current balance after transaction

While inputting the data record the following validation will check:

- the account numbers will generate automatically

- the name, address should not blank

- transaction date will be the system date/current date

- initial deposit for any account not less than ` 500/-- daily transaction will be entered either the word Cash/Cheque

and D for deposit and W for withdraw

Write a menu driven program for making a daily transaction process for thedisplaying following menu options.

1. Open New Account

2. List of Accounts

3. See Individual Account

4. Daily Transaction

5. Monthly Report

6. Edit Account

In the edit account menu the following processing will occur:


44/57

1. Modify Account2. Close Account

3. Quit

This project is developed using C++ class concept and having number of

different user defined function (UDFs) as follows:

line_hor(.....)

This function passes four parameter including three integer and one

character to draw different lines to design the screen beautiful. Thecharacter parameter draw the ASCII character line-by-line on screen.

So, for horizontal line draw this function is useful.

line_ver(.....)

The DRAW_VER(.....)function is helpful for drawing vertical lines on

screen to design either menu or program forms for data entry, modify,

display, delete etc..

box(.....)

This function creates different size of boxes on screen according to the

respective parameters. Out of all the parameters they draw boxes till the

limit you want.

main_ menu(.....)

This is the main screening menu which will display your 6 different prompts

and having different activities. Each prompt is connected with different

functions to perform the respective purposes. Out of all the options the last

one produces another sub-menu for modifying and deleting existing accountinformation.

While handling the main menu you can press any selective number to

perform the operation or press () (Zero) to exit from the main menu . But

it is also helpful in almost all menus that, you can press () (Zero) to exit

from the respective menu.

edit_menu(.....)


45/57

This is one of the sub function which is connected from the main_menu ()function to perform the modification and deletion operation on banking

account data from INITIAL.dat and BANKING.dat data file.

All the ways the menus are perform the operation according to the account

number (accno) except the Open New Account of main_menu()function

because, the Open New Account form automatically creates the account

number after a brief search to the existing account numbers. Basically, the

numbers are generating automatically, like your 1, 2, 3 ... respectively.

add_to_file(.....)

The function add_to_file is used to append new account details into the

INITIAL.dat file. This function receives all the fields as parameter way

from the new _account()function and adds in the data file.

display_list()

This function is used to display all the account data in the screen. Which

display the acconto#, name, address and their respective balance amount in

bank. Also show the total bank balance in the screen. All the records are

extracted from INITIAL.dat data file.

delete_account()

This function is used to delete the account details from INITIAL.dat data file.

This is a copy method which transfers all the records except deleted accno#.

And on the same way the records are reversed from the TEMP.dat file to the

original data file INITIAL.dat.

update_balance()

When there is a fresh transaction happens on an existing account eitherdeposit (D) or withdraw (W), then the respective balance has to updated in

the INITIAL.dat data file. While the transactions complete, the balance

amount is overwritten in the data file. This technique occurs by locating the

position in the data file only.

modify()


46/57

When there is any modification occurs to the account name and addressor to the balance mount, the simultaneously it becomes modified in the

INITIAL.dat data file through the modify_account() function. This process

highly depends on the key field account number.

last_accno()

When a new record has to append into the data file, it has to create an

automatic accno#. This process happens when we know the last account

number. To know the last account number by using the last_accno()

function. After finding the last account no. it returns the last account value

into the new_ account()function for generating next account number.

found_ account()

To do any operation: either for modification, deletion, report(s) or updating,

every time the found_ account()function first checks the account which is

entered by the user is their in the INITIAL.dat data file or not. If it is their

a true value is returned else a false value is returned. While depending the

value further process can occurs.

*return_name()

When any reports are occur, on top of the report the account name is

displayed. This function returns the name of the account holder and

displays in appropriate report.

*return_address()

When any reports occur, on top of the report the account address is

displayed. This function returns the address of the account holder and

displays in appropriate report.

give_balance()

While daily transaction is occurs, the last balance is always required to

update the INITIAL.dat data file. So, to know the last balance at the time

of daily transaction the give_balance function returns the value to the

transaction() function.

recordno()


47/57

Either for new_account, update account, or modify account, or modifybalance the recordno() function finds the record position of existing account

no. in the data files, where the transacted re cord can over written.

display()

The function is use d to display the account detail from either INITIAL.dat

or BANKING.dat data file. While the modify() function actives, the accno

parameter searches this account details from the respective file to display

on the screen before modify.

modify_ account()

This function is used to modify the existing accounts name and address at

the existing location. To modify the account it first searches the accounts

location and over written at the same location using seekg() function.

new_ account()

This function is use d to create a new account of a customer after entering

all the details of the same. In this screen the automatic account number is

created and a proper validations are their into name, address and initial

deposit. After entering all the information related to the customer, the

records are appended in the INITIAL.dat and BANKING.dat data file by

using a function add_to_file of both class initial and account.

close_ account()

On the same way like delete_ account() function, the close_ account()

function also closes all the transaction record in BANKING.dat data file.

After closing the account there is no transaction records are in the data files.

display_ account()

This function is used to display all the transaction including the initial deposit

in the screen. This is a global report to display all the transaction records in

screen. It shows all the deposits and withdraw column and date wise balance

also.

transaction()


48/57

This transaction() function provides a screen for making daily transaction.While transaction it show the balance amount, and then either a transaction

for deposit(D) or withdraw(W) on either CASH or CHEQUE. Then the

transacted record is updated in the INITIAL.dat and BANKING.dat data

file. Also the same functions used two important function update_balance()

and add_to_file to update balance in INITIAL.dat data file and the transacted

record in BANKING.dat data file.

clear()

The function is used to clear the screen from a specified row and column

position.

month_report()

Like any other banking transaction, when a customer want his monthly

report

this function helps to generate the repot on the screen. When you enter a date

an account number, it searches all the transaction of the previous month of

the enter date and extracts a previous balance (B/F...) amount first on the

screen and then the entered month all the transaction on the screen . Finally

shows the current balance amount also.

add_to_file()

This function is used to append new record into BANKING.dat data file.

While the function actives, it passed all the fields as parameter into the

function and appends as a fresh record into the file.

delete_ account()

This function is used to delete the account from the BANKING.dat data file.

This is a copy method to delete the account from file.

no_of_days()

This function is used to find total number of years, months and days between

two days.


49/57

box_for_display()

This function is used to display the heading of the report as:

Date Particular Deposit Withdraw Balance


50/57

[ Input Design ]

This input design of this project is as follows. Point considered for the design

of easy to fill out from are given below which conforms to the design of the

project:

Designing form with proper flow.

Logical grouping of information.

Labels holding suitable caption & textboxes to accept the data.

Usage of other tools, such as radio buttons, checkboxes, combo

boxes etc.

also serve purpose for the better recording, processing, storing andretrieval of information.

The appearance of the form has been tried to be kept as attractive as

possible to help in better and logical organization of details.

Since e know good screen design like good form design is an important

instrument.

For steering the course of work, our design of input is guided by the

following six objectives:

Effectiveness

Accuracy

Ease to use

Consistency

Simplicity

Attractiveness

Our screens show only that data which is necessary for the particular

action being undertaken.

Screens are kept consistent by locating information in the same area

each time a new screen is accessed.

We have made it easy to move from one screen to another through the

use of icons, which channels the way to other screens apart from direct

access to screens through the main menu.

Rather than jamming all data onto one screen and cluttering up the

screens, we have made use of multiple screens which add the user appeal,

thus are more productive and are prone to less errors.


51/57

Data Capture Information

a) Identification of dataThe identifying data item in each transaction recode is called KEY.

Therefore details of account holder are identified by the unique account

number.

b) Details of the retrieval systemThis in which reference to the stored data can be quickly retrieved

from the system files. This is done when we perform search on a

particular criterion to draw the records or details of the search

parameters.

c) Output designUser generally merit the system by its output. Thus, in order to create

the most useful output, system analyst works closely with the user

through the interactive process, until the result is considered to be

satisfactory.

The objectives of the output design are:

1. Serve the intended purpose.

2. Output should satisfy the user.

3. Assured output where is needed.

4. Output on time.

5. Choose appropriate output methods.

i.) Reports.

ii.) Message ( on screen).

iii.) Document on help.

Depending on the circumstance and the contents, the output may be

display or printed. Output contents may originate from these source:

Retrieval from data stores.

Transmission from a process or system activity.

Directly from input source.


52/57

Keeping the above in mind, we have taken best to represent our information

with the most clear and readable output. Our details are convincing enough to

make the decisions fast and accurate.

Our report represent one feature of output to present the various details in

discrete categories. These reports can be viewed on screen as well as can be

kept as a hardcopy in the printed layouts. Our system produces following

reports:

1. List of Accounts.

2. See Individual Account.

3. Individuals Monthly Report.

Data Base Design

The following are various entities along with attributes for the project:

Branch_Details- (bname, bcity, assets)

Customer_Details- (cus_no, cname, caddress, cus_city)

Employee_Details- (emp_no, balance, salary, dept, doj, tel_no)

Saving_Account- (acc_no, balance, interest_rate)

Current_Account- (acc_no, balance, overdraft_amt)

Loan_Details- (l_no, lamt, lbranch)

Payment_Detail- (p_no, paydate, p_amt)

After these step, coding in any programming languages can be done and then

the system will be tested against the requirements of the user. The tested

system will be implemented either by direct conversion or parallel conversion.


53/57

REFERENCES

In my project, for concerning the idea of BANK MANAGEMENT

SYSTEM . I concerned with Mr. Faculty of computer ScienceinAdvance computer Education Institute. Then for data, I refer the books:

Turbo C++ by Robert Lafore.

Object Oriented Programming with C++ by E Balagurusamy.

Introduction to System Development .

Implementation and Security of System & MIS


54/57

ABSTRACT

BANK MANAGEMENT SYSTEM is an automatic bankmanagement system. It is based upon a Bank. Bank provides facilities and

services to its customer.

THE SCREEN OF PROJECT GIVEN AS UNDER :

WELCOME TO THE BANK PROJECT

Through this project your can keep record of daily banking transaction. This

program is capable of holding any no. of account. This program provides your

following services:

In first option you can open new account.

In second option you can see the list of all accounts.

In third option you can see all the transaction of individual

account.

Through fourth option you can do banking

transaction(Deposit/Withdraw).

In fifth option you can take month wise individual account

report.

In sixth option you can modify or delete any account.

Note-: Opening amount should not less that Rs. 500/-.

And last option is quit(Exit to Window).


55/57

CONCLUSION OF THE PROJECT

This project will be very much useful for BANK

MANAGEMENT SYSTEM. It can help to storage the record of the

person and it can update and delete data of the existing records fromtime to time.

And once you record the specific data and other information can be

used in future for searching its record as per the descriptions of the

personal. This project can also use by different banks.

This project gives the persons many facilities. And you can use the

details without any problem, because in this project there are many

menus so you can use it conveniently.


56/57

CODING


57/57

CONTENTS

DESCRIPTION

TITLE OF THE PROJECT

FACULTY CERTIFICATE

ACKNOWLEDGEMENT

OBJECTIVE AND SCOPE OF THE PROJECT

DEFINITION OF THE PROBLEM

USER REQUIREMENT

DETAILS OF HARDWARE AND SOFTWARE USWD

FEATURES OF C++

COST BENEFIT ANALYSIS

TANGIBLE OR INTANGIBLE COST AND BENEFITS

DIRECT OR INDIRECT COST AND BENEFITS

FIXED OR VARIABLE COCT AND BENEFITS

Documents

nehaproject 2pages