Вы находитесь на странице: 1из 15

09CSA10

Payroll 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. mployee $etails
3.1.3. Salary $etails
3.1.&. !odify
3.2. '!% $iagram
3.2.1. 'se case $iagram
3.2.2. Class $iagram
3.2.3. Se#uence $iagram
3.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 /alidation +esting
..3. /alidation +est Criteria
..&. Coverage Analysis
.... !emory %ea0s
09CSA10
Synopsis
This is a small scale project for payroll system .The basic idea is
that the manager of the company maintains the details about the
employees, the designation and salary. It consists of employee details,
payroll system, status and exits. The manager can enter the name and
employee ID and get the salary details of that particular employee. In
payroll system we can calculate the net salary of the employee based on
input.
In the Employee details module various details like employee ID,
ame, Designation, !asic pay are obtained from the user.In the Display
module the total database is displayed. In the salary Details module, the
individual database is displayed which shows the "#, D$, %&$ and et
salary of the particular employee. !y using the 'odify module we can
modify and update the employee personal details on the database stored.
09CSA10
Phase 1 Project Analysis and Planning
1.1. Study of the Problem
The "ayroll processing is critical to businesses and other organi(ations
because of the significant amounts of money involved in employee remuneration and
the complexity of the legal re)uirements. This is a small scale project for payroll
processing. The basic idea is that the manager of the company maintains the
information such as company*s name, its branches all over. The employee details
maintain the employee ID, ame along with personal information. The total salary
details determine the net pay of the employee. This pay roll processing involves with
two types of users.
+,E&
$D'II,T&$T-&
USERS ROLE:
The user*s can login.logout the database. %e.,he can view his.her personal
details, monthly pay details, and company details. The user can just view the
information whereas he.she could not make changes in the database.
AD!"!S#RA#OR ROLE:
The administrator plays a vital role in the payroll system. The administrator
controls the entire database. The net salary 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 payroll processing. This
specification defines the non/functional re)uirement of the system such a
Functionality:
,ince it stand alone application, a single user may use it at a time.
Usability:
Desktop interface
0indows 12.3444.5p
Reliability:
The system is available at 36 hours a day, seven days a week.
Performance:
The performance depends on hardware specification
09CSA10
1.(. Ob%e&t)*es
The purpose of this document is to define the re)uirements of payroll
processing. This supplementary specification lists the re)uirements that are not readily
captured in the use case model. ,upplementary specification and the use case model
capture a complete set of re)uirement 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. #rom 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 re)uirements. $ software cost estimate process is the set of techni)ues 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 )s d)ff)&ult a,d error 'ro,e -
,oftware cost estimation re)uires a significant amount of effort to perform it
correctly.
,7E is often done hurriedly, without an appreciation for the effort re)uired.
8ou need experience at developing estimates, especially for large projects.
%uman bias i.e $n Estimator is likely to consider how long a certain portion of
the system would take, and then to merely extrapolate this estimate to the rest of
the system, ignoring the non/linear aspects of software development.
#he &auses of 'oor a,d ),a&&urate est)mat)o,
ew software projects are nearly always different form the last.
,oftware practitioners don9t collect enough information about past
projects.
Estimates are forced to match the resources available.
$.1. Cost a,d Pr)&),.
09CSA10
-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;app<.
$ team of :: members is re)uired for completing the task.
It takes a time span of = weeks to shape the project.
There are no specific environmental constraints.
Phase 3 !odeling the "e#uirements
(.1. odule Des&r)'t)o,
3.1.1. Login
It is the login session for the $dministrator, +ser and Exit.
3.1.2. Employee Details
It is used to add employee details into the database.
3.1.3. Net alary
It is used to determine the employee net salary.
3.1.!. "o#ify
It is used to modify and any update in the database.
(.$. UL D)a.ram
3.2.1. Use case Diagram
+se 7ase 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.
$ctor:
$n actor is 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.
09CSA10
Admi nistrator
Vi ew and Print the Salary Details
Empl oyee
Empl oyee Detai ls
Payroll Processing
Val idity Check
Database
System
3.2.2. &lass Diagram
$ class diagram describes the types of objects in the system and the various
kinds of static relationships that exist among them.i.e.,$ graphical representation of a
static view on declarative static elements. $ class is the description of a set of objects
having similar attributes, operations, relationships and behavior.
database
empid
name
age
designation
payroll
processing
basic pay
HRA
PF
net pay
calculation!
administrator
empid
name
department
age
basic pay
HRA
PF
net pay
insert!
delete!
update!
system
show details!
"alidity check!
employee
emp id
name
department
age
designation
"iew!
3.2.3. e'uence Diagram
09CSA10
$ se)uence diagram in +nified 'odeling >anguage ;+'>< is a kind of
interaction diagram that shows how processes operate with one another and in what
order. It is a construct of a 'essage ,e)uence 7hart. ,e)uence diagrams are
sometimes called event diagrams, event scenarios, and timing diagrams
employee
administrator system database payroll
processing
pro"ide #D
Enter #D
Validation check
Pro"ide details
Processing
Send details
$i"e details
View details
3.2.!. &ollaboration Diagram
$ 7ollaboration diagram is very similar to a ,e)uence diagram in the purpose
it achieves? in other words, it shows the dynamic interaction of the objects in a
system. $ distinguishing feature of a 7ollaboration 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
,e)uence diagram. $ 7ollaboration 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 se)uence of
invocation of these objects, a number is placed next to each of these arrows.
administrat
or
employee
system
database payroll
processing
%& pro"ide #D
'& Validation check
(& Pro"ide details
)& Processing
*& Send details
+& View details
,& Enter #D
-& $i"e details
09CSA10
Phase & Configuration !anagement
7onfiguration management is also used in software development, where it is
called +nified 7onfiguration 'anagement ;+7'<. +sing +7', developers can keep
track of the source code, documentation, problems, changes re)uested, and changes
made. $n advantage of a configuration management application is that the entire
collection of systems can be reviewed to make sure any changes made to one system
do not adversely affect any of the other systems
/.1. S0+ Re1u)reme,ts
OS@ 0indows
La,.ua.e@ Aisual !asic
/.$. 20+ Re1u)reme,ts
Intel "II "rocessor with =44 '%( speed.
B6 '! &$'
:4'! %ard disk space
/.(. #ools
Des)., #ool@ &ational &ose suite
/./. Soft3are De*elo'me,t
!.!.1. Form &reation
Form1:
09CSA10
Form2:
Form3:
09CSA10
Form!:
09CSA10
!.!.2. cript
Cod),. for form1:
"rivate ,ub 7ommand:C7lick;<
End
End ,ub
"rivate ,ub 7ommand3C7lick;<
If Text:.Text D EmanimaranE $nd Text3.Text D EwelcomeE Then
Text:.Text D EE
Text3.Text D EE
#orm3.Aisible D True
Else
'sg!ox Einvalid username and passwordE
Text:.Text D EE
Text3.Text D EE
Text:.,et#ocus
End If
End ,ub
Cod),. for form$:
"rivate ,ub 7ommand:C7lick;<
#orm=.,how
End ,ub
"rivate ,ub 7ommand3C7lick;<
#orm6.,how
End ,ub
"rivate ,ub 7ommand=C7lick;<
+nload 'e
End ,ub
"rivate ,ub 7ommand6C7lick;<
End
End ,ub
Cod),. for form(:
Dim db $s Database
Dim rs $s &ecordset
"rivate ,ub 7ommand:C7lick;<
Text1.Text D ;;Aal;TextF.Text< G Aal;TextB.Text< G Aal;TextH.Text<< /
;Aal;Text2.Text<<<
End ,ub
"rivate ,ub 7ommand3C7lick;<
#orm6.,how
End ,ub
09CSA10
"rivate ,ub 7ommand=C7lick;<
+nload 'e
+nload #orm3
End ,ub
"rivate ,ub 7ommand6C7lick;<
End
End ,ub
"rivate ,ub 7ommandFC7lick;<
rs.'ove#irst
Text:.Text D rs;4<
Text3.Text D rs;:<
Text=.Text D rs;3<
Text6.Text D rs;=<
TextF.Text D rs;6<
TextB.Text D rs;F<
TextH.Text D rs;B<
Text2.Text D rs;H<
End ,ub
"rivate ,ub 7ommandBC7lick;<
rs.'ove"revious
Text:.Text D rs;4<
Text3.Text D rs;:<
Text=.Text D rs;3<
Text6.Text D rs;=<
TextF.Text D rs;6<
TextB.Text D rs;F<
TextH.Text D rs;B<
Text2.Text D rs;H<
End ,ub
"rivate ,ub 7ommandHC7lick;<
rs.'oveext
Text:.Text D rs;4<
Text3.Text D rs;:<
Text=.Text D rs;3<
Text6.Text D rs;=<
TextF.Text D rs;6<
TextB.Text D rs;F<
TextH.Text D rs;B<
Text2.Text D rs;H<
End ,ub
"rivate ,ub 7ommand2C7lick;<
rs.'ove>ast
Text:.Text D rs;4<
09CSA10
Text3.Text D rs;:<
Text=.Text D rs;3<
Text6.Text D rs;=<
TextF.Text D rs;6<
TextB.Text D rs;F<
TextH.Text D rs;B<
Text2.Text D rs;H<
End ,ub
"rivate ,ub #ormC>oad;<
,et db D -penDatabase;E(@Imani.mdbE<
,et rs D db.-pen&ecordset;EtableE<
End ,ub
Cod),. for form/:
Dim db $s Database
Dim rs $s &ecordset
"rivate ,ub 7ommandBC7lick;<
+nload 'e
+nload #orm=
+nload #orm3
End ,ub
"rivate ,ub 7ommandHC7lick;<
End
End ,ub
"rivate ,ub 7ommand=C7lick;<
rs.$ddew
rs;4< D Text:.Text
rs;:< D Text3.Text
rs;3< D Text=.Text
rs;=< D Text6.Text
rs;6< D TextF.Text
rs;F< D TextB.Text
rs;B< D TextH.Text
rs;H< D Text2.Text
rs.+pdate
'sg!ox Erecord insertedE
End ,ub
"rivate ,ub 7ommand6C7lick;<
Text:.Text D EE
Text3.Text D EE
Text=.Text D EE
Text6.Text D EE
TextF.Text D EE
TextB.Text D EE
TextH.Text D EE
09CSA10
Text2.Text D EE
End ,ub
"rivate ,ub 7ommandFC7lick;<
+nload 'e
#orm3.,how
End ,ub
"rivate ,ub #ormC>oad;<
,et db D -penDatabase;E(@Imani.mdbE<
,et rs D db.-pen&ecordset;EtableE<
End ,ub
Phase . Soft,are +esting
4.1. Pre'ar),. #est Pla,
"reparing 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.
4.$. Perform 5al)dat)o, #est),.
,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.
4.(. 5al)dat)o, #est Cr)ter)a
,oftware validation is achieved through a series of black box test that
demonstrates conformity with re)uirements.
4./. Co*era.e A,alys)s
7overage analysis is used to identify untested code. +sing rational pure
coverage, untested code can easily be identified.
09CSA10
4.4. emory Lea6s
'emory leak testing has been done using rational purity software.
Result:
!ased on the system re)uirements specification "$8&->> I#-&'$TI-
,8,TE' has been designed and implemented.