final payroll report 2003 format

8/13/2019 Final Payroll Report 2003 Format

1/116

A

PROJECT REPORT ON"COLLEGE PAY ROLL MANAGEMENT

SYSTEM"

A Project Report submitted to partial fulfillment of the requirement

for the degree of

Bachelors of Computer Sciences.

SUBMITTED TO:-

DEPARTMENT OF COMPUTER SCIENCE

G.C.W PARADE, JAMMU

(2012-2013SUBMI!" B#$ U%"!R &! 'UI"A%C!

()$


2/116

COLLEGE PAY ROLL MANAGEMENT SYSTEM

PRII BA'A* B&ARA SIR M(%I+A

S&ARMA RA"&I+A

&A%"A %!&A 'UPA

CERTIFICATE

This is to certify that PRITI BAGAL, MONI!A

SARMA, RADI!A ANDA, NEA GUPTAhave

prepared the report on the project entitled "COLLEGE

PAY ROLL MANAGEMENT SYSTEM" under mysupervision and guidance .Further they have fulfilled all

the statutory requirements for the submission of the

project. the project report is found worthy of acceptance

for the award of Bachelor of Computer Application.

UNDER THE GUIDANCE OF BY: - HOD

BHARAT MAHAJAN !. B#$%&'CA%

(DEPARTMENT OF

COMPUTER SCIENCES)

G.C.W PARADE2


3/116


AC!NOWLEDGEMENT

,e are con-inced that it is -irtuall impossible for us to

underta/e and complete a project of this /ind 0ithout the

encouragement1 guidance and assistance from teachers and

friends.

At the -er outset 0e e2press our heartfelt gratitude to

persons1 our guide Mr. Bharat Mahajan for his sincere ad-ice1

inspiring guidance1 constructi-e criticism 1 fruitful

suggestions 1 useful super-ision and importantl1 for allo0ing

us to ta/e up this project.

%o 0ords of gratitude are sufficient to appreciate the

encouragement 0e ha-e been recei-ing from time to time from

our teachers1 in all our ears of learning.

*ast but not the least 0e remain grateful to our parents and our

classmates for their moral support and inspiration in the

completion of this stud.

PR!!I BA'A*

M(%I+A S&ARMA

RA"&I+A &A%"A

G.C.W PARADE3


4/116


%!&A 'UPA

INDEX

S%(. C(%!%S PA'! %(.

I%R("UCI(% 3

3. S#S!M "!4!*(PM!% SRA!R'# 567

5. S#S!M A%A*#SIS 86

35

9. S#S!M "!SI'% 396

3:

;. "AA )*(, "IA'RAM 3. !R6"IA'RAM 536

55

7. ,(R+I%' !%4IR(%M!% 596

5;

8. !C&%(*('# ?4B.%!@ 5>6

95

G.C.W PARADE4


5/116


:. SCR!!% S&(S 996

9what? to high level >how?.

INTERNAL DESIGN

0nternal design involves conceiving* planning out and specifying the internal structure

and processing details of the software product. the goals of internal design are to

specify internal structure and processing details to record designing decisions and

indicate why certain alternative and trade


24/116


interoverall testing? include entity0nput design is a process of converting user oriented inputs to a computeri;ed

format?. 0nput design is the basic thing to be considered in the system design. 0n this

process the input screens for the data entry. 0n such an interfaced design* the user

inputs the data by filling the ban+s basis on the screens. &ach entry from has its own

command button* which provides users the facility to insert a new world record* delete

G.C.W PARADE 1@


25/116


and modify an e5isting record. The major approaches to input design are menu*

formatted from* prompts and alerts.

OUTPUT DESIGN

This is based on user requirements and the format is designed +eeping views of

hose necessities. thus2?the output design emphasi;es on providing a hard copy of

information required or displaying the output on a C!T screen in a predefined format?.

FORMS DESIGN

Computer out put is the most important and direct source of information to the user.

ence* an intelligent and efficient output design improves the system relationship withthe user and helps in decision = ma+ing. A major forms of output is the hard copy

from the printer >.forms design elaborates on the way output is presented and the

layouts available for capturing information >. The data available in any system is vital

to that system. 'o1 the data must be provided in the right forms for input and the

information produced must be in a format acceptable to the user.

>A form is a tool with a message2 it is a physical carrier of data of information >. A

poorly designed form is a poor administration tool. The suffecient space has been

provided in all forms to avoid comple5ity and over crowing of data. ence F:!-'

must be attractive and graphical user interface.

USER INTERFACE DESIGN

Any software product in addition to being effective and fast in functionality should also

be user friendly. For designing a good (#0 developer should consider the following

principles2

Clarity

$isual feedbac+

(ood response

Audible feedbac+

Traceable paths

G.C.W PARADE 2


26/116


27/116


DATA F3O8 DIA2RAM OF

CO33E2E PAY RO33

MANA2EMENT SYSTEM

G.C.W PARADE 22


28/116


CAPTER #

!R6"IA'RAM

G.C.W PARADE 23


29/116


ER-DIAGRAM OF

PAYROLL

MANAGEMENT SYSTEM

G.C.W PARADE 24


30/116


G.C.W PARADE 25


31/116


CAPTER $

WOR!INGEN%IRONMENT

8OR9IN2 EN6IRONMENT

TECHNICA3 SPECIFICATIONS:-

HARD8ARE EN6IRONMENT

G.C.W PARADE 2(


32/116


P / 'ollo/& o'&,r%#&o

Proe""or: - P / m&&m,m ;+ 2H.

RAM: - < 2B

H%r! !&"4: - ;P*6&"#%+

BAC9 END: - M&ro"o'# S73 Server (


33/116


34/116


:ne of the major areas of change is in eb development. /rior to .%&T* eb

application programming was all about A'/. The script based technology had its own

shortcomings and inefficiencies and the lessons derived from the e5perience resulted

in the creation of the web development technology named A'/.%&T. $isual

'tudio.%et which includes A'/.%&T furthered the concept by ma+ing the code andthe interfaces similar across various programming disciplines


35/116


The .%&T framewor+ is a revolutionary program by -icrosoft for developing

applications29 System.Drawin.FontStyle.6old9 System.Drawin.raphicsnit.Point9C/ype(,9 6yte22

=e.$abel+.ForeColor ! System.Drawin.SystemColors.Acti3eCaption =e.$abel+.$ocation ! New System.Drawin.Point(+09 +L2 =e.$abel+.=arin ! New System.indows.Forms.Paddin(+9 ,9 +9 ,2 =e.$abel+.Name ! $abel+ =e.$abel+.SiGe ! New System.Drawin.SiGe(119 +K2 =e.$abel+./abInde< ! +0 =e.$abel+./e


88/116


;Form0 ; =e.AutoScaleDimensions ! New System.Drawin.SiGeF(K.,>9 10.,>2 =e.AutoScale=ode ! System.indows.Forms.AutoScale=ode.Font =e.6ac5Color ! System.Drawin.Color.FromArb(C/ype(C/ype(1H+9 6yte29Inteer29 C/ype(C/ype(1H+9 6yte29 Inteer29 C/ype(C/ype(+JJ9 6yte29 Inteer22

=e.ClientSiGe ! New System.Drawin.SiGe(L109 KK02 =e.Controls.Add(=e.roup6o


89/116


Friend ith%3ents t


90/116


cnn.Close(2 %lse cnn.8pen(2 =s6o 2 %nd I-

;cnn.Close(2 Catch e< As %


91/116


Pri3ate Sub Form4$oad(6y7al sender As System.8b*ect9 6y7al e AsSystem.%3entArs2 :andles =y6ase.$oad ;/8D8) /his line o- code loads data into the;PayrollDataSet+.emppersonal; table. Eou can mo3e9 or remo3e it9 as needed. =e.%mppersonal/ableAdapter1.Fill(=e.PayrollDataSet+.emppersonal2

;/8D8) /his line o- code loads data into the ;PayrollDataSet1.payband;table. Eou can mo3e9 or remo3e it9 as needed. =e.Payband/ableAdapter.Fill(=e.PayrollDataSet1.payband2 ;/8D8) /his line o- code loads data into the;PayrollDataSet.emppersonal; table. Eou can mo3e9 or remo3e it9 as needed. =e.%mppersonal/ableAdapter.Fill(=e.PayrollDataSet.emppersonal2

t


92/116


93/116


cmdedit.Connection ! cnn

cmdedit.%


94/116


+. Name etc..2

%nd I- cnn.Close(2 cmddelete.Dispose(2

%nd Sub

Pri3ate Sub btne


95/116


%nd Sub%nd Class

F8'= D%SIN%' C8D% (%=P$8E%%INF8'=A/I8N2Imports System.Data.SqlClientImports System

Public Class Form Dim cmdetdata As New SqlCommand Dim cmdadd As New SqlCommand Dim cmdSearch As New SqlCommand Dim cmddelete As New SqlCommand Dim cmdedit As New SqlCommand

Dim cnn As New SqlConnection(Data Source!."S#$%&P'%SSAttachDbFilename!C)"Pro*ects"+,1+ pro*ects"payrollcwp"payroll"payroll"payroll.md-InteratedSecurity!/rueConnect /imeout!0,ser Instance!/rue2 Pri3ate Sub btnadd4Clic5(6y7al sender As System.8b*ect9 6y7al e AsSystem.%3entArs2 :andles btnadd.Clic5

;Call -illte


96/116


%lseI- cmbscale.SelectedInde< ! 1 /hen t


97/116


t


98/116


99/116


%nd I- cnn.Close(2 cmdedit.Dispose(2

%nd Sub

Pri3ate Sub btndelete4Clic5(6y7al sender As System.8b*ect9 6y7al e AsSystem.%3entArs2 :andles btndelete.Clic5

I- t


100/116


Pri3ate Sub Fill6y/oolStrip6utton4Clic5(6y7al sender As System.8b*ect96y7al e As System.%3entArs2 :andles Fill6y/oolStrip6utton.Clic5 /ry =e.%mppersonal/ableAdapter.Fill6y(=e.PayrollDataSet.emppersonal2 Catch e< As System.%


101/116


Dim cmdadd As New SqlCommand

Dim cnn As New SqlConnection(DataSource!."S#$%&P'%SSAttachDbFilename!C)"Pro*ects"+,1+pro*ects"payrollcwp"payroll"payroll"payroll.md-InteratedSecurity!/rueConnect /imeout!0,ser Instance!/rue2

Pri3ate Sub 8R4Clic5(6y7al sender As System.8b*ect9 6y7al e AsSystem.%3entArs2 :andles 8R.Clic5 Dim cmd As New SqlCommand I- sername/e


102/116


103/116


=e.sername$abel.$ocation ! New System.Drawin.Point (1+9 +2 =e.sername$abel.Name ! sername$abel =e.sername$abel.SiGe ! New System.Drawin.SiGe (++,9 +02 =e.sername$abel./abInde< ! , =e.sername$abel./e


104/116


=e.Controls.Add(=e.Password/e


105/116


Pri3ate Sub %


106/116


Form.Show(2 %nd Sub

Pri3ate Sub =DIParent14$oad(6y7al sender As System.8b*ect9 6y7al e AsSystem.%3entArs2 :andles =y6ase.$oad

%nd Sub

Pri3ate Sub Salary/oolStrip=enuItem4Clic5(6y7al sender As System.8b*ect96y7al e As System.%3entArs2 :andles Salary/oolStrip=enuItem.Clic5 Form0.Show(2 %nd Sub

Pri3ate Sub pdation/oolStrip=enuItem4Clic5(6y7al sender As System.8b*ect96y7al e As System.%3entArs2 :andles pdation/oolStrip=enuItem.Clic5 Form+.Show(2

%nd Sub

Pri3ate Sub pdation/oolStrip=enuItem14Clic5(6y7al sender As System.8b*ect9

6y7al e As System.%3entArs2 :andles pdation/oolStrip=enuItem1.Clic5 Form1.Show(2

%nd Sub

Pri3ate Sub %


107/116


108/116


; =e.=enuStrip.Items.Add'ane(New System.indows.Forms./oolStripItem(2M=e.%mployee/oolStrip=enuItem9 =e.Department/oolStrip=enuItem9=e.Payband/oolStrip=enuItem9 =e.%


109/116


=e.pdation/oolStrip=enuItem1./e


110/116


=e./oolStripSeparator1.Name ! /oolStripSeparator1 =e./oolStripSeparator1.SiGe ! New System.Drawin.SiGe(K9 +J2 ; ;Print/oolStrip6utton ; =e.Print/oolStrip6utton.DisplayStyle !

System.indows.Forms./oolStripItemDisplayStyle.Imae =e.Print/oolStrip6utton.Imae !C/ype(resources.et8b*ect(Print/oolStrip6utton.Imae29 System.Drawin.Imae2 =e.Print/oolStrip6utton.Imae/ransparentColor !System.Drawin.Color.6lac5 =e.Print/oolStrip6utton.Name ! Print/oolStrip6utton =e.Print/oolStrip6utton.SiGe ! New System.Drawin.SiGe(+09 ++2 =e.Print/oolStrip6utton./e


111/116


=e.6ac5roundImae !C/ype(resources.et8b*ect(Uthis.6ac5roundImae29 System.Drawin.Imae2 =e.ClientSiGe ! New System.Drawin.SiGe(K0+9 J02 =e.Controls.Add(=e./oolStrip2 =e.Controls.Add(=e.=enuStrip2 =e.Controls.Add(=e.StatusStrip2

=e.Is=diContainer ! /rue =e.=ain=enuStrip ! =e.=enuStrip =e.Name ! =DIParent1 =e./e


112/116


%nd Class

=8D$% C8D%=odule =odule1 Public Sub -illte


113/116


CAPTER 10

TESTING

G.C.W PARADE 1


114/116


115/116


To verify whether it fulfills the requirement of the proposed system.

The individual modules were tested and results measured against manual

calculations. %ecessary corrections and proper error handlers have been when error

was detected. 'uitable test data was used. The users of the system were involved all

through the testing procedure and their suggestions are considered.

TYPES OF TESTING PERFORMED

There are various types of testing studied under the 'oftware &ngineering course.

'ome of these are2

UNIT TESTING

This concentrates on each unit of the software as implemented in source code.

&ach system modules were tested individually.

Chec+ing the uniqueness of the +ey values in client interface.

0nput output format

%ecessary corrections

0t addresses the issues associated with the dual problems of verification and

programming. Blac+ bo5 test design case techniques are the most prevalent at thisstage. 0n this* many unit tested modules are combined into sub systems* which are

then tested. The goal is to see if the modules can be integrated properly. ence* the

emphasis is on testing interfaces between modules.

SYSTEM TESTING

'ystem tested after integration of all modules.

Chec+ing the module interaction and collective wor+ing.

%ecessary corrections.

FUNCTIONAL TESTING

G.C.W PARADE 11


116/116


The goal is to see if the modules can be integrated properly. ence* the emphasis is

on testing interfaces between modules. The structure of the program is not

considered. Test cases were decided on the basis of the requirements or

specifications of the modules. Test cases were first chec+ed manually and then

chec+ed on the system. %ecessary corrections were made wherever necessary.

PERFORMANCE TESTING

/erformance Testing is designed to test the run< time performance of the software

within the conte5t of an integrated system. /erformance Testing was performed at

each level of the software development. /erformance Testing was performed on

individual modules. /erformance tests are coupled with stress testing and often

required both hardware and software instrumentation.

WHITE BOX TESTING

0t uses the control structure of the procedural design to derive test cases. 0t is

predicted on close e5amination of procedural design. /roviding test case that

e5ercise specific sets of condition and loops tests logical paths through the software.

final payroll report 2003 format

Documents