Banking System1

8/9/2019 Banking System1

1/17

09CSA10

Banking System

Contents

Phase 1 Project Analysis and Planning

1.1. Study of the Problem

1.2. Project Scope

1.3. Objectives

Phase 2 Cost stimation

Phase 3 !odeling the "e#uirements

3.1. !odule $escription

3.1.1. %ogin

3.1.2. $eposit And &ithdra' Amount

$etails 3.1.3. (alance $etails

3.1.). !odify

3.2. *!% $iagram

3.2.1. *se case

$iagram 3.2.2. Class

$iagram 3.2.3.

Se#uence $iagram3.2.). Collaboration $iagram

Phase ) Configuration !anagement

).1. S+& "e#uirements

).2. ,+& "e#uirements

).3. -ools

).). Soft'are $evelopment

).).1. orm Creation

).).2. Script

Phase / Soft'are -esting

/.1. Preparing -est Plan

/.2. Perform 0alidation -esting

/.3. 0alidation -est Criteria


2/17

09CSA10

/.). Coverage Analysis

/./. !emory %eas

Synopsis

This is a small scale project for banking system .The basic idea of this

system is the manager of the bank can maintains the details about the customers,

withdraw and deposit amount. It consists of customer details, banking system,

balance details. The manager of the bank can enter the customer’s account number

and get the amount details of that particular customer. In banking system we can

calculate the customer’s account balance based on withdraw and deposit amount.

In the customer details module various details like account number, Name,

deposit amount, withdraw amount, balance are obtained from the user. In the

Display module the total database is displayed. In the balance Details module, the

individual database is displayed which shows the balance details of the particular

customer. y using the !odify module we can modify and update the customer

details on the database stored.


3/17

09CSA10

Phase 1 Project Analysis and Planning

1.1. Study of the Problem

The banking system is critical to businesses and other organi"ations because of the

significant amounts of money involved in customers withdraw or deposit process. This is a

small scale project for banking process. The basic idea is that the manager of the bank maintains

the information such as bank’s name, its branches all over. The customer details maintain the

#ustomer’s account$number , Name along with personal information. The balance details

determine by the deposit and withdraw amount of the customer. This banking system involves

with two types of users.

• %&'(

• )D!INI&T()T*(

USERS R!"E#

The user’s can login+logout the database. e+&he can view his+her personal details,

balance details. The user can just view the information where as he+she could not make changes

in the database.

A$%&'&S(RA(!R R!"E#

The administrator plays a vital role in the banking system. The administrator controls the

entire database. The balance calculations are calculated by the administrator itself. The main role

of the administrator is to safeguard the database.

1.). Pro*e+t S+o,e

The supplementary specification applies to banking process. This specification defines

the non-functional reuirement of the system such as/Functionality:

&ince it stand alone application, a single user may use it at a time.

Usability:

Desktop interface

0indows 12+3444+5p


4/17

09CSA10

Reliability:

The system is available at 36 hours a day, seven days a week.

Performance:

The performance depends on hardware specification

1.-. !b*e+ties

The purpose of this document is to define the reuirements of banking system. This

supplementary specification lists the reuirements that are not readily captured in the use case

model. &upplementary specification and the use case model capture a complete set of

reuirement of the system.

Phase 2 Cost stimation)n estimate is a prediction based upon probabilistic assessment. It is the responsibility of

the project manager to make accurate estimations of effort and cost. This is particularly true for

projects subject to competitive bidding where a bid too high compared with competitors would

result in loosing the contract or a bid too low could result in a loss to the organi"ation. This does

not mean that internal projects are unimportant. 7rom a project leaders estimate the management

often decide whether to proceed with the project. Industry has a need for accurate estimates of

effort and si"e at a very early stage in a project. owever, when software cost estimates are done

early in the software development process the estimate can be based on wrong or incomplete

reuirements. ) software cost estimate process is the set of techniues and procedures that

organi"ations use to arrive at an estimate. )n important aspect of software projects is to know the

cost, The major contributing factor is effort.

/hy SCE is diffi+ult and error ,rone

• &oftware cost estimation reuires a significant amount of effort to perform it correctly.

• ' is often done hurriedly, without an appreciation for the effort reuired.

• 8ou need e9perience at developing estimates, especially for large projects.

• uman bias i.e )n 'stimator is likely to consider how long a certain portion of the

system would take, and then to merely e9trapolate this estimate to the rest of the system,

ignoring the non-linear aspects of software development.


5/17

09CSA10

(he +auses of ,oor and ina++urate estimation

• New software projects are nearly always different form the last.

• &oftware practitioners don:t collect enough information about past projects.

• 'stimates are forced to match the resources available.

).1. Cost and Pri+ing

*ur project is of high range and is highly efficient which can satisfy the payroll calculation

for almost all software companies. The chances of error occurrence is very limited and so our

costs around (s ;4, 44,444 weeks to shape the project.

• There are no specific environmental constraints.

Phase 3 !odeling the "e#uirements

-.1. %odule $es+ri,tion

3.1.1. Login

It is the login session for the )dministrator, %ser and '9it.

3.1.2. Deposit And it!dra" Amount Details

It is used to know the withdraw and deposit amounts of the customer.

3.1.3. #alance Details

It is used to determine the balance details.

3.1.$. %odify

It is used to modify and any update the database.

-.). U%" $iagram

3.2.1. Use case Diagram

%se #ase diagrams show the various activities the users can perform on the

system. The &ystem is something that performs a function. They model the dynamic aspects of

the system. It provides a user’s perspective of the system.


6/17

09CSA10

Actor:

)n actoris a user of the system playing a particular role.

Use case:

%se case is a particular activity a user can do on the system.

Relations!ip:

(elationships are simply illustrated with a line connecting actors to use cases.

account creation

login

deposit

account details db

withdraw

get account balance

customer bank

3.2.2. &lass Diagram

) class diagram describes the types of objects in the system and the various kinds

of static relationships that e9ist among them.i.e.,) graphical representation of a static view on


7/17

09CSA10

declarative static elements.) class is the description of a set of objects having similar attributes,

operations, relationships and behavior.

database

account no : variant

pass word : variant

balance : variant

print()

update()

customer1

name : variant

password : variant

account no : variant

login()

withdraw()

deposit()

bank1

name : variant

age : variant

pass word : variant

account creation()

3.2.3. 'e(uence Diagram

) seuence diagram in %nified !odeling ?anguage


8/17

09CSA10

3.2.$. &ollaboration Diagram ) #ollaboration diagram is very similar to a &euence diagram in the purpose it

achieves@ in other words, it shows the dynamic interaction of the objects in a system. )

distinguishing feature of a #ollaboration diagram is that it shows the objects and their association

with other objects in the system apart from how they interact with each other. The association

between objects is not represented in a &euence diagram.


9/17

09CSA10

) #ollaboration diagram is easily represented by modeling objects in a system and representing

the associations between the objects as links. The interaction between the objects is denoted by

arrows. To identify the seuence of invocation of these objects, a number is placed ne9t to each

of these arrows.

6: provide request details

customer

bank

database

8: check account details9: withdraw/deposit1: create an account

4: login: withdraw/deposit

!: account created11: get mone"/receipt

#: account updated$: request to provide service

1%: updated

Phase ) Configuration !anagement

#onfiguration management is also used in software development, where it is called

%nified #onfiguration !anagement


10/17

09CSA10

.1. S2/ Re3uirements

!S# 0indows

"anguage# Aisual asic

.). 42/ Re3uirements

Intel BII Brocessor with >44 !" speed.

C6 ! ()!

;4! ard disk space.-. (ools

$esign (ool# (ational (ose suite

.. Soft5are $eelo,ment

$.$.1. Form creation

Form 1:


11/17

09CSA10

Form 2:

Form 3:


12/17

09CSA10

Form $:

Form ):


13/17

09CSA10

Form *:

$.$.2 'cript

Coding for form1#

Brivate &ub #ommand;$#lick


14/17

09CSA10

Brivate &ub #ommandC$#lick


15/17

09CSA10

%nload !e

'nd &ub

Brivate &ub #ommand3$#lick


16/17

09CSA10

'nd &ub

Brivate &ub Te9t;$#hange$#lick.(efresh

Data;.%pdate(ecord

%nload !e7orm>.&how

'nd &ub

Brivate &ub #ommand6$#lick


17/17

09CSA10

Phase / Soft'are -esting

7.1. Pre,aring (est Plan

Breparing test plan is the first step in the last phase of software development cycle

.The test plan consists of all the activities that had to be done in the software testing phase. This

test plan has been documented using the rational test manager software.

7.). Perform alidation (esting

&oftware is completely assembled as a package interfacing errors have been

uncovered and a final series of software test validation testing may begin. Aalidation successive

when the customer is satisfied.

7.-. alidation (est Criteria

&oftware validation is achieved through a series of black bo9 test that

demonstrates conformity with reuirements.

7.. Coerage Analysis

#overage analysis is used to identify untested code. %sing rational pure coverage,

untested code can easily be identified.

7.7. %emory "eaks

!emory leak testing has been done using rational purity software.

Result#

ased on the system reuirements specification )NKINL IN7*(!)TI*N &8&T'!

has been designed and implemented.

Banking System1

Documents

Transcript of Banking System1