Gyan Ganga College of Technology,

Jabalpur (M.P.)

A
MINOR PROJECT REPORT

Online Examination System

Submitted to the

Department of Information Technology

Submitted by
Asmita Rai : 0208IT111012
Ruchika Shrivastava:0208it111043
Under Guidance
of

Saurabh Sharma
Asst. Professor
in partial fulfillment of the requirements for the award of the degree of

BACHELOR OF ENGINEERING
(Information Technology)
VII Semester
under

RAJIV GANDHI PRODYOGIKI VISHWAVIDYALAYA,

BHOPAL(M.P.)

Gyan Ganga College of Technology,

Jabalpur
Department of Information Technology

Certificate
This is to certify that the Major Project report entitled Employee
Management System submitted by Asmita Rai and Ruchika
Shrivastava has been carried out under my guidance & supervision. The
project report is approved for submission towards partial fulfillment of the
requirement for the award of degree of Bachelor of Engineering in
Information Technology from Rajiv Gandhi Proudyogiki
Vishwavidyalaya, Bhopal (M.P).

Mr. Saurabh Sharma

Project Guide
Dept. of IT

Mrs. Vimmi Pandey

HOD
Dept of IT,GGCT

Gyan Ganga College of Technology,

Jabalpur
Department of Information Technology

Certificate
This is to certify that the Major Project report entitled
Employee Management System is submitted by Asmita Rai and
Ruchika Shrivastava for the partial fulfillment of the requirement for the
award of degree of Bachelor of Engineering in Information Technology
from Rajiv Gandhi Proudyogiki Vishwavidyalaya, Bhopal (M.P).

Internal Examiner

External Examiner

Date :

Date :

Declaration
I hereby declare that the project entitled Employee
Management System which is being submitted in partial fulfillment of the
requirement for award of the Degree of Bachelor of Engineering in
Computer

Science

and

Engineering

to

RAJIV

GANDHI

PROUDYOGIKI VISHWAVIDYALAYA, BHOPAL (M.P.) is an

authentic record of our own work done under the guidance of Mr. Saurabh
Sharma, Department of Information Technology, GYAN GANGA
COLLEGE OF TECHNOLOGY, JABALPUR..
The matter reported in this Project has not been submitted
earlier for the award of any other degree.

Date:
Place : Jabalpur

Ruchika Shrivastava
0208it111043
Asmita Rai
0208IT111012

Acknowledgment
I sincerely express indebtedness to esteemed and revered guide
Mr. Saurabh Sharma, Asst Professor in Department Of Information
Technology for his invaluable guidance, supervision and encouragement
throughout the work. Without his kind patronage and guidance the project
would not have taken shape.
I take this opportunity to express deep sense of gratitude to
Mrs. Vimmi Pandey, Head of Department of Information Technology
for his encouragement and kind approval. Also we thank him in providing
the computer lab facility. We would like to express our sincere regards to
him for advice and counseling from time to time.
I owe sincere thanks to all the lecturers in Department of
Information Technology for their advice and counseling time to time.

Date :
Place : Jabalpur

Ruchika Shrivastava
0208it111043
Asmita Rai
0208IT111012

TABLE OF CONTENTS
1.

Introduction......................................................................................................................2
1.1

Project Overview......................................................................................................3

1.2

Project Deliverables..................................................................................................4

2.

Project Organization.........................................................................................................5
2.1

Product perspective...................................................................................................5

2.2

Software Process Model............................................................................................6

2.3

Roles and Responsibilities........................................................................................6

3.

Project Management Plan...............................................................................................10

3.1

4.

Resources Needed...................................................................................................10

Software Requirement Specification...............................................................................12

4.1

Installation..............................................................................................................12

4.2

Implementation.......................................................................................................12

4.1

User Interface..........................................................................................................13

4.2

Hardware & Software Interface..............................................................................15

4.3

Database Requirements...........................................................................................15

5.

Software Design Description..........................................................................................19

5.1

5.2

Design Overview/ Algorithms.................................................................................19

System Design............................................................................................................20

5.2.1

Use Case Diagram...............................................................................................22

5.2.2

Data Flow Diagram.............................................................................................23

5.3.1

Screen Images.....................................................................................................27

6.

System Overview............................................................................................................38

7.

Conclusion......................................................................................................................39

8.

References......................................................................................................................40

1.

Introduction
The computer has brought revolution in every sphere of human life, whether it is

business, education field, governance, medical science etc. The computer has reduced the
human work load, businesses are going global and every thing is available at the click of
mouse.
In any organisation top management is using computer in almost every
department. Human Resource Department is also a very important department of every
organisation, whether it is public or private. All needs to record their employee related
details, like their general information, pay related details and details of

to other

departments. I hear and see most of application working in this field except any
application which will trace employee details and generate his/her related documents.
So that I am developing an application for maintaining information related to
Employees and generating the related documents. This application would be facilitating
the Human Resource Department (Higher Management) to
Search the employee
Make new s
Update records

1.1

Project Overview
Human Resource Department is actively involved in development of the

application for Employees. In all, application systems were to be developed and

implemented. System maintains the information about the Employee records, it maintain
the each and every record about the employee regarding their posting, leave, vacancy
position etc., it maintains the details of all Employees located at various field offices. The
application software takes care of database and day-to-day operations. This project will
help in capturing information regarding Human Resources through field offices. So, that
manpower can be monitored at Head Quarter. For the ease of the user and for the public
the existing systems were migrated to web-based applications. The purpose of Employee
Information System is to provide:

Finding ground level employee performance by the topmast manager.

Maintenance of profile details of the employees, and retrievals as and when

required.

Overall & detailed view of the organization hierarchy, which is very much
essential in making effective decisions.

Judging the potentiality of the employees.

Maintenance of the data when the organization has many branches spread over
wide geographical area.

Accessing one branch information from another branch.

Future planning issues based on the current HR information.

Employees success planning.

Vacancy situations and their priority /effect on the organizations performance.

Employee pays report, service report management.

1.2

Project Deliverables
The proposed software will solve all the problems they are facing now. This
software is designed such way that it will generate the salary automatically every
month in time. So there not much worries.

This software also equipped with to enter the attendance of each employee in the
organization, it help them to track each employee attendance, based on this we can
generate the salary.

The software built to generate individual pay slip and summary of the payroll. It
also has option to generate the report for Provident Fund and ESI. So they can take
the print out of Provident Fund and ESI to submit to the department.

This application allows the administrative department to collect accurate and

comprehensive employee information.

It allows authorized users to access the system by typing a valid login name and
password.

This application enables you to modify the records of existing employees.

2.

Project Organization

2.1

Product perspective

The application contains two subprograms, each subprogram related to the different
employees, and there is a centralized database located on the main computer on which the
software is running.

Module Description:

Admin Module

Employee Module

Admin Module:
Administrator controls the entire application. Administrator can add, delete, edit and view
all employee details and admin can create Employee Pay slip. Administrator also
manages the data related to organizations and businesses. Administrator generates reports
abased on various criteria. Administrator can also view attendance and service reports for
performance analysis.
Employee Module:
Employees must have valid login information to access the application. Each employee
can view the details of Attendance, Pay slip ,his/her profile, and service reports.

2.2

Software Process Model

The goal of software engineering is to provide models that lead to the production

of well documented software in a manner that is predictable. For a mature process, it

should be possible to determine in advance how much time and effort will be required to
produce the final product.
To develop the software successfully I have used the Waterfall Model (Classic
Life Cycle). In this model first of all the existed system is observed. Then customer
requirements are taken in consideration then planning, modeling, construction and finally
deployment.

Fig.1. Waterfall Model

2.3

Roles and Responsibilities

Developers Role & Responsibilities

Gathers and analyze data for developing information systems. Responsible for studying
problems in the existing system and recognizing needs for the new system.

To design and develop the proposed system to solve the problem with the existing
system, the developer is responsible for the following events:

Evaluates project for feasibility.

Analyses current systems for problems and opportunities.

Defines requirements for improving the system.

Design system interface, flow and procedure.

Performs interviews and data gathering.

Evaluates technological possibilities for technical, operational and economic

feasibility.

Designs file and database structure.

Designs user interfaces (input/output) to computer system.

Designs data collection forms and technique.

Developing the system.

Installing the s/w on the clients system(s).

Conducting any user training that might be necessary for using the system.

Maintaining the system after installing

2.4

Tools And Techniques

The inventors of java wanted to design a language which could offer solution to some of
the problems encountered in model programming. They wanted the language to be not
only reliable, portable and distributed but also simple, compact and interactive sun
Microsystems.

Compiled and interpreted

Platform independent and portable

Object oriented and robust and secure

Distributed

Familiar, simple and interactive

Multi threaded and interactive

High performance dynamic and extensible

COMPILED AND INTERPRETED:

Usually a computer language is either compiled or interpreted, java combined both these
approached thus making a two stage system. First java compiler translates source code
into what is known as byte code instruction. Byte codes are not machine instruction and
therefore in the second stage, java interpreter generates machine code that can be directly
executed by the machine that is running the java program.
PLATFORM INDEPENDENT AND PORTABLE:
The most significant distribution of java over other language is its portability, java
programs can be easily moved from one computer system to another, any where and
anytime changes and upgrade in operating system, process and system resources will not
face any change in java programs. This is the reason why java has become a popular
language for programming on internet which interconnects different kinds of system
worldwide.

OBJECT ORIENTED:
Java is a true object oriented language. Almost everything in java is an object. All
program code and data reside within objects and classes. Java comes with an extensive
set of classes, arranged in packages that we can use in our program by inheritance. The
object model in java is simple and easy to extend.
ROBUST AND SECURE:
Java is a robust language. It provides many safeguards to ensure reliable code. It has
strict compile time and run time checking for data type. It is designed as garbage
collected language relieving the programmers virtually all memory management
problems, java also incorporates the concept of exception handling captures series errors
and eliminates any risk of crashing the system.
MS ACCESS
Access is a relational database program .Access is used to enter, edit, and analyze lists of
data. Relational databases minimize redundant data
Advantages of Access
Duplicate data is minimized

Information is more accurate

Data entry is faster and easier

Information can be viewed and sorted in multiple ways.

Information is more secure

Information can be shared among several users

Information retrieval is faster and easier

3.

Project Management Plan

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.

3.1

Resources Needed

The existing system comprises of a system in which details are to be manually handled.
This is not user friendly. 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 employees 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.
1.

Planned approach towards working: - The working in the organization will be

well planned and organized. The data will be stored properly in data stores, which will
help in retrieval of information as well as its storage.

2.

Accuracy: - The level of accuracy in the proposed system will be higher. All

operation would be done correctly and it ensures that whatever information is coming
from the center is accurate.
3.

Reliability: - The reliability of the proposed system will be high due to the above

stated reasons. The reason for the increased reliability of the system is that now there
would be proper storage of information.
4.

No Redundancy: - In the proposed system utmost care would be that no

information is repeated anywhere, in storage or otherwise. This would assure economic

use of storage space and consistency in the data stored.
5.

Immediate retrieval of information: - The main objective of proposed system is

to provide for a quick and efficient retrieval of information. Any type of information
would be available whenever the user requires.
6.

Immediate storage of information: - In manual system there are many problems

to store the largest amount of information.

7.

Easy to Operate: - The system should be easy to operate and should be such that

it can be developed within a short period of time and fit in the limited budget of the user.

4.

Software Requirement Specification

The application software is based on Human Resource Management The application

software is developed in Java & Access. The central database is based on Access. The
system can be accessed over the System.
4.1

Installation

The Application installation scripts have to be generated from the current server where
the application source code is saved and installed in the main server from where the
application is to be run. This was done using a special code, which generates all to insert
preliminary data (like menu entries, code in code directories etc) at server and the
operational modules of the application made available to the end users successfully.
4.2

Implementation

The system is still under construction few reports are yet to me made after that this
system will be implanted at client side. Users will be given a training to use the package
and special workshops are conducted by the Organizations for the purpose. And
according to their feedback the changes are implanted in the software.

4.1

User Interface

User interface design creates an effective communication medium between a human and
a computer. Following asset of interface design principles, design identifies objects and
action and then creates a screen layout that forms the basis for a user interface prototype.
Interface design of Employee Management System is based on the following three
principles.
Place the user in control
During the information gathering session for Employee

Management System

(BrowseWire IT Solutions), BrowseWire IT Solutions was asked about the attributes that
he would like to have in the GUI interface. This was done to simplify the usage of
software.
Reduce the user memory load
During The design Process of Employee Management System all the possibilities such as
using mnemonics for Particular action, providing visual cues etc. are worked out to make
user comfortable working with our software and to make him remember less information.
Make the interface consistent
All possible efforts are undertaken to maintain standard user interface.
Some of these are:
All visual information (likes form) is organized according to a standard that is maintain
throughout all screen displays. Consistent navigation is defined and implemented.
Information is display to the user in an easily understandable way and layout. Visual

layout is based on a real world image. Entry filling process first shows list that is for
categorizing information and then information is saved according to that categorization.
Different indications are provided to enable the user to know the context of the work at
hand.
Indications
Proper interaction is necessary for good interface design. As computer industry grows it
becoming more and more versatile. There are number of interaction device present in the
Market like keyboard, mouse, digital pen, voice recognition commands etc. which can be
used for giving input. Also interaction is not only concerted with device interaction, it is
also concerned with system interaction mean how much comfortable user feels while
interaction with system.
Design feature of interaction:
Since different use have different preference as someone like to work thought mouse or
someone thought keyboard therefore choice have been provided to user for using for
using mouse and keyboard. Software interact equally well with both using the device.
Our System is designed for interruptible interaction mean when involved in sequence of
action the use can interrupt the sequence to do something else (without loosing the work
that had been done).
Login Screen
When a user starts the software, the first form he encounters is the login form. In the
login form the user has to choose store name then fill his Username and password. The
form is used to keep check in, so that unauthorized users are granted access to the system.

4.2

Hardware & Software Interface

Minimum Requirements:
Computer with a 2.27 GHz or faster processor(core i3)

3GB of RAM or more

220 GB of available hard-disk space
5400 RPM hard drive
1024 x 768 or higher-resolution display
DVD-ROM Drive
Additional features may require Internet access. Fees may apply.
Recommended:
2.2 GHZ or higher CPU, 1024 MB or more RAM, 1280x1024 display, 7200 RPM or
higher hard drive Running on Windows Vista: 2.4 GHz CPU, 768 MB RAM

4.3

Database Requirements

The database for the Employee Management System would has 4 tables each table has
a specific motive behind its creation. These tables will be created so that there will least
amount of redundancy and data is retrieved easily and efficiently.

TABLE : ADMINDETAILS
This table stores the information about a particular administrator. This table has 8 field
and represents different attributes of the system administrator.
The AdminID serves as the primary key.
Fields
AdminID
AdminName
Password
Retype
Address
City
PhoneNo
Email

Data type
varchar(50)

Discription
Adminstrators Identity

varchar(50)
varchar(50)
varchar(50)
varchar(50)

No.
Admin.s Name
Password for Login
Retype Password
Address of the

varchar(50)
varchar(50)
varchar(50)

Adminstrator
City Name
Contact No.
Email Address

Constraint
Primary Key

TABLE : EMPLOYEEDETAILS
This table stores the information about a particular administrator. This table has 8 field
and represents different attributes of the system administrator.
The EmployeeID serves as the primary key.
Fields
EmployeeID
EmployeeName
Password
Retype
Address
City
PhoneNo
Email

Data type
varchar(50)
varchar(50)
varchar(50)
varchar(50)
varchar(50)

Discription
Employees Identity No.
Employee Name
Password for Login
Retype Password
Address of the

varchar(50)
varchar(50)
varchar(50)

Adminstrator
City Name
Contact No.
Email Address

Constraint
Primary Key

TABLE : EMPLOYEEDETAILS
This table stores the information about a particular administrator. This table has 10 field
and represents different attributes of the system administrator.
The EmployeeID serves as the foreign key.
Fields
EmployeeID
EmployeeName
Role
CurrentDepartment
Department
RelivingDate

Data type
varchar(50)
varchar(50)
varchar(50)
varchar(50)

Discription
Employees Identity No.
Employee Name
Current Occupation
Department in which

varchar(50)
varchar(50)

working
Deparment to which
Date of reliving from

Constraint
Foreign Key

current location and

JoiningDate
Location
CurrentLocation
WorkExperience

varchar(50)
varchar(50)
varchar(50)

deparment
Date of joing where red
Name of place where
Name of place where

varchar(50)

currently working
Work Experience

TABLE : EMPLOYEEREQUEST

This table stores the information about a particular administrator. This table has 9 field
and represents different attributes of the system administrator.
The EmployeeID serves as the foreign key.
Fields
EmployeeID
EmployeeName
Role

Data type
varchar(50)
varchar(50)
varchar(50)

Discription
Employees Identity No.
Employee Name
Current Occupation

Constraint
Foreign Key

WorkExperience
Department
CurrentProject
CurrentLocation
Project
Location

varchar(50)
varchar(50)
varchar(50)
varchar(50)

Work Experience
Current Department Name
Current Project in Hand
Name of place where

varchar(50)
varchar(50)

currently working
Project in which red
Name of place where

5.

Software Design Description

5.1

Design Overview/ Algorithms

Employees Basic
Details
Employee_ID_Number
Personal_ID_Number
First_Name
Middle_Name
Last_Name
Day_of_Birth
Month_of_Birth
Year_of_Birth
Cellular_Phone
Home_Phone
City
Address
Postal_Code
Qualification
Current_Experience
Start_Date_Day
Start_Date_Month
Start_Date_Year
End_Date_Day
End_Date_Month
End_Date_Year
Type_of_Employee
Gender
Marital_Status

Working History
Employee_ID_Number
Company_Name
Employer_Name
Company_Employer_Address
Company_Employer_Cellular_Phone
Company_Employer_Office_Phone
Previous_Qualification
Previous_Experience
p_Start_Date_Day
p_Start_Date_Month
p_Start_Date_Year
p_End_Date_Day
p_End_Date_Month
p_End_Date_Year

Time_Information
Employee_ID_Number
Wroked_Hours
Off_Hours
Days_off
Over_Time
Extra_Days
w_From_Date_Day
w_From_Date_Month
w_From_Date_Year
w_To_Date_Day
w_To_Date_Month
w_To_Date_Year

5.2

System Design

Analysis collects a great deal of unstructured data through interviews, questionnaires, onsite observations, and procedural manuals and like. It is required to organize and convert
the data through system flowcharts, data flow diagrams, structured English, decision
tables and the like which support future development of the system.
The Data flow diagrams and various processing logic techniques show how, where, and
when data are used or changed in an information system, but these techniques do not
show the definition, structure and relationships within the data.
It is a way to focus on functions rather than the physical implementation. This is
analogous to the architects blueprint as a starting point for system design. The design is a
solution, a how to approach, compared to analysis, a what is orientation.
System design is a highly creative process. This system design process is also referred as
data modeling. The most common formatted used the E-R notation explains the
characteristics and structure of data independent of how the data may be stored in
computer memories.
The process of system design can be divided into three stages. They are:
Database design
Interface design
The steps involved during system design were as follow: -

1. LOGICAL AND PHYSICAL DESIGN

The current physical system was thoroughly reviewed from point of view how the data
flows, what are its file contents, its volumes and frequency etc.
After this input, output specifications security & control specification were prepared. It
was also decided that how physical information will flow through the system and a
physical design walkthrough.

2. OUTPUT DESIGN
Program output is most important and direct source of information to the user. Efficient
intelligible output design improves the systems relationship with the user and help in
decision making. A major form of output is a hardcopy from printer. The format of
outputs is designed in such a way that it is simple to read and interpret In the present
output we have clearly labeled title it contains date and time and all the fields are clearly
mentioned (labeled).

3. INPUT DESIGN
Input design is the process of converted user originated inputs to a computer based format
in accurate input data are the most cause of errors in data processing. So, the input should
be well design and error free. Input data is collected and organized into groups of similar
data once identified appropriate input media is selected for processing.

4.

SCREEN DESIGN

The screen design for inputting the inputs were also panned as the format of inputs.

5.2.1

Use Case Diagram

5.2.2

Data Flow Diagram

Emp_name
,
Emp_ID

Update
EmployeeCR
entry

Find
particular
Employee
entry

Emp_ID,Cryear,
Received,remark
s

Listing
Employee
s
EmployeeCR
Emp_ID,
Emp_name

Employee
Emp_ID,Cryear,
Received,remarks
Add new
entry of
EmployeeC
R

User

DFD
Login form

user

usertable
userlevel

Allocating
particular
menu

Username,
password

userlevel

loginform

Username,
password

Verifying
user

Menuorder,
menugroup,
menutitle,
menulink,
itemorder

menutable

DFD of Leave
form

Emp_name,Emp_ID

Emp_name,
Emp_ID
Finding
particular
entry

Listing
Leave
Details

Type,fro
m,to,Re
marks,D
ate

Updating
entry
Emp_name,
Emp_ID

Type, From, To,

Reason

Employee
Type, From, To,
Reason

Adding new
entry

Type, From, To,

Reason

User

5.2.3 E-R Diagram

5.3.1

Screen Images

6.

Software Test Documentation

Objectives of Testing:
This section introduces the concept of testing and how important is, for the successful
implementation of the project. Different phases of testing are described along with the
level of testing incorporated in this particular project.
Testing is vital to the success of any system. Testing is done at different stages within the
phase. System testing makes a logical assumption that if all phases of the system are
correct, the goals will be achieved successfully. Inadequate testing at all leads to errors
that may come up after a long time when correction would be extremely difficult.
Another objective of testing is its utility as a user-oriented vehicle before implementation.
The testing of the system was done on both artificial and live data.
Testing involves operation of a system or application under controlled conditions and
evaluating the results (e.g., if the user is in interface A of the application while using
hardware B and does C, then D should not happen). The controlled conditions should
include both normal and abnormal conditions.
Typically, the project team includes a mix of testers and developers who work closely
together, with the overall QA processes being monitored by the project managers.
TYPES OF TESTING
Black Box Testing
Also known as functional testing, this is a software testing technique whereby the tester
does not know the internal working of the item being tested. Black-box test design treats

the system as a black-box, so it does not explicitly use knowledge of the internal
structure. Black-box test design is usually described as focusing on testing functional
requirements. Synonyms for black-box includes: behavioral, functional, opaque-box and
closed-box.
White Box Testing
White box test design allows one to peek inside the box, and it focuses specifically on
using internal knowledge of the software to guide the selection of test data. Synonyms for
white-box include: structural, glass-box and clear-box.
Condition Testing
An improvement over White-box testing, the process of condition testing ensures that a
controlling expression has been adequately exercised whist the software is under test by
constructing a constraint set for every expression and then ensuring that every member
on the constraint set is included in the values whish are presented to the expression
Data Life-Cycle Testing
It is based upon the consideration that in the software code, a variable is at some stage
created, and subsequently may have its value changed or used in a controlling expression
several times before being destroyed. If only locally declared Boolean used in control
conditions are considered then an examination of the sources code will indicate the place
in the source code where the variable is created, places where it is given a value is used
as a part of a control expression and the place where it is destroyed.
This approach to testing requires all possible feasible lifecycles of the variable to be
covered whilst the module is under test.

Unit Testing
The purpose of this phase is to test the individual units of the developing software
component. This phase is recursive and is to be repeated, as many as there are, levels of
testing.
Functional Testing:
This is done for each module / sub module of the system. Functional testing serve as a
means of validating whether the functionality of the system Confers the original user
requirement i.e. does the module do what it was supposed to do? Separate schedules were
made for functional testing. It involves preparation of the test data, writing of test cases,
testing for conformance to test cases and preparation of bugs listing for non-conformities.
System Testing:
System testing is done when the entire system has been fully integrated. The purpose of
the system testing is to test how the different modules interact with each other and
whether the entire system provides the functionality that was expected.
System testing consists of the following steps:

Program Testing
String Testing
System Testing
System Documentation
User Acceptance Testing

Various Levels Of Testing

Before implementation the system is tested at two levels:
Level 1
Level 2
Level 1 Testing (Alpha Testing)
At this level a test data is prepared for testing. Project leaders test the system on this test
data keeping the following points into consideration:
Proper error handling
Exit Pints in code
Exception handling
Input / Output format
Glass box testing
Black box testing
If the system is through with testing phase at LEVEL 1 then it is passed on to LEVEL 2.
Level 2 Testing (Beta Testing)
Here the testing is done on the live database. If errors are detected then it is sent back to
LEVEL 1 for modification otherwise it is passed on to LEVEL 3. This is the level at
which the system actually becomes live and implemented for the use of END USERS.
We have also checked the proposed system for:

Recovery & Security

A forced system failure is induced to test a backup recovery procedure for file integrity.
Inaccurate data are entered to see how the system responds in terms of error detection and
protection. Related to file integrity is a test to demonstrate that data and programs are
secure from unauthorized access.
Usability Documentation & Procedure:
The usability test verifies the user-friendly nature of the system. This relates to normal
operating and error-handling procedures.
Quality Assurance
Proper documentation is must for mainframe of any software. Apart from In-line
documentation while coding. Help coding, help files corresponding to each program were
prepared so as to tackle the person-dependency of the existing system.

6.

System Overview

During the implementation stage the system is physically created. Necessary programs
are coded, debugged and documented. A new hardware is selected, ordered and installed.
System Specification
Every computer system consists of three major elements.
1. The Hardware
2. Application Software such as visual studio.
3. Operating system

For successful operation of the package following must be kept in mind:

Too many packages should not be used, as very few systems may have all those packages
installed due to memory problem. Thus, the compatibility of the system developed will
get reduced.
7.

Conclusion

Today we are at the cross roads of innovation. The right direction to take will only evolve
with time, but effort has to be taken seriously by everyone involved in education; the
school/University, administration, faulty, students and parents.
By designing the Employee Management System through Java technology, we are able
to provide the basic functionality related to the submission activities with great ease. The
use of Java technology has made it easier to design and develop the architecture of this
application.
Hence we may conclude that the application system being developed helps a great deal in
modifying the computerized Employee Management System. The Employee
Management System is a big and ambitious project. I am thankful for being provided
this great opportunity to work on it. As already mentioned, this project has gone through
extensive research work. On the basis of the research work, we have successfully
designed and implemented Employee Management System.

8.

References

E.Balagurusamy, Programming with Java: A Primer, 4 th Edition, McGrawHill

Publication, 2010.
Herbert Schildt, The Complete Reference Java2, 5th Edition, McGrawHill Publication,
2002.
Gail Anderson and Paul Anderson, Java Studio Creator Field Guide, 2 nd Edition,
Prentice-Hall, Inc., 2004.
Elias M. Awad, Systems Analysis and Design, 2nd Edition, Galgotia Publication, 2008.
Petkovi, Microsoft Sql Server 2005: A Beginners Guide, Tata McGraw-Hill, 2006
IGNOU, CS-05 Elements of System Analysis and Design.
IGNOU, CS-67 RDBMS LAB Book 1.
IGNOU, CS-70 Introduction to Software Engineering.
IGNOU, CS-74 Introduction to Internet Programming.

Websites:
http://javalessons.com/
http://http://javabeginner.com/
http://netbeans.org/kb/articles/learn-java.html
http://www.roseindia.net/