nework banking report

8/6/2019 Nework Banking Report

1/35

[T

PROJECT REPORT

NETWORK BANKING

Submitted To:

Mr. .

ACKNOWLEDGEMENT1

2010

Submitted By:

ALAKH.S.DIXIT

ANKIT NIGAM

ABHISHEK

BAJPAI

Th Sem

PRANVEER SINGH INSTITUTE OFTECHNOLOGY


2/35

The completion of this project has been possible due to almighty and the

enduring help and over-lasting guidance of many people. I avail this

opportunity to express my deep gratitude to them.

This project holds a high position in my career. My determination,

knowledge and perseverance have helped me to put my best in this project.

My goal was to give an appreciating and outstanding performance.

The sole efforts of an individual are not sufficient to accomplish the

successful completion of a project. It involves interest & efforts of many

people & so this becomes obligatory on my part to record my thanks to

them.

Any change to the project for its betterment & improvisation are

welcomed.

2


3/35

ABSTRACT

This project entitled NETWORK BANKING has been designed towards

improving the Management of Customer Information in the field offices of

BANKINKG. It maintains deposits, withdrawal, Transfer & and other

basic information of CUSTOMERS.

The project has been an enriching experience for me in the field of

programming and Enterprise Application development. The project has

been developed to fulfil the requirements of the BANK NETWORKS.

The tools and technologies used for developing the software are JAVA for

analysis and design phases, for developing the code for the application and

MS -Access as the back-end tool on Microsoft windows 2007 platform.

3


4/35

ContentsACKNOWLEDGEMENT ............................................................................................. 1

Contents ................................................................................................................ 4

INTRODUCTION ...................................................................................................... 6

1.1 Background .................................................................................................. 7

1.2 Motivation ..................................................................................................... 7

1.3 Realization of the Problem ......................................................................... 7

1.4 Broad outline of work .................................................................................... 7

PROBLEM FORMULATION ....................................................................................... 9

2.1 Detailed description of the project .......................................................... 9

2.1.1 Major Functions ...................................................................................... 9

2.2 Methodology to be used for carrying out the study ......................................9

2.3 Existing System ...................................................................................... 10

2.4 The proposed system ............................................................................. 10

SYSTEM ANALYSIS AND DESIGN ........................................................................... 11

3.1 Defining a System ...................................................................................... 11

3.1.1 System Life Cycle ................................................................................ 11

3.1.2 System Analysis ................................................................................... 12

3.2 Analysis and development of the actual solution ....................................12

3.3 Project Overview ...................................................................................... 13

3.3.1 Product prospective .............................................................................. 13

3.3.2 User Interface ....................................................................................... 13

3.3.3 Hardware Software Interface ............................................................. 13

3.3.4 Memory Constraints ............................................................................. 13

3.3.5 Product Function ................................................................................... 14

3.4 Constraints .............................................................................................. 14

3.4.1 General Constraints .............................................................................. 14

4


5/35

3.4.2 Hardware Constraints ...................................................................... 14

3.4.3 Security Constraints ............................................................................. 14

3.5 Feasibility Study ......................................................................................... 15

3.5.1 Technical Feasibility ............................................................................. 15

3.5.2 Operational Feasibility .......................................................................... 15

3.5.3 Economic Feasibility ............................................................................. 15

3.5.4 Legal Feasibility .................................................................................... 16

3.6 Information Gathering ............................................................................. 16

3.6.1 Information about project: .................................................................... 16

3.6.2 Information Sources: ............................................................................ 16

3.7 DFD ............................................................................................................ 17

3.8 Processing Logic ..................................................................................... 23

3.8.1 FOLDERS :........................................................................................... 23

3.8.2 Data Structures .................................................................................. 24

3.9 Application Architecture ......................................................................... 25

3.10 Database: ................................................................................................ 26

3.11 Input / Output Specification ..................................................................... 26

3.11.1 Screen Layouts .................................................................................. 26

3.11.2 Report Layout .................................................................................... 26

3.11.3 Help Facilities .................................................................................... 26

3.12.4 Connecting to a Database: ................................................................. 27

1. JDBC tool is used to connect the database................................................27

2. It provides a bridge to connect the database through ODBC....................27

3. Data source name (DSN) is created to connect with the database. ..... ... .27

TESTING AND IMPLEMENTATION .......................................................................... 28

4.1 Objectives of Testing:............................................................................... 28

4.2 Types of Testing ........................................................................................ 28

4.2.1 Black Box Testing ................................................................................. 28

5


6/35

4.2.2 White Box Testing ............................................................................... 28

4.2.3 Condition Testing ................................................................................. 29

4.2.4 Data Life-Cycle Testing ........................................................................ 29

4.2.5 Unit Testing .......................................................................................... 29

4.2.6 Functional Testing: ............................................................................... 29

4.2.7 System Testing: .................................................................................... 29

4.3 Various Levels Of Testing ........................................................................ 30

4.3.1 Level 1 Testing (Alpha Testing) ........................................................... 30

4.3.2 Level 2 Testing (Beta Testing) ............................................................. 30

4.4 Quality Assurance ...................................................................................... 31

4.5 System Implementation ............................................................................. 31

4.6 System Specification ................................................................................. 31

4.6.1 Hardware Requirements ...................................................................... 32

4.6.2 Software Requirements ....................................................................... 32

RESULT AND CONCLUSION .................................................................................. 33

5.1 Conclusion .................................................................................................. 33

5.2 Future Scope of Improvement .................................................................... 33

F: Bibliography ................................................................................................ 34

CHAPTER 1

INTRODUCTION

This section presents the background and motivation of the system that has been

designed and prototyped in this project. The section also reviews the objective of the

project.

6


7/35

1.1 Background

In terms of background the NETWORK BANKING has been developed for BANKS.

The System maintains the information regarding TRANSACTIONS of customers.

The application software takes care of database and day to day operations. For the ease

of the user, the web-based application is developed using JAVA and MS-Access. The

different modules were added to the system as per BANKS Desk requirement.

1.2 Motivation

Realizing a higher need of development efforts and the investment of time for

developing uniform, more user-friendly application software for implementation, this

project was started. Keeping use in mind, supporting existing business process

of BANKS appears as a fruitful concept for adding more value. Thereby increasing

quality of services offered.

1.3 Realization of the Problem

The proposed system for BANKS will be implemented as an Intranet application. The

application software will be hosted on the web server located at the BANKS office

located at. The application software will be developed in JAVA. The central database is

based on MS-Access.

The function of the system will be managing CUSTOMERS at various field offices from

the BANKS .It manages information about CUSTOMERS of BANKS at various Field

offices.

1.4 Broad outline of work

Chapter 1 - This chapter has introduced the problem along with brief description of the

project.

Chapter 2 - The second chapter describes the problem formulation. What is the need ofwork?

Chapter 3 - This chapter deals with analysis and design of the system, application of

new system, the hardware and software requirements for implementing the system and

stating the choice of the language used.

Chapter 4 - This chapter discusses the implementation part of the system. The

hardware and software requirement for implementing the system have been discussed.

The operation manual and input requirement to the system have also been taken up in

this chapter.

7


8/35

Chapter 5 - This chapter deals with result and discussion of the new system,

interpretation of the results, and importance of the work.

8


9/35

CHAPTER 2

PROBLEM FORMULATION

Introduction

Problem introduction or problem stating is the starting point of the software

development activity. The objective of this statement is to answer: Exactly what must

the system do? The software project is initiated by the clients need. In the beginning,

these needs are on the minds of various people in the clients organization. The analyst

has to identify the requirements by talking to the people and understanding their needs.It goes without saying that an accurate and through understanding of Software

requirements is essential to the success of the software development effort.

All further developments like system analysis, System design and coding will depend on

how accurate and well understood the requirements are. Poorly analysed and specified

software will disappoint the user and will bring grief to the developer, no matter how

well designed and well coded the software is. Software requirement gathering appears

to be a relatively simple task, but appearances are often deceiving. Chances of

misinterpretation are very high, ambiguity is probable and communication gap between

customer and developer is bound to bring confusion. Requirement understandingbegins with a clear and concise heading, stating in a sentence, the task to be performed.

Then Requirements are described in a technical manner in precise statements.

2.1 Detailed description of the project

System maintains the information about the Customer records. It maintains each and

every record about the customer - regarding their deposits, transfer etc. It maintains

the details of all Customers located at various field offices. The application software

takes care of database and day-to-day operations.

2.1.1 Major Functions

Customer Management

The function of the system will be managing Customers at various field offices .It

manages information about Customers of BANKS at various Field offices.

2.2 Methodology to be used for carrying out the study9


10/35

Studying the existing system - This will involve the amount of information, the

manpower, equipment, space and other resources used for the information storage.

After analysing the existing set-up, this study would suggest a new management set-up.

The benefits and disadvantages of existing and new system would be critically revised.

Cost-Benefit Analysis study will be done.

The database structure and information storage retrieval process will also be studied

and a new system for faster response using operation research techniques will be

designed.

2.3 Existing System

The existing system comprises of a system in which details are to be manually handled.

This is not user friendly.

2.4 The proposed system

It will be able to manage information about Customer in more user friendly way.

This system will manage Customers information at various field offices. User ID and

password has been given to all the field offices so that they can enter their customers

information into central database. Their access to the central database is restricted to

their information only. Various reports based on the data entered by customers at field

offices. These reports are helpful in Manpower management decisions.

10


11/35

CHAPTER 3

SYSTEM ANALYSIS AND DESIGN3.1 Defining a System

Collections of components, which are interconnected, and work together to realize some

objective, form a system. There are three major components in every system, namely

input, processing and output.

INPUT OUTPUT

3.1.1 System Life Cycle

The sequencing of various activities required for developing and maintaining systems in

an ordered form is referred to as System Life Cycle. It helps in establishing

a system project plan as it gives overall list of process and sub-processes required for

developing any system. Here, the system life cycle will be discussed with reference to

the development of NETWORK BANKING.

Broadly, following are the different activities to be considered while defining the system

development cycle for the said project:

Problem Definition

Systems analysis

Study of existing system

Drawbacks of the existing system

Proposed system

System Requirement study

11

Processing


12/35

Data flow analysis

Feasibility study

Systems design

Input Design (Database & Forms)

Updating

Query /Report Design

Administration

Testing

Implementation

Maintenance

3.1.2 System Analysis

System analysis is a logical process; the objective of this phase is not actually to solve

the problem but to determine what must be done to solve the problem. The basic

objective of the analysis stage is to develop the logical model of the system using tools

such as the data flow diagram and elementary data description of the elementary

algorithm. The logical model is subject to review by both the management and the user

who agree that the model does in fact reflect what should be done to solve the problem.

System analysis is not a precise science. It is in fact more of an art, aided by scientific

approach to find definition and recording data. Gathering traditional structures is only

one part of the system analysis. The next step is to examine the data, assess the situation

and looking at the alternatives.

3.2 Analysis and development of the actual solution

A complete understanding of the requirement for the new system is very important for

the successful development of a software product. Requirement Specification is the

foundation in the process of software development. All further developments

like system analysis, designing and coding will depend on how accurate and well

documented the requirement specification is.

Requirement specification appears to be a relatively simple task, but appearance is

often deceiving. There is always a chance of wrong specification because of

communication gap between the user and the Developer. Requirement Specificationbegins with a clear statement of the problem and the task to be performed. Then the

12


13/35

requirement is described in a technical manner in precise statements. After the initial

specification reports are received, they are analysed and redefined through customer

interaction.

3.3 Project Overview

3.3.1 Product prospective

It will be able to manage information about Customer in more user friendly way.

This system will manage Customers information at various field offices. User ID andpassword has been given to all the field offices so that they can enter their customers

information into central database. Their access to the central database is restricted to

their information only. Various reports based on the data entered by customers at field

offices are generated at Headquarters. These reports are helpful in

Manpower management decisions.

3.3.2 User Interface

The system will be having user privileges based menu.

User will have to select the options from the given menu.

The system will be entering the information into the database to generate reports.

The forms will be designed to enter the data.

Buttons will be used to insert, retrieve or modify the data.

Links will be provided to shift from one form to another.

3.3.3 Hardware Software Interface

An Internet Web Server, running IIS, in this case Windows 2000 advanced server is

used to host the application. The application software, Customer Management, is

developed in JAVA. The backend database is MS-Access. The Client systems with

internet facility, equipped with web browser will be able to access the system

3.3.4 Memory Constraints

No memory constraints are applicable. A normal memory configuration is more than

sufficient.

13


14/35

3.3.5 Product Function

It is advisable to have weekly data backups. The system administrator will do the data

recovery. Selection of panel is user-initiated operation, while indent handling is client

initiated

3.4 Constraints

3.4.1 General Constraints

This system will not take care of any virus problem, which might occur either on the

client or the server system. Avoiding the use of pirated software and ensuring that

floppies and other removable media are scanned for viruses before use could minimize

the possibility of viral infection.

Recovery of data after a system crash will be possible only if backups are taken at

regular intervals.

Manual interfaces cannot be fully avoided. Documented proofs like dates etc. will have

to be verified by the concerned staff before entering it into the computerized system

3.4.2 Hardware Constraints

Constraints of the Internet & Intranet will be applicable to the system. The

performance of the system will be dependent on the network conditions like network

congestion, bandwidth etc. The primary memory (RAM) and the secondary memory

(Hard Disk Space) requirement of the system at the client end will be the same as that

required by the web browser and the operating system. At the server end, memory

requirements will be that of the server software (Operating system, Database Software,

etc) and the space required to store the data. The space required to store the data would

increase as more and more records are added to the system.

3.4.3 Security Constraints

User will be authenticated by the use of username and passwords. This does not Provide

complete security and the system could be hacked into.

Assumptions and Dependencies

1. It is assumed that the user is familiar with the basic computer fundamentals.

2. Timely backup of data should be taken to avoid data loss in case of system crash.

14


15/35

3. The use of pirated software should be avoided as it may lead to data loss

and system crashes due to viral infections.

4. Floppies and other removable media should be scanned for viruses before use.

6. It is assumed that the maintenance of the database will be assigned to the authorizedperson only.

7. Only authorized persons will be allowed inside the server room.

3.5 Feasibility Study

The main objective of the feasibility study is to study the technical, operational, logical

and economic feasibility of developing the computerized system. All systems are

feasible, given unlimited resources and infinite time. It is both necessary and prudent to

evaluate the feasibility of the project at System in the study phase itself. The feasibility

study to be conduced for this project involves

1. Technical Feasibility

2. Operational Feasibility

3. Economic Feasibility

4. Logical Feasibility

3.5.1 Technical Feasibility

Technical feasibility includes Risk, Resources availability and technologies.

The management provides latest hardware and software facilities for the successful

completion of the projects. With these latest hardware and software support,

the system will perform extremely well. The system is available through Internet.

3.5.2 Operational Feasibility

In the existing manual system, it is very difficult to maintain and update huge amount

of information. The development of the system was started because of the requirement

put forward by the management of the concerned department. This system will handle

the request in a better way and make the process easier. Thus, it is sure that

the system developed is operationally feasible.

3.5.3 Economic Feasibility

In the economic feasibility, the development cost of the system is evaluated weighing it

against the ultimate benefit derived from the new system. It is found that the benefit,

from the new system would be more than the cost and time involved in its development.

15


16/35

3.5.4 Legal Feasibility

In the legal feasibility, it is necessary to check that the software we are going to develop

is legally correct which means that the ideas which we have taken for the

proposed system will be legally implemented or not. So, it is also an important step in

feasibility study.

3.6 Information Gathering

We have taken an approach of gathering information with sensitivity and precautions.

3.6.1 Information about project:

During the analysis, we collected information from staff members of the BANKS

3.6.2 Information Sources:

We have collected the information about the current system from:

1. Reports

2. Personal staff

3. System Documentation

4. Trainees

5. Existing System

16


17/35

3.7 DFD

Login form

17

loginform

user

Username,password

Verifyin

g user

usertable

Allocating

particular

menu

menutable

Username,

password

userlevel

userlevel

Menuorder,

menugroup,

menutitle,

menulink,

itemorder


18/35

18

Listing

Leave

Details

Findingparticula

r entryUpdating

entry

Adding

new entry

Custome

r

Emp_name,Emp_ID

Emp_nam

e,Emp_ID

Emp_na

me,Emp_I

DType,fr

om,to,

Remar

ks,Dat

e

Type, From,

To, Reason

Type, From,

To, Reason

User

Type, From,

To, Reason

DFD of Leave form


19/35

DFD of Transfer

Dfd of form Customer

19

Select

Region

Finding

particula

r entry

Updating

entry

Adding

new entry

Region,prev_R

egion,prev_sta

tn,

Emp_ID

Prev_reg

n,Prev_st

Region

Customer Posting

User

1

1

1.Emp_name,Prev_Region,Pr

ev_station,new_Region,new_

designation,Date


20/35

20

Listing

Designat

ion

Find

particula

r entry

Update

particula

r entry

GnrlCod

eCustomer

Adding

new entry

Region,

Designation

Designatio

n,

Region

Region,

Designatio

n

1

1.Emp_ID,name,seniority,dob,Desig

,post,

basic.file_no,category,station,dt_

posting,dt_presentstn,dt_entry,po

stname,qualification,description,r

emarks,increment,perm/temp,dt_

comfirmation,dt_leaving,reason_l

eaving

User

1


21/35

21

ListingStation

Finding

Particular

entries

Adding new

entry

Updating an

entry

StationVacancyPositio

n

User

Region,

Station

Region,

Station,

Designatio

n

1.

Date,Sanction_perm,Sanctioned_temp,fillperm_R

,fillperm_T,fillperm_A, fillperm_C

,filltemp_C,filltemp_A,Remarks

DFD of Vacancyposition

1

1

Region,

Station,

Designatio

n


22/35

DFD of CustomerCR

22

Add new

entry of

Customer

CR

Find

particular

Customer

CR entry

CustomerCR

Update

CustomerCR

entry

Region,

Station,

Emp_nam

e,

Emp_ID

User

Region,Station,

Emp_name,Emp_ID

Emp_ID,Cryea

r,Received,re

marks

Listing

Custome

rs

Emp_ID,E

mp_nam

e

Customer

Emp_ID,Crye

ar,Received,

remarks


23/35

3.8 Processing Logic

The NETWORK BANKING has been designed and developed for various field offices

of BANKS to capture the information about customers transactions. Various details

about the customer is entered in the system with all details like Customer name, Date ofbirth, Station, Region, etc. There are some major activities which is taken care of by

the NETWORK BANKING.

NETWORK BANKING

All of the Customer record such as his name, Region, station, his balance detail, , etc., is

entered into the computerized system by the Customers .

The operations and features in this are those that we can see in any other bankings.

There are three levels of users.

Administrator:

He has the power to create account, delete account, edit and update account,

view account, view account logs, client monitoring and port termination.

1) Intermediate Administrator Or Teller:

He has the privilage to deposit money to accounts.

2) Client:

He can view his account, view logs, transfer money, withdraw money,

account options such as change pin, password, etc..

On giving these details, some reports and queries are generated by the system.

3.8.1 FOLDERS :

To make some order, files are placed in separate folders!

"BANKCLIENTS" - contains clients station files.

"BANKSERVER" - contains server files.

23


24/35

3.8.2 Data Structures

The Database of BANKS contains the tables that contain the information related

to system and the data needed to run the software. The tables are discussed in detail:

** BANKSERVER DIRECTORY

1) Server.java (Main File)

2) AccessDbase.java

3) AccessServer.java

4) AdminCreateAcc.java

5) AdminDeleteAcc.java

6) AdminEditAcc.java

7) AdminEntryLevel.java

8) AdminMainMenu.java

9) AdminUpdateAcc.java

10) AdminViewAcc.java

11) AdminViewreport.java

*SERVERDB.mdb (DATABASE)

**BANKCLIENTS DIRECTORY

1) ClientLog.java (Main File)

2) ClientAcctOptions.java

3) ClientDeposit.java

4) ClientMainMenu.java

5) ClientPassPin.java

6) ClientTransMoney.java

7) ClientValidatePin.java

24


25/35

8) ClientViewAcc.java

9) ClientViewLog.java

10) ClientWithDraw.java

**** 11 FILES IN BANKSERVER AND 10 FILES IN BANKCLIENTS..****

3.9 Application Architecture

Most of the users database system is not present at user premises, but clients connect to

it. In our system, the information about personnel and post exist in the central database.

But it needs to be accessed from BANKS offices. So that customers can view, enter or

modify their personal information through their user-id and password. This can bedone only through web based application architecture, as shown in the next

.

25

User

Application

Client (Customers)

Database System


26/35

3.10 Database:

Database is maintained in MS-Access.

3.11 Input / Output Specification

3.11.1 Screen Layouts

For Screen layouts refer annexure Forms Layouts.

3.11.2 Report Layout

For report layout refer annexure Report Layouts.

From the BANKS Portal the user will login by given user ID and password in the login

dialogue box. After user validation the system will display the customized home page

and menu options depending upon user roles and access permissions.

3.11.3 Help Facilities

Document has user manual to the user separately.

Suitable error messages should be flashed on error arising from Data inputs, which iseasily understood by the user.

26


27/35

Choice of Tools and Technologies

Introduction

Technologies and tools are strongly related to the approach of software development.What the tools can or cannot do significantly impact what principles can be used, as

well as what objectives can be fulfilled. While selection of a particular methodology may

imply use of certain tools, the tools themselves often leave significant room for

developers to choose how to use them. The selection has therefore been based mainly on

the objectives of the project, while the methodologies were selected after the tools were

selected, due to the fact that technologies and tools poses certain restrictions of how

development can be done.

3.12.4 Connecting to a Database:

1. JDBC tool is used to connect the database.

2. It provides a bridge to connect the database through ODBC.

3. Data source name (DSN) is created to connect with the database.

27


28/35

CHAPTER 4

TESTING AND IMPLEMENTATION4.1 Objectives of Testing:

This section introduces the concept of testing and how important is, for the successful

implementation of the project. Different phases of testing are described along with the

level of testing incorporated in this particular project.

Testing is vital to the success of any system. Testing is done at different stages within the

phase. System testing makes a logical assumption that if all phases of the system are

correct, the goals will be achieved successfully. Inadequate testing leads to errors that

may come up after a long time when correction would be extremely difficult. Another

objective of testing is its utility as a user-oriented vehicle before implementation. The

testing of the system was done on both artificial and live data.

Testing involves operation of a system or application under controlled conditions and

evaluating the results (e.g., if the user is in interface A of the application while using

hardware B and does C, then D should not happen). The controlled conditions should

include both normal and abnormal conditions.

Typically, the project team includes a mix of testers and developers who work closely

together, with the overall QA processes being monitored by the project managers.

4.2 Types of Testing

4.2.1 Black Box Testing

Also known as functional testing, this is a software testing technique whereby the tester

does not know the internal working of the item being tested. Black-box test design treats

the system as a black-box, so it does not explicitly use knowledge of the internalstructure. Black-box test design is usually described as focusing on testing functional

requirements. Synonyms for black-box includes: behavioral, functional, opaque-box

and closed-box.

4.2.2 White Box Testing

White box test design allows one to peek inside the box, and it focuses specifically on

using internal knowledge of the software to guide the selection of test data. Synonyms

for white-box include: structural, glass-box and clear-box.

28


29/35

4.2.3 Condition Testing

An improvement over White-box testing, the process of condition testing ensures that a

controlling expression has been adequately exercised whist the software is under test by

constructing a constraint set for every expression and then ensuring that every member

on the constraint set is included in the values which are presented to the expression

4.2.4 Data Life-Cycle Testing

It is based upon the consideration that in the software code, a variable is at some stage

created, and subsequently may have its value changed or used in a controlling

expression several times before being destroyed. If only locally declared Boolean used in

control conditions are considered then an examination of the sources code will indicatethe place in the source code where the variable is created, places where it is given a

value is used as a part of a control expression and the place where it is destroyed.

This approach to testing requires all possible feasible lifecycles of the variable to be

covered whilst the module is under test.

4.2.5 Unit Testing

The purpose of this phase is to test the individual units of the developing software

component. This phase is recursive and is to be repeated, as many times as there arelevels of testing. In the BANKS project, each individual form has been tested using

techniques of testing namely:

Each individual form has been validated so that user enters only valid data at every

time.

4.2.6 Functional Testing:

This is done for each module / sub module of the system. Functional testing serve as a

means of validating whether the functionality of the system confers the original userrequirement i.e. does the module do what it was supposed to do? Separate schedules

were made for functional testing. It involves preparation of the test data, writing of test

cases, testing for conformance to test cases and preparation of bugs, listing for non-

conformities.

4.2.7 System Testing:

System testing is done when the entire system has been fully integrated. The purpose of

the system testing is to test how the different modules interact with each other and

whether the entire system provides the functionality that was expected.

29


30/35

System testing consists of the following steps:

Program Testing

String Testing

System Testing

System Documentation

User Acceptance Testing

4.3 Various Levels Of Testing

Before implementation the system is tested at two levels:

Level 1

Level 2

4.3.1 Level 1 Testing (Alpha Testing)

At this level, a test data is prepared for testing. Project leaders test the system on this

test data keeping the following points into consideration:

Proper error handling

Exit Points in code

Exception handling

Input / Output format

Glass box testing

Black box testing

If the system is through with testing phase at LEVEL 1 then it is passed on to LEVEL

2.

4.3.2 Level 2 Testing (Beta Testing)

Here the testing is done on the live database. If errors are detected then it is sent back to

LEVEL 1 for modification. Otherwise, it is passed on to LEVEL 3.

This is the level at which the system actually becomes live and implemented for the use

of END USERS.

30


31/35

We have also checked the proposed system for:

Recovery & Security

A forced system failure is induced to test a backup recovery procedure for file integrity.Inaccurate data are entered to see how the system responds in terms of error detection

and protection. Related to file integrity is a test to demonstrate that data and programs

are secure from unauthorized access.

Usability Documentation & Procedure:

The usability test verifies the user-friendly nature of the system. This relates to normal

operating and error-handling procedures.

4.4 Quality AssuranceProper documentation is must for mainframe of any software. Apart from In-line

documentation while coding, help coding, help files corresponding to each program

were prepared so as to tackle the person-dependency of the existing system.

4.5 System Implementation

During the implementation stage, the system is physically created. Necessary programs

are coded, debugged and documented. A new hardware is selected, ordered and

installed.

4.6 System Specification

Every computer system consists of three major elements.

1. The Hardware

2. Application Software such as visual studio.

3. Operating system

For successful operation of the package, following must be kept in mind:

Too many packages should not be used, as very few systems may have all those

packages installed due to memory problem. Thus, the compatibility of

the system developed will get reduced.

31


32/35

4.6.1 Hardware Requirements

Intel Pentium processor at 500 MHz or faster, minimum of 364 MB available disk space

for installation (including IBM SDK), minimum of 256 MB memory,512 MB

recommended, CD-ROM drive.

4.6.2 Software Requirements

The application software is hosted on the BANKS .The application software is

developed in JAVA. The central database is based on MS-Access. The system can be

accessed.

Installation

The Application installation have to be generated from the system where the application

source code is saved and installed where the application is to be run. This was done

using a special code operational modules of the application made available to the end

users successfully.

Implementation

The system is still under construction. Few reports are yet to be made. After that,

this system will be implanted at client side. Users will be given a training to use the

package and special workshops are conducted by BANKS for the purpose. And

according to their feedback the changes are implanted in the software.

32


33/35

CHAPTER 5

RESULT AND CONCLUSIONThis section discuses the result of the work done in this project And also mentions the

future scope for improvement.

5.1 Conclusion

Today we are at the cross roads of innovation. The right direction to take will only

evolve with time, but effort has to be taken seriously by everyone involved in education:

the school/University, administration, faculty, students and parents.

By designing the NETWORK BANKING through JAVA technology, we are able to

provide the basic functionality related to the submission activities with great ease. The

use of JAVA technology has made it easier to design and develop of this application. We

were using the Microsoft Software Development Platform for the development of this

project, which had given a complete, tight and integrated approach for the process of

design and development of this project.

Hence we may conclude that the application system being developed helps a great deal

in modifying the processes at BANKS

5.2 Future Scope of Improvement

The NETWORK BANKING for BANKS is a big and ambitious project. I am

thankful for being provided this great opportunity to work on it. As already mentioned,

this project has gone through extensive research work. On the basis of the research

work, we have successfully designed and implemented NETWORK BANKING.

Front-end-----JAVA

Back-end----MS-ACCESS

33


34/35

F: Bibliography

S. No. Title Author/Publisher

1 GOOGLE INTERNET

2 Software Engineering A .Roger, S. Pressman

Practitioners approach

3 JAVA Complete Reference

34


35/35

nework banking report

Documents