EMPLOYEE RECORD

SYSTEM
Submitted By-
Rohit Rawat, Sachin Kumar, Sahil Kohar,
Samrat kumar, Sarique Anwar

Submitted to-
Asst. Prof. Rishi Sharma
CONTENT
• Introduction​
• ER Diagram
• ​Data Dictionary
• Extended ER Model
• Written Documents
• Table Instance Chart
• Conclusion
 INTRODUCTION
Employee Record System is used to manage the
data of the employees such as personal details,
education, details, work experience, etc.

Aim of the Employee’s Record System:

 Keep the record of the Employees
 Manage Salaries and Bonuses
 Manage Job Departments and Status
 Manage and Monitor Transaction Records
ER DIAGRAM
DATA DICTIONARY
COMPANY
Field Name Data Field Size Description
type
Cno integer 11 No./id of company

C_name varchar 255 Name of company

address varchar 255 Address of company

DEPARTMENT
Field Name Data type Field Size Description

Dno integer 11 No./id of department

D_name varchar 255 Name of department

Location varchar 255 Location of Department

EMPLOYEE PROJECT
Field Name Data Field size Description Field Name Data Field size Description
type type
Pno integer 11 No. of project Pno integer 11 No. of project
Pname varchar 255 Name of project
Pname varchar 255 Name of project
Plocation varchar 255 location
Salary integer 11 Salary of employee Plocation varchar 255 location

dob date Date of birth

Gender varchar 11 Gender of employee

DEPENDENT
Field Name Data type Field size Description
name varchar 255 Name of dependent
dob date Date of birth
sex varchar 11 Gender of dependent
Relationship varchar 255 Relationship with
employee
EXTENDED ER MODEL
SPECIALIZATION
 An EMPLOYEE can be Permanent,
Temporary and Part-time.
 EMPLOYEE a higher level entity is
broken down into three low level
entities : PERMANENT,
TEMPORARY, PARTTIME.
 These low level entities Inherits the
attributes of the EMPLOYEE entity
apart from that they have their own
attributes.
AGGREGATION

Employee working for a project may use

some machinery. So, “use” relationship
is needed between relationship “works
on” and entity MACHINERY. Using
aggregation, “works on” relationship
with its entities EMPLOYEE and
PROJECT is aggregated into single
entity and relationship “use” is created
between aggregated entity and
MACHINERY.
9
WRITTEN DOCUMENTS
INFORMATION REQUIREMENTS

 Data must be up-to-date

 It must also keep track of the employee ’s work ethic, leaves taken,
behaviour, etc and based on which increments in the employee ’s
salary is done.
 It must keep track of the employee’s place of residence or address.
 It must contain information about the employee ’s dependent like
their address, name and relationship with the client for emergency
situations.
BUSINESS REQUIREMENTS ASSUMPTIONS

 A employee may be an orphan or  More information about the

have no dependents. employee like their taken leaves,
 Many employees may work in a information about their work ethic
single department. and behaviour with other
employees are stored elsewhere
 A single employee gets only a
but are accessible by this system.
specific amount of salary.
 Employees are aware that some
 A single department is in charge of a
part of this information can be
single project.
seen by their superiors and some
 Many employees work on a single
part of this information is hidden.
project.
 A single employee may become the
manager of a department.
RECOMMENDATIONS

 Some additional applications can be implemented and integrated

like for instance.
 An employee is usually given an increment in his/her salary every
year and as such the Salary entity can have more attributes to
reflect this.
 Instead of using the Full_Name composite attribute in the
Employee entity we can use the Full_Name as a single attribute to
reduce redundancy.
 The relationship between the employee and dependent is left
unclear from the dependent side, so for future work it must be
resolved.
TABLE INSTANCE CHART
COMPANY
Column Name Cno C_name address
Key type pk
Nulls/Unique Unique & Not Not null
null
Sample Data 1195280 Unicorn limited Delhi

DEPARTMENT
Column Name Dno D_name LocationId
Key type pk
Nulls/Unique Unique & Not Not null
null
Sample Data 1 10 Human 201
Resources
Sample Data 2 14 Sales 302
Sample Data 3 17 IT 220
 PROJECT
EMPLOYEE Column Name Pno Pname Plocation
Column Eid Name Addre salary dob Gender Key type pk
Name ss Nulls/Unique Unique & not Not null
Key type pk null
Nulls/ Unique Not Not null Sample Data 1 21089 Durango 201
Unique & Not null Sample Data 2 22069 Eagle Wink 301
null Sample Data 3 21054 Apollo 220
Sample 189990 Reena Delhi 30000 12- F
Data 1 Sharma may-
1998
Sample 178989 Akshit Mumb 40000 13- M
Data 2 Arora ai feb-
1997
DEPENDENT
Sample 167889 Shalini Agra 35000 01- F
Data 3 Mathur dec- Column name dob sex Relationshi
1996 Name p
Key type
Nulls/ Not null Not null
unique
Sample anita 13-feb- F Wife
Data 2023
CONCLUSION
• This system is designed for the particular need of the
company to carry out its operations in a smooth and
effective manner.
• This design is built for use in small scale organizations
where the number of employees is limited.
• The main objective of this framework is to save time,
make the system cost effective and manage records
efficiently.
THANK YOU