You are on page 1of 81

EMPLOYEE MANAGEMENT SYSTEM

Submitted By
Vivek S. Shah
Exam No-230

Developed GEA Process Engineering (India) Private


For : Limited
1. Project Profile

Project Title EMPLOYEE MANAGEMENT SYSTEM


Developed For GEA Process Engineering (India) private Limited
Project Description This Application Provide the Employee Self Service Employee
Management
Project Duration 6 Months.
Type Of Application Intranet (Multi User System )
Front end tools JAVA Technology (JSP, Servlets, JDBC) Using MVC Architecture
Back end tools ORACLE 10.2.1G
Tools IDE : Netbeans 6.8 Reporting Tool : Jasper Report
2. About the Organization

GEA Process Engineering (India) Private Limited, formerly known as L&T-Niro Limited and Food
Division (Dairy) of Larsen & Toubro Limited, India, are now a part of GEA Process Engineering Division
(Processing, Membrane Filtration, Concentration, Drying, Powder Processing & Handling, and supplies
customized and advanced plant & equipment with safe and reliable process controls. GEA P-Division is
part of the Process Engineering segment of GEA Group Aktiengesellschaft, Germany.

GEA Process Engineering (India) Private Limited has a strong Project Management Team and we have
supplied several high-tech plants to the leading manufacturers in Food & Dairy, Brewery and Chemical
sectors on a turnkey and EPC (Engineering, Procurement & Construction) basis. We offer total
solutions - from "Concept to Commissioning" with GEA's integrated strength in Process Technology,
Basic & Detailed Engineering, Equip-Division), world leader in liquid and solid processing
technologies. GEA P-Division focuses on Liquid ent Fabrication, Automation, Project
Management, Construction & Commissioning to build turnkey projects for a complete range of plants
& systems.

GEA Process Engineering (India) Private Limited is a part of the GEA Process Engineering Division (P-
Division) of GEA Group Germany. GEA stands for Global Engineering Alliance and is a leading global
technology group.
3.1 Existing System

 Existing EMS (Employee Management System) is based on Standalone system.


 It is developed under Access 95 that’s why it is not compatible with new operating system.
 The HR Administration falls short of controlling the employee’s activities in analyzing
his/her strengths and weakness.
 The decision for appraisal of assigning next project to the employee or to train him/her to
enhance the skills – where lies with proper projection.
 He is not provided with the detailed project information done or to be assigned based on
Application / Verticals
 Existing EMS is not much user-friendly.
3.2 Drawback of existing
System
 Need of extra manual effort.
 As current system is standalone normal employees cannot track their employment status.
 It used to take much time to find any employee
 Not very much accurate.
 System is compatible up to windows XP.
 Danger of losing the files in some cases.
 Certain required report is not available
 it is much complex to interact with existing EMS.
4.1 Need For New System
 The proposed system is intranet based system so employee can also participate in this
system and track their status.
 The Proposed system provides domain login as per organization requirement so no need to
remember user id or password.
 The proposed system provides detail general information about the employee along with
Educational, Certification, Skill and Project details.
 It enhances the HR Management in adding, viewing and updating employees’ details and
generates various reports regarding employee’s skill and experience.
 The proposed system of HR Module is the right software to be incorporated into the
Automation of HR Software for helping the organization needs with respect to skilful
Human Resource.
4.2 Advantages of New System

 AS it is intranet application it can be accessed by multiple user at a time.


 Proposed system provides domain login facility so no need to remember user id and
password.
 Very fast and accurate.
 No need of any extra manual effort.
 Just need a little knowledge to operate the system.
 Doesn’t require any extra hardware device.
5.1 Hardware Requirement

Component Web Server Database Server Client

System Dell Server Dell Server Dell Desktop

Processor Intel Xeon 2.8 GHZ Intel Xeon 2.8 GHZ Intel Pentium IV

Main Memory 512 GB 2 GB 512 GB

Hard Disk 8 GB IDE (Seagate) 30 GB IDE (Seagate) 2 GB IDE (Seagate)


5.2 Software Requirement
WEB SERVER SYSTEM

Software Used Remark


Apache Tomcat 6.0 It is being used as application server as well as web server.
IE 7 or Later It is being used as front end of the system and even for testing

DATABASE SERVER SYSTEM

Software Used Remark


Oracle 10.2.1 G C Server It is being used as back-end which holds all the database

CLIENT SYSTEM

Software Used Remark


IE 7 or Later It is being used as front end of the system and even for testing
6.1 Project Management | Project
Development

To solve actual problems in an industry setting, a software engineer or a team of engineers must
incorporate a development strategy that encompass the process, methods, and tools layers.

Our software is based on Waterfall Model.

The waterfall model is a sequential software development process, in which progress is seen as
flowing steadily downwards (like a waterfall) .

The waterfall development model has its origins in the manufacturing and
construction industries; highly structured physical environments in which after-the-fact changes
are prohibitively costly, if not impossible. Since no formal software development methodologies
existed at the time, this hardware-oriented model was simply adapted for software
development.
6.1 Project Management | Project
Development

The unmodified "waterfall model". Progress flows from the top to the bottom, like a waterfall.
6.2 Project Management | Project
Planning

Project Management is the discipline of planning, organizing, and managing resources to ring
about the successful completion of specific project goals and objectives.

The primary challenge of project management is to achieve all of the project goals and
objectives while adhering to classic project constraints—usually scope, quality, time and budget.

The secondary—and more ambitious—challenge is to optimize the allocation and integration of


inputs necessary to meet pre-defined objectives.
6.2 Project Management | Project
Planning

Month Employee Information Manager Module


Learning MVC Architecture & other useful technologies Such as JavaScript, CSS, JSP, Servlets, EJB, Jasper
Dec
Report
Jan Analyzing companies existing automated standalone HRIS.
Analyzing company’s behavior to meet new requirements.
Prototyping of HRIS to meet new requirements.
Deciding the dataflow of system
Feb Database designing
System Designing
March Development of System (bean classes, Dao classes and Servlets)
April Development of System (bean classes, Dao classes and Servlets)
Preparing Application server for deploying system
Deploying and testing system
May Integrating system with actual data
Designing report (using jasper report) required by company
integrating system with other module
Documentation
June Documentation
6.3 Project Management | GANNT Chart
7.1 System User | Introduction
For every web application complexity is directly proportional to the number of user’s categories for
the system.

The users of “GEA EIM (Employee Information Manager)” reside at three levels in the organization.
As requirements of all levels users are considered in development of the system, it can be easily fit
to all expectations of all types of system users of any level.

There are three types of users:

 Administrator.
 Line Manager.
 Employee.

Administrator : Can Add, Edit employee information. Permission to build different reports.
Line Manager: can access information of employee under his/her department.
Employee : can access his own details
7.2 System User | User Hierarchy
The categories of end-user who will interact with the “GEA EIM (Employee Information Manager)” web
application. User categories are relatively limited. However, when the number of user categories
grows, it is advisable to develop a user hierarchy as shown below:
8.1 System Analysis | Feasibility
Study

…not everything imaginable is feasible, not even the software as it may appear basically a
software is acceptable if it is technically, financially and operationally feasible.

 what does Technically Feasibility means


whether suggested technology exist or can be acquired from the market or not

 what does Financial Feasibility means


It is financially feasible if it is build at cost which is affordable by its client

 what does Operational Feasibility means


should be used to reduce the defects or fulfill the requirements matching the user’s needs.
& should not affect the existing operations of the organization and can be put into use by
easy without resistance (to acquire the new skills required).
8.1 System Analysis | Feasibility
Study

Technical Feasibility:
The minimum requirement to implement the system is Pentium-IV processor with 512 MB RAM,
Any Operating System, Java Run Time Environment. These are the software’s which are most
popular and easily available in the market.

Economical Feasibility:
It is more commonly a cost-benefit analysis of the system. The ratio of one time cost or recurring
cost should not exceed the benefits from the system. Cost of acquiring Machine, Software,
Operational Setup, training cost. As Said earlier Company is Multinational and it is well
infrastructure. No Extra cost for set up of operating environment needed as the computer is
already in use for other purposes. And the staff is well conversant and familiar with the computer
technology. Only the use of the ‘GEA EIM’ is needed. The system is User friendly and need
minimum data entry from the end users, thus is easy to use.

Operational Feasibility:
This system will reduce the work load and loss of information, saves time and would help to the
system generalized rather than person dependent
8.3 System Analysis | Activity
Diagram
8.3 System Analysis | Use Case
Diagram

For Admin User :


8.3 System Analysis | Use Case
Diagram

For Line Manager User :


8.3 System Analysis | Use Case
Diagram

For Simple User :


8.4 System Analysis | Data Flow Diagram

Context Diagram : Add Employee


Administrator

View Employee

Edit employee

Report building
Trace Employee

Employee
Information
Manager

Access own profile

Report builder

View employee

Access own profile

Line Manager Simple Employee


8.4 System Analysis | Data Flow Diagram

First Level Diagram :


Successfully login
Domain login Checks domain name
Result
Establishment
Administrator masters Table

result Domain
Login

masters

result

Master table
Master tables
operation

Employee list

result
Employee list
Employee
result Informaiton Employee details
Manager

Employee list
Line Manager
Result
8.4 System Analysis | Data Flow Diagram

Second Level Diagram (Adding Employee) :


Add employee Add employee
Result Result
Verify employee Establishment
Administrator
Result details

Employment details
Result

Employee
Employment
Information
details
Manager
Employee details
Insert employee details
Result Result

Employee
Employee
details
8.4 System Analysis | Data Flow Diagram

Second Level Diagram (For tracing employee and reporting utility :

Trace Employee
Result

Establishment
Table

Report
Trace Employee Utilities Result

Employee
Result
Details
Result
Administrator Report
Report Result

Employment
Details
8.5 System Analysis | Technology
Used

 Servlet
 Jsp
 Ajax
 XML & Java
 JDBC
 MVC (Model–View–Control) Architecture
 Oracle 10g
 i-Report
 jQuery
 JavaScript
 CSS(Cascading Style Sheets)
9.1 System Design | Introduction

This phase is a move from user requirement to defining how system will work thus it
is quite technical it specifies

 Exactly each input , output, data audit and control requirement will be handled
 Acceptance test plan/ scheduled
 Facilities, equipments and personal required
 Manual procedures required to operate system.

Database Design :
The most popular relational database model is used for permanent storage of data. It is two
dimensional and easy to handle. Thus logical and physical changes are easy to handle.
9.2 System Design | Data Dictionary
TABLE - MASTERGROUP
This table consist of all master table used in application
COLUMN_NAME DATA_TYPE CONSTRAINTS Description
GROUPID NUMBER(2,0) Primary Key Master Group ID
GROUPNAME VARCHAR2(60 BYTE) - Master Tables Description

TABLE - EIMRIGHTS (Employee Information Manager)


This table consist of List of all HR Rights given to each employee For Example Simple User Right, Line Manager Right, Admin Right
COLUMN_NAME DATA_TYPE CONSTRAINTS Description
HRRIGHTSID NUMBER(1,0) Primary Key Human Resource Rights ID
GROUPID NUMBER(2,0) Foreign Key Master Group ID
HRRIGHTSNAME CHAR(12 BYTE) - Human Resource Rights Description

TABLE - TRRIGHTS (Time Regestration)


This table consist of List of all TR Rights given to each employee For Example No Right, Key in right, Approval Right, Create Project right, block project right.
COLUMN_NAME DATA_TYPE CONSTRAINTS Description
TRRIGHTSID NUMBER(1,0) Primary Key Time Regestration Rights ID
GROUPID NUMBER(2,0) Foreign Key Master Group ID
TRRIGHTSNAME CHAR(15 BYTE) - Time Regestration Rights Description

TABLE - BLOODGROUP
This table consist of List of all blood group (A+, B+, AB+, O+ … ETC)
COLUMN_NAME DATA_TYPE CONSTRAINTS Description
BLOODGROUPID NUMBER(2,0) Primary Key Bloodgroup ID
GROUPID NUMBER(2,0) Foreign Key Master Group ID
BLOODGROUPNAME VARCHAR2(7 BYTE) - Bloodgroup Description

TABLE - CATEGORY
This table consist of List of all category (General, SC, ST, OBC)
COLUMN_NAME DATA_TYPE CONSTRAINTS Description
CATEGORYID NUMBER(1,0) Primary Key Category ID
GROUPID NUMBER(2,0) Foreign Key Master Group ID
CATEGORYNAME CHAR(7 BYTE) - Category Description
9.2 System Design | Data Dictionary
TABLE - GENDER
This table consist of List of gender (Male, Female)
COLUMN_NAME DATA_TYPE CONSTRAINTS Description
GENDERID NUMBER(1,0) Primary Key Gender ID
GROUPID NUMBER(2,0) Foreign Key Master Group ID
GENDERNAME CHAR(6 BYTE) - Gender Description

TABLE - MARITALSTATUS
This table consist of List of marital status (Single, Married, Divorcee, Widow)
COLUMN_NAME DATA_TYPE CONSTRAINTS Description
MARITALSTATUSID NUMBER(1,0) Primary Key Marital Status ID
GROUPID NUMBER(2,0) Foreign Key Master Group ID
MARITALSTATUSNAME CHAR(8 BYTE) - Marital Status Description

TABLE - NATIONALITY
This table consist of List of nationality (Indian, Foreign)
COLUMN_NAME DATA_TYPE CONSTRAINTS Description
NATIONALITYID NUMBER(1,0) Primary Key Nationality ID
GROUPID NUMBER(2,0) Foreign Key Master Group ID
NATIONALITYNAME CHAR(7 BYTE) - Nationality Description

TABLE - RELIGION
This table consist of List of all religions (Hindu, Jain, Muslim, Christan…ETC)
COLUMN_NAME DATA_TYPE CONSTRAINTS Description
RELIGIONID NUMBER(2,0) Primary Key Religion ID
GROUPID NUMBER(2,0) Foreign Key Master Group ID
RELIGIONNAME CHAR(30 BYTE) - Religion Description
9.2 System Design | Data Dictionary
TABLE - EDUCLASS
This table consist of List of education result class (Dist, First, Second, Pass)
COLUMN_NAME DATA_TYPE CONSTRAINTS Description
EDUCLASSID NUMBER(1,0) Primary Key Education Class ID
GROUPID NUMBER(2,0) Foreign Key Master Group ID
EDUCLASSNAME CHAR(6 BYTE) - Education Class Description

TABLE - EDULEVEL
This table consist of List of education levels (Diploma, Bachelor, Masters, Professional, Other)
COLUMN_NAME DATA_TYPE CONSTRAINTS Description
EDULEVELID NUMBER(1,0) Primary Key Education Level ID
GROUPID NUMBER(2,0) Foreign Key Master Group ID
EDULEVELNAME CHAR(12 BYTE) - Education Level Description

TABLE - RELATION
This table consist of List of relationships (Father, Mother, Brother, Sister, Spouse, Son, Daughter, Other)
COLUMN_NAME DATA_TYPE CONSTRAINTS Description
RELATIONID NUMBER(1,0) Primary Key Relationship ID
GROUPID NUMBER(2,0) Foreign Key Master Group ID
RELATIONNAME CHAR(8 BYTE) - Relationship Description

TABLE - STATE
This table consist of List of all states with in india
COLUMN_NAME DATA_TYPE CONSTRAINTS Description
STATEID NUMBER(2,0) Primary Key State ID
GROUPID NUMBER(2,0) Foreign Key Master Group ID
STATENAME VARCHAR2(60 BYTE) - State Description
9.2 System Design | Data Dictionary
TABLE - LANGUAGES
This table consist of List of languages (English, Hindi, Tamil, Gujarati, Marathi…ETC)
COLUMN_NAME DATA_TYPE CONSTRAINTS Description
LANGUAGESID NUMBER(2,0) Primary Key Language ID
GROUPID NUMBER(2,0) Foreign Key Master Group ID
LANGUAGESNAME CHAR(60 BYTE) - Language Description

TABLE - LANGUAGEFLUENCY
This table consist of List of language Fluency (Read, Write, Speak)
COLUMN_NAME DATA_TYPE CONSTRAINTS Description
LANGFLUENCYID NUMBER(1,0) Primary Key Language Fluency ID
GROUPID NUMBER(2,0) Foreign Key Master Group ID
LANGFLUENCYNAME CHAR(25 BYTE) - Language Fluency Description

TABLE - NOMINEESCHEME
This table consist of List of nomination scheme (EPF, EPS, Grauity)
COLUMN_NAME DATA_TYPE CONSTRAINTS Description
NOMINEESCHEMEID NUMBER(1,0) Primary Key Nominee Scheme ID
GROUPID NUMBER(2,0) Foreign Key Master Group ID
NOMINEESCHEMENAME CHAR(8 BYTE) - Nominee Scheme Description

TABLE - TRAININGTYPE
This table consist of List of type of training (Managerial, Technical)
COLUMN_NAME DATA_TYPE CONSTRAINTS Description
TRAININGTYPEID NUMBER(1,0) Primary Key Training ID
GROUPID NUMBER(2,0) Foreign Key Master Group ID
TRAININGTYPENAME CHAR(12 BYTE) - Training Description
9.2 System Design | Data Dictionary
TABLE - EMPSTATUS
This table consist of List employee status (Confirm, Probation, Contract, Retainership)
COLUMN_NAME DATA_TYPE CONSTRAINTS Description
EMPSTATUSID NUMBER(1,0) Primary Key Employee Status ID
GROUPID NUMBER(2,0) Foreign Key Master Group ID
EMPSTATUSNAME CHAR(12 BYTE) - Employee Status Description

TABLE - FUNCTIONS
This table consist of List employee functionality
COLUMN_NAME DATA_TYPE CONSTRAINTS Description
FUNCTIONSID NUMBER(2,0) Primary Key Employee Function ID
GROUPID NUMBER(2,0) Foreign Key Master Group ID
FUNCTIONSNAME CHAR(30 BYTE) - Employee Function Description

TABLE - DEPARTMENTS
This table consist of List of all departments with In organization
COLUMN_NAME DATA_TYPE CONSTRAINTS Description
DEPARTMENTSID NUMBER(2,0) Primary Key Department ID
GROUPID NUMBER(2,0) Foreign Key Master Group ID
DEPARTMENTSNAME CHAR(60 BYTE) - Department Description

TABLE - DESIGNATION
This table consist of List of all designation
COLUMN_NAME DATA_TYPE CONSTRAINTS Description
DEPARTMENTSID NUMBER(2,0) Foreign Key Department ID
DESIGNATIONID NUMBER(2,0) Primary Key Designation ID
GROUPID NUMBER(2,0) Foreign Key Master Group ID
DESIGNATIONNAME CHAR(60 BYTE) - Designation Description
9.2 System Design | Data Dictionary
TABLE - ESTABLISHMENT
This table consist of establishment details of each employee such as employee code, employee name, domaiin name, email address etc.
COLUMN_NAME DATA_TYPE Constraints Description
ESTABLISHMENTCODE NUMBER(7,0) Primary Key Employee Code
FIRSTNAME CHAR(15 BYTE) Not Null First Name
MIDDLENAME CHAR(15 BYTE) - Middle Name
LASTNAME CHAR(15 BYTE) Not Null Last Name
DOMAINNAME VARCHAR2(35 BYTE) Unique Domain Name
EMAIL VARCHAR2(50 BYTE) Unique Email Address
REGDATE DATE - Date of Establsihement Form
STATECLIENT NUMBER(2,0) - State For Tracking work of Simple user
STATEADMIN NUMBER(1,0) - State For Tracking work of Admin user
HRRIGHTS NUMBER(1,0) Foreign Key HR Right to Employee
TRRIGHTS NUMBER(1,0) Foreign Key TR Right to Employee
9.2 System Design | Data Dictionary
TABLE - EMPLOYEEDETAILS
This table consist of personal details, contact details, emergency contact dertails, immigration details and employment details of each employee
COLUMN_NAME DATA_TYPE Constraints Description
ESTABLISHMENTCODE NUMBER(7,0) Foreign Key Employee Code
PD_DOB DATE - Date of Borth
PD_GENDER NUMBER(1,0) Foreign Key Gender
PD_NATIONALITY NUMBER(1,0) Foreign Key Nationality
PD_BLOODGROUP NUMBER(2,0) Foreign Key Bloodgroup
PD_MARITALSTATUS NUMBER(1,0) Foreign Key Marital
PD_CATEGORY NUMBER(1,0) Foreign Key Category
PD_RELIGION NUMBER(2,0) Foreign Key Religion
PD_LICENSENUM VARCHAR2(14 BYTE) - Licenses number
CD_Add1 VARCHAR2(35 BYTE) - Present Address1
CD_Add2 VARCHAR2(35 BYTE) - Present Address2
CD_Add3 VARCHAR2(35 BYTE) - Present Address3
CD_CITY VARCHAR2(50 BYTE) - Present Address City
CD_STATE NUMBER(2,0) Foreign Key Present Address State
CD_PINCODE NUMBER(6,0) - Present Address Pincode
CD_PAdd1 VARCHAR2(35 BYTE) - Permanent Address1
CD_PAdd2 VARCHAR2(35 BYTE) - Permanent Address2
CD_PAdd3 VARCHAR2(35 BYTE) - Permanent Address3
CD_PCITY VARCHAR2(50 BYTE) - Permanent Address City
CD_PSTATE NUMBER(2,0) Foreign Key Permanent Address State
CD_PPINCODE NUMBER(6,0) - Permanent Address Pincode
CD_OPHONE NUMBER(15,0) - Office Phone
CD_RPHONE NUMBER(15,0) - Resident Phone
CD_MOBILE NUMBER(13,0) - Mobile Number
CD_OEMAIL VARCHAR2(35 BYTE) - Other Email ID
9.2 System Design | Data Dictionary

COLUMN_NAME DATA_TYPE Constraints Description


ED_RELATION NUMBER(1,0) - Emergency Contact Person Relation
ED_Add1 VARCHAR2(35 BYTE) - Emergency Contact Person Add1
ED_Add2 VARCHAR2(35 BYTE) - Emergency Contact Person Add2
ED_Add3 VARCHAR2(35 BYTE) - Emergency Contact Person Add3
ED_CITY VARCHAR2(50 BYTE) - Emergency Contact Person City
ED_STATE NUMBER(2,0) Foreign Key Emergency Contact Person State
ED_MOBILE NUMBER(13,0) - Emergency Contact Person Mobile
ID_PASSNUM VARCHAR2(7 BYTE) - Passport Number
ID_YOI NUMBER(4,0) - Year of Issue (Passport)
ID_YOE NUMBER(4,0) - Year of Expiry (Passport)
ID_POI VARCHAR2(25 BYTE) - Place of Issue (Passport)
JD_EMPSTATUS NUMBER(1,0) Foreign Key Employee Status
JD_DOJ DATE - Date of Joining
JD_DOL DATE - Date of Leaving
JD_FUNCTIONS NUMBER(2,0) Foreign Key Employee Function
JD_DEPT NUMBER(2,0) Foreign Key Department
JD_DESIGNATION NUMBER(2,0) Foreign Key Designation
RD_EMPCODE NUMBER(7,0) Foreign Key Report to Employee Code
ND_PFNUM VARCHAR2(18 BYTE) - EPF Number
ND_EPSNUM VARCHAR2(17 BYTE) - EPS Number
Primary Key : ESTABLISHMENTCODE
9.2 System Design | Data Dictionary
TABLE - PHOTO
This table contains photo of each employee
COLUMN_NAME DATA_TYPE Constraints Description
ESTABLISHMENTCODE NUMBER(7,0) Foreign Key Employee Code
UP_PHOTODATA BLOB - Uploaded Photo Content
Primary Key : ESTABLISHMENTCODE

TABLE - FAMILYDETAILS
This table contains family details of each employee
COLUMN_NAME DATA_TYPE Constraints Description
ESTABLISHMENTCODE NUMBER(7,0) Foreign Key Employee Code
DD_ID NUMBER(7,0) Primary Key Person ID
DD_DNAME CHAR(35 BYTE) - Person Name
DD_DRELATION NUMBER(1,0) Foreign Key Relationship with employee
DD_DDOB DATE - Person Date of birth
DD_AGE NUMBER(3,0) - Person Age
DD_OCCUPATION VARCHAR2(50 BYTE) - Person Occupation
Primary Key : DD_ID

TABLE - LANGUAGES
This table contains languages known by each employee
COLUMN_NAME DATA_TYPE Constraints Description
ESTABLISHMENTCODE NUMBER(7,0) Foreign Key Employee Code
LD_LANGID NUMBER(2,0) Foreign Key Language Id
LD_LANGFLUENCY NUMBER(1,0) Foreign Key Language Fluency Id
Primary Key : ESTABLISHMENTCODE + LD_LANGID
9.2 System Design | Data Dictionary
TABLE - EDUCATIONSCHOOL
This table contains schooling education data of each employee
COLUMN_NAME DATA_TYPE Constraints Description
ESTABLISHMENTCODE NUMBER(7,0) Foreign Key Employee Code
QD_SCH_LEVEL NUMBER(1,0) Foreign Key SSC or HSC
QD_SCH_NAME VARCHAR2(75 BYTE) - School Name
QD_SCH_BNAME VARCHAR2(50 BYTE) - Board Name
QD_SCH_YOQ NUMBER(4,0) - Year of Qualification
QD_SCH_PERCENTAGE NUMBER(5,2) - Result
Primary Key : ESTABLISHMENTCODE +
QD_SCH_LEVEL

TABLE - EDUCATIONCOLLAGE
This table contains education details of each employee
COLUMN_NAME DATA_TYPE Constraints Description
ESTABLISHMENTCODE NUMBER(7,0) Foreign Key Employee Code
QD_COL_ID NUMBER(7,0) Primary Key Qualification ID
QD_COL_LEVEL NUMBER(3,0) Foreign Key Diploma, Bachelor, Masters or Professional
QD_COL_DEGREE VARCHAR2(75 BYTE) - Degree Name
QD_COL_NAME VARCHAR2(75 BYTE) - Collage Name
QD_COL_UNAME VARCHAR2(50 BYTE) - University Name
QD_COL_YOQ NUMBER(4,0) - Year of Qualification
QD_COL_PERCENTAGE NUMBER(5,2) - Result
Primary Key : QD_COL_ID
9.2 System Design | Data Dictionary
TABLE - TRAININGDETAILS
This table contains training details of each employee
COLUMN_NAME DATA_TYPE Constraints Description
ESTABLISHMENTCODE NUMBER(7,0) Foreign Key Employee Code
TD_ID NUMBER(7,0) Primary Key Training ID
TD_TYPESOF NUMBER(1,0) Foreign Key Types of Training
TD_FACULTY VARCHAR2(50 BYTE) - Faculty of Training
TD_DURATIONOF NUMBER(3,0) - Duration of Training
TD_YEAROF NUMBER(4,0) - Year of Training
TD_COSTOF NUMBER(7,0) - Cost of Training
TD_STATE NUMBER(1,0) - state for tracking Training
Primary Key : TD_ID

TABLE - EXPERIENCE
This table contains experience details of each employee
COLUMN_NAME DATA_TYPE Constraints Description
ESTABLISHMENTCODE NUMBER(7,0) Foreign Key Employee Code
XD_ID NUMBER(7,0) Primary Key Experience ID
XD_EMPLOYERNAME VARCHAR2(50 BYTE) - Employer Name
XD_EMPLOYERADDRESS VARCHAR2(120 BYTE) - Employer Address
XD_ANAME VARCHAR2(20 BYTE) - Signatory Person Name
XD_ACONTACT NUMBER(15,0) - Signatory Person Contact Number
XD_AEMAIL VARCHAR2(35 BYTE) - Signatory Person Email Address
XD_DESIGNATION CHAR(25 BYTE) - Designation
XD_DOJ DATE - Date of Joining
XD_DOL DATE - Date of Leaving
XD_DURATION NUMBER(4,0) - Duation
XD_SALARY NUMBER(7,0) - Salary
Primary Key : XD_ID
9.2 System Design | Data Dictionary
TABLE - NOMINEE
This table contains nomination details of each employee
COLUMN_NAME DATA_TYPE Constraints Description
ESTABLISHMENTCODE NUMBER(7,0) Foreign Key Employee Code
ND_NOMINEEID NUMBER(7,0) Primary Key Nominee ID
ND_SCHEME NUMBER(1,0) - Nomination Scheme
ND_NAME VARCHAR2(30 BYTE) - Nominee Name
ND_RELATION NUMBER(1,0) - Nominee Relation
ND_ADDRESS VARCHAR2(100 BYTE) - Nominee Address
ND_SHARE NUMBER(3,0) - Nominee Share
ND_DOB DATE - Nominee DOB
ND_STATE NUMBER(1,0) - Tracking state of Nominee
Primary Key : ND_NOMINEEID

TABLE - GUARDIAN
This table contains guardian details in case of nominee is minor
COLUMN_NAME DATA_TYPE Constraints Description
GD_NOMINEEID NUMBER(7,0) Foreign Key Nominee ID
GD_NAME VARCHAR2(30 BYTE) - Guardian Name
GD_ADDRESS VARCHAR2(100 BYTE) - Guardian Address
Primary Key : GD_NOMINEEID

TABLE - SALARY
This table contains salary details of each employee
COLUMN_NAME DATA_TYPE Constraints Description
ESTABLISHMENTCODE NUMBER(7,0) Foreign Key Employee Code
SD_DATE DATE - Date of Salary Implementation
SD_FIXEDCTC NUMBER(9,2) - Basic Salary
SD_EXTRA NUMBER(9,2) - Extra Incomes from allowances.. ect
Primary Key : ESTABLISHMENTCODE + SD_DATE
9.3 System Design | PORCEDURAL
DESIGN

Algorithm for Administrator


STEP:1 Open the web site

STEP:2A you are domain user this website will automatically trace your profile

STEP: 2A-1 After successful login then it can access desired right to the site

STEP: 2A-2 can see list of all employees

STEP: 2A-3 can see full profile of each employee

STEP: 2A-4 can update information of any employee

STEP: 2A-5 can insert more details for any employee

STEP: 2A-6 can trace any employees profile and work on behalf of him

STEP: 2A-7 can generate various reports

STEP: 2A-8 can view his/her own profile

STEP:2B You are not domain user

STEP:2B-1 contact to administrator with employee code and domain name


9.3 System Design | PORCEDURAL
DESIGN

Algorithm for Line Manager


STEP:1 Open the web site

STEP:2A you are domain user this website will automatically trace your profile

STEP: 2A-1 After successful login then it can access desired right to the site

STEP: 2A-2 can see list of all employees who is working under him/her

STEP: 2A-3 can see full profile of each employee who is working under him/her

STEP: 2A-4 can generate various reports

STEP: 2A-5 can view his/her own profile

STEP:2B You are not domain user

STEP:2B-1 contact to administrator with employee code and domain name


9.3 System Design | PORCEDURAL
DESIGN

Algorithm for Simple user


STEP:1 Open the web site

STEP:2A you are domain user this website will automatically trace your profile

STEP:2A-1 After successful login then it can access desired right to the site

STEP:2A-2 can view his/her own profile

STEP:2B You are not domain user

STEP:2B-1 contact to administrator with employee code and domain name


9.4 System Design | Flow Design
Start

Checks
Contact to
administrator
No domain name
of user

yes

Select module

yes Admin EIM Time Regestration

Change
module

No

END
9.5 System Design | Design of Input
Screen

Input screen are user friendly and care is taken that minimum amount of data entry is done.

The master information once entered and stored is displayed in a combo box or as a list for further
input thus there are no chances of error in data entry as the use only has to select the information
from the provided list.

Key data is displayed from the master tables where ever needed if any redundancy exists then the
data is not reentered it is fetch form appropriate tables. e.g. while entering master information it is
verified that data already exist for that entity only then further data is accepted. Thus duplication
and redundancy is properly handled. Link for saving is enabled only after proper verification and
validation of data is done.

And basic information is first validated and then further data entry is allowed thus it saves
unnecessary data typing. Proper messages are provided where ever needed. Thus care is taken for
control of data and correctness of data with minimum typing efforts.

proper conversions of data type and formats are done.

Here domain login is provided so no need to remember user id and password.


10.1 Implementation | Implementation
Environment

This application is made by keeping in mind the basic concept of collaboration, the application can
be used by each of the person at a time on their respective systems.

At a time more than one user can use the web interface made to support the actual application.
Also the web site does not require any type of external interaction and makes user able to have
dynamic browsing on intranet, it is never ever affected by the number of users accessing it at a time
on their respective location.

This application is also made in such a way as to provide user with the most effective graphical
Interface so that the user can easily perform their task.

So, as the conclusion of above two points, this application is having the multiuser and effective GUI
environment for the users.
10.2 Implementation | Security Features
Authentication is necessary to enter into the system. This is required to prevent
unauthorized access to the system.

System can automatically identify user through domain name if it is not in application
database then user is not allowed to enter in system.

Server maintains the information is Sessions when particular user enters into the system.
The Session is regularly checked whenever it is required.
10.2 Implementation | Coding Standard

The Software needs to be updated from time to time according the changing needs of
Users. So some standards are to be maintained in implementation and Coding, so that
if the software needs to be modified due to some changes in User needs or some
enhancements to be done, then it’s easy for the person to find some specific modules,
pages, functions, variables or even the tables or stored procedures in the database.

 Package Standard
 Variable Standard
 Comment Standard
 Functional Standard
 General Standard
11 Testing

Testing is vital to the success of the system. System testing makes logical assumption that if all
the parts of system are correct, the goal will be successfully achieved. This system is tested by
following test cases and prepared for final implementation.

Test Case 1
Case : Testing of the Domain Login
Result : All the Operations work successfully.

Test Case 2
Case : Testing of the Basic Module
Result : System is not able to detect and generate correct
information and Exception Problem, validation problem.
Reason : This occurred because query is not proper format, script problem
Solution : After giving the proper function and query, we can able to get correct result.
11 Testing
Test Case 3
Case : Testing of the EMS Module
Result : System is not able to generate correct out put.
Reason : This occurred because database was not normalized.
Solution : After making proper normalized we can able to get correct result

Test Case 4
Case : Testing of the Generated Report
Result : System is not able to generate correct out put.
Reason : his occurred because query is not properly fired
Solution : After giving the proper query, we can able to get correct result.

Test Case 5
Case : Testing of the admin(master) Module(Employee rights)
Result : All the Operations work successfully.
12. Screen Shot | Home Page of
Admin
12. Screen Shot | Add Employee
12. Screen Shot | Assign Domain
Name
12. Screen Shot | Personal Details
Form
12. Screen Shot | Contact Details
Form
12. Screen Shot | Emergency Contact
Details Form
12. Screen Shot | Immigration Details
Form
12. Screen Shot | Family Details Form
12. Screen Shot | Qualification Details
Form
12. Screen Shot | Languages Details
Form
12. Screen Shot | Training Details
Form
12. Screen Shot | Experience Details
Form
12. Screen Shot | Nomination (EPF)
Form
12. Screen Shot | Nomination (EPS)
Form
12. Screen Shot | Uploading Photo
12. Screen Shot | Verification in
Pending
12. Screen Shot | Home page of Admin
12. Screen Shot | Verification Report
12. Screen Shot | Employment details
Form
12. Screen Shot | Report to details
Form
12. Screen Shot | Salary details Form
12. Screen Shot | Employee List View
12. Screen Shot | Employee Profile
View
12. Screen Shot | Updating an
Employee
12. Screen Shot | Adding more details in
future
12. Screen Shot | Reporting Utility
12. Screen Shot | Tracking Employee
12. Screen Shot | Home Page of Line
Manager
12. Screen Shot | EIM View of Line
Manager
12. Screen Shot | Home Page of
Employee
12. Limitation and Future
Enhancement
Limitations:
GEA Employee management system is limited up to process department of GEA Group only.

GEA Employee management system is not on internet application.

Future Enhancement:
GEA Employee management system will be enhanced up to all departments of GEA Group.

Integrating Leave management and Attendance system.

As organization is multinational make application internet base.

You might also like