ProjectReport

On

Attendanceandpayrollmanagementsystem

Submitted in partial fulfillment of the requirements

for the award of the degree of

MasterOfComputerApplication(MCA)
Guru Gobind Singh Indraprastha University, Delhi

Guide:

Ms.NehaBajpai

SubmittedBy:

Enroll.no0101184408

CentreForDevelopmentOfAdvanceComputing(CDac)

Noida

Akash


Annexure-II

Certificate

I Mr. Akash Roll No. 0101184408, certify that the Project Report entitled Attendance And Payroll
Management System is done by me and it is an authentic work carried out by me at CETPA
Infotech Pvt. Ltd. The matter embodied in this project work has not been submitted earlier for the
award of any degree or diploma to the best of my knowledge and belief.

Signature of the Student

Date:

Certified that the ProjectReportentitledAttendanceAndPayrollManagementSystem

donebyAkashRollNo0101184408,iscompletedundermyguidance.

Signature of the Guide

Date:
Name of the Guide:
Ms. Neha Bajpai
Designation: Lecturer
Address: CDAC, Noida

ACKNOWLEDGEMENT

It was very exciting for us to work on the project of ATTENDANCE AND PAYROLL MANAGEMENT
SYSTEM. During this work we have gained both practical as well as theoretical knowledge of great
significance.

We are thankful to our guide Mr. MOHIT DAGAR. It has been a highly encouraging and knowledge gaining
experience. He has been a source of inspiration throughout the project and has helped us in all our problems.
This being the first company experience has proved to be of great help for the overall development of the
future.

We are highly obliged to the CMC ACADEMY and its management and technical staff for its support and cooperation. We thank CMC ACADEMY and its staff for everything but the most for giving us an opportunity to
work under.

Contents

SR.NO

Title

page

1.

Certificate..

2.

Acknowledgement.

3.

Abstract

4.

CompanyProfile.

5.

Tables

i)listoffigures

ii)listoftables..

Chapter
1.0

Title

Introduction.

10

1.1

ProjectProfile

11

1.2

SystemOverview.

12

1.3

Objective

13

1.4

Scope.

13

ProjectManagement.

14

2.1

15

SystemRequirementStudy.

17

3.1

UserCharacterstics.

18

3.2

HardwareAndSoftwareRequirement..

19

3.3

Constraints..

19

3.3.1 SecurityAndReliabilityStudy

20

2.0

ProjectDevelopmentApproach.

3.0


3.3.2 OrganisationalRequirement.

21

3.3.3 ExternalRequirement.

21

4.0

SystemAnalysis.

23

4.1

StrengthAndWeaknessOfCurrentSystem..

24

4.2

RequirementOfNewSystem

26

4.2.1.1 UserRequirement
4.3

4.4

5.0

26

FeasibilityStudy26
4.3.1

DoesTheNewSystemContributeToTheOverallObjectiveOfThe
Organisation..27

4.3.2

CanTheSystemBeImplementedUsingCurrentTechnology..27

FeaturesOfNewSystem28

ContextDiagram30

5.1

DataFlowDiagram31

5.2

DataModelling45

5.2.1

DataDictionary45

5.2.2

ERDiagram57

6.0

UserManual59

7.0

Testing....92

8.0

LimitationAndFutureEnhancement99

9.0

SUMMARY 103

10.0

CONCLUSION 105

REFERENCES


Attendanceandpayrollmanagementsystem
Abstract

This document is meant for describing all the features and procedures that were followed while developing the system.

This document specially mentions the details of the project how it was developed, the primary requirement, as well
as various features and functionalities of the project and the procedures followed in achieving these objectives.

ATTENDANCE AND PAYROLL MANAGEMENT SYSTEM forms the lifeline of the organisation and Institutes
to the functioning of the attendance. It is very essential for an organisation to handle the attendance and their results.
It is very useful for an organisation to check its employee continuously for their working in the company. This
system is helpful for maintaining the per day attendance of the employees of different departments and accordingly
maintaining their records.

With the effective use, any organization can apply the Attendance and Payroll Management System for
maintaining records of the employees and generate the records accordingly and getting better results in less time.


COMPANYPROFILE
CETPAInfotechPvt.Ltd.isanorganization,whichwasestablishedintheyear2002andsincelastnineyearsithas
becometheleadingTrainingProgramProviderintheNorthernIndia.CETPAistheassociation,whichisproviding
theopenplatformforsoftwaredevelopment.CETPAthinkthatdevelopmenttoolsshouldbeprovidedfreeofcost
sothatthetechnologycanbeemergedwithflyingcolors.

CETPAhastwotypesofclubsprofessionalclubandstudentclub.Inprofessionalclubwetheprofessionalswhich
aresupportingtheenhancementofCETPAandseriouslyworkingfortheassociation.CETPAstudentclubisagroup
ofstudentswhicharethepartofCETPA.Thesestudentmembersaregivenopportunitytopresenttheirpaperson
particularresearchworkontheprojectsintheseminars,andthesepapersarepublishedonwebsite.Selected
projectswhicharetheuniquewillbesupportedandsponsoredinthenationalandinternationalseminarsfor
paperpresentationandpublishing.
AsiahasbeenhelpinginternationalvendorstodemonstratetheirlatestembeddedtechnologiestoTaiwan's

engineersandtechnicalmanagerswhohasworkedalotintheseproducts.CETPAprovidesseminarsindifferent
institutionsandcompaniesfreeofcost.Theseseminarshelpstudentsandprofessionalstogettheknowledgeof
advancetechnologies.

MISSION:

QUALITY:

Providingintelligentsolutions

SOLUTIONS:

Isassuredwithstandardbusinesspractices,cuttingedgetechnologyandrightprocesses.

Developedintime,inbudgetandaccordingtovaryingbusinessneedsofourcustomers.


ListOfFigures

Sr.no

FigureNo.

Title

1.

2.1

WaterfallModel

16

2.

5.1

ContextDiagram

30

3.

5.2

DFD(LEVEL0)

32

4.

5.3

LoginProcessDfd(Level1)

33

5.

5.4

AddEmployeeDfd(Level1)

34

6.

5.5

EditEmployeeDfd(Level1)

35

7.

5.6

DeleteEmployeeDfd(Level1)

36

8.

5.7

FindEmployeeDfd(Level1)

37

9.

5.8

GenerateReportDfd(Level1)

38

10.

5.9

AddEmployeeDfd(Level2)

39

11.

5.10

EditEmployeeDfd(Level2)

40

12.

5.11

DeleteEmployeeDfd(Level2)

41

13.

5.12

FindEmployeeDfd(Level2)

42

14.

5.13

GenerateReportDfd(Level2)

43

15.

5.14

CompleteProcessDfd(Level3)

44

16.

5.15

EntityRelationshipDiagram

58

page

ListOfTables

Sr.no

Tableno.

Title

page

1.

5.1

Admindata

45

2.

5.2

Employee_Info

47

3.

5.3

Employeepersonal

48

4.

5.4

Payrollinfo

49

5.

5.5

Tax_Info

50

6.

5.6

Attendi

51

7.

5.7

[AttendanceDatabase]

53

8.

5.8

Paymentinfo

55

Chapter
Introduction

10

INTRODUCTION

1.1 PROJECT PROFILE:

1. Project Partners
Strength :- 1
Names:o Akash

2. Hardware / Software Environment

Hardware
o Pentium IV
o 80 GB Hard Disk
o 512 MB RAM
Software
o Operating System
Microsoft Windows XP Professional Service Pack 3,XP 7
Development Tools
o Microsoft C#.NET 2010
o Database Microsoft SQL Server 2008
Documentation & Presentation Tools
o Microsoft excel 2003

11

1.2 SYSTEM OVERVIEW

Attendance and Payroll Management System is built on C#.net, SQL Server 2008,and excel 2007.
The Window application is built to serve the following areas.

User Friendly: The proposed system is user friendly because the retrieval and storing
of data is fast and data is maintained efficiently. Moreover the graphical user interface
is provided in the proposed system, which provides user to deal with the system very
easily.
Reports are easily generated: Reports can be easily generated in the proposed system
so user can generate the report as per the requirement (monthly) or in the middle of the
session. User can give the notice to the employee so he/she become regular.

Very less paper work: The proposed system requires very less paper work. All the
data is feted into the computer immediately and reports can be generated through
computers. Moreover work become very easy because there is no need to keep data on
papers.

Computer operator control: Computer operator control will be there so no chance of

errors. Moreover storing and retrieving of information is easy. So work can be done
speedily and in time.

Payment generation: The administrator can generate the payment easily on the basis
of the no of hours the employee works in the organization and and can generate the
records of attendance and payment.

12

1.3 OBJECTIVE
Create a Window application to be used in place of old paper based employee
Attendance process.
Use C#.NET and SQL Server technology to create strong and secured database
connectivity.

1.4 SCOPE

Attendance Management System is designed for Organisation ,Institutes like Any small

organization where people works in different departments and also work on weekly and monthly basis.
The system handles all the operations which saves the precious time of data operators to store empoloyee
information and generate the employee reports of attendance and work hours in the company.

13

Chapter2

14

ProjectManagement

Project Management

2.

2.1 PROJECT DEVELOPMENT APPROACH

Software Process Model
To solve actual problems in an industry, software developer or a team of developers must incorporate a
development strategy that encompasses the process, methods and tools layers and generic phases. This strategy is
often referred to as process model or a software developing paradigm. A process model for software developing is
chosen based on the nature of project and application, the methods and tools to be used, and the controls and
deliverables that are required. All software development can be characterized as a problem solving loop in which
four distinct stages are encountered: Status quo, Problem definition, technical development and solution
integration. Regardless of the process model that is chosen for a software project all of the stages coexist
simultaneously at some level of detail.

Our Project Follows the Waterfall Model

THE WATERFALL MODEL
U

The steps of the typical Waterfall Model are:

1. Requirement Definition
2. System & Software Design
3. Implementation
4. Integration & System Testing
5. Operation and Maintenance

15

Chapter2

ProjectManagement

Waterfall model

There have been some variations from the typical waterfall model for this project lifecycle.
They are:
1. Maintenance has been omitted from the current project.
2.

Not all testing methods which are present in theoretical model are implemented.

16

Chapter3

SystemRequirementStudy

17

3.

System Requirement Study

USER CHARACTERISTICS
This system will be used in only one User Modules which is Administrator. As user have different
requirements for each modules of the proect the modules are designed to meet his needs and avoid any
type Of confusion.

User can do the following functions:

1. User can login through his account.
2. If the user wants to change password it can be done by verification.
3. User can add the new employee information.
4. User can delete the particular employee.
5. User can change the information in the database in case of descrepancies if occurred.
6. User can generate the attendance on the day basis and month basis..
7. User can check the details of the employee at any time.
8. User can generate the employee payment on the basis of no.of hours worked by the employee.
9. User can generate the report in excel format.

18

Chapter 3

3.2

System Requirement Study

System Requirement
Hardware
Pentium IV
200 MB Hard Disk Space
512 MB RAM
Software
Microsoft .NET Framework Version 2.0 Or above

3.3

CONSTRAINTS

3.3.1 Security and Reliability Requirements

Security
The Information should be Secure; there should not be any kind of malfunctioning. All the re details of
Employees taken are stored securely in the system. System Information will not be changed by any person rather
than the management.
Reliability
System should be reliable. It should keep secure all the information regarding to particular Employees and
administrator . It should work effectively in tremendous rush. The system must give the perfect results in kind of
damn situation. The Particular result must be listed in to the particular user only; there should not be any kind of
data integrity or other problem between employees.
Flexibility
System is working easily in the organisation with the username and password of the user. The system can
also work on other kind of technology with the little modification. System should be quite flexible to install and
maintain.

19

Efficiency
System should be efficient enough to meet all kinds of requirements as required by the Administrator. The
system should not hang or lose its efficiency in any kind of worse conditions. It should provide the correct output
in all manners.

User Friendliness
System should be user friendly, so that new user(administrator) can work on the system.

20

Chapter 3

System Requirement Study

3.3.2 Organizational Requirements.

Implementation Requirements

It requires good skill for implementation of project. As this project is using 3- tier business
architecture. All the classes, functions, procedures and objects are created in the system wise
architecture. The three tiers are given below.
1) GUI
2) Business Logic Layer
3) Data Access Layer
Entire coding will be done using Microsoft Visual .Net 2010 and Microsoft SQL Server 2008. Soft copy for
the documentation is provided in Microsoft Word Format. Entire coding would not be shown to the client for
any reasons. Implementation does not require any more software support without as mentioned below in the
system requirements.

Standards Requirements
Industry standards will be followed by us in any negotiation or deal related to the product
software. Coding, Documentation and final product delivery will be followed by the standards.

3.3.3 External Requirements.

Ethical Requirements
Product Software should be negotiated with human ethics and it is wished that the software should be used
with ethical requirements. Any non ethical use of this software will be at the users own risk.

21

Chapter 3

System Requirement Study

Legislative Requirements
1) Privacy Requirements
Privacy of any particular things and strategy will be served based on prior negotiation and it should Be
cleared purposed for that requirement.
3) Safety Requirements
Safety will be provided based on the requirement of the members and necessary critical points.

22

CHAPTER 4
System analysis

23

Chapter 4

SYSTEM ANALYSIS

4.1 Study And Weakness Of Current System

Current System
The Current system of manually attendance management is highly complicated and expensive.
Whenever attendance are to be done there are various tasks that have to be done again and again.
Very typical to maintain for large employee.
For different employee different records to be maintained.
Similar names creates problem some time.
Needs large records to be change during any single change.
Payroll generation is typical.
Any missing day causes the problem to update each record.
Preparing reports for each employee is very tedious.

Generate reports for each employee is very time consuming.

Weaknesses in Current System

The current system is as mentioned earlier very complicated and expensive as compared to the
new system. It also wastes the precious time of the operators which can then be used in solving other problems.
Current system requires lot of data to be maintained for some employees who are not for longer time with the
organization.In case of any employee records needs to be deleted the current system requires lot of work to be
done.

24

Chapter 4

System Analysis

As management person are humans and so prone to errors, there can be mistakes.In attendance
to be maintained , calculating day of presence and the no of hours present also can cause a lot of mistakes to

be done. Only preventive measures are taking a double check to ensure these errors dont happen which
would again require extra time.

Thus, the current system is in every way ineffective for maintaining attendance and payroll of the
employees day by day in these days when time is more costly than anything and they also pose a threat to the
environment when we are amidst a global crisis and in the need of a Green Revolution.

25

Chapter 4

System Analysis

4.2 REQUIREMENT OF NEW SYSTEM

4.2.1

User Requirements.

The User requirements for the new system are to make the system fast, flexible, less prone to errors and
reduce expenses and save time.
A system that can automate the attendance of employees which are pre-stored so that results can be
generated as soon as the employees entered in to the company.
A facility that can generate result charts as per required without manual interference for providing
how a task is to be done instead only asking what is to be done.
The system should have the reports to be generated any time so that the records can be generated
for the attendance of employee at the particular date can be checked.
The New system should be more secure in managing employees records and reliable enough to be
used in any condition.
Finally, it should prove cost effective as compared to the current system.

4.3 Feasibility Study

A key part of the preliminary investigation that reviews anticipated costs and benefits and recommends a
course of action based on operational, technical, economic, and time factors. The purpose of the study is to
determine if the systems request should proceed further.

26

Chapter 4

System Analysis

4.3.1 Does the New System Contribute to the Overall Objectives of the
Organization?

The new system would contribute to the overall objectives to of the organization. It would provide a
quick, error free and cost effective solution to the current process. It would provide a solution to many issues

in the current system. As the new system is flexible and scalable it can also be upgraded and extended to meet
other complex requirements which may be raised in the future. However it is up to the organization to upgrade
or extend it.

4.3.2 Can the New System be Implemented Using Current Technology?

The organization has a computer laboratory which has about 50 machines connected by Internet Lan and
managed by a server. It would be very easy to set up the system in the current environment as the application is
windows based it does require to be installed on every machine. The database and IIS are set up on the server and
the .Net Framework installed on every machine, the system can be started as quick as required by the management.

27

Chapter 4

System Analysis

4.4 Features of the New System.

The new system has been designed as per the user requirements so as to fulfill almost all them.

Quick Scheduling

Attendance can be done quickly as the employees entered in to the organization and the time starts
accordingly after entering in to the organization.
Immediate reports

One of the most important draw backs of the current system is that the administrator needs to check
the no of hours the employee present in the organization and accordingly the payment needs to be
maintained in the records of the particular employees.. The new system will generate the reports as soon as
the attendance of the day is finished and will also store it in the database for further usage.
Easy to Store and Retrieve Information

The new system makes it easy to store and retrieve information as required and does not involve
storing information in separate sheets or papers. It thus saves data management problems faced in the current
system as it has a Database Management System of it own which allows to make the reports as needed.
Cost Effective

One of the main reasons of the new system is its cost effectiveness. It saves the amount spend on
stationary as well as overall cost maintaining the time calculating the no of days present and also to generate
salary accordingly for different-different employees.

28

Chapter 5
System design

29

Chapter 5

System Design

5.1 CONTEXT DIAGRAM.

The context diagram is a top-level view of an information system that shows the boundaries and scope. It
describes the main objective of the system and the entities involved.

Context Diagram Of Attendance And Payroll Management

30

Chapter 5

5.2

System Design

DATA FLOW DIAGRAM (DFD)

The DFD (also known as bubble chart) is a simple graphical formalism that can be Used to

represent a system in terms of the input data into the system, various processes carried on these data, and the output

data generated by the system. The main reason why the DFD technique is so popular is because the fact that the

DFD is a very simple formalism it is simple to understand And use. A DFD model uses a very limited number of

primitive symbols to represent the functions Performed by a system and the data flow among the functions. Starting

with a set of high-level Functions that a system performs, a DFD model hierarchy represents various sub-functions.

31

Chapter 5

System Design

1.0

Admindata

Loginprocess

Login

2.0
Enterdetail
process

Addemployee

Employee_info

3.0

Editemployee

Administrator

Employeepersonal

Editprocess

Payrollinfo

4.0

Deleteemployee

Tax_info

Deleteemployee
process

Findemployee

5.0

Reportgeneration

Searchemployee
process

6.0

DFD LEVEL-0

Reportgenerate
process

32

Attendi

Paymentinfo

Chapter 5

System Design

DFD LEVEL 1

1.1

LOGINPROCESS

Store Username And Paasword

Enter User Name And Password

Change Password

ADMINDATA

Accept/Reject

ADMINISTRATOR

accept or reject change

1.2
CHANGEPASSWORD
PROCESS

(Administrator login)

33

Chapter 5

System Design

DFD-(LEVEL-1)

(Add employee)

34

Chapter 5

System Design

DFD (LEVEL-1)

(Edit employee)

35

Chapter 5

System Design

DFD (LEVEL-1)

(Delete Employee)

36

Chapter 5

System Design

DFD (LEVEL-1)

(Find employee)

37

Chapter 5

System Design

DFD (LEVEL-1)

(Report Generation)

38

Chapter 5

System Design

DFD (LEVEL-2)

39

Chapter 5

System Design

DFD (LEVEL-2)

40

Chapter 5

System Design

DFD (LEVEL-2)

41

Chapter 5

System Design

DFD (LEVEL-2)

42

Chapter 5

System Design

DFD (LEVEL-2)

43

Chapter 5

System Design

DFD (LEVEL-3)

44

Chapter 5

System Design

5.3 DATA MODELLING

Data Dictionary

5.3.1

Table 5.1 Admindata

Description: details of administrator

Field Name

Description

Constraints

Size

Data Type

User_name

Contains user name

Primary key

10

varchar

Old_password

Contains user old

password for
verification

Not null

10

varchar

New_password

Set new password

and store it for
verification use

null

10

varchar

It contains the
value of user is
either login or
logout

True/false

bit

Add_emp

It contains bit
value if
administrator
wants to add new
employee.

True/false

bit

Edit_emp

It sets the bit value

if administrator
wants to edit
information for
particular
employee.

True/false

bit

Delete_emp

It sets the bit value

if administrator

True/false

bit

valu

45

wants to delete
information for
particular
employee.

Find_emp

46

It sets the bit value

if administrator
wants to find
information for
particular
employee.

True/false

bit

Chapter 5

System Design

Table 5.2 : Employee_info

Description: Contains employee office details

Field Name

Description

Constraints

Size

Data Type

Name

Contains employee

Not null

15

Varchar

Name
Badge_id

Contains employee
badge id.

Primary key

10

Varchar

Pin

Contains employee
unique pin no.

Foreign key

10

Int

Shift

Contains employee

Not null

50

Varchar

Shift.
Department

Contains employee
respective
department.

Not null

50

Varchar

Date_of_birth

Contains employee
date of birth.

Not null

10

Datetime2

Hire_date

Contains employee
hire date.

Not null

10

Datetime2

Notes

Contains any note

regarding
particular
employee.

null

50

Varchar

47

Chapter 5

Table: 5.3

System Design

Employeepersonal

Description: Contains employee personal information.

Field Name

Description

Constraints

Size

Data Type

Employee_pin

Contains employee
pin no.

Primary key

10

Int

address

Contains employee
address.

Not null

50

Varchar

Home_ph

Contains employee
house phone no.

null

10

Int

Alternate_no

Contains employee
alternate no.

Not null

10

Int

Cell_no

Contains employee
cell no.

null

10

Int

Emergency_no

Contains employee
emergency no.

Not null

10

Int

48

Chapter 5

Table 5.4

System Design

payrollinfo

Description: Contains payroll information according to employee details.

Field Name

Description

Constraints

Size

Data Type

Security_no

Contains employee pin

no.

Primary key

10

Int

Employement_type

It contains permanent
or contract based
employee information.

Not null

50

Varchar

Payment_type

Contains payment
information as
wekly,hourly,monthly.

Not null

50

Varchar

Normal_rate

The normal rate of

salary given to
employee.

Not null

10

float

Ot_rate

Overtime rate given to

employee.

Not null

10

float

Salary_period

Salary period i.e

monthly,weekly,houly.

Not null

50

varchar

Salarypperiod

Fix salary for any

particular period.

Not null

10

float

Overtime

Overtime hours.

null

10

float

49

Chapter 5

Table 5.5

System Design

tax_info

Description : Contains tax information if any employee having.

Field Name

Description

Constraints

Size

Data Type

Employee_pin

Contains employee
pin no.

Primary key

10

Int

Employment_type

Contains type of
the employee as
permanent or
contractual basis

Not null

50

Varchar

Marital_status

Shows marital
status.

Not null

10

Varchar

Exemption

Contains
information about
tax if paying or
not.

null

50

Varchar

50

Chapter 5

Table 5.6

System Design

attendi

Description: Contains attendance database of particular date.

Field Name

Description

Constraints

Size

Emp_id

Contains employee
pin no.

Primary key

10

Int

Emp_name

Contains employee
name.

Not null

50

Varchar

Time_in

It check the check

in time of the
employee.

Null(default date
value)

20

Datetime2

Time_out

It check the
checkout time of
the employee.

Null(default date
value)

20

Datetime2

Total_time

It saves the total

time for which
employee was
poresent.

Null(default 0
value)

20

varchar

Day

It shows the day in

which employee
was present .

Null(default 0
value)

10

Int

Hour

It calculates the no
of hours employee
was present.

Null(default 0
value)

10

Int

Minutes

It saves the
minutes other than
hour the employee
was present.

Null(default 0
value)

10

Int

Second

It contains the
seconds employee

Null(default 0

20

Int

51

Data Type

was present .

value)

Status

It check the status

the employee is
present or not.

True/false(not null)

Int

Date

It contains the date

of the record.

Null(default date
value)

10

datetime

52

Chapter 5

Table 5.7

System Design

[attendance database]

Description: Contains all data saved for all days.acts as a backup for large data.

Field Name

Description

Constraints

Size

Emp_id

Contains employee
pin no.

null

10

Int

Emp_name

Contains employee
name.

null

50

Varchar

Time_in

It check the check

in time of the
employee.

Null(default date
value)

20

Datetime2

Time_out

It check the
checkout time of
the employee.

Null(default date
value)

20

Datetime2

Total_time

It saves the total

time for which
employee was
poresent.

Null(default 0
value)

20

varchar

Day

It shows the day in

which employee
was present .

Null(default 0
value)

10

Int

Hour

It calculates the no
of hours employee
was present.

Null(default 0
value)

10

Int

Minutes

It saves the
minutes other than
hour the employee
was present.

Null(default 0
value)

10

Int

Second

It contains the
seconds employee

Null(default 0

20

Int

53

Data Type

was present .

value)

Status

It check the status

the employee is
present or not.

True/false( null)

Int

Date

It contains the date

of the record.

Null(default date
value)

10

datetime

54

Chapter 5

Table:

System Design

paymentinfo

Description: It contains the information for the payment of particular employee at particular
month.

Field Name

Description

Constraints

Size

Data Type

Emp_no

Contains
employee pin
no.

null

10

Int

Emp_name

Contains
employee
name

null

50

varchar

Employement_type

Contains
employee type

null

50

varchar

Payment_type

Contains
employee
payment type

null

50

varchar

Normal_rate

Contains
normal rate
paid to
employee

null

10

Varchar

Ot_rate

Contains
overtime rate

null

10

varchar

Salary_period

Contains
salary period.

null

10

Varchar

Salarypperiod

Contains
salary per
period.

null

10

Varchar

Overtime

Contains
overtime.

null

10

Varchar

No_of_hour_work

Contains no of
hours woked

null

10

Varchar

55

in a month.

56

month

Contains
month for
which salary is
generated

null

10

Varchar

salary

Contains
salary

null

20

float

Chapter 5

System Design

5.3.2 Entity Relationship Diagram

An Entity-relationship model is an abstract conceptual representation of structured data.
Entity relationship modeling is a relational schema database medeling method, used in Software
Project Management to produce a type of conceptual data model (or semantic data model) of a
system, often a relational database, and its requirements in top-down fashion.

57

Chapter 5

58

System Design

Chapter 6
User Manual

59

Chapter 6

6.1

User Manual

Administrative Module
Login page:
This is the login page administrator must have to set paasword and user name.
This is the first page to load in the application without administrator entry nothing will happen
in the application.

60

Chapter 6

The file menu contains the administrator name and password field to enter.

61

User Manual

Chapter 6

User Manual

This the login page user needs to varify its user name and password before going further in the
application.

After entering password user will need to go further.User can change the password if required.

62

Chapter 6

User Manual

Change password page:

This the change password page user needs to first varify the old password then he can set the new
password only.

63

Chapter 6

User Manual

Security page:
If the user is not the authenticated one and enters password wrongly three times the application will
going to shut down automatically with the warning.

64

Chapter 6

User Manual

Sucessful login:

If the user is the authenticated one and enters the field correctly then he will enter in to administrative
Account and can work on the application.

65

Chapter 6

User Manual

Sucessful login:
After sucessful login all the tabs will become in active mode and the administrator will go further in
the application
The employee contains the employee name and by the help of employee code the attendance of the
employee will go in to the record.

66

Chapter 6

User Manual

6.2 Attendance module:

This page contains the employee with the name and employee code which is unique for each of
the employee in the organisation.
Employee can check in by giving their employee code .
The respective time of the employee will be maintained in the record for calculating the no of
hours the employee have worked in the organisation.

67

Chapter 6

User Manual

6.3 Add employee module:

This module will be active after sucessful login of the adminisrator .
This module will be used when the adminisrator wants to enter new employee record.

68

Chapter 6

User Manual

Sub module:
Employee detail:
This is the sub module which will take all the respective information for the
employee record to be added.

69

Chapter 6

User Manual

Sub module:
personal detail
This is sub module that takes the information of employee personal detail for
record purpose.

70

Chapter 6

User Manual

Sub module: Tax information:

This sub module takes the tax information on the employee if any..

Sub module:
Payroll information:
This module will takes the payroll information on which the payroll information
is collected.

71

Chapter 6
Addition of the record in the employee record sub module:

Addition of the personal record in add module:

72

User Manual

Chapter 6

Addition of payroll information :

Addition of the tax information in add module..:

73

User Manual

Chapter 6

6.4.

User Manual

Record Edit Module:

This module will be activated after sucessful login of the administrator.
This module is used to edit the selected employee records in the database.

74

Chapter 6

User Manual

Sub module:
Employee detail edit record:
This submodule is used to edit the employee detail in the records.

75

Chapter 6

User Manual

Sub module:
Personal detail:
This module edit the personal details of the employee..

Sub module:
Payroll information:
This sub module edit the payroll information in the employee records..

76

Chapter 6

User Manual

Sub module:
Tax information:
This sub module is used to edit the tax information of the employee.

77

Chapter 6

6.5.

User Manual

Record Delete Module:

This record is active only during the valid administrator login.
This record delete the employee records from each database.

During activation of this module on the basis of the employee pin no the record is deleted.

78

Chapter 6

79

User Manual

Chapter 6

6.6.

User Manual

Record Find Module:

This module becomes active when administrator sucessfully login the
application.
By this module the record of the employee is searched accordingly.

80

Chapter 6

User Manual

Sub module :
Find employe Detail record:
In this module the employee detail is finding out on the basis of employee pin
no.
If the record does not found in the database the particular message is generated.

81

Chapter 6

User Manual

Sub module:
Find employee payroll information:
This sub module is used to find the employee payroll information in the record
on the basis of the pin no.

82

Chapter 6

User Manual

6.7 Report generation module:

This module becomes active when the administrator sucessfully login the
application.
This module is used to generate the employee attendance and the daily working
Hour duration of the employee.
This module is used to generate the report of the employee attendance in the
excel sheet..

83

Chapter 6

User Manual

Sub module attendance generation report:

Attendance of the employee is generated on the basis of the the employee id and of the
particular date on which the record is required.

84

Chapter 6

User Manual

This module transfer the employee attendance information to that of excel shet so that the
records copy can be generated as requred..

85

Chapter 6

File showing attendance of the particular employee after filtering the data.

86

User Manual

Chapter 6

User Manual

Sub module Payment report Generation :

This module generates the report of the employee payments on the basis of no.
of hours the employee worked in the organisation.

87

This module becomes active when administrator sucessfully log in ..

Chapter 6

User Manual

This submodule will take the no of hours of working in the organisation and after that by the
no of hours of overtime the salary will be calculated..

88

Chapter 6

User Manual

Ion this module after generating report on the query basis there result will be retrieve out and
will be transferred for the storage.

89

Chapter 6

The resule of the report will be stored in the file.

90

User Manual

Chapter 6

File showing the payment of the employee

91

User Manual

Chapter 7
Testing

92

Chapter 7

Testing

Testing
Testing Methodology:
Software testing is critical element of software quality assurance and represents the ultimate review of
specification,designandcoding.Itisusedtodetecterrors.Testingisadynamicmethodforverificationandvalidation,
wherethesystemtobetestedisexecutedandthebehaviorofthesystemisobserved.

Testing Objectives:

Testingisaprocessofexecutingaprogramwiththeintentoffindinganerror.

Agoodtestcaseisonethathasahighprobabilityoffindinganasyetundiscoverederror.

Asuccessfultestisonethatuncoversanasyetundiscoverederror.

The above objectives imply a dramatic change in viewpoint. They move counter to the commonly held
view that a successful test is one in which no errors are found. Our objective is to design tests that
systematically uncover different classes of errors and do so with a minimum amount of time and effort.
If testing is conducted successfully (according to the objectives stated above), it will uncover errors in
the software.
Testing cannot show the absence of defects, it can only show that software errors are present.

TestingTechnique:
The techniques followed throughout the testing of the system are as under

Black-Box Testing:
Blackboxtestingfocusesonthefunctionalrequirementsofthesoftware.Thatis,BlackBoxtestingenables
thesoftwareengineertoderivesetsofinputconditionsthatwillfullyexerciseallfunctionalrequirements
foraprogram.BlackBoxTestingisnotanalternativetowhiteboxtechniques.Rather,itisacomplementary
approachthatislikelytouncoveradifferentclassoferrorsthanwhiteboxmethods.

93

Chapter7

Testing

BlackBoxTestingattemptstofinderrorsinthefollowingcategories:

Incorrectormissingfunctions.

Interfaceerrors.

Errorsindatastructuresorexternaldatabaseaccess.

Performanceerrors.

Initializationandterminationerrors.

Unlike White Box Testing, which is performed early in the testing process, Black Box Testing tends to be
applied during later stages of testing. Because Black Box Testing purposely disregards control structure,
attention is focused on the information domain. Tests are designed to answer the following questions:

Howisfunctionalvaliditytested?

Whatclassesofinputwillmakegoodtestcases?

Isthesystemparticularlysensitivetocertaininputvalues?

Howaretheboundariesofadataclassisolated?

Whatdataratesanddatavolumecanthesystemtolerate?

Whateffectwillspecificcombinationsofdatahaveonsystemoperation?

Byapplyingblackboxtechniques,wederiveasetoftestcasesthatsatisfythefollowingcriteria:

Testcasesthatreduce,byacountthatisgreaterthanone,thenumberofadditionaltest

casesthatmustbedesignedtoachievereasonabletesting.

Testcasesthattellussomethingaboutthepresenceorabsenceofclassesoferrors,rather

thanerrorsassociatedonlywiththespecifictestathand.

94

Chapter7

Testing

White-Box Testing:
White Box Testing knowing the internal workings of a product tests can be conducted to ensure that internal
operations are performed according to specifications and all internal components have been adequately
exercised.
Usingwhiteboxtestingmethodsthetestcasesthatcanderivedare:

Allindependentpathswithinamodulehavebeenexercisedatleastonce.

Exercisealllogicaldecisionsontheirtrueandfalsesides.

Executeallloopsattheirboundariesandwithintheiroperationalbounds.

Exerciseinternaldatastructurestoensuretheirvalidity.

Control Structure Testing

ConditionTesting:
Condition testing is a test case design method that exercises the logical conditions contained in a program
module. If a condition is incorrect then at least one component of the condition is incorrect. Therefore types of
errors in a condition include the following.
Booleanoperatorerror
Booleanvariableerror
Booleanparenthesiserror
Relationaloperatorerror
Arithmeticexpressionerror

1) LoopTesting:
Loops are the corner stone for the vast majority of all algorithms implemented in software. Loop testing is
a white-box testing technique that focuses exclusively on the validity of loop constructs. Four different classes
of loops:

95

Chapter 7

SimpleLoops

NestedLoops

ConcatenatedLoops

unstructuredLoops

2)

DataflowTesting:

Testing

The dataflow testing method selects test paths of a program according to the location of definitions and uses
of variables in the program. In this testing approach, assume that each statement in a program is assigned a
unique statement number and that each function does not modify its parameters or global variables.
It is useful for selecting test paths of a program containing nested if and loop statement. This approach is
effective for error detection. However, the problems of measuring test coverage and selecting test paths for
data flow testing are more difficult than the corresponding problems for condition testing.

96


Chapter7

Testing

TestingStrategies
A strategy for software testing integrates software test case design methods into a well planned series of steps
that result in the successful construction of software. A software testing strategy should be flexible enough to
promote a customized testing approach.

Unit Testing:
Unit testing focuses verification efforts on the smallest unit of software design. It is white box oriented. Unit
testing is essentially for verification of the code produced during the coding phase and hence the goal is to test
the internal logic of the module. Others consider a module for integration and use only after it has been unit
tested satisfactorily.

Themoduleinterfaceistestedtoensurethatinformationproperlyflowsinandoutofprogram

Localdatastructureisexaminedtoensurethatdatastoredtemporarilymaintainitsintegrity.

Boundaryconditionsaretestedtoensurethatmodulesoperateproperlyatboundarylimitsofprocessing.

Allindependentpathsareexercisedtoensureallstatementsinamodulehavebeenexecutedatleastonce.

Allerrorhandlingpathsaretested.

Integration Testing:
Integration testing focuses on design and construction of the software architecture. For example: - We
followed a systematic technique for constructing the program structure that is putting them togetherinterfacing at the same time conducting tests to uncover errors. We took unit tested components and build a
program that has been dictated by design.

Validation Testing:
It is achieved through a series of Black Box tests. An important element of validation process is configuration
review. It is intended for all the elements are properly configured and cataloged. It is also called AUDIT.

97

Chapter 7

Testing

System Testing:
The last high-order testing step falls outside the boundary of software engineering and into tile broader
context of computer system engineering. Software, once validated, must be combined with other system
element (e.g., hardware, people, and database).
System testing verifies that all elements mesh properly and that overall system function/performance is
achieved.
It is a series of different tests whose primary purpose is to fully exercise the computer-based system. Although
each test has a different purpose all work to verify that system elements have been properly integrated and
perform allocated functions.

98

Chapter 8
Limitation And Future Enhancement

99

Chapter 8

8.1

Limitation And Future Enhancement

Limitations
The new system has been designed to meet the requirement of small organisation where the

record to be maintained is not in very large.but instead of it,it has some limitations also.some of which can be
Enhanced in the future enhancements and updates.
8.1.1

Supports small organization data:

It supports only small organization database where data to be
Maintained is small in amount and also the data need to be changed very frequently.

8.1.2

No Image Support:
It does not support image data to be stored. as the employee
Records and database contains some other information to be store but image database is
Not applied to be store in this which can be enhanced in the future .

8.1.3

Reports cannot be generated in the normal format:

Reports can not be generate in other formats than that of excel
Format. Reports which once created must be transferred to the excel sheet and then the
Particular action can be taken.

8.14

Database is not that much secure:

Database is not that much secure to be used as if anyone knows
The administrator password can change the database easily.

8.15

Partial data information entry causes no error:

Partial data information in the database causes no error in the
database.

100

Chapter 8

8.16

Limitation And Future Enhancement

Only administrator having the authority :

Only administrator having the authority to access the application

and change the database and control the application which causes the application not that much
secure.

8.17

It needs some manually calculation to generate the payment report:

It needs some manually calculation for generation of payment of

Employee that manually calculation causes the no of hour to calculate for the working of the
employee.

8.18

Future change causes the some part to be change completely :

Future terms and condition of the organization can cause the

some module to be changed completely but not the whole application.

8.2

FUTURE ENHANCEMENTS
Enhancements are the perquisite for development of a system. Every existing system

has proposed enhancements which make it better and easier to use and more secure. The enhancements that
have been proposed for this system are listed here.
8.2.1

Supports image :
The existing system has no image support due to which the images cannot be

used. It will be one of the priorities in the proposed enhancements to enable Image Support in
the system.

101

Chapter 8

8.2.2

Limitation And Future Enhancement

Support no. of hour to calculate automatically:

It has no support of calculating no of hour work of the employee automatically
Which causes it to be calculate some extra work. It will be one of the priority in
proposed enhancement to Enable calculate no hour automatically.

8.2.3

Support to generate report in different format:

It has no support of generating the report in the graphicaaly format.which causes
it not to be seen the report in the different format.it wil also be one of the priority in the
proposed enhancement to enable it to generate reports in different readable formats.

8.2.4 Security will be larger:

It has not that much security so that any one who knows the password and user
name of the administrator can easily login and can change the records.the enhanced
system must have that security so that it will not be so easy to access the record.

8.2.5 Capability to add extra module:

It has further capability to add extra module in the s\w so that it can be easily
added according to the new requirement.

102

Chapter 9
Summary

103

Chapter 9

9.1

Summary

Summary Of The Project

Project Title

Attendance And Payroll Management System

Software used
Microsoft visual studio 2010
Microsoft sql server 2008
Microsoft excel

Documentation tools
Microft word 2007

External project guide

Mr. Mohit dagar

Organisation :
Cetpa infotech pvt. Ltd.

Internal project guide

Ms Neha Bajpayee

Submitted by
Akash

Submitted To:
Center For Development Of Advance Computing(Cdac,noida)

104

Chapter 10
Conclusion

105

Chapter 10

10.1

Conclusion

CONCLUSION
The development of software includes so many people like user system developer, user of

system and the management, It is important to identify the system requirements by properly collecting required
data to interact with supplier and customer of the system. Proper design builds upon this foundation to give a blue
print, which is actually implemented by the developers.

On realizing the importance of systematic documentation all the processes are implemented
using a software engineering approach. Working in a live environment enables one to appreciate the intricacies
involved in the System Development Life Cycle (SDLC).

We have gained a lot of practical knowledge from this project, which we think, shall make us stand in a good state
in the future.

106

References/Bibliography

Appendix A

www.w3schools.com
http://www.c-sharpcorner.com
http://www.csharp-station.com/Default.aspx

Appendix-B

107

List Of Useful Website

List Of Useful Books

Programming in c# by e balagurusamy

Pro C# 2008 .NET 3.5 Platform Fourth Edition by Andrew Troelsen

ADO.net programming by Terrence j joubert and ryan n payet

C# school by faraz rasheed

PL/SQL programming Evan Bayross