PROJECT

ON

EMPLOYEE MANAGEMENT SYSTEM

REPORT SUBMITTED IN LIEU OF

6 WEEKS SUMMER INDUSTRIAL TRAINING
OF
B.TECH (C.S.)2nd YEAR
(2008 –2009)

Submitted by:
MASROOR AHMAD
MUNIB FAZAL
MD TAJ RAZA
 Department of computer science
Jamia Hamdard (Hamdard University)

2
 ACKNOWLEDGEMENT

MASROOR AHMAD, MUNIB FAZAL & MD TAJ RAZA Student of

JAMIA HAMDARD (IV) Semester hereby acknowledges that we have completed this
project under the guidance of Mr. EHITRAM RAZA KHAN.

I extend my gratitude towards him for continuously giving him full Cooperation and
Suggestion for the betterment of the Project as Well as helping me to solve my
difficulties. It was his custom, ever willing help and constant encouragement that made
this study possible; no words are enough to express my sincere thanks to providing
necessary facilities for completion of this Project.

3
MASROOR AHMAD,
MD TAJ RAZA
& MUNIB FAZAL

Place: - Delhi

IDEA BEHIND THE PROJECT

Every organization whether it is private or government, Database system in order to
basic information regarding its activity and functionality.
Employee management also maintains such system. In Employee management

system, Information is given by the system on the basis of whatever we stored about

the company information employee, information and pay scale etc.

This project is Employee management system developed in C++, It is an attempt to

relieve the burden of department to almost all extent by providing user friendly, fully

automated, highly recurred software. The main objective of this software is to keep

4
 track of information regarding the management of Employee. Here on of the exquisite

techniques of structure design of the database is followed also has some security

checks for reliability. This system generates all designed reports in improved and

more informative format. The input forms have been designed with the view that

operator of this software has minimum knowledge of computer. Of course! There is

always a room for future enhancement so it has been designed to accommodate

further changes in a particular regiment without disturbing others.

SYSTEM SPECIFICATION
MINIMUM HARDWARE SPECIFICATION

Hardware:

Processor : Pentium IV
Ram : 256 MB
Hard Disk : 20 GB

SOFTWARE SPECIFICATION

Operating System : Windows XP

Compiler : Turbo C++

5
The project entitled "EMPLOYEE MANAGEMENT" is choosen by me because I have a
great interest in management systems and specially the"EMPLOYEE MANAGEMENT
SYSTEM" have its various attractive features which forced me to choose this project.

SCOPE AND OBJECTIVE: The objective of my project is to provide EASY,

EFFECTIVE, SECURE access to the users so that the compl-exity of accessing is
removed and to provide proper DATABASE to sto- re the records.The scope of my
project is also vast due to presence of nearly all basic features of a normal EMPLOYEE
MANAGEMNT SYSTEM.

FEATURES

There are various attractive features of this project which makes its effective and more
acceptable.I give some of these features which will present this software well:-

1.SECURITY: Due to password facility no one other than faculty can access this system
so it makes this system more secure than any other system without password facility.

2.EASY TO UNDERSTAND FOR NEW USER: Due to use of easy coding and
keywords any user can work on this system and access the system data easily if he/she is
a faculty member.

3.STORES THE COMPLETE ADD. OF CUSTOMER: As compared to any other

systems this system have sufficient quqlities and capacity to store the complete
information of the customer which makes the identification process very easy.

4.EFFECTIVE DATABASES: There are effective concepts of the database in this project
.Due to presence of different databases for different type of data chances of mixing of
data are ery less.

6
 TESTING

For this project (Employee Manageme nt System)we are doing two types of testing to
make the project effective and error free.

1. Black-box testing: - it is also called behavioral testing, focuses on the functional

requirements of the software. That is black-box testing enables the software engineer to
derive sets of input conditions that will fully exercise all functional requirement for a
program.
In this project black box testing helps us to find errors in the following categories:-
Incorrect or missing functions.
Interface errors.
Errors in data structures external database access.
Behavior or performance errors.
Initialization or termination errors.

Tests are designed to answer the following questions:-

How is a functional validity test?
How is system behavior and performance tested?
How are the boundaries of a data class isolated?

7
White-box testing: - It is also known as glass-box testing. It is a test design method that
uses the control structure of the procedural design to derive test cases. using white box
testing method ,the s/w engineer can derive test case that:-

Guarantee that all independent path within a module have been exercised at least once
Exercise all logical decisions on their true or false sides.
Execute all loops at their boundaries and within their operational bounds.
Exercise internal data structures to ensure their validity.

8
 FEASIBILITY STUDY
All projects are feasible – given unlimited resources and
infinite time. Unfortunately, the development of a
computer – based system is more likely to be plagued by a
scarcity of resources and difficulty delivery dates. It is
both necessary and prudent to evaluate the feasibility of
the project at the earliest possible time. Months and years
of effort, thousands or millions of dollars, and untold
professional embarrassment can be averted if an ill-
conceived system is recognized early in the definition
phase.

Feasibility and risk analyses are related in many ways.

The feasibility study is carried out to test if the proposed

system is worth being implemented. Feasibility study is a
test of the proposed system regarding its workability,
impact on the organization, the ability to meet
requirements and the effective use of resources. It is
usually carried out by a small group of people who are
familiar with information system techniques and
understand the part of the business or organization that
will be involved and affected by the project, and are
skilled in the system analysis and design process.

In this phase, the development team visits the customer and studies their need. By the end
of the feasibility study, the team furnishes a document that holds the different specific
recommendations for the candidate system. It also includes the personnel assignments,
costs, project schedule, and target dates. The requirements gathering process is intensified
and focused specially on software. To understand the nature of the program(s) to be built,
the system engineer (“analyst”) must understand the information domain for the software,
as well as required function, behavior, performance and interfacing.

9
 An Important step before choosing the software paradigm is to investigate
whether the system requested is feasible. We studied the feasibility of the
project to determine whether the software tool requested by the Placement
Department was feasible or not!!! The following three main considerations
were taken into account
as shown in Fig. below:

Technical Feasibility

Economical Feasibility

Behavioral Feasibility

FEASIBILITY

STUDY

TECHNICAL

FEASIBILITY

ECONOMIC

FEASIBILITY

BEHAVIORAL
Figure Feasibility Study
FEASIBILITY

10
 Technical Feasibility

The technology presently available will suffice for the development

of our software. Also for implementation of the software no special
hardware resources are needed. So the budget would not become a
constraint or a limiting factor for the software under development. Hence,
the software is technically feasible.

Economical Feasibility

This is an in house project and is going to be used inside the organization by its
Placement Department. A cost analysis of the project was done. All the costs and
benefits associated with the software were considered. It was found that the
software would result in increased productivity for the business. Overall it was
conducted that the benefits outweigh the costs associated with the software. Hence,
software is economically feasible.

Behavioral Feasibility

The staff of the organization was open-minded towards the acceptance of this new
concept. No specialized training would be needed, only a few hours of instructed
demo needs to be given to the user. Hence, the software exhibits behavioral
feasibility.

Time Estimates
Time is a very critical factor and as mentioned before in the project constraints, the time
available for the completion wasn’t overly adequate. However, the major tasks were
identified and time estimates were planned. Using tools such as Gantt charts and Project
tables, once can keep track of the time allocated. Using project tables, one can keep tab
on the labor as well. These charts and tables can be prepared for the whole project or for
individuals or even for separate functions.

REQUIREMENT ANALYSIS:
Requirement analysis is done in order to understand the problem the software system, is
to solve. The problem could be automating an existing manual process, developing a
new automated system, or a combination of two. For large systems that have many

11
features, and that need to perform many different tasks, understanding the requirements
of the system is a major task.

There are two major activities in this phase: problem understanding or analysis
and requirement specification. In problem analysis the analyst has to understand the
problem and its context. A clear understanding is needed of the important data entities
in the system, major centers where the action is taken, the purpose of the different
actions that are performed, and inputs and outputs.

Understanding the existing system is usually just the

starting activity in problem analysis. The goal of this activity is to understand the
requirements of the new system that is to be developed. The analyst has to make the
client aware of the new possibilities.

Once the problem is analyzed and the essentials

understood, the requirements must be specified in the requirement specification
document. The requirements document must specify all the functional and performance
requirements; the format of input and outputs; and all design constraints that exist due
to economic,

Environmental, and security reasons. In other words, besides the functionality required
from the system, all the factors that may affect the design and the proper functioning of
the system should be specified in the requirement document. A

preliminary user manual that describes all the major user interfaces frequently forms a
part of requirement document.

12
 METHODOLOGY TO BE USED CARRYING OUT THE STUDY

• Studying the existing system. This will involve the amount

of information, the manpower equipment space and other
resources used for the information storage.

• After analysing the existing setup this study would suggest

a new management setup. The benefits and disadvantages
of existing and new system would be critically revised.

• Cost Benefit Analysis study will done.

• The database structure and information storage retrieval

process will also be studied and a new system for faster
response using operation research techniques will be
designed.

13
 Project Overview

Product prospective

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.

User Interface

 The system will be having user privileges based menu.

 User will have to select the options form the given menu.

 The system will be entering the information into the

database to generate reports.

 The forms will be designed to enter the data.

 Buttons will be used to insert, retrieve or modify the data.

 Links will be provided to shift from one form to another.

Product Function

14
It is advisable to have weekly data backups. The system administrator will do the data
recovery. Selection of panel is user-initiated operation, while indent handling is client
initiated

Constraints

General Constraints

1) This system will not take care of any virus problem, which
might occur either on the client or the server system.
Avoiding the use of pirated software and ensuring that
floppies and other removable media are scanned for viruses
before use could minimize the possibility of viral infection.

2) Recovery of data after a system crash will be possible only

if backups are taken at regular intervals.

3) Manual interfaces cannot be fully avoided. Documented

proofs like dates etc. will have to be verified by the
concerned staff before entering it into the computerized
system

Assumptions and Dependencies

1. It is assumed that the user is familiar

with the basic computer
fundamentals.

2. Timely backup of data should be

taken to avoid data loss in case of
system crash.

15
 3. The use of pirated software should
be avoided as it may lead to data loss
and system crashes due to viral
infections.

4. Floppies and other removable media

should be scanned for viruses before
use.

5. Proper configuration of the client,

database server and network is
necessary for the system to function
as intended.

6. It is assumed that the maintenance of

the database will be assigned to the
authorized person only.

7. Only authorized persons will be

allowed inside the server room.

OPERATIONAL MANUAL:
To use this system, there is a user identification number to each user of the system. There
is a password facility and different persons are given access according to their roles.

MODES:
Most of the modules work under five modes. They are Insert, Updation, Retrieval,
Deletion and Exit.

16
INSERT MODE: This mode allows insertion of new records. Integrity of database is
maintained and no duplicate records can be entered. A message will flash indicating the
error.

DELETE MODE: This mode allows deletion of a particular record depending upon the
primary key.

RETRIEVAL MODE: This mode allows the retrieval of records with the help of
retrieval arguments.

UPDATION MODE: This mode allows the Updation of records and if any, Integrity
violation is there, and no changes are committed.

17
 THE WATER FALL MODEL

18
 The waterfall model derives its name due to the cascading

Effect from one phase to another as illustrated in figure 1.1 in

This Model each phase well define starting and ending point

With Identifiable delivers to the next phase.

This model consists of six distinct stages or phases.

1. REQUIREMENT PHASE

2. SPECIFICATION

3. DESIGN

4. IMPLEMENTATION

5. INTEGRATION

6. MAINTENANCE

NOTE

THIS MODEL IS SOME TIMES REFFERED TO AS THE LINEAR

SEQUENTIAL MODEL OR THE SOFTWARE LIFE CYCLE

19
 UPDATED
REQUIRMENT
REQUIREMENT PHASE

SPECIFICATION PHASE

DESIGN PHASE

IMPLEMENTATION PHASE

INTEGRATION PHASE

MAINTENANCE PHASE

SIX PHASES OF WATER FALL MODEL

20
 1. REQUIREMENT PHASE
i) In this phase problem is specified along with desired services
Objectives (goals)

ii) The constraints are identified

2. SPECIFICATION PHASE
i) In this phase system specification is produced.

ii) This document should clearly define the product function

NOTE: that in some text, the requirement analysis and

Specification phases are combined and represented

As single phase.

3. DESIGN PHASE

i) In this phase the system specification are translated into

A software representation. The software engineer at this
Stage is concerned with:

The software engineer at this Stage is concerned with:

21
DATA SRUCTURE
SOFTWARE ARCHITECTURE
ALGORITHMIC DETAIL
INTERFACE REPRESENTATION

The hardware requirements are also determined at this stage along with a picture
of the all over system architecture. By the end of this stage the software engineer
should be able to identify the relationship between the hared ware and soft ware
and the associated interfaces. Any fault in the specification should ideally not pass
down the stream.

4. IMLPMENTATION AND TESTING PHASE

At this stage the designs are translated into soft ware

Domain

Detail documentation from the design phase can

Significantly reduces the coding effort

Testing at this stage focuses on making sure that any

Error are identified and the software meets its required

Specification

5. INTEGRATION AND SYSTEM TESTING PHASE

In this stage, all the program units are integrated and tested to ensure that
the complete system meets the software requirements.

22
 AFTER THIS STAGE THE SOFTWARE IS DELIVERED TO THE
CUSTOMER,

6. MAINTENANCE PHASE

In this stage the software is updated to:

Meet the changing needs of customer

Adapted to accommodate changes in the external

Environment

Correct errors and oversights previously undetected in

The testing phases

Enhancing the efficiency of the software

NOTE

OBSERVE THAT THE FEED BACK LOOP ALLOW FOR

CORRECTION TO BE INCORPORATED IN TO MODEL

For example: updating in the designing phase

Requires a ‘Revisit’ to the specification phase the

Relevant document should be up dated to reflect the Changes.

ADVANTAGES of testing
TESTING IS INHERENT TO EVERY PHASE OF WATER FALL MODEL.

IT IS AN ENFORCED DISCIPLINED APPROACH.

23
ITS DOCUMENTATION DRIVEN, THAT IS ITS DOCUMENTATION IS
PRODUCED AT EVERY STAGE.

QUALITY OF A PRODUCT IS MAINTAINED

LIMITATIONS
The waterfall model is the oldest and the most widely used paradigm. However
projects rarely follow its sequential flow. This due to the inherent problems
associated with it rigid format

i) It only incorporates iteration indirectly, thus changes may cause

considerable confusion as the project progress

ii) As the client usually only has a vague idea of exactly what is required
from the software project, this WM has difficulty accommodation the
natural uncertainty that exist at the beginning of the project

iii) The customer sees a working version of the project after it has been
coded. This may result in disaster if any undetected problems are
precipitate to this stage

iv) It is at time difficult for the client for the client to explicitly state the
requirement as a Result, modification is performed at every stage which
consume lot of time and resources

DFD (0 LEVEL)

24
EMPLOYEE DATABASE REPORTS
INFORMATION
USER
EMPLOYEE SEARCHING
UPDATE
INFORMATION
TRANSACTION
25
26
27
 DFD (Ist Level)

EMPLOYEE
GETS
INFORMATION

CHEEK EMPLOYEE
EMPLOYEE MANAGEMENT CALCULATE
CODE SYSTEM PAY
DATABASE

EMPLOYEE
ATTENDENCE
CALCULATE
PAY

GETS CHEEK
EMPLOYEE
ATTENDENCE

SEARCH

EPLOYEE’s
GET USER
INFORMATION,
INFORMATIO
ATTENDENCE,
N
TRANSITION &
USER INFORMATION

USER
INFORMATION
REPORT

28
 e1
EMPLOYEE WORKS FOR

DEPARTMENT

e2

r1  d1
e3 

r2
  d2
e4
 r3

 d3
e5 r4
 

r5  d4
e6 
  d5
r6

 d6
e7
 r7
  d7


 

 

ER-SCHEMA displaying relationship type works for

between Employee and Department entity types
29
 BIBIOGRAPHY

Following books are preferred by me for this project "EMPLOYMENT

MANAGEMENT SYSTEM" by me:

BOOK NAME WRITER INFO

LET US C YASHWANT KANITKAR

OBJECT ORIENTED PROGRAMMING BALAGURUSWAMI

GRAPHICS UNDER C YASHWANT KANITKAR

30
31