TABLE OF CONTENTS [ T O C ]

SNO DESCRIPTION PAGE NO

01 ACKNOWLEDGEMENT 04

02 INTRODUCTION 05

03 OBJECTIVES OF THE PROJECT 05

04 PROPOSED SYSTEM 06

05 SYSTEM DEVELOPMENT LIFE CYCLE (SDLC) 07

06 PHASES OF SYSTEM DEVELOPMENT LIFE CYCLE 08

07 FLOW CHART 15

08 SOURCE CODE 18

09 OUTPUT 29

10 TESTING 30

11 HARDWARE AND SOFTWARE REQUIREMENTS 31

12 BIBLIOGRAPHY 32

4
 PROJECT ON EMPLOYEE MANAGEMENT SYSTEM

INTRODUCTION

This Employee Management System created to manage the employee data. This system
created to record all data of the employee. You can add, edit, and delete data in this system.
The other function, you can change also the password.
Employee Management System Project is an essentially software designed to keep
track of employee information in any company. It stores data such as their employees'
personal information. The goal of "Employee Management System" is to create a work center
scheduling system. Scheduling is a technology that makes the process of informing activities
and notifications in the company where it is implemented simple and even online. The
employee management system project gives managers a better idea of their employees and
helps them plan and manage their work hours in order to cut costs and boost productivity. It
gives appropriate directions and supervisions for employees. It also secures and manages
information that are important to the employees including personal and work-related
information.

OBJECTIVES OF THE PROJECT

Employee Management System is a distributed application, developed to maintain the details

of employees working in any organization. It maintains the information about the personal
details of their employees, also the details about the payroll system which enable to generate
the payslip/[Link] management system is an application that allows us to add,
update, delete and maintain records of all employees working in multiple organizations for
multiple projects. Users can login into this application and modify the employees details as
well as he can add ,update delete and maintain the records of project as well as company.

5
PROPOSED SYSTEM

Employee Record Management System project used to manage the data of the employees
such as personal details, education details, work exp etc. This project will reduce the paper
work of the company .
 Admin Login
 Admin can manage all employee records.
 Admin can update / edit user personal details/ work exp. details / Education.
 Admin can delete Employee and employee record.
 Admin can update own profile
 Change password
 Logout

It will be able to manage information about Employee in more user friendly way. This system
will manage Employees information at various field offices. User ID and password has been
given to all the field offices so that they can enter their employee’s information into central
database. Their access to the central database is restricted to their information only. Various
reports based on the data entered by employees at field offices are generated at Head Quarter.
These reports are helpful in Manpower management decisions.

Featured System

1. Add new employee data

2. Edit employee data
3. Delete employee data
4. Change employee password
5. Filter employee data

Project will allow admin to add new employees after proper authentication. Admin can also
add new departments and posts. It can allocate employees to different departments at
different posts. Database should store all personal details of employees such as date of birth

6
full name etc. and his educational background, work experience, skill sets, current and past
projects in different tables with proper relations. Administrator will maintain the employee
information and timesheet. In this system the administrator will issue a specific ID to the
employee. The employee duty is to get registered in the system and submit his particulars.

SYSTEM DEVELOPMENT LIFE CYCLE (SDLC)

The systems development life cycle is a project management technique that divides
complex projects into smaller, more easily managed segments or phases. Segmenting projects
allows managers to verify the successful completion of project phases before allocating
resources to subsequent phases.
Software development projects typically include initiation, planning, design,
development, testing, implementation, and maintenance phases. However, the phases may be
divided differently depending on the organization involved.
For example, initial project activities might be designated as request, requirements-
definition, and planning phases, or initiation, concept-development, and planning phases. End

7
users of the system under development should be involved in reviewing the output of each
phase to ensure the system is being built to deliver the needed functionality.

PHASES OF SYSTEM DEVELOPMENT LIFE CYCLE

INITIATION PHASE

The Initiation Phase begins when a business sponsor identifies a need or an opportunity.

The purpose of the Initiation Phase is to:

Identify and validate an opportunity to improve business accomplishments of the

organization or a deficiency related to a business need.
Identify significant assumptions and constraints on solutions to that need.
Recommend the exploration of alternative concepts and methods to satisfy the need
including questioning the need for technology, i.e., will a change in the business
process offer a solution?
Assure executive business and executive technical sponsorship. The Sponsor
designates a Project Manager and the business need is documented in a Concept
Proposal. The Concept Proposal includes information about the business process
andthe relationship to the Agency/Organization.
Infrastructure and the Strategic Plan. A successful Concept Proposal results in a
Project Management Charter which outlines the authority of the project manager to
begin
the project.

Careful oversight is required to ensure projects support strategic business objectives

and resources are effectively implemented into an organization's enterprise architecture. The
initiation phase begins when an opportunity to add, improve, or correct a system is identified
and formally requested through the presentation of a business case. The business case should,
at a minimum, describe a proposal’s purpose, identify expected benefits, and explain how the
proposed system supports one of the organization’s business strategies. The business case
should also identify alternative solutions and detail as many informational, functional, and
network requirements as possible.

8
SYSTEM CONCEPT DEVELOPMENT PHASE

The System Concept Development Phase begins after a business need or opportunity is
validated by the Agency/Organization Program Leadership and the Agency/Organization
CIO.

The purpose of the System Concept Development Phase is to:

Determine the feasibility and appropriateness of the alternatives.

Identify system interfaces.
Identify basic functional and data requirements to satisfy the business need.
Establish system boundaries; identify goals, objectives, critical success factors, and
performance measures.
Evaluate costs and benefits of alternative approaches to satisfy the basic functional
requirements
Assess project risks
Identify and initiate risk mitigation actions, andDevelop high-level technical
architecture, process models, data models, and a concept of operations. This phase
explores potential technical solutions within the context of the business need.
It may include several trade-off decisions such as the decision to use COTS software
products as opposed to developing custom software or reusing software components,
or the decision to use an incremental delivery versus a complete, onetime deployment.
Construction of executable prototypes is encouraged to evaluate technology to support
the business process. The System Boundary Document serves as an important
reference document to support the Information Technology Project Request (ITPR)
process.
The ITPR must be approved by the State CIO before the project can move forward.

9
PICTORIAL REPRESENTATION OF SDLC:

PLANNING PHASE

The planning phase is the most critical step in completing development, acquisition,
and maintenance projects. Careful planning, particularly in the early stages of a project, is
necessary to coordinate activities and manage project risks effectively. The depth and
formality of project plans should be commensurate with the characteristics and risks of a
given project. Project plans refine the information gathered during the initiation phase by
further identifying the specific activities and resources required to complete a project.
A critical part of a project manager’ sjob is to coordinate discussions between user,
audit, security, design, development, and network personnel to identify and document as

10
many functional, security, and network requirements as possible. During this phase, a plan is
developed that documents the approach to be used and includes a discussion of methods,
tools, tasks, resources, project schedules, and user input. Personnel assignments, costs,
project schedule, and target dates are established.
A Project Management Plan is created with components related to acquisition
planning, configuration management planning, quality assurance planning, concept of
operations, system security, verification and validation, and systems engineering management
planning.

REQUIREMENTS ANALYSIS PHASE

This phase formally defines the detailed functional user requirements using high-level
requirements identified in the Initiation, System Concept, and Planning phases. It also
delineates the requirements in terms of data, system performance, security, and
maintainability requirements for the system. The requirements are defined in this phase to
alevel of detail sufficient for systems design to proceed. They need to be measurable,
testable, and relate to the business need or opportunity identified in the Initiation Phase. The
requirements that will be used to determine acceptance of the system are captured in the Test
and Evaluation MasterPlan.

The purposes of this phase are to:

Further define and refine the functional and data requirements and document them in
the Requirements Document,
Complete business process reengineering of the functions to be supported (i.e., verify
what information drives the business process, what information is generated, who
generates it, where does the information go, and who processes it),
Develop detailed data and process models (system inputs, outputs, and the process.
Develop the test and evaluation requirements that will be used to determine
acceptable system performance.

11
DESIGN PHASE

The design phase involves converting the informational, functional, and network
requirements identified during the initiation and planning phases into unified design
specifications that developers use to scriptprograms during the development phase. Program
designs are c onstructed in various ways. Using a top-down approach, designers first identify
and link majorprogram components and interfaces, then expand design layouts as they
identify and link smaller subsystems and connections. Using a bottom-up approach, designers
first identify and link minor program components and interfaces, then expand design layouts
as they identify and link larger systems and connections. Contemporary design techniques
often use prototyping tools that build mock-up designs of items such as application screens,
database layouts, and system architectures. End users, designers, developers, database
managers, and network administrators should review and refine the prototyped designs in an
iterative process until they agree on an acceptable design. Audit, security, and quality
assurance personnel should be involved in the review and approval process. During this
phase, the system is designed to satisfy the functional requirements identified in the previous
phase. Since problems in the design phase could be very expensive to solve in the later stage
of the software development, a variety of elements are considered in the design to mitigate
risk. These include:

Identifying potential risks and defining mitigating design features.

Performing a security risk assessment.
Developing a conversion plan to migrate current data to the new system.
Determining the operating environment.
Defining major subsystems and their inputs and outputs.
Allocating processes to resources.
Preparing detailed logic specifications for each software module. The result is a draft
System Design Document which captures the preliminary design for the system.
Everything requiring user input or approval is documented and reviewed by the user.
Once these documents have been approved by the Agency CIO and Business Sponsor,
the final System Design Document is created to serve as the Critical/Detailed Design
for the system.

12
 This document receives a rigorous review byAgency technical and functional
representatives to ensure that it satisfies the business requirements. Concurrent with
the development of the system design, the Agency Project Manager begins
development of the Implementation Plan, Operations and Maintenance Manual, and
the Training Plan.

DEVELOPMENT PHASE

The development phase involves converting design specifications into executable

programs. Effective development standards include requirements that programmers and
other project participants discuss design specifications before programming begins. The
procedures help ensure programmers clearly understand program designs and functional
requirements. Programmers use various techniques to develop computer programs. The
large transaction oriented programs associated with financial institutions have
traditionally been developed using procedural programming techniques. Procedural
programming involves the line-by-line scripting of logical instructions that are combined
to form a [Link] completion of the previous stages is a key factor in the
success of the Development phase. The Development phase consists of:

Translating the detailed requirements and design into system components.

Testing individual elements (units) for usability.
Preparing for integration and testing of the IT system.

INTEGRATION AND TEST PHASE

Subsystem integration, system, security, and user acceptance testing is conducted

during the integration and test phase. The user, with those responsible for quality
assurance, validates that the functional requirements, as defined in the functional
requirements document, are satisfied by the developed or modified system. OIT
Security staff assess the system security and issue a security certification and
accreditation prior to installation/implementation.

13
Multiple levels of testing are performed, including:

Testing at the development facility by the contractor and possibly supported by end
users

Testing as a deployed system with end users working together with contract personnel

Operational testing by the end user alone performing all functions. Requirements are
traced throughout testing,a final Independent Verification & Validation evaluation is
performed and all documentation is reviewedand accepted prior to acceptance of the
system.

IMPLEMENTATION PHASE

This phase is initiated after the system has been tested and accepted by the user. In
this phase, the system is installed to support the intended business functions. System
performance is compared to performance objectives established during the planning phase.
Implementation includes user notification, user training, installation of hardware, installation
of software onto production computers, and integration of the system into daily work
processes. This phase continues until the system is operating in production in accordance
with the defined userrequirements.

OPERATIONS AND MAINTENANCE PHASE

The system operation is ongoing. The system is monitored for continued performance
in accordance with user requirements and needed system modifications are incorporated.
Operations continue as long as the system can be effectively adapted to respond to the
organization’s needs. When modifications or changes are identified, the system may reenter
the planning phase.

The purpose of this phase is to:

Operate, maintain, and enhance the system.

14
 Certify that the system can process sensitive information.
Conduct periodic assessments of the system to ensure the functional requirements
continue to be satisfied.
Determine when the system needs to be modernized, replaced, or retired.

TESTING

Software Testing is an empirical investigation conducted to provide stakeholders with

information about the quality of the product or service under test[1] , with respect to the
context in which it is intended to operate. Software Testing also provides an objective,
independent view of the software to allow the business to appreciate and understand the risks
at implementation of the software. Test techniques include, but are not limited to, the process
of executing a program or application with the intent of finding software bugs.
It can also be stated as the process of validating and verifying that a software
program/application/product meets the business and technical requirements that guided its
design and development, so that it works as expected and can be implemented with the same
characteristics. Software Testing, depending on the testing method employed, can be
implemented at any time in the development process, however the most test effort is
employed after the requirements have been defined and coding process has been completed.

TESTING METHODS
Software testing methods are traditionally divided into black box testing and white
box testing. These two approaches are used to describe the point of view that a test engineer
takes when designing test cases.

BLACK BOX TESTING

Black box testing treats the software as a "black box," without any knowledge of
internal implementation. Black box testing methods include: equivalence partitioning,
boundary value analysis, all-pairs testing, fuzz testing, model-based testing, traceability
matrix, exploratory testing and specification-based testing.

15
SPECIFICATION-BASED TESTING

Specification-based testing aims to test the functionality of software according to the

applicable requirements.[16] Thus, the tester inputs data into, and only sees the output from,
the test object. This level of testing usually requires thorough test cases to be provided to the
tester, who then can simply verify that for a given input, the output value (or behaviour),
either "is" or "is not" the same as the expected value specified in the test case. Specification-
based testing is necessary, but it is insufficient to guard against certain risks

ADVANTAGES AND DISADVANTAGES

The black box tester has no "bonds" with the code, and a tester's perception is very
simple: a code must have bugs. Using the principle, "Ask and you shall receive," black box
testers find bugs where programmers don't. But, on the other hand, black box testing has been
said to be "like a walk in a dark labyrinth without a flashlight," because the tester doesn't
know how the software being tested was actually constructed.
That's why there are situations when (1) a black box tester writes many test cases to
check something that can be tested by only one test case, and/or (2) some parts of the back
end are not tested at all. Therefore, black box testing has the advantage of "an unaffiliated
opinion," on the one hand, and the disadvantage of "blind exploring," on the other.

WHITE BOX TESTING

White box testing, by contrast to black box testing, is when the tester has access to the
internal data structures and algorithms (and the code that implement these)

Types of white box testing:-

The following types of white box testing exist:
api testing - Testing of the application using Public and Private APIs.
Code coverage - creating tests to satisfy some criteria of code coverage.
For example, the test designer can create tests to cause all statements in the program
to be executed at least once.

16
 fault injection methods.
mutation testing methods.
static testing - White box testing includes all static testing.

CODE COMPLETENESS EVALUATION

White box testing methods can also be used to evaluate the completeness of a test
suite that was created with black box testing methods. This allows the software team to
examine parts of a system that are rarely tested and ensures that the most important function
points have been tested.

Two common forms of code coverage are:

Function Coverage: Which reports on functions executed and
Statement Coverage: Which reports on the number of lines executed to
complete the test.
They both return coverage metric, measured as a percentage

17
Flowchart:

Username Admin Password

Login

User Id
Post id 1

1 M
Employee Check data entry User data
Post Insert Information
1 M System
Detail
1
Post

Registration

Employee

Empl. Id Detail

18
 HARDWARE AND SOFTWARE REQUIREMENTS

 OPERATING SYSTEM : WINDOWS 7 AND ABOVE

 PROCESSOR : PENTIUM(ANY) OR AMD
ATHALON(3800+- 4200+ DUAL
CORE)
 RAM : 512MB+
 Hard disk : SATA 40 GB OR ABOVE
 CD/DVD r/w multi drive combo: (If back up required)
 MONITOR 14.1 or 15 -17 inch
 Key board and mouse
 Printer : (if print is required – [Hard copy])

SOFTWARE REQUIREMENTS:

I. Windows OS
II. Python

19
Employee

20
21
# importing required libraries

import [Link]

from datetime import date

import re

'''

CREATE DATABASE employee;

use employee;

CREATE TABLE empdata (

Id INT(11) PRIMARY KEY , Name VARCHAR(1800),

Email_Id TEXT(1800),

Phone_no BIGINT( 11 ),

Address TEXT(1000),

Post TEXT(1000),

Salary BIGINT(20));

'''

22
# for validating an Email

regex = r'\b[A-Za-z0-9._%+-]+@[A-Za-z0-9.-]+\.[A-Z|a-z]{2,}\b'

# for validating an Phone Number

Pattern = [Link]("(0|91)?[7-9][0-9]{9}")

def askUser():

print('=============================')

print('= Welcome to Employee Payroll . Menu =')

print('=============================')

print(" 1. Employee Entry" )

print(" 2. Employee Promotion")

print(" 3. Delete Employee ")

print(" 4. View Employees ")

print(" 5. Employee Salary Breakup")

print("99. Quit")

command1 = int(input("Enter your command: "))

menuSelection(command1)

def menuSelection(CHOICE):

if CHOICE == 1:

empentry()

elif CHOICE == 2:

23
 UpdateSal()

elif CHOICE == 3:

delemp()

elif CHOICE == 4:

viewemp()

elif CHOICE == 5:

salcal()

elif CHOICE == 99:

exit()

def empentry():

print('= Employee New Entry =')

print('=============================')

Id = input("Enter Employee Id: ")

if (check_employee(Id) == True):

print("Employee ID Already Exists\nTry Again..")

press = input("Press Any Key To Continue..")

empentry()

Name = input("Enter Employee Name: ")

Email_Id = input("Enter Employee Email ID: ")

if([Link](regex, Email_Id)):

print("Valid Email")

else:

print("Invalid Email")

24
 press = input("Press Any Key To Continue..")

empentry()

Phone_no = input("Enter Employee Phone No.: ")

if([Link](Phone_no)):

print("Valid Phone Number")

else:

print("Invalid Phone Number")

press = input("Press Any Key To Continue..")

empentry()

Address = input("Enter Employee Address: ")

Post = input("Enter Employee Post: ")

Salary = input("Enter Employee Salary: ")

con = [Link](host ="localhost",user ="root",passwd ="aathi123",database =

"employee")

# preparing a cursor object

cur = [Link]()

[Link]("insert into empdata values(%s,%s,%s,%s,%s,%s,%s)",(Id, Name, Email_Id, Phone_no,

Address, Post, Salary))

[Link]()

[Link]()

print(" Employee Record Added Succesful")

CHOICE = int(input('Enter 98 to continue or 99 to exit: '))

if CHOICE == 98:

askUser()

else:

exit()

25
def check_employee(employee_id):

#employee_idd=int(employee_id)

con = [Link](host ="localhost",user ="root",passwd ="aathi123",database =

"employee")

# preparing a cursor object

cur = [Link]()

[Link]("select * from empdata where Id = %s",(employee_id,))

row=[Link]()

if row!=None:

return True

else:

return False

def UpdateSal():

print('= Update Salary =')

print('=============================')

Id = input("Enter Employee Id: ")

# checking If Employee Id is Exit Or Not

if(check_employee(Id) == False):

print("Employee Record Not exists\nTry Again")

press = input("Press Any Key To Continue..")

askUser()

else:

Amount = int(input("Enter Increase Salary: "))

#query to fetch salary of Employee with given data

26
 con = [Link](host ="localhost",user ="root",passwd ="aathi123",database =
"employee")

# preparing a cursor object

cur = [Link]()

[Link]("select Salary from empdata where Id = %s",(Id,))

#fetching salary of Employee with given Id

r = [Link]()

t = r[0]+Amount

cur = [Link]()

#query to update salary of Employee with given id

[Link]("update empdata set Salary = %s where Id = %s",(t, Id))

[Link]()

print("Employee Promoted")

CHOICE = int(input('Enter 98 to continue or 99 to exit: '))

if CHOICE == 98:

askUser()

else:

exit()

def delemp():

print('= Delete Employee =')

print('=============================')

27
 Id = input("Enter Employee Id: ")

# checking If Employee Id is Exit Or Not

if(check_employee(Id) == False):

print("Employee Record Not exists\nTry Again")

press = input("Press Any Key To Continue..")

askUser()

else:

con = [Link](host ="localhost",user ="root",passwd ="aathi123",database =

"employee")

# preparing a cursor object

cur = [Link]()

[Link]("delete from empdata where Id = %s",(Id,))

[Link]()

[Link]()

print("Delete Successful")

CHOICE = int(input('Enter 98 to continue or 99 to exit: '))

if CHOICE == 98:

askUser()

else:

exit()

def viewemp():

print('= View Employees =')

print('=============================')

con = [Link](host ="localhost",user ="root",passwd ="aathi123",database =

"employee")

28
 # preparing a cursor object

cur = [Link]()

[Link]("select * from empdata")

myresult=[Link]()

for x in myresult:

print(x)

[Link]()

CHOICE = int(input('Enter 98 to continue or 99 to exit: '))

if CHOICE == 98:

askUser()

else:

exit()

def salcal():

print('= Employee Salary Receipt =')

print('=============================')

Id = input("Enter Employee Id: ")

# checking If Employee Id is Exit Or Not

if(check_employee(Id) == False):

print("Employee Record Not exists\nTry Again")

press = input("Press Any Key To Continue..")

askUser()

else:

con = [Link](host ="localhost",user ="root",passwd ="aathi123",database =

"employee")

# preparing a cursor object

29
cur = [Link]()

[Link]("select * from empdata where Id = %s",(Id,))

row=[Link]()

name=row[1]

basic=float(row[6])

da=float(basic*0.25)

hra=float(basic*0.15)

pf=float((basic+da)*0.12)

ta=float(basic*0.075)

netpay=float(basic+da+hra+ta)

grosspay=float(netpay-pf)

print("\n\n")

print("S A L A R Y D E T A I L E D B R E A K U P ")

print("==============================================")

print(" NAME OF EMPLOYEE : ",name)

print(" BASIC SALARY : ",basic)

print(" DEARNESS ALLOW. : ",da)

print(" HOUSE RENT ALLOW.: ",hra)

print(" TRAVEL ALLOW. : ",ta)

print("==============================================")

print(" NET SALARY PAY : ",netpay)

print(" PROVIDENT FUND : ",pf)

print("==============================================")

print(" GROSS PAYMENT : ",grosspay)

print("==============================================")

30
 CHOICE = int(input('Enter 98 to continue or 99 to exit: '))

if CHOICE == 98:

askUser()

else:

exit()

askUser()

31
 CONCLUSION

This project is used for computerizing employee management work in offices,

schools, etc. The software keeps record of employee’s attendance, provident fund, gratuity
and salary and generates the slip of salary too. The software is capable of easy storage of
information related to employee through database.

BIBLIOGRAPHY

1. [Link]
2. [Link]
3. [Link]

32