CASE STUDY ON

EMPLOYEE MANAGEMENT SYSTEM

Semester: V
Batch: 2020-24

Prepared by:
NAME OF STUDENT
NEHA SINGH
01UG20020032
Verified by:
MRS. PRINCY DIWAN

SCHOOL OF ENGINEERING
Department of Computer Science and Engineering

O P JINDAL UNIVERSITY
O P JINDAL KNOWLEDGE PARK, PUNJIPATRA, RAIGARH –
496109

1
 INDEX

S.No. Experiment Title DoP DoS Sign. Grade/Remark

1 Introduction to Software
Engineering-LAB.
2 Data flow diagram:
a. What processes make up a
system?
b. What data are used in each
process?
c. What data are stored?
d. What data enter and leave
the system?

3 Sample Design:
a. Class Diagram
b. Sequence Diagram
c. State Chart Diagram
d. Use-Case Diagram

4 Project Title:

4.1 Write down the problem statement

for a suggested system of relevance.
4.2 Do requirement analysis and
develop Software Requirement
Specification Sheet (SRS) for
suggested system.
4.3 Perform the Data Flow Diagram
(DFD).
4.4 Performa the Sequence Diagram.
4.5 Perform the State Chart Diagram.
4.6 Perform The Use-Case Diagram.
4.7 Perform the ER Diagram (If
Database applicable).
4.8 Prepare time line chart/Gantt
Chart/PERT Chart for selected
project.
5 a. Result
b. conclusion

2
 Experiment 1:
Introduction to Software Engineering-LAB

Objective:
To find the requirement specification (both functional and non-functional) of given Problem.
Step 1:
Introduction
Identify the product whose software requirements are specified in this document. Describe the
scope of the product that is covered by this SRS, particularly if this SRS describes only part
of the system or a single subsystem. Describe the different types of user that the document is
intended for, such as developers, project managers, marketing staff, users, testers, and
documentation writers. Describe what the rest of this SRS contains and how it is organized.
Suggest a sequence for reading the document, beginning with the overview sections and
proceeding through the sections that are most pertinent to each reader type.
Project Scope
Provide a short description of the software being specified and its purpose, including relevant
benefits, objectives, and goals. Relate the software to corporate goals or business strategies. If
a separate vision and scope document is available, refer to it rather than duplicating its
contents here. An SRS that specifies the next release of an evolving product should contain its
own scope statement as a subset of the long-term strategic product vision.
Step 2:
Overall Description
Product Perspective:
Describe the context and origin of the product being specified in this SRS. For example, state
whether this product is a follow-on member of a product family, a replacement for certain
existing systems, or a new, self-contained product. If the SRS defines a component of a larger
system, relate the requirements of the larger system to the functionality of this software and
identify interfaces between the two. A simple diagram that shows the major components of
the overall system, subsystem interconnections, and external interfaces can be helpful.
Product Features
Summarize the major features the product contains or the significant functions that it
performs or lets the user perform. Only a high level summary is needed here. Organize the
functions to make them understandable to any reader of the SRS. A picture of the major
groups of related requirements and how they relate, such as a top level data flow diagram or a
class diagram, is often effective.
User Classes and Characteristics
Identify the various user classes that you anticipate will use this product. User classes may be
differentiated based on frequency of use, subset of product functions used, technical expertise,
security or privilege levels, educational level, or experience. Describe the pertinent
characteristics of each user class. Certain requirements may pertain only to certain user
classes. Distinguish the favored user classes from those who are less important to satisfy.

3
Operating Environment
Describe the environment in which the software will operate, including the hardware
platform, operating system and versions, and any other software components or applications
with which it must peacefully coexist.
Design and Implementation Constraints
Describe any items or issues that will limit the options available to the developers. These
might include: corporate or regulatory policies; hardware limitations (timing requirements,
memory requirements); interfaces to other applications; specific technologies, tools, and
databases to be used; parallel operations; language requirements; communications protocols;
security considerations; design conventions or programming standards (for example, if the
customer’s organization will be responsible for maintaining the delivered software).
Step 3:
System Features
This template illustrates organizing the functional requirements for the product by system
features, the major services provided by the product. You may prefer to organize this section
by use case, mode of operation, user class, object class, functional hierarchy, or combinations
of these, whatever makes the most logical sense for your product.
System Feature 1
Don’t really say “System Feature 1.” State the feature name in just a few words.
1 Description and Priority
Provide a short description of the feature and indicate whether it is of High, Medium, or Low
priority. You could also include specific priority component ratings, such as benefit, penalty,
cost, and risk (each rated on a relative scale from a low of 1 to a high of 9).
2 Stimulus/Response Sequences
List the sequences of user actions and system responses that stimulate the behaviour defined
for this feature. These will correspond to the dialog elements associated with use cases.
3 Functional Requirements
Itemize the detailed functional requirements associated with this feature. These are the
software capabilities that must be present in order for the user to carry out the services
provided by the feature, or to execute the use case. Include how the product should respond to
anticipated error conditions or invalid inputs. Requirements should be concise, complete,
unambiguous, verifiable, and necessary.
<Each requirement should be uniquely identified with a sequence number or a
meaningful tag of some kind.>
REQ-1:
REQ-2:
Step 4:
External Interface Requirements

4
User Interfaces
Describe the logical characteristics of each interface between the software product and the
users. This may include sample screen images, any GUI standards or product family style
guides that are to be followed, screen layout constraints, standard buttons and functions (e.g.,
help) that will appear on every screen, keyboard shortcuts, error message display standards,
and so on. Define the software components for which a user interface is needed. Details of the
user interface design should be documented in a separate user interface specification.
Hardware Interfaces
Describe the logical and physical characteristics of each interface between the software
product and the hardware components of the system. This may include the supported device
types, the nature of the data and control interactions between the software and the hardware,
and communication protocols to be used.
Software Interfaces
Describe the connections between this product and other specific software components (name
and version), including databases, operating systems, tools, libraries, and integrated
commercial components. Identify the data items or messages coming into the system and
going out and describe the purpose of each. Describe the services needed and the nature of
communications. Refer to documents that describe detailed application programming
interface protocols. Identify data that will be shared across software components. If the data
sharing mechanism must be implemented in a specific way (for example, use of a global data
area in a multitasking operating system), specify this as an implementation constraint.
Communications Interfaces
Describe the requirements associated with any communications functions required by this
product, including e-mail, web browser, network server communications protocols, electronic
forms, and so on. Define any pertinent message formatting. Identify any communication
standards that will be used, such as FTP or HTTP. Specify any communication security or
encryption issues, data transfer rates, and synchronization mechanisms.
Non-functional Requirements
Performance Requirements
If there are performance requirements for the product under various circumstances, state them
here and explain their rationale, to help the developers understand the intent and make
suitable design choices. Specify the timing relationships for real time systems. Make such
requirements as specific as possible. You may need to state performance requirements for
individual functional requirements or features.
Safety Requirements
Specify those requirements that are concerned with possible loss, damage, or harm that could
result from the use of the product. Define any safeguards or actions that must be taken, as
well as actions that must be prevented. Refer to any external policies or regulations that state
safety issues that affect the product’s design or use. Define any safety certifications that must
be satisfied.
Security Requirements

5
Specify any requirements regarding security or privacy issues surrounding use of the product
or protection of the data used or created by the product. Define any user identity
authentication requirements. Refer to any external policies or regulations containing security
issues that affect the product. Define any security or privacy certifications that must be
satisfied.
Software Quality Attributes
Specify any additional quality characteristics for the product that will be important to either
the customers or the developers. Some to consider are: adaptability, availability, correctness,
flexibility, interoperability, maintainability, portability, reliability, reusability, robustness,
testability, and usability. Write these to be specific, quantitative, and verifiable when possible.
At the least, clarify the relative preferences for various attributes, such as ease of use over
ease of learning.
Other Requirements
Define any other requirements not covered elsewhere in the SRS. This might include
database requirements, internationalization requirements, legal requirements, reuse
objectives for the project, and so on. Add any new sections that are pertinent to the
project.

Experiment 2
Data flow diagram
Requirements: Any UML Software (Recommended: IBM Rational Rose, Umple, UMLet,
Modelio, diagrams.net/draw.io, JetUML, PlantUML, StarUML etc..)
Data analysis attempts to answer four specific questions:
a. What processes make up a system?
b. What data are used in each process?
c. What data are stored?
d. What data enter and leave the system?
Data drive business activities and can trigger events (e.g. new sales order data) or is processed
to provide information about the activity. Data flow analysis, as the name suggests, follows
the flow of data through business processes and determines how organization objectives are

6
accomplished. In the course of handling transactions and completing tasks, data are input,
processed, stored, retrieved, used, changed and output. Data flow analysis studies the use of
data in each activity and documents the findings in data flow diagrams, graphically showing
the relation between processes and data.
Physical and Logical DFDs
There are two types of data flow diagrams, namely physical data flow diagrams and logical
data flow diagrams and it is important to distinguish clearly between the two:
Physical Data Flow Diagrams
An implementation-dependent view of the current system, showing what tasks are carried out
and how they are performed. Physical characteristics can include:
a. Names of people
b. Form and document names or numbers
c. Master and transaction files
d. Equipment and devices used
Logical Data Flow Diagrams
An implementation-independent view of a system, focusing on the flow of data between
processes without regard for the specific devices, storage locations or people in the system.
The physical characteristics listed above for physical data flow diagrams will not be specified.

Experiment 3:
Sample Design
a. Class diagram

CLASS DIAGRAM FOR COLLEGE MANAGEMENT SYSTEM

7
B. Sequence Diagram

SEQUENCE DIAGRAM FOR ATM MECHINE

8
C. State-Chart Diagram

STATE CHART FOR MICRO OVEN

9
d.Use-case Diagram

USE CASE DIAGRAM FOR BANKING APP

Experiment 4:

Project:
A. Write down the problem statement for a suggested system of relevance.
PROBLEM STATEMENT
The problem definition for designing the system is to maintain data of employee, to make
easy controlling of employees, to divide jobs and access control between employees, to use
technology for accurate and timely processing by fully privacy and fully authority access The
objective of the project is to set up employee information system about status of employee
and attendance of employee and monthly salary process and delivery.

To eliminate or reduce as much as possible the handships of existing system and avoid errors
while entering data. No formal knowledge is needed for user to use the system. Whole system
is completely protected
B. Do requirement analysis and develop Software Requirement Specification Sheet
(SRS) for suggested system.

10
REQUIREMENT ANALYSIS:-
The aim of requirement analysis is to understand the exact requirement of the customer and to
document and to document them properly. Requirement analysis involves obtaining a clear
and thorough understanding of the product to be developing with a view to remove all
ambiguities and inconsistencies from the initial customer perception the problem.
The question arising during the requirement analysis phases is: -
● What is the problem?
● Why is it important to solve the problem?
● What are the possible solutions to the problem?
● What exactly are the data inputs and data outputs by system?
● What are the likely the complex cities that might arise while solving the problem?

During requirement analysis there exist mainly two activities.

1. Requirement gathering
2. Analysis of gathered requirements.

 Requirement gathering: - This involves interviewing the end user and customers to
collect all possible information regarding the bank.
 Analysis of gathered requirement: - The main purchase of analysis is to collect
information to clearly understand the exact requirement of customer and resolve
anomalies, conflicts and inconsistencies in the gathered requirement.

SOFTWARE REQUIREMENT SPECIFICATION (SRS)

The aim of the system is to develope “EMPLOYEE MANAGEMENT SYSTEM” software,
which should automate the process to create and store employee details . The system is
supposed to be used as a subsystem in a large office system, which could be manual system or
a computerized one. Therefore, the proposed system must be able to function under both
circumstances. The proposed system is not a freeware and due to the usage of swings,
becomes user interactive.

 The project demand a page of employee details that include:

 Employees personal detail.
 Employees salary, allowances, deductions.

C. Perform the Data Flow Diagram (DFD).

 Employee Management System DFD Level 0

To start with, let us familiarize what is Employee Management System DFD level 0.
The Employee Management System DFD level 0 is also known as context diagram. It's shows
an abstract view of main processes included in Employee managing.

11
This DFD level 0 illustration of the Employee Management System depicts the overall
structure as a single bubble. Then it will explain the processes as the dfd levels gets more
specific. It also comes with incoming/outgoing indicators showing input and output data.

 Employee Management System DFD Level 1

Next to the context diagram is the level 1 data flow diagram.
The content of Employee Management System DFD level 1 must be in accord from the idea
of context diagram. Then the context diagram will be broken down into its sub processes
which must display or reveal further processing information.
The following are essential data to accommodate:
• Employee Records
• Employee Information
• Time in Records
• Time out Records
• Leave Records

12
•Performance Report

 Employee Management System Level 2

After presenting the Employee Management System DFD levels 0 and 1, next in line is the
level 2.
Here's what you need to consider in creating data flow diagram level 2 for Employee
Management System.
• DFD Level 2 should present the system basic component, database and flow of data between
the processes in Employee Management.
• Since the DFD level 2 is the highest abstraction level, Employee Management System
processes must be detailed that is continuation of the DFD level 1.
The Processes that the system should prioritize are as follows:
• Manage Employee Information
• Check Time-in and out
• Manage Employee Leave
• Monitor Working days and hours
• Record Employees' Monthly Performance

13
D. Performa the Sequence Diagram.
This is the UML sequence diagram of Employee Management System which shows the
interaction be- tween the objects of Employee. Registration, Submit ,login. The instance of
class objects involved in this UML Sequence Diagram of Employee Management
System are as follows:

E. Perform the State Chart Diagram

State Chart Diagram is also called State Machine. It describes the flow of control from one
state to another state. States are defined as a condition in which an object exists and it changes

14
when some event is triggered. So the most important purpose of state char diagram is to
model life time of an object from creation to termination. As a result, state char diagram
shows the possible states of an object and the transitions that cause a change in state. We have
designed four state machines for our project. As state chart diagram is similar to activity
diagram so we will satisfy the following state machines

F. Perform The Use-Case Diagram.

Use Case Diagram is the combination of use cases of a system, a use case shows a single
function of the system. By looking at the use case diagram the stakeholder will know what
functionality the system have or will be included. They will know exactly who will be
interacting with system. And identify which functionality is excluded. So, we have designed
the following use case diagram for our project

15
G. Perform the ER Diagram (If Database applicable).

16
H. Prepare time line chart/Gantt Chart/PERT Chart for selected project.

Task Name % Completion Status

Workplaceplanning 80% Ongoing
Requirement & Selection Process 70% Ongoing
Employee Engagement Strategy 100% Completed
Performance Management Assessment & Strategy 55% Ongoing
Employee Retention Strategy 20% Ongoing

Diagrammtitel
0
EMPLOYEE RETENTION STRATEGY
20%

PERFORMANCE MANAGEMENT ASSESSMENT 0

&STRATERGY 55%

0
EMPLOYEE ENGAGEMENT STRATEGY
100%

0
RECRUIMENT & SELECTION PROCESS
70%

0
WORKPLACE PLANNING
80%

0% 20% 40% 60% 80% 100% 120%

Status %Completion

RESULT
17
Realization effect of main functions of the system

1. Login module.

The login module is used to verify the legitimacy of the user. The system can be entered after
verification, so as to prevent illegal users from entering the EMS. The user enters the system
by entering the user name and password created by the administrator. Below fig shows the
login page.

2.Employee Management System

Personnel management is used to input, query, add, modify and delete all the information of
enterprise staff from entering the duty to exiting the duty. Below fig shows the interface of
employee management system.

Fig manifests that after entering the personnel management page of the system, the
administrator needs to enter the employee’s certificate, the employee ’s work number in the
company, the date of birth, gender, the postal code of the location, the bank account number
of the payroll card, the employee’s educational background and the information of the

18
graduating school, family address, contact mode, the current department in the company and
the position of the employee for later query and deletion.

3. Organization management.

Organizational management is a comprehensive management of enterprise architecture and

job information, including comprehensive information of various departments, existing
positions and vacant positions, so that enterprises can adjust and deploy relevant departments
and positions in a timely manner in the development process. Below fig shows the interface
of the organizational management.

4. Recruitment management.

Recruitment management is the most basic part of EMS, which is mainly used to track and
record the recruitment process of new employees, including recruitment content promotion,
resume reception, appointment interview and entry approval. Fig shows the interface of the
recruitment management.

19
5. Training management.

Training management is an important part of EMS, which is mainly used to track the whole
process of enterprise training, including training plan, training implementation, training
feedback and opinions. Below fig shows the interface of training management.

6. Salary management.

Salary management is mainly used for the accounting, recording and managing of wages and
insurance of employees. It includes compensation accounting and management, wage data
records, employee tax and social security cost accounting, welfare payment schedule records
and open query permissions of employees. Below fig shows the interface of the salary
management.

20
Performance of the system

In the system performance test, 100 users operate the system at the same time. Below
fig show the results of performance test.

Fig A manifests that, the system’s personnel management, organizational management,

recruitment management, training management and compensation management of the five
major functional modules in the processing of business host throughput are 101.36 times/s,

21
102.28 times/s, 100.67 times/s, 100.29 times/s, and 101.59 times/s; more than 100 times/s.
Besides, the success rates of event processing are 99.5%, 99.7%, 99.7%, 99.6% and 99.8%,
respectively; more than 99%, the success rate is high. Fig B shows that the average response
time of the terminal side of the 5 functional modules is 0.34s, 0.4s, 0.38s, 0.35s and 0.29s,
respectively, which is maintained below 0.5s. The average response time of business-side
processing is 0.24s, 0.31s, 0.29s, 0.21s and 0.26s, respectively, which is less than 0.4s and
meets the standard. Fig C indicates that the CPU occupancy rates of the five functional
modules in the system are 25%, 19%, 21%, 29% and 17%, respectively, which are less than
30%. The memory occupancy rates are 20%, 22%, 11%, 27% and 15%, respectively, and are
all below 30%. In summary, the system designed here has excellent throughput, event
processing ability, and response speed. When dealing with business, its CPU and memory
occupancy rates are low, which is suitable for application in enterprises to improve the overall
efficiency and management quality.

Conclusions
Talent management is the key section for enterprises to stand out in the fierce market
competition. It is very important to have a high level of employee management system. At the
beginning, analyzation is made on the overall needs, feasibility, and key technologies of
enterprise EMS system. Then based on the user’s key functional requirements and related
technologies, a reasonable and easy to maintain EMS is designed and developed. The system
mainly includes six modules: personnel management, organizational management,
recruitment management, training management, salary management and system management,
which integrates enterprise information and realizes the functions of easy access and easy
query of information database. Interface simple, easy to understand, easy to operate; low
investment, low cost, high safety, good performance and easy maintenance, these factors
within the system can make it improve the work efficiency and modern management level of
enterprises. In the end, the operation performance of the system is tested. The results show
that the throughput of the main function modules in the system is greater than 100 times/s
when dealing with the business, and the success rate of event processing is greater than 99%.
The average response time of the business end is less than 0.4s, and the average response time
of the terminal side is less than 0.5s, which all meet the standards. System CPU occupancy
rate can be basically controlled below 30%, memory usage rate is below 30%. In summary,
the system designed here has the basic functions but also to ensure good performance,
suitable for enterprise personnel management, organizational management, recruitment
management, training management and salary management. The deficiency is that the system
is still in the design and developing stage, and it is not used in the actual enterprise work.
Whether it is suitable for most enterprises remains to be further verified. In the future, this
system should be promoted and tested in different types of enterprises. In this process, the
function and performance of the system should be continuously improved according to the
needs of different enterprises and the problems found. The design and development of this
system aims to provide technical support for the service quality of enterprise human resource
management business, improve the overall efficiency, promote the pace of enterprise strategic
development, and enhance the market competitiveness of enterprises.

22