HR MANAGEMENT

SYSTEM
Semester 6. Final Year project 2013-2014

Name:Roll No:
 Index

1|Page
Sr. No TOPIC
PRELIMINARY INVESTIGATION
1.1 ORGANIZATIONAL OVERVIEW
1.2 OBJECTIVES
1.3 CURRENT SYSTEM
1.4 LIMITATION OF CURRENT SYSTEM
1.5 PROPOSED SYSTEM AND ITS ADVANTAGES
1.6 FEASIBILITY STUDY
1.7 STAKEHOLDER
1.8 PROCESS MODEL
1.9 GANTT CHART
SYSTEM ANALYSIS
2.1 EVENT TABLE CONTENTS
2.2 USE CASE DIAGRAM
2.3 E-R DIAGRAM
2.4 ACTIVITY DIAGRAM
2.5 CLASS DIAGRAM
2.6 SYSTEM SEQUENCE DIAGRAM
2.7 SEQUENCE DIAGRAM
SYSTEM DESIGN
3.1 CONVERTING ERD TO CLASS DIAGRAM
3.2 DATA DICTIONARY
3.3 COMPONENT DIAGRAM
3.4 PACKAGE DIAGRAM
3.5 DEPLOYMENT DIAGRAM
3.6 MENU TREE
3.7 CRUD TABLE
SYSTEM CODING
4.1 VALIDATION
4.2 TEST CASE, TEST DATA, TEST RESULT
4.3 SCREEN LAYOUT
MAINTENANCE AND EVALUATION
5.1 FUTURE ENHANCEMENT
5.2 REFERENCES AND BIBLIOGRAPHY

2|Page
 Preliminary

Investigation

3|Page
1.1 Organization Overview:
HRMS (HR Management System) is a global services provider
delivering technology - driven business solutions that meet the strategic
objectives of our clients. We deliver unmatched business value to
customers through a combination of process excellence, quality
frameworks and service delivery innovation.

We committed to invest in new technology and development which

offers a comprehensive range of integrated software. We innovate in the
area of Marketing, Training, Business Operations and Technology.

We continue to set the standard of making clients successful and

helping them realizes the opportunities that exist within their
organizations. We achieve our commitment to their success, empowering
people and organizations to give competitive advantage by creating
powerful interactive relationships.

 Vision:
Our company philosophy has always focused on customer
satisfaction with
Uncompromising integrity. Vital Softech vision is to be the one top IT
services provider in contracting as well as projects to a diverse and
targeted base of established and emerging corporations.

 Mission:
Our mission is to be known and trusted by our customers to deliver
top quality IT contracting and technology services. We do not want to see
our Clients just satisfied, but delighted with our services. We approach our
work with passion and creativity.

4|Page
1.2 Current System:
Manually it is very difficult to manage the human resource. With
the help of computer it becomes easy and faster to manage the system. In
this project it is the facilities to storing and managing all the information
about the employee working in that company and the projects handle by
the company.

1.2.1 Human Resources:

Add here how this HR Management works…..

1.2.2 Functions of human resource management system:

The function of Human Resources departments is generally

administrative and not common to all organizations. Organizations may
have formalized selection, evaluation, and payroll processes. Efficient and
effective management of "Human Capital" has progressed to an
increasingly imperative and complex process.
The HR function consists of tracking existing employee data which
traditionally includes personal histories, skills, capabilities,
accomplishments and salary. To reduce the manual workload of these
administrative activities, organizations began to electronically automate
many of these processes by introducing specialized Human Resource
Management Systems. HR executives rely on internal or external IT
professionals to develop and maintain an integrated HRMS.
Before the client–server architecture evolved in the late 1980s,
many HR automation processes were relegated to mainframe computers
that could handle large amounts of data transactions. In consequence of
the low capital investment necessary to buy or program proprietary
software, these internally-developed HRMS were unlimited to
organizations that possessed a large amount of capital. The advent of
client–server, Application Service Provider, and Software as a Service or
SaaS Human Resource Management Systems enabled increasingly higher
administrative control of such systems.

5|Page
Currently Human Resource Management Systems encompass:

1. Payroll.
2. Work Time.
3. Benefits Administration.
4. HR management Information system.
5. Recruiting.
6. Training/Learning Management System.
7. Performance Record.
8. Employee Self-Service.

6|Page
1.3 Limitations of current system:
There were problems related to current system such as employee
details storage problem, maintain privacy, cost and budget, etc…

1. Employee Privacy: Your employee entrust you with personal

information. Everything from Social Security numbers to private health
information and marital status gets stored in HR Management System.

2. Cost: One of the main limitation/disadvantage of HR Management

System is its cost.

3. Loss of Subjectivity: All personal data of any employee was easily

leaked.

4. Difficult of Analysis: Due to huge amount of data stored in your system

it becomes difficult to analyze the data.

7|Page
1.4 Proposed System and its Features:
Using today’s updated software and running technologies we have
developed software which can come overcome the problems of current
system.

The solutions made by proposed system are as follows:

1. Fast retrieval of data: Response of data retrieving was improved by

proposed system with high throughput.
.
2. Security: Personal information data of employee was secured.

3. Ease of use: Propose system must be user-friendly.

4. Payroll: The payroll module of HR Management System automates the

payment process by gathering data of employee time and attendance,
calculating various tax, etc.

5. Work Time: The work time gathers standardized time and work related
effort.

6. Administration: The admin module of HRMS handles all operations

related to employee.

7. Training module

8. Employee self-service module

8|Page
1.5 Feasibility Study:
The feasibility studies are undergone as follows:

1. Economic Feasibility:
More commonly known as Cost/Benefit Analysis. The procedure is to
determine the benefits and savings that are expected from a candidate
system and compare them with costs. If the benefits outweigh costs, then
decision is made to design and implement the system. Considering the
facts it is becoming evident that the system will be economically feasible
both for developer as well as for client’s respect.

2. Technical Feasibility:
Technical feasibility centers on the existing computer system
(hardware, software, etc.) and to what extent it can support the proposed
addition. If the budget is a serious constraint, then the project is judged
not feasible. In our case this does not become an obstacle.

HARDWARE REQUIREMENTS:

Content Description
HDD 20 GB Min
40 GB Recommended
RAM 512 GB Min
1 GB Recommended

SOFTWARE REQUIREMENTS:

Content Description
OS Windows XP with SP2 or Windows
Vista
Database MS-SQL server 2005
Technologies ASP.NET with C#.NET
IDE Ms-Visual Studio .Net 2008
Browser IE

9|Page
 3. Legal Feasibility:
A determination of any infringement, violation or liability that could
result from the development of the system. But the system to be
developed will be 100% legal.

4. Operational feasibility:
The management & operators desire to be well acquainted with the
requisite skill needed. Here most of the members in development team
having technical expatriation.

5. Time feasibility:
The management & operators here concern about whether the project
will completed timely or not. But considering the facts and figures
collected by us regarding our project it can be easily assumed that the
project will be completed within the specified time frame.

10 | P a g e
1.6 Stake Holders:
A person, group or organization that has direct or indirect stake in
an organization, can be affected by the organizations actions, objectives
and policies. Key stakeholders in a business organization include creditors,
directors, employees, government (and it agencies), owners
(stakeholders), suppliers, unions and the community from which the
business draws its resources.

Although stake holding is usually self-legitimating (those who judge

themselves to be stakeholders are stakeholders), all stakeholders are not
equal and different stakeholders are entitled to different consideration.
For example, a company’s customers are entitled to fair trading practices
but they are not entitled to the same consideration as the company’s
employees.

 Project Leader:
Here the project leader is our Professor._______________ and
Professor _______________. who guided me in this project.

 Developer:
Here in this project the developer is_______________.

 Admin:
In this project, the administrator role will be played by staff & HOD.
ie Head of Department.

 Organizational Manager:
Here the Organizational Manager is Mr. Anil. Karekar and Mr. Raju.
Sawant.

 Organizational Employee:
Here the employee is the company Manager who will use the
project.

11 | P a g e
 Before the development of this software, a meeting was conducted
with the members of the organization to discuss their requirements
and their expectations with the product.

12 | P a g e
1.7 Process Model:
The Process Model means the design, testing and implementation
of the project. This is also known as Classic Life Cycle Model or Linear
Sequential Model or Waterfall Model. It includes various phases and
activities. The activities are as listed below in the following manner:

1. System Analysis and Design:

Easy track is based on waterfall model of software engineering. In

“WATERFALL MODEL”, the process software development is divided into
separate process phases. Software design, implementation, testing and
maintenance. All these phases are cascaded to each other so that second
phase is starts as and when defined set of goals are achieved for the first
phase and it is signed off. So the name is suggested as “WATERFALL
MODEL”.

General view of a “WATERFALL MODEL” is given below,

13 | P a g e
 The stages of “WATERFALL MODEL” are requirement of the system
to develop are captured in this phase. Requirements are the set of
functionalities and constraints that the end-user (who will be using this
system) accepts from the end-user. The requirements are gathered from
the end-user by consultation these requirements are analyzed for their
validity and the possibility of incorporating the requirements in the
system to develop is also studied.

Finally, a requirement specification document is carried which

serves the purpose of guidelines for the next phase of the model. It is
called as Software Requirement Specification (SRS).

2. System and Software Design:

Before starting to the actual coding of any project, it is highly easy

to understand what we are going to create and what it should look like?
The requirement specification from first phase is studied in the phase and
the system design is prepared. System design helps in specifying hardware
and system requirement and also helps in defining overall system
architecture. The system design specification serves as input for the next
phase of the model.

3. Analysis:

The overall code of software in larger system is identified during

system engineering. However it’s necessary to take a harder look at the
software’s role to understand the specific requirements that must be
achieved to build high quality software. That’s the job of software
requirements analysis.

The requirement modeling activity for a system c/s from the

analysis modeling methods applied to more conventional computers
architectures because analysis modeling avoids specification of
implementation detail issues associated with the allocation of software
components of client and server are considered as only as transaction
made to design. However, an evolutionary approach to software
engineering is applied for c/s system. Implementation decision on over all
c/s approach may be made during early analysis and design iterations.

14 | P a g e
 The steps involved in analysis include data; functional and
behavioral requirements begin identified by electing information from the
customer. Requirements are refined and analyzed to access their clarity,
completeness and consistency. A specification incorporating a model of
software is created and then validated.

Analysis has a set of operational principles which are as follows:

1. The information domain of a problem must be represented and

understood.

2. The functions that the software has to perform must be defined.

3. The behavior of the software must be represented.

4. The models that depict information function and behavior must be

partitioned in a manner that uncovers detail in layered fashion.

5. The analysis process should move from essential information towards

implementation detail.

4. Requirement Analysis:

Requirement analysis is software engineering task that bridges the

gap between the system level requirement and software design. These
activities result in the specification of the software operational
characteristics indicate the software interface with other systems
elements and establish constraints that the software must meet.

System Engineering

System Requirement Analysis

Software Design

15 | P a g e
 5. Implementation and Unit Testing:

On receiving system design document i.e. SRS (Software

Requirement Specification) now the work is divided into modules or in
units and actual coding of a project is started. The system is first
developed in small programs and then they are integrated in the next
phase. After each unit development it is tested and its functionality is
checked, this is referred as unit testing.

Unit testing mainly modified if the models or units meet their

specification.

6. Integrated and System Testing:

As specified above the system is divided in units which are

developed and tested for their functionalities. These units are integrated
into a complete system as a whole behaves as per the specifications. After
successfully testing the software, it is delivered to the customer.

7. Operation and Maintenance:

This phase of the “WATERFALL MODEL” is virtually never ending

phase. Generally, problems with the system developed come up after its
practical use starts, so the issues related to the system are solved after
development of the system. Not all the problems come in picture directly
but they arise time to time and needs to be solved, hence this process is
referred to as maintenance.

Requirement

Design

Implementation

Verification

Maintenance

16 | P a g e
 The waterfall model development helped us because our team size
was small as it was just two members working on this project so it is
precise, as compared to vastness and complexity of the project. It helped
us to meet with business deadlines by customers with prototype, thereby
enabling partial functionality without inordinate delay.

We delivered our first trial version, the core product at no charge to

the organization for a trial period. This helped the customer get feel of the
system and more of gave us useful suggestion and feedback that helped
us plan what could be implemented in the next version. The feedback
helped us to modify the core product to better the needs of the customer
and delivery of additional needs and functionality.

17 | P a g e
 System Analysis

18 | P a g e
 Event Table Content

19 | P a g e
 2.1 Event Table:
A UML Event Table is an interaction between user and a system.
The user sends an event which is fired by a trigger from source after that
interaction is done with the system and response given back to the user.

1. Trigger is an occurrence that tells the system that an event has

occurred, either the arrival of data needing processing or of a point
in time.

2. Source is an external agent or actor that supplies data to the

system.

3. Activity is a behavior that the system performs when an event

occurs.

4. Response is an output, produced by the system that goes to a

destination.

5. Destination is an external agent or actor that receives data from

the system.

Sr. Events Triggers Source Use-Case Response Destinatio

No n
1. Login Admin Admin Enter Successfull Admin
request for Admin id y logged in
login and
password
2. Register Admin Admin Enter New user Data base
request for required got register
registration registration successfully
details

3. Forgot Admin Data Enter mail- Mail send Admin

Password request for base Id required to the
new details Admin
password

20 | P a g e
4. Change Admin Admin Enter New Data base
Password request for required password
update details set
password successfully

5. Accepting Admin Admin Confirm New user Database

registration accepts request for got
of user new registration registered
registration

6. Delete Admin Admin Delete User Database

registration deletes registration deleted
of user registration

7. Add Project User enters Admin Enter Project Database

details of project required details
user details details entered
successfully

8. View User views Data Look up for Project Admin

Project project base Project Details
details of details Details
user

9. Update Admin Admin Enter Project Database

Project updates required details
details of project details updated
user details successfully

10. Delete Admin Admin Remove Project Database

Project deletes project details
details of project details deleted
user details successfully

11. Add Admin Admin Enter Personal Database

Personal enters required details
details of Personal details entered
user details successfully

21 | P a g e
12. View Admin Data Look up for Personal Admin
Personal views base Personal Details
details of personal Details
User details

13. Update Admin Admin Enter Personal Database

Personal updates required details
details of personal details updated
User details successfully

14. Delete Admin Admin Remove Personal Database

Personal deletes personal details
details of personal details deleted
user details successfully

15. Add Salary Admin Admin Enter Salary Database

Details of adds salary required details
user details details added
successfully

16. View salary Admin view Data Look up for Salary Admin
details of salary base salary Details
user details details

17. Update Admin Admin Enter Salary Database

salary updates required details
details of salary details updated
user details successfully

18. Delete Admin Admin Enter Salary Database

salary deletes required details
details of salary details deleted
user details successfully

19. Add Admin Admin Enter Attendance Database

attendance adds required details
details of attendance details added
user details successfully

22 | P a g e
20. View Admin Data Look up for Attendance Admin
attendance views base attendance details
details of attendance details
user details

21. Update Admin Admin Enter Attendance Database

attendance updates required details
details of attendance details updated
user details successfully

22. Delete Admin Admin Enter Attendance Database

attendance deletes required details
details of attendance details deleted
user details successfully

23. Add tax Admin Admin Enter Tax details Database

details of adds tax required added
user details details successfully

24. View tax Admin view Data Look up for Tax Details Admin
details of tax details base tax details
user

25. Update tax Admin Admin Enter Tax details Database

details of updates tax required updated
user details details successfully

26. Delete tax Admin Admin Enter Tax details Database

details of deletes tax required updated
user details details successfully

27. Generate Admin Data Look up for Report Admin

User generates base Personal generated
Personal report Detail successfully
Details
Report of
user

23 | P a g e
28. Generate Admin Data Look up for Report Admin
Salary generates base Salary generated
Details report Details successfully
report of
user

29 Add Admin Admin Enter Organizatio Database

organizatio adds required n details
n details organizatio details added
n details successfully

30 Update Admin Admin Enter Organizatio Database

organizatio updates required n details
n details organizatio details updated
n details successfully

31 Delete Admin Admin Deletes Organizatio Database

organizatio deletes required n details
n details organizatio details deletes
n details successfully

24 | P a g e
 Use Case Diagram

25 | P a g e
Use case diagram for Admin
Admin login

Admin register User

Admin deletes User

Database

Admin adds, updates, view, delete

User

Admin Admin adds, updates, view, delete

User’s personal details

Admin adds, updates, view, delete

User’s salary

Admin adds, updates, view, delete

User’s attendance

Admin adds, updates, view, delete

User’s tax details

Admin adds, updates, view, delete

organisation details

Admin generates salary slip.

26 | P a g e
Use case diagram for Client
Client ID

Client Basic Salary

Client Tax
Database

Organisation ID

Client Organisation name, phone no, FAX,

address details

Client Total attendance

Client Leaves

Client Payment

Client pending payment

Client total payment

27 | P a g e
Use case diagram for Organization
Organization ID

Organization Name

Admin deletes User

Database

Organization Address

Org
Organization Phone no

Organization FAX

28 | P a g e
 Use case diagram for Attendance And Salary
Client ID

Organization ID

Client DOJ
Database

Client Basic Salary

Admin
Client Leaves

Client Total Salary

Clients salary after deduction

29 | P a g e
 E R Diagram

30 | P a g e
 RegisterUser
ProjName RequiredSkil UserID
l

Supervisor ProjID Password

NewProj Pay
Admin ChangePasswor

Provide Work

EmpDetails
MobileNo
EmpD

HomeNo
EmpName

WorkNo
EmpAdd

Status
City

Supervisor
EmpID

HiredDate
EmpEmail
EmpID
Departmen
BloodGrp
AttendID
EmpGender
Attendance
Nationality
Date

MarkAttend

Payment

EmpID
one AssignedEmp
ProjName

Department ProjID
one

Skills
one
designation
one
31 | P a g e
 Activity Diagram

32 | P a g e
Activity Diagram for Admin
ADMIN SYSTEM
Display admin login
Connect to login form

Enter user name and Verify

password Incorrect username
password

Display main page

Change Password Update login details

View, Add, Modify, Update

Delete Organization Organization details

View, Add, Modify, Update emp

Delete emp details

View, Add, Modify, Update attendance

Delete attendance details
details

View, Add, Modify, Update proj

Delete proj details details

View, Add, Modify,

Update salary details
Delete salary details

Exit Logout

33 | P a g e
 Class Diagram

34 | P a g e
 1 Admin
EmployeeDetails NewProject UserID 1

EmpID ProjID Password

EmpFirstName ProjName ChangePassword
EmpMiddleName Supervisor RegisterEmp
EmpLastName SkillRequired +ManageClients
EmpAdd +ViewEmp +ManageOrganisations
EmpDOB +ViewEmpSalary +ManageSalary
EmpPhone +ManageEmp +ManageProjects
EmpEmail +ManageSkills +ManageEmpLeaves
EmpSalary +ViewSkills +ManageAttendance
EmpGender +ViewProject
Empstatus 1
EmpDepartment 1
EmpDesignation 1
1
EmpSkills Attendance
+ViewEmp EmpID
+AddEmp 1
AttendID
+AddPersonalDetails Date
+AddOrgDetails MarkAttend
+AddSalary 1 +ViewEmployee
+AddAttendance
1 +AddLeaves
+AddSalary
AssignedEmp +AddTotalPresenty
EmpID
ProjID
Designation
ProjectName
Department
Skills
+ViewEmp
+AddProj
+AddDesignation
+AddDepartment
+AddSkills

35 | P a g e
 Sequence Diagram

36 | P a g e
 Sequence diagram for Login:

System Database

Admin

Enter User name and password

Verification

Login Verified
Provide Access to system

Else

Unauthorized user

Invalid user

37 | P a g e
 Sequence diagram for Changing Password

System Database

Admin

Request for change password

Verification

Ask old and new password

Submit old and new password

Verification

Password protected

Update Password

Password updated

Receive confirmation

38 | P a g e
 Sequence diagram for adding or deleting Project and Supervisor

System Database

Admin
Request for Add/Update/Delete
Project or Supervisor

Add/ Update/ Delete

Project or Supervisor
Details

Add confirmation

View request form

Submit Project or Supervisor

details

Receive confirmation

Else

Project or Supervisor
already exits

User exit’s

39 | P a g e
 Sequence diagram for Checking Employee Salary

System Database

Admin
Request for Salary

Verification of Salary

Promote to insert details

Provide Information

Verification of information

Display Salary information

If any change

Changes Successful

40 | P a g e
 Sequence diagram for Checking Apply Leaves

System Database

Admin
Request for Leave

Verification of Leave

Promote to insert details

Provide Information

Verification of information

Confirmation of Leave

If any change

Changes Successful

41 | P a g e
 Sequence diagram for Checking Attendance

System Database

Admin
Request for Attendance

Verification of Attendance
Promote to insert details

Provide Information

Verification of information

Provide Information

If any change

Changes Successful

42 | P a g e
 Sequence diagram for adding or deleting attendance

System Database

Admin
Request for Add/Update/Delete
attendance

Add/ Update/ Delete

attendance Details

Add confirmation

View request form

Submit attendance details

Receive confirmation

Else

attendance already updated

User exit’s

43 | P a g e
 System Sequence

Diagram

44 | P a g e
 System Sequence Diagram for
Human Resource Management System

SYSTEM

ADMIN
Authenticate Admin

Admin authenticated

Change password

Update Password

Check Employee details

Add/ Modify/ Delete Employee

Check Project details

Add/ Modify/ Delete Project

Check daily attendance

Update daily attendance

Check approved leaves

Update approved leaves

Check Salary/ Deduction

Update Salary/ Deduction

45 | P a g e
 System Design

46 | P a g e
 Converting ERD to

tables

47 | P a g e
 Admin And Database

Admin

-username
Handles Database
-password -HRMS
-email

Admin And Employee

EmployeeDetails
Admin
-EmpID
Handles
-username -EmpAdd
-password -EmpFirstName
-email -EmpLastName
-EmpDOB
-EmpNationality
-EmpAddress
-EmpCity
-EmpState
-EmpPhoneNo
-EmpEmailID
-EmpSalary
-EmpGender
-EmpStatus
-EmpDepartment
-EmpDOJ
-EmpDesignation
-EmpSkills

48 | P a g e
 Admin And Attendance

Admin Attendance
Handles
-username -EmpID
-password -AttendID
-email -Date
-MarkAttend

Admin And NewProjects

NewProject
Admin
-ProjID
Handles
-username -ProjName
-password -Supervisor
-email
-SkillsRequired

Admin And AssignedEmployee

Admin AssignedEmp

Handles
-EmpID
-username
-ProjID
-password
-Designation
-email
-ProjName
-Department
-Skills

49 | P a g e
 Data Dictionary

50 | P a g e
 List Of Tables With Attributes And Constraints.

51 | P a g e
 Component Diagram

52 | P a g e
53 | P a g e
 Package Diagram

54 | P a g e
 VIEW LAYER

Admin Login Attendance New Project

Employee
Details

Employee
Assigned

DOMAIN LAYER

Attendance New Project

Admin Class
Class Class

EmpDetail
Class

EmpAssigned
Class

DATA ACCESS LAYER

dbo.Attendanc dbo.NewProjec
dbo.Admin
e t

dbo.EmpDetail

dbo.EmpAssign
ed

55 | P a g e
 CRUD Table

56 | P a g e
 Table Process Admin Employee Emp New Project Employee
Attendance Assigned

Emp Main Form C R

Emp Add Form R,U R

Emp Modify Form U

Emp Remove Form D

Project Main Form C R C

Project Add Form R,D R U

Project Modify U R U,D

Form

Project Remove D R D
Form

Attendance Main C R R
Form

Attendance Add R,U R U C,U

Form

Attendance U U U
Modify Form

Attendance D D D
Remove Form

Mark Attendance R,U,D R,U

Form

Add Skills Form U,D U U

Add designation U,D R U U

Add Department U,D U U

Leave Setup Form U,D R,U C,U,D

57 | P a g e
 Deployment Diagram

58 | P a g e
 Add

Database Update

Delete

Add

.Net frame Software Update

work
Delete

Application

Application
Execution Administrator

59 | P a g e
 System Coding

60 | P a g e
 Menu Tree Diagram/

Site Map

61 | P a g e
 Admin

Login

Employee

Employee Details

Employee Attendance

Mark Attendance

New Project

Department

SkillsRequired

62 | P a g e
 Validations

63 | P a g e
 i. Validation for empty ID field:
If the ID field is empty then display a message box— ID Field Empty.

ii. Validation for empty Password field:

If the Password field is empty then display a message box—
Password Field Empty.

iii. Validation for mandatory field:

If the mandatory field is empty then display a message box— Field
marked mandatory cannot be blank.

iv. Validation for Email field:

If the Email field is not valid then display a message box— Invaild
Email.

v. Validation for Employee code field:

If the code entered is already present in employee table then
display a message box— Code already exists.

vi. Validation for Project code field:

If the code entered is already present in product table then display
a message box— Code already exists.

vii. Validation for Attendance code field:

If the code entered is already present in attendance table then
display a message box— Code already exists.

viii. Validation for Department code field:

If the code entered is already present in department table then
display a message box— Code already exists.

ix. Validation for Employee leaves:

If the leave entered is more then total number of leaves display a
message box— Leave is unapproved.

x. Validation for Month Selection:

If the selection of month is not made display a message box—
Please select proper month.
64 | P a g e
xi. Validation for Mobile Number:
If the mobile number is not of 10 digits then display a message
box— Please enter proper number.

xii. Validation for Skills:

If the code entered is already present in skills table then display a
message box— Code already exists.

65 | P a g e
 Test Cases, Test

Data, Test Result

66 | P a g e
 Form Name Test Case Test Data State Test Input Expected
Value Result

Login Form User name and User name Valid Admin and Will allow to
password is and password *** enter into main
correct correct form

Employee Add Mandatory All fields filled Valid Numeric Accurate

Form fields fill, text properly fields, Text Employee data
values, fields saved in
numeric values database
field fill
properly

Project Add Mandatory All fields filled Valid Numeric Accurate

Form fields fill, text properly fields, Text Project data
values, fields, email saved in
numeric values ID fields database
field fill
properly

Designation Add Mandatory All fields filled Valid Numeric Accurate

Form fields fill, text properly fields, Text Designation
values, fields, email data saved in
numeric values ID fields database
field fill
properly

Required Skills Mandatory All fields filled Valid Numeric Accurate

Form fields fill, text properly fields, Text required skills
values, fields, email payment data
numeric values ID fields saved in
field fill database
properly

Employee Mandatory All fields filled Valid Numeric Accurate

Attendance fields fill, text properly fields, Text Employee
Form values, fields, email Attendance
numeric values ID fields records saved
field fill in database
properly

67 | P a g e
 Screen Layouts

68 | P a g e
69 | P a g e
 Maintenance and

Bibliography

70 | P a g e
 Future Enhancement

71 | P a g e
This software manages company’s employee details and applications such
as attendance details, employee leaves, Employee skills, department and
many more.

It provides the Manager with effective tools to keep track of the records
and easily manipulate them.

The software has wide scope in the future as its vast calculation of salary
earnings and deduction.

In future it can be enhanced with some more features like:

 Distributed systems.
 External modules like TDS.
 Extra modules like overtime.
 Full financial accounting system.
 A complete payroll software.

72 | P a g e
 Reference and

Bibliography

73 | P a g e
  C# 2010 Programming Black Book Covers .NET 4.0

By Kogent Learning Solutions

 Head first C# 2nd Edition 2nd Edition (Paperback)

By Andrew Stellman

 Professional Microsoft SQL Server 2008 Programming (paperback)

By Robert Vieira

 Microsoft SQL Server 2005: A Beginner's Guide (Paperback)

By Dusan Petkovic

 Beginning SQL Server 2012 For Developers

By Robin Dewson

Websites
 msdn.microsoft.com

 www.tutorialspoint.co

74 | P a g e