Financial Management System Capstone Project

8/9/2019 Financial Management System Capstone Project

1/67

INTRODUCTION

The project entitled “Financial Management System " which keep the day by day tally

record as a complete banking or financial system. It can keep the information of Saver

!oaner and Share older and also managed it. The e#citing part of this project is$ itdisplays the day book %rofit and !oss &cc Statistical S'mmary and Interest Information.

SYNOPSIS

The project entitled “Financial Management System " which keep the day by

day tally record as a complete banking or financial system. It can keep the information of Saver !oaner and Share older and also managed it. The e#citing part of this project is$

it displays the day book %rofit and !oss &cc Statistical S'mmary and Interest

Information.

AIM

In the e#isting system the transactions are done only man'ally b't in

proposed system we have to comp'teri(e all the banking transaction 'sing the software

Financial management system.They are)

&dminestrative Mod'le

ADMINISTRATIVE MODULE

This mod'le is the main mod'le which performs all the main operations in

the system. The major operations in the system are)

• &dmin login

• &dd*+elete*,pdate*-iew*Save mployee

• &dd*+elete*,pdate*-iew*Save Member

• Transaction mod'le

• #pendit're mod'le

• Income mod'le

• /ontra mod'le

• +aybook mod'le

• %rofit and !oss

• S'mmary mod'le

0


2/67

SYSTEM STUDY AND ANALISYS

SYSTEM ANALYSIS

System analysis is a process of gathering and interpreting facts diagnosing problemsand the information to recommend improvements on the system. It is a problem solving

activity that re1'ires intensive comm'nication between the system 'sers and system

developers. System analysis or st'dy is an important phase of any system development process. The system is st'died to the min'test detail and analy(ed. The system analyst

plays the role of the interrogator and dwells deep into the working of the present system.

The system is viewed as a whole and the inp't to the system are identified. The o'tp'ts

from the organi(ations are traced to the vario's processes. System analysis is concernedwith becoming aware of the problem identifying the relevant and decisional variables

analy(ing and synthesi(ing the vario's factors and determining an optimal or at least asatisfactory sol'tion or program of action. & detailed st'dy of the process m'st be made by vario's techni1'es like interviews

1'estionnaires etc. The data collected by these so'rces m'st be scr'tini(ed to arrive to a

concl'sion. The concl'sion is an 'nderstanding of how the system f'nctions. This systemis called the e#isting system. 2ow the e#isting system is s'bjected to close st'dy and

problem areas are identified. The designer now f'nctions as a problem solver and tries to

sort o't the diffic'lties that the enterprise faces. The sol'tions are given as proposals. The proposal is then weighed with the e#isting system analytically and the best one is

selected. The proposal is presented to the 'ser for an endorsement by the 'ser. The

proposal is reviewed on 'ser re1'est and s'itable changes are made. This is loop that

ends as soon as the 'ser is satisfied with proposal.%reliminary st'dy is the process of gathering and interpreting facts 'sing the

information for f'rther st'dies on the system. %reliminary st'dy is problem solving

activity that re1'ires intensive comm'nication between the system 'sers and systemdevelopers. It does vario's feasibility st'dies. In these st'dies a ro'gh fig're of the

system activities can be obtained from which the decision abo't the strategies to be

followed for effective system st'dy and analysis can be taken.

EXISTING SYSTEM In the e#isting system the transactions are done only man'ally b't in proposedsystem we have to comp'teri(e all the banking transaction 'sing the software financial

management system.

2. 1.1 PROBLEMS WITH EXISTING SYSTEM

• !ack of sec'rity of data.

• More man power.

• Time cons'ming.

• /ons'mes large vol'me of pare work.

3


3/67

• 2eeds man'al calc'lations.

• 2o direct role for the higher officials.

• +amage of machines d'e to lack of attention.

To avoid all these limitations and make the working more acc'rately the system needs to

be comp'teri(ed.

PROPOSED SYSTEM

The aim of proposed system is to develop a system of improved facilities. The

proposed system can overcome all the limitations of the e#isting system. The system provides proper sec'rity and red'ces the man'al work.

2. 2. 1 ADVANTAGES OF THE PROPOSED SYSTEM

The system is very simple in design and to implement. The system re1'ires very low

system reso'rces and the system will work in almost all config'rations. It has got

following feat'res

• Sec'rity of data.

• ns're data acc'racy4s.

• %roper control of the higher officials.

• 5ed'ce the damages of the machines.

• Minimi(e man'al data entry.

• Minim'm time needed for the vario's processing.

• 6reater efficiency.

• 7etter service.

• ,ser friendliness and interactive.• Minim'm time re1'ired.

2.3. FEASIBILITY STUDY

Feasibility st'dy is made to see if the project on completion will serve the p'rpose of

the organi(ation for the amo'nt of work effort and the time that spend on it. Feasibility

st'dy lets the developer foresee the f't're of the project and the 'sef'lness. & feasibilityst'dy of a system proposal is according to its workability which is the impact on the

organi(ation ability to meet their 'ser needs and effective 'se of reso'rces. Th's when a

new application is proposed it normally goes thro'gh a feasibility st'dy before it is

approved for development.

The doc'ment provide the feasibility of the project that is being designed and lists

vario's areas that were considered very caref'lly d'ring the feasibility st'dy of this project s'ch as Technical conomic and 8perational feasibilities. The following are its

feat'res)

9


4/67

2.3.1. TECHNICAL FEASIBILITY

The system m'st be eval'ated from the technical point of view first. The assessment

of this feasibility m'st be based on an o'tline design of the system re1'irement in theterms of inp't o'tp't programs and proced'res. aving identified an o'tline system the

investigation m'st go on to s'ggest the type of e1'ipment re1'ired method developing

the system of r'nning the system once it has been designed.

Technical iss'es raised d'ring the investigation are)

+oes the e#isting technology s'fficient for the s'ggested one:

/an the system e#pand if developed:

The project sho'ld be developed s'ch that the necessary f'nctions and performanceare achieved within the constraints. The project is developed within latest technology.

Thro'gh the technology may become obsolete after some period of time d'e to the fact

that never version of same software s'pports older versions the system may still be 'sed.So there are minimal constraints involved with this project. The system has been

developed 'sing ;ava the project is technically feasible for development.

2.3.2. ECONOMIC FEASIBILITY

The developing system m'st be j'stified by cost and benefit. /riteria to ens're that

effort is concentrated on project which will give best ret'rn at the earliest. 8ne of thefactors which affect the development of a new system is the cost it wo'ld re1'ire.

The following are some of the important financial 1'estions asked d'ring preliminaryinvestigation)

• The costs cond'ct a f'll system investigation.

• The cost of the hardware and software.

• The benefits in the form of red'ced costs or fewer costly errors.

Since the system is developed as part of project work there is no man'al cost to spendfor the proposed system. &lso all the reso'rces are already available it give an indication

of the system is economically possible for development.

2.3.3. BEHAVIORAL FEASIBILITY

This incl'des the following 1'estions)

Is there s'fficient s'pport for the 'sers:


5/67

The project wo'ld be beneficial beca'se it satisfies the objectives when developed andinstalled. &ll behavioral aspects are considered caref'lly and concl'de that the project is

behaviorally feasible.

SYSTEM DESIGN

3.1 INTRODUCTION

+esign is the first step into the development phase for any engineered prod'ct or

system. +esign is a creative process. & good design is the key to effective system. The

term “design> is defined as “the process of applying vario's techni1'es and principles for the p'rpose of defining a process or a system in s'fficient detail to permit its physical

reali(ation>. It may be defined as a process of applying vario's techni1'es and principles

for the p'rpose of defining a device a process or a system in s'fficient detail to permit its physical reali(ation. Software design sits at the technical kernel of the software

engineering process and is applied regardless of the development paradigm that is 'sed.

The system design develops the architect'ral detail re1'ired to b'ild a system or prod'ct.

&s in the case of any systematic approach this software too has 'ndergone the best

possible design phase fine t'ning all efficiency performance and acc'racy levels. Thedesign phase is a transition from a 'ser oriented doc'ment to a doc'ment to the

programmers or database personnel. System design goes thro'gh two phases of development) !ogical and %hysical +esign.

LOGICAL DESIGN:

The logical flow of a system and define the bo'ndaries of a system. It incl'des the

following steps)

• 5eviews the c'rrent physical system ? its data flows file content vol'mes

fre1'encies etc.

• %repares o'tp't specifications ? that is determines the format content and

fre1'ency of reports.• %repares inp't specifications ? format content and most of the inp't f'nctions.

• %repares edit sec'rity and control specifications.

• Specifies the implementation plan.

• %repares a logical design walk thro'gh of the information flow o'tp't inp't

controls and implementation plan.

• 5eviews benefits costs target dates and system constraints.

PHYSICAL DESIGN:

%hysical system prod'ces the working systems by define the design specifications that

tell the programmers e#actly what the candidate system m'st do. It incl'des the followingsteps.

• +esign the physical system.

• Specify inp't and o'tp't media.

• +esign the database and specify back'p proced'res.

• +esign physical information flow thro'gh the system and a physical design


6/67

• %repare a conversion sched'le and target date.

• +etermine training proced'res co'rses and timetable.

• +evise a test and implementation plan and specify any new hardware*software.

• ,pdate benefits costs conversion date and system constraints

Desi!"S#e$i%i$&'i(! &$'i)i'ies:

• /oncept form'lation.• %roblem 'nderstanding.

• igh level re1'irements proposals.

• Feasibility st'dy.

• 5e1'irements engineering.

• &rchitect'ral design.

MODULE DESIGN

A*+i!

The &dministrator logs in 'sing the admin login. In this mod'le two operations

are done. +'ring login the !ogin and %assword is verified with that in the database

INPUT DESIGN

The design of inp't foc'ses on controlling the amo'nt of inp't re1'ired controlling

the errors avoiding delay avoiding e#tra steps and keeping the process simple. The inp't

is designed in s'ch a way so that it provides sec'rity and ease of 'se with retaining the

privacy. Inp't +esign considered the following things)

o


7/67


8/67

• To str'ct're the data so that there is no repetition of data this helps in saving.

• To permit simple retrieval of data in response to 1'ery and report re1'est.

• To simplify the maintenance of the data thro'gh 'pdates insertions deletions.

• To red'ce the need to restr'ct're or reorgani(e data which new application

re1'irements arise.

RELATIONAL DATABASE MANAGEMENT SYSTEM -RDBMS:

& relational model represents the database as a collection of relations. ach relationresembles a table of val'es or file of records. In formal relational model terminology a

row is called a t'ple a col'mn header is called an attrib'te and the table is called a

relation. & relational database consists of a collection of tables each of which is assigneda 'ni1'e name. & row in a tale represents a set of related val'es.

RELATIONS/ DOMAINS 0 ATTRIBUTES:

& table is a relation. The rows in a table are called t'ples. & t'ple is an ordered set of n

elements. /ol'mns are referred to as attrib'tes. 5elationships have been set betweenevery table in the database. This ens'res both 5eferential and ntity 5elationship

Integrity. & domain + is a set of atomic val'es. & common method of specifying a

domain is to specify a data type from which the data val'es forming the domain are

drawn. It is also 'sef'l to specify a name for the domain to help in interpreting its val'es.very val'e in a relation is atomic that is not decomposable.

RELATIONSHIPS:

Table relationships are established 'sing Dey. The two main keys of prime importance

are %rimary Dey E Foreign Dey. ntity Integrity and 5eferential Integrity 5elationships

can be established with these keys.ntity Integrity enforces that no %rimary Dey can haven'll val'es.5eferential Integrity enforces that no %rimary Dey can have n'll val'es.

5eferential Integrity for each distinct Foreign Dey val'e there m'st e#ist a matching

%rimary Dey val'e in the same domain. 8ther key are S'per Dey and /andidate Deys.5elationships have been set between every table in the database. This ens'res both

5eferential and ntity 5elationship Integrity.

NORMALIATION:

&s the name implies it denoted p'tting things in the normal form. The application

developer via normali(ation tries to achieve a sensible organi(ation of data into proper tables and col'mns and where names can be easily correlated to the data by the 'ser.

2ormali(ation eliminates repeating gro'ps at data and thereby avoids data red'ndancywhich proves to be a great b'rden on the comp'ter reso'rces. These incl'des)

2ormali(e the data.

/hoose proper names for the tables and col'mns.

/hoose the proper name for the data.


9/67

Fis' N(+& F(+)

The First 2ormal Form states that the domain of an attrib'te m'st incl'de only atomic

val'es and that the val'e of any attrib'te in a t'ple m'st be a single val'e from thedomain of that attrib'te. In other words 02F disallows “relations within relations> or

“relations as attrib'te val'es within t'ples>. The only attrib'te val'es permitted by 02F

are single atomic or indivisible val'es.

The first step is to p't the data into First 2ormal Form. This can be donor by moving

data into separate tables where the data is of similar type in each table. ach table isgiven a %rimary Dey or Foreign Dey as per re1'irement of the project. In this we form

new relations for each nonatomic attrib'te or nested relation. This eliminated repeating

gro'ps of data.

& relation is said to be in first normal form if only if it satisfies the constraints that

contain the primary key only.

Se$(!* N(+& F(+)

&ccording to Second 2ormal Form For relations where primary key contains m'ltipleattrib'tes no nonkey attrib'te sho'ld be f'nctionally dependent on a part of the primary

key.

In this we decompose and set'p a new relation for each partial key with its dependent

attrib'tes. Make s're to keep a relation with the original primary key and any attrib'tes

that are f'lly f'nctionally dependent on it. This step helps in taking o't data that is only

dependant on apart of the key.

& relation is said to be in second normal form if and only if it satisfies all the first

normal form conditions for the primary key and every nonAprimary key attrib'tes of therelation is f'lly dependent on its primary key alone.

T4i* N(+& F(+)

&ccording to Third 2ormal Form 5elation sho'ld not have a nonkey attrib'te

f'nctionally determined by another nonkey attrib'te or by a set of nonkey attrib'tes. That

is there sho'ld be no transitive dependency on the primary key.

In this we decompose and set 'p relation that incl'des the nonkey attrib'tes that

f'nctionally determines other nonkey attrib'tes. This step is taken to get rid of anything

that does not depend entirely on the %rimary Dey.

& relation is said to be in third normal form if only if it is in second normal form and

more over the non key attrib'tes of the relation sho'ld not be depend on other non keyattrib'te.

G


10/67

TABLES STRUCTURE

Table) 'sertable%rimary Dey) 'sername

Fie* D&'& T5#e C(!s'&i!'s Des$i#'i(!

'sername /harH0@ %rimary key ,ser name

password 2'mberHG password

Table) employeeJtable

%rimary Dey) emp id


mp id 2'mberHG %rimary key

name charH9K

gender charH9K

+87 date

&ddress charH9K

phone n'mber

cell n'mber joindate date

department charH9K

Table) memberJtable%rimary Dey) member id


+e+6e i* N7+6e-8 Pi+&5 9e5

!&+e $4&-3

e!*e $4&-3

DOB *&'e

A**ess $4&-3

#4(!e !7+6e

$e !7+6e

0K


11/67

;(i!*&'e *&'e

'5#e C4&-2

&ccJno n'mber

fee /harH3K

Table) bankJtable

%rimary bank id


6&!9 i* N7+6e-8 Pi+&5 9e5

!&+e $4&-3

'5#e $4&-3

*&'e *&'e

A**ess $4&-3

'('& !7+6eA$$

Table) e#pensetrans

%rimary Dey) emp id


e+# i* N7+6e-8 Pi+&5 9e5

#&'i$7& $4&-37!*e65 $4&-3

*&'e *&'e

$4e=7e *&'e

$&s4 !7+6e

6i* !7+6e

Table) bankwithdraw%rimary Dey) b id


e+# i* N7+6e-8 Pi+&5 9e5

!&+e $4&-3

A$$

*&'e *&'e

00


12/67

&+(7!' N7+6e

Table) bankdeposit%rimary Dey) b id


e+# i* N7+6e-8 Pi+&5 9e5

!&+e $4&-3

A$$

*&'e *&'e

&+(7!' N7+6e

Table) loan%rimary Dey) loan id


(&! i* N7+6e-8 Pi+&5 9e5

Me+6e i* N7+6e

*&'e *&'e

&+(7!' N7+6e

Table) incometransaction

%rimary Dey) emp id


e+# i* N7+6e-8 Pi+&5 9e5

#&'i$7&s C4&-3

*&'e *&'e

Table) saver %rimary Dey) mem id


+e+ i* N7+6e-8 Pi+&5 9e5

'('& N7+6e

03


13/67

7!*e65 $4&-3

*&'e *&'e

$4e=7e *&'e

$&s4 !7+6e

B i* !7+6e

Table) capital

%rimary Dey) amo'nt


#&'i$7&s C4&-3

&+(7!' !7+6e

Table) cash

%rimary Dey) amo'nt


&+(7!' !7+6e

Table) loaninterest

%rimary Dey) mem id


+e+ i* N7+6e-8 Pi+&5 9e5

&+(7!' N7+6e

*&'e *&'e

Table) saverinterest

%rimary Dey) mem id


+e+ i* N7+6e-8 Pi+&5 9e5

&+(7!' N7+6e

*&'e *&'e

09


14/67

Table) share%rimary Dey) mem id


+e+ i* N7+6e-8 Pi+&5 9e5

&+(7!' N7+6e

*&'e *&'e

Table) loaninterest

%rimary Dey) mem id


+e+ i* N7+6e-8 Pi+&5 9e5

&+(7!' N7+6e

*&'e *&'e

0=


15/67

SYSTEM DEVELOPEMENT

>.1 SYSTEM SPECIFICATION

HARDWARE RE?UIREMENTS

%rocessor ) LB /ompatible processor with 0.C 6( /lock speed

5&M ) @03 M7 or more

ard disk ) 3K 67 or more

Monitor ) -6&*S-6&

Deyboard ) 0K= Deys

Mo'se ) 3 b'ttons* 9 b'ttons

SOFTWARE RE?UIREMENTS

8perating System )


16/67

in a te#t bo# can be converted to a n'meric data by 'sing the f'nction -alHte#t. Thefollowing e#ample ill'strates a simple program that processes the inp't from the 'ser.

E@&+#e 3.1

In this program two te#t bo#es are inserted into the form together with a few labels. The

two te#t bo#es are 'sed to accept inp'ts from the 'ser and one of the labels will be 'sedto display the s'm of two n'mbers that are entered into the two te#t bo#es. 7esides a

command b'tton is also programmed to calc'late the s'm of the two n'mbers 'sing the

pl's operator. The program 'se creates a variable s'm to accept the s'mmation of val'esfrom te#t bo# 0 and te#t bo# 3.The proced're to calc'late and to display the o'tp't on the

label is shown below. The o'tp't is shown in Fig're 9.3

%rivate S'b /ommand0J/lickHOTo add the val'es in te#t bo# 0 and te#t bo# 3

S'm P -alHTe#t0.Te#t Q -alHTe#t3.Te#t

OTo display the answer on label 0!abel0./aption P S'm

nd S'b

Fi7e 3.2

3.2.2 T4e L&6e

The label is a very 'sef'l control for -is'al 7asic as it is not only 'sed to provide

instr'ctions and g'ides to the 'sers it can also be 'sed to display o'tp'ts. 8ne of its most

important properties is C'i(!. ,sing the synta# &6e.C'i(! it can display te#t andn'meric data . No' can change its caption in the properties window and also at r'ntime.

%lease refer to #ample 9.0 and Fig're 9.0 for the 'sage of label.

3.2.3 T4e C(++&!* B7''(!The command b'tton is one of the most important controls as it is 'sed to e#ec'te

commands. It displays an ill'sion that the b'tton is pressed when the 'ser click on it. Themost common event associated with the command b'tton is the /lick event and the

synta# for the proced're is

%rivate S'b /ommand0J/lick HStatements

0B


17/67


18/67

e#ample if yo' wish to add a n'mber of items to /ombo bo# 0 yo' can key in thefollowing statements

E@&+#e 3.3

%rivate S'b FormJ!oad H

/ombo0.&ddItem “Item0>/ombo0.&ddItem “Item3>

/ombo0.&ddItem “Item9>

/ombo0.&ddItem “Item=>nd S'b

3.2. T4e C4e$9 B(@

The /heck 7o# control lets the 'ser selects or 'nselects an option.


19/67

%rivate S'b 8ptionBJ/lickHShape0.Shape P @

nd S'b

3.2.1 T4e Di)e Lis' B(@

The +rive !ist7o# is for displaying a list of drives available in yo'r comp'ter.


20/67

SYSTEM IMPLEMENTATION AND TESTING

.1 CODING

Main Form /oding

8ption #plicit%'blic str &s String

+im cflag &s 7oolean

+im mflag &s 7oolean+im flag &s 7oolean+im lstmain0 &s !istItem

+im st &s String

%'blic vbmsgbo# &s -bMsg7o#5es'lt%rivate S'b /heck9J/lickH

nd S'b

%rivate S'b calJ/lickH

Shell H"calc.e#e" vb2ormalFoc's

nd S'b

%rivate S'b /heckTInche1'eJ/lickH If /heckTInche1'e.val'e P 0 Then

lblTIn7id.-isible P Tr'e

combTIn7id.-isible P Tr'e t#tTInche1'e.-isible P Tr'e

lse

lblTIn7id.-isible P False combTIn7id.-isible P False

t#tTInche1'e.-isible P False t#tTInche1'e.Te#t P ""

nd If nd S'b

%rivate S'b chkT#/ashJ/lickH

3K


21/67

If chkT#/ash.val'e P 0 Then t#tT#/ash.-isible P Tr'e

lse

t#tT#/ash.Te#t P ""

t#tT#/ash.-isible P False nd If

nd S'b

%rivate S'b chkT#/he1'eJ/lickH

If chkT#/he1'e.val'e P 0 Then

lbl7ankid.-isible P Tr'e t#tT#/he1'e.-isible P Tr'e

combT#7id.-isible P Tr'e

lse lbl7ankid.-isible P False

t#tT#/he1'e.-isible P False

combT#7id.-isible P False

t#tT#/he1'e.Te#t P " nd If

nd S'b

%rivate S'b cmd&bo'tJ/lickH

SSTab0.Tab P Gnd S'b

%rivate S'b cmd&ddJ/lickH Form3.Show

Frame0.-isible P False

nd S'b

%rivate S'b cmd7ank&ddJ/lickH Frame0.-isible P False

[email protected]

nd S'b

%rivate S'b cmd7ank+eleteJ/lickH

+im a &s Integer st P !ist7ank.Te#t

str P "select from tbl7ank where bJidP" E st

/'stom5ecordSet8pen str


22/67

.Move2e#t .,pdate7atch

Msg7o# "+eleted S'ccessf'lly..."

lse

#it S'b nd If


23/67

!ist7ank.&ddItem UbJid .Move2e#t


24/67

comb/Type.Te#t P ""nd S'b

%rivate S'b cmd/#itJ/lickHnd S'b

%rivate S'b cmd/ditJ/lickH

cmd/Save.-isible P Tr'e

cmd/&dd.nabled P Falsecmd/+elete.nabled P False

cmd/dit.nabled P False

comb/Type.nabled P False

t#t/&ccno.nabled P Falset#t/2ame.SetFoc's

nd S'b

%rivate S'b cmd/SaveJ/lickH

st P !istM.Te#t str P "Select nameaddressgenderphonecelljoinJdatetypeaccJno from member

where mmbrJidP" E st

str P "Select from member where mmbrJidP" E st



25/67

comb/Type.nabled P Tr'e t#t/&ccno.nabled P Tr'e

nd S'b

%rivate S'b cmd/-iewJ/lickH cmd/+elete.nabled P Tr'e

cmd/dit.nabled P Tr'e

If mflag P False Then mflag P Tr'e

st P "Select from member"

/'stom5ecordSet8pen st


26/67

nd


27/67

#it S'b nd If

st P "select amo'nt from tblcash "


If Hres.8F P Tr'e &nd res.78F P Tr'e Then


28/67

nd S'b

%rivate S'b cmd!oanSaveJ/lickH

+im a &s Integer +im b &s String

+im temp &s String

a P Msg7o#H"&re yo' s're..." vb8D/ancelIf Ha P vb8D Then

st P "loan"



29/67

/lose5ecordSet st P "select amo'nt from tblcash "


If Hres.8F P Tr'e &nd res.78F P Tr'e Then


30/67

vbmsgbo# P Msg7o#H"5ecord dit S'ccessf'lly..." vbInformationcmdSave.-isible P False

cmd&dd.nabled P Tr'e

cmd+elete.nabled P Tr'e

cmddit.nabled P Tr'e/lose5ecordSet

nd S'b

%rivate S'b cmdSavingJ/lickH

FormB.ShowForm0.Frame0.-isible P False

nd S'b

%rivate S'b cmdSavingSaveJ/lickH

+im a &s String

+im b &s Stringdbconnection

str P "tblsaver"

/'stom5ecordSet8pen str a P Msg7o#H"&re No' S'reUUU" vb8D/ancel

If Ha P vb8D Then


31/67

nd


32/67

+im a &s Integer +im data &s +ate

data P +T%icker0.val'e

MSFle#6rid3./lear

MSFle#6rid3./ols P @ MSFle#6rid3.Te#tMatri#HK 0 P "+ate"

MSFle#6rid3.Te#tMatri#HK 3 P "%artic'lar"

MSFle#6rid3.Te#tMatri#HK 9 P "+ebit" MSFle#6rid3.Te#tMatri#HK = P "/redit"

st P "select datepartic'lartotal from tbl#penseTrans where date like " E data E ""

/'stom5ecordSet8pen st a P 0


33/67

MSFle#6rid3.Te#tMatri#Ha 9 P "" MSFle#6rid3.Te#tMatri#Ha = P Uamo'nt

.Move2e#t

a P a Q 0

s'm P a


34/67

MSFle#6rid3.Te#tMatri#Ha 9 P "" MSFle#6rid3.Te#tMatri#Ha = P Uamo'nt

.Move2e#t

a P a Q 0

s'm P a


35/67

Upartic'lar P "mid" E "H" E cmbShare.Te#t E "" Uamo'nt P t#tShare&mo'nt.Te#t

.,pdate7atch

nd


36/67

t#tT/apital&mo'nt.SetFoc's #it S'b

nd If

st P "select amo'nt from tblcash "

/'stom5ecordSet8pen st If Hres.8F P Tr'e &nd res.78F P Tr'e Then


37/67

UbJid P combT#7id.Te#t Utotal P t#tT#Total.Te#t

.,pdate7atch

nd


38/67

chkT#/ash.val'e P K chkT#/he1'e.val'e P K

t#tT#Total.Te#t P ""

combT#,nder7y.Te#t P ""

t#tT#Id.SetFoc'st#tTIn.Te#t P ""

t#tTIn%artic'lar.Te#t P ""

checkTincash.val'e P K/heckTInche1'e.val'e P K

t#tTInTotal.Te#t P ""

nd S'b

%rivate S'b cmdTInSaveJ/lickH+im a &s Integer

str P "tblIncomeTrans"


a P Msg7o#H"&re yo' S'reUUU" vb8D/ancel If Ha P vb8D Then


39/67

nd


40/67

/ombo0.Te#t P ""!ist./lear

nd If

nd S'b

%rivate S'b cmd


41/67


42/67

t#t#Total.Te#t P -alHt#t#/ash&mo'nt.Te#t Q -alHt#t#/he1'e&mo'nt.Te#t MSFle#6rid0./ols P @

MSFle#6rid0.Te#tMatri#HK 0 P "+ate"

MSFle#6rid0.Te#tMatri#HK 3 P "%artic'lar"

MSFle#6rid0.Te#tMatri#HK 9 P "/ash" MSFle#6rid0.Te#tMatri#HK = P "/he1'e"

st P "select date partic'lar cash che1'e from tbl#penseTrans where 'nder7y P " E

str E "" st P "tbl#penseTrans"


a P 0


43/67

fle#Income.Te#tMatri#HK = P "/he1'e" st P "select date partic'lars cash che1'e from tblIncomeTrans where 'nder7y P " E

str E ""


a P 0


44/67

Form0.Frame0.-isible P FalseFormG.Show

nd S'b

%rivate S'b fle#IncomeJ/lickH

fle#Income.Sort P 0nd S'b

%rivate S'b FormJ!oadH

dbconnection

SSTab0.Tab P Gnd S'b

%rivate S'b FormJ'n!oadHcancel &s Integer Frame0.-isible P False

nd S'b

%rivate S'b !abel3J/lickH

FormC.Shownd S'b

%rivate S'b listJ/lickH+im str &s String

str P !ist.Te#t

/'stom5ecordSet8pen "select namegenderdobaddressphonecelljoinJdatedepartmentfrom employee where empJidP" E str


45/67

%rivate S'b !ist7ankJ/lickH

st P !ist7ank.Te#t

str P "Select nameaddressdateaccJnotypetotal from tbl7ank where bJidP" E st /'stom5ecordSet8pen str


46/67

+im temp0 &s +o'ble +im temp3 &s +o'ble

st P "select s'mHamo'nt as tot from tbl%l!oanInterest"


t#t%lInInterest.Te#t P resUtot /lose5ecordSet

st P "select s'mHinterest as tot from tbl%lSaverInterest"

/'stom5ecordSet8pen st t#t%l#Interest.Te#t P resUtot

/lose5ecordSet

st P "select s'mHtotal as tot from tbl#penseTrans where 'nder7y like " E"Indirect #penses" E ""


t#tple#.Te#t P resUtot /lose5ecordSet

st P "select s'mHtotal as tot from tbl#penseTrans where 'nder7y like " E "+irect

#penses" E ""

/'stom5ecordSet8pen st t#tpld#.Te#t P resUtot

/lose5ecordSet

st P "select s'mHtotal as tot from tbl#penseTrans where 'nder7y like " E"%'rchase" E ""


t#tplpam.Te#t P resUtot /lose5ecordSet

+im myTotal &s +o'ble

+im flag &s 7oolean

+im ttotal &s +o'ble myTotal P K

flag P False

/'stom5ecordSet8pen "tblIncomeTrans"


47/67

t#t%l+In.Te#t P myTotal nd If

/lose5ecordSet

nd


48/67

nd If If flag P False Then

t#t%l8I.Te#t P "K"

lse

t#t%l8I.Te#t P myTotal nd If

/lose5ecordSet

#it S'b nd


49/67

st P "select s'mHcash as cashtots'mHche1'e as che1'etot from tbl#penseTrans" /'stom5ecordSet8pen st

t#tTtotal.Te#t P resUcashtot Q resUche1'etot

/lose5ecordSet

st P "select s'mHcash as cashtots'mHche1'e as che1'etot from tblIncomeTrans" /'stom5ecordSet8pen st

t#tTIn.Te#t P resUcashtot Q resUche1'etot

/lose5ecordSet st P "select bJid from tbl7ank where typeP&ssets"


combT#7id./lear #pendit're 7ank Id comb+epId./lear +eposit 7ank Id

comb


50/67

st P "Select +istinct ,nder7y from tblIncomeTrans" /'stom5ecordSet8pen st

combIncome./lear


51/67

%rivate S'b fle#JdisplayH+im s'm &s Integer

+im a &s Integer

+im data &s +ate

data P +T%icker3.val'e MSFle#6rid3./ols P @

MSFle#6rid3.Te#tMatri#HK 0 P "+ate"

MSFle#6rid3.Te#tMatri#HK 3 P "%artic'lar" MSFle#6rid3.Te#tMatri#HK 9 P "+ebit"

MSFle#6rid3.Te#tMatri#HK = P "/redit"

st P "select datepartic'lartotal from tbl#penseTrans where date like " E data E "" /'stom5ecordSet8pen st

a P 0


52/67

MSFle#6rid3.Te#tMatri#Ha 3 P U2ame MSFle#6rid3.Te#tMatri#Ha 9 P ""

MSFle#6rid3.Te#tMatri#Ha = P Uamo'nt

.Move2e#t

a P a Q 0 s'm P a


53/67

MSFle#6rid3.Te#tMatri#Ha 3 P "Save &mo'nt 5eceipt MId by " E "H" E UmmbrJid E ""

MSFle#6rid3.Te#tMatri#Ha 9 P ""

MSFle#6rid3.Te#tMatri#Ha = P Uamo'nt

.Move2e#t a P a Q 0

s'm P a


54/67

%rivate S'b Timer@JTimerH

+T%ickerSaving P +ate

nd S'b

%rivate S'b TimerBJTimerH+T%ickerShare P +ate

nd S'b

%rivate S'b TimerCJTimerH

dateloan P +atend S'b

%rivate S'b TimerJTimerHdate


55/67

%rivate S'b t#tShare&mo'ntJ!ostFoc'sH +im a &s +o'ble

a P t#tShare&mo'nt.Te#t

If H-alHt#tShare&mo'nt.Te#t V 9KK 8r H-alHt#tShare&mo'nt.Te#t W @KKK Then

Msg7o# "nter amo'nt between 9KK and @KKK" vbInformation t#tShare&mo'nt.Te#t P ""

t#tShare&mo'nt.SetFoc's

#it S'b nd If

nd S'b

%rivate S'b t#tT#/he1'eJ!ostFoc'sH

st P combT#7id.Te#t

str P "Select total from tbl7ank where bJidP " E st


If -alHt#tT#/he1'e.Te#t VP resUtotal Then Msg7o# "&mo'nt is &vailable..." vbInformation

t#tT#Total P -alHt#tT#/ash.Te#t Q -alHt#tT#/he1'e.Te#t

lse Msg7o# "&mo'nt is not availble"

t#tT#/he1'e P ""

t#tT#/he1'e.SetFoc's nd If

/lose5ecordSet

nd S'b

%rivate S'b t#tTInche1'eJ!ostFoc'sH

t#tT#Total P -alHt#tT#/ash.Te#t Q -alHt#tT#/he1'e.Te#t t#tTInTotal.Te#t P -alHt#tTIncash.Te#t Q -alHt#tTInche1'e.Te#t

nd S'b

@@


56/67

.2 SYSTEM IMPLEMENTATION AND TESTING

Implementation is the stage of the project where the theoretical design is t'rned into a

working system. It can be considered to be the most cr'cial stage in achieving a

s'ccessf'l new system gaining the 'sers confidence that the new system will work andwill be effective and acc'rate. It is primarily concerned with 'ser training and

doc'mentation. /onversion 's'ally takes place abo't the same time the 'ser is being

trained or later. Implementation simply means convening a new system design into

operation which is the process of converting a new revised system design into an

operational one.

.2.1. SYSTEM TESTING

Software Testing is the process of e#ec'ting software in a controlled manner in order

to answer the 1'estion A +oes the software behave as specified:. Software testing is often'sed in association with the terms verification and validation. -alidation is the checking

or testing of items incl'des software for conformance and consistency with an

associated specification. Software testing is j'st one kind of verification which also 'sestechni1'es s'ch as reviews analysis inspections and walkthro'ghs. -alidation is the

process of checking that what has been specified is what the 'ser act'ally wanted.

-alidation : &re we doing the right job:-erification : &re we doing the job right:

Software testing sho'ld not be conf'sed with deb'gging. +eb'gging is the process of analy(ing and locali(ing b'gs when software does not behave as e#pected. &ltho'gh the

identification of some b'gs will be obvio's from playing with the software a methodical

approach to software testing is a m'ch more thoro'gh means for identifying b'gs.+eb'gging is therefore an activity which s'pports testing b't cannot replace testing.

8ther activities which are often associated with software testing are static analysis and

dynamic analysis. Static analysis investigates the so'rce code of software looking for

problems and gathering metrics witho't act'ally e#ec'ting the code. +ynamic analysis

looks at the behavior of software while it is e#ec'ting to provide information s'ch as

e#ec'tion traces timing profiles and test coverage information.

Testing is a set of activity that can be planned in advanced and cond'cted

systematically. Testing begins at the mod'le level and work towards the integration of entire comp'ters based system. 2othing is complete witho't testing as it vital s'ccess of

@B


57/67

the system testing objectives there are several r'les that can serve as testing objectives.They are

Testing is a process of e#ec'ting a program with the intend of finding an error.& good test

case is one that has high possibility of finding an 'ndiscovered error.& s'ccessf'l test isone that 'ncovers an 'ndiscovered error.

If a testing is cond'cted s'ccessf'lly according to the objectives as stated above itwo'ld 'ncovered errors in the software also testing demonstrate that the software

f'nction appear to be working according to the specification that performance

re1'irement appear to have been met.

There are three ways to test program.

• For correctness

• For implementation efficiency

• For comp'tational comple#ity

Test for correctness are s'pposed to verify that a program does e#actly what it was

designed to do. This is m'ch more diffic'lt than it may at first appear especially for large programs.

TEST PLAN

& test plan implies a series of desired co'rse of action to be followed in accomplishingvario's testing methods. The Test %lan acts as a bl'e print for the action that is to be

followed. The software engineers create a comp'ter program its doc'mentation and

related data str'ct'res. The software developers is always responsible for testing theindivid'al 'nits of the programs ens'ring that each performs the f'nction for which it

was designed. There is an independent test gro'p HIT6 which is to remove the inherent

problems associated with letting the b'ilder to test the thing that has been b'ilt. Thespecific objectives of testing sho'ld be stated in meas'rable terms. So that the mean time

to fail're the cost to find and fi# the defects remaining defect density or fre1'ency of

occ'rrence and test workAho'rs per regression test all sho'ld be stated within the test

plan.

The levels of testing incl'de)

• ,nit testing

• Integration Testing

• +ata validation Testing

• 8'tp't Testing

UNIT TESTING

,nit testing foc'ses verification effort on the smallest 'nit of software design ? thesoftware component or mod'le. ,sing the component level design description as a g'ide

@C


58/67

important control paths are tested to 'ncover errors within the bo'ndary of the mod'le.The relative comple#ity of tests and 'ncovered scope established for 'nit testing. The 'nit

testing is whiteAbo# oriented and step can be cond'cted in parallel for m'ltiple

components. The mod'lar interface is tested to ens're that information properly flows

into and o't of the program 'nit 'nder test. The local data str'ct're is e#amined to ens'rethat data stored temporarily maintains its integrity d'ring all steps in an algorithm4s

e#ec'tion. 7o'ndary conditions are tested to ens're that all statements in a mod'le have

been e#ec'ted at least once. Finally all error handling paths are tested.

Tests of data flow across a mod'le interface are re1'ired before any other test is

initiated. If data do not enter and e#it properly all other tests are moot. Selective testingof e#ec'tion paths is an essential task d'ring the 'nit test. 6ood design dictates that error

conditions be anticipated and error handling paths set 'p to rero'te or cleanly terminate

processing when an error does occ'r. 7o'ndary testing is the last task of 'nit testing step.Software often fails at its bo'ndaries.

,nit testing was done in SellASoft System by treating each mod'le as separate entity

and testing each one of them with a wide spectr'm of test inp'ts. Some flaws in theinternal logic of the mod'les were fo'nd and were rectified.

INTEGRATION TESTING

Integration testing is systematic techni1'e for constr'cting the program str'ct're

while at the same time cond'cting tests to 'ncover errors associated with interfacing. Theobjective is to take 'nit tested components and b'ild a program str'ct're that has been

dictated by design. The entire program is tested as whole. /orrection is diffic'lt beca'se

isolation of ca'ses is complicated by vast e#panse of entire program. 8nce these errors

are corrected new ones appear and the process contin'es in a seemingly endless loop.

&fter 'nit testing in SellASoft System all the mod'les were integrated to test for any

inconsistencies in the interfaces. Moreover differences in program str'ct'res wereremoved and a 'ni1'e program str'ct're was evolved.

VALIDATION TESTING OR SYSTEM TESTING

This is the final step in testing. In this the entire system was tested as a whole with all

forms code mod'les and class mod'les. This form of testing is pop'larly known as7lack 7o# testing or System testing.

7lack 7o# testing method foc'ses on the f'nctional re1'irements of the software.

That is 7lack 7o# testing enables the software engineer to derive sets of inp't conditionsthat will f'lly e#ercise all f'nctional re1'irements for a program.

7lack 7o# testing attempts to find errors in the following categories$ incorrect or missing f'nctions interface errors errors in data str'ct'res or e#ternal data access

performance errors and initiali(ation errors and termination errors.

OUTPUT TESTING OR USER ACCEPTANCE TESTING

@


59/67

The system considered is tested for 'ser acceptance$ here it sho'ld satisfy the firm4sneed. The software sho'ld keep in to'ch with perspective system$ 'ser at the time of

developing and making changes whenever re1'ired. This done with respect to the

following points

Inp't Screen +esigns

8'tp't Screen +esigns

8nline message to g'ide the 'ser and the like.

The above testing is done taking vario's kinds of test data. %reparation of test data playsa vital role in the system testing. &fter preparing the test data the system 'nder st'dy is

tested 'sing that test data.


60/67

APPENDIX

SCREEN SHOTS

L(i!

H(+e

BK


61/67

E+#(5ee

Me+6e

B0


62/67

T&!s&$'i(!

B3


63/67

E@#e!*i'7e

I!$(+e

C(!'&

B9


64/67

D&5 B((9

B=


65/67

P(%i'"L(ss A$$(7!'

S7++&5 Re#('

B@


66/67

CONCLUSION

The project entitled “Financial Management System " which keep the day by day tally

record as a complete banking or financial system. It can keep the information of Saver

!oaner and Share older and also managed it. The e#citing part of this project is$ it

displays the day book %rofit and !oss &cc Statistical S'mmary and Interest Information.

BIBLIOGRAPHY

788DS)

1. /harles ampfed H3KKK O-is'al 7asic4 ,niversity of

Toronto

2. erbert Schildt H3KKK O-is'al 7asic B.K4 Tata Mc6raw ill

3. ;ohn X'kowski H3KKK O-is'al 7asic B.K4 O7%7 %'blications

>. ;amie ;aworsky O-is'al 7asic B.K4Techmedia

BB


67/67

. Stefen +enninger O-is'al 7asic B.K4&'thor4s %ress

. Ian Somerville OSoftware engineering4

. 5ajeev mall OSoftware engineering4

. lmasri 2avathe OF'ndamentals of database systems4

ONLINE REFERENCE:

www.w9schools.com

www.vis'al.com

Financial Management System Capstone Project

Documents

Transcript of Financial Management System Capstone Project