1.

INTRODUCTION
1.1 Development of Employee Performance Management An Overview:
Employee Performance Management is an Oracle based application program designed for effective functioning of the Skills and Performance Tracking of the employee in an organization. This project aims in defining the task by the manager to the employee and also allows the managers to track the effort spend by the employee for the particular task.

The system developed should have the task details that been assign by manager to the employee as per the skill set they possess. The task effort been captured by the employee for the particular task assigned to them. The effort capture been tracked by the manager to analyze which of the skills been utilized and those which are not utilized. This effort capture will be cumulatively stored in a table which will be updated every day. The manger analyze the everyday effort spend by the employee for the task and finally produce a report of the employees which of the skills been utilized and which are not utilized.

1.2Objectives of the Project

The objective of the project is to design and develop a new strategy for skill and performance tracking process of an organization. The system is used to track the employees effort spent for the particular task assigned by the manager. The system has user-friendly layout of screens making it very simple to use. It is a completely web-based system that can be run on companies Internet. It can be made available on an organization allowing authorized users to access the system. This project helps manager analyze the skills that been utilized and not utilized by the employee in the organization.

1.3 BACKGROUND STUDY 1.3.1 STUDY ON EXISTING SYSTEM

The existing system is developed in Visual Basic as front end and oracle 8i as back end. This system fails in accuracy, efficiency and it is really a tedious task to maintain properly. At present managing expense is really complicated in the organization. A great deal of effort is required for maintaining up-to-date information of task assigning and effort capturing. The system fails in security as the user process vary with their work. Selected problems No resource request handling No way to view the status of the request. Absence of resume screening mechanism System cannot upload and download. System does not have mail process. Navigation menus are not properly designed. Takes more time to generate the reports. User interactive area is tedious.

2. SYSTEM ANALYSIS
System Analysis is a management technique, which helps in designing a new system or improving an existing system. System Analysis is the process of gathering and interpreting facts, diagnosing problems, using information to recommend improvements to the system. There are four basic elements of system analysis-Output, Input, Files, processes. For computerization of any system, the existing system must be thoroughly being understood to determine how the computer can be best used to make its operation most effective.

2.1 STUDIES ON PROPOSED SYSTEM

The proposed system rectifies most of the problem in the present system, the system. The most important aspect of the new system is that flexible to incorporate changes. Data validation is done during data entry itself so that the errors are minimized. To upgrade the process we included some features in the proposed system. We provide the separate login for every user. User can access any where inside the organization. In this system we are capturing the required designs of the employees. The status of every process can be shown in this system. The existing system is not convenient for the user. If the system crashes the data will be loss.

NEED FOR PROPOSED SYSTEM Software solution is an IT solution provider for a dynamic environment where business and technology strategies converge. Their approach focuses on new ways of business combining IT innovation and adoption while also leveraging an organization and new products or service and to implement prudent business and technology strategies in todays environment. The benefits of the proposed system are, The data is more secure. The user can access anywhere inside the organization. It is an integrated system so that the data can be shared and updated easily. This application avoids the burden in deploying in each client machines. It is a platform independent. Support and maintenance of the system is easier.

2.1.2 DEFINING THE PROBLEM

During the development, the management needs to keep track of information about the status of project the tools available do not have such features. The system has also not useful for large organization that have multiple branches. The proposed system is designed based on the objectives prepared to fulfill the existing system drawbacks. The system design concentrates on deriving efficient process flow, which uses optimum resources, and deliver maximum results. The system concentrates on cost estimation, instant access of information. It provides very easy flow than the existing system.

FEASIBILTY STUDY The feasibility of the project is analyzed in analysis phase and business proposal is put forth with a very general plan for the project and some cost estimates. During system analysis the feasibility study of the proposed system is to be carried out. This is to ensure that the proposed system is not a burden to the company. For feasibility analysis, some understanding of the major requirements for the system is essential.

Three key considerations involved in the feasibility analysis are Economical feasibility Technical feasibility Social feasibility

ECONOMICAL FEASIBILITY This study is carried out to check the economic impact that the system will have on the organization. The amount of fund that the company can pour into the research and development of the system is limited. The expenditures must be justified. Thus the developed system as well within the budget and this was achieved because most of the technologies used are freely available. Only the customized products had to be purchased.

TECHNICAL FEASIBILITY This study is carried out to check the technical feasibility, that is, the technical requirements of the system. Any system developed must not have a high demand on the available technical resources. This will lead to high demands on the available technical resources. This will lead to high demands being placed on the client. The developed system must have a modest requirement, as only minimal or null changes are required for implementing this system.

SOCIAL FEASIBILITY The aspect of study is to check the level of acceptance of the system by the user. This includes the process of training the user to use the system efficiently. The user must not feel threatened by the system, instead must accept it as a necessity. The level of acceptance by the users solely depends on the methods that are employed to educate the user about the system and to make him familiar with it. His level of confidence must be raised so that he is also able to make some constructive criticism, which is welcomed, as he is the final user of the system.

2.1.2 DEVELOPING SOLUTION STRATEGIES Top down Approach

Top-down and bottom-up are strategies of information processing and knowledge ordering, mostly involving software, but also other humanistic and scientific theories (see systemic). In practice, they can be seen as a style of thinking and teaching. In many cases topdown is used as a synonym of analysis or decomposition, and bottom-up of synthesis. The Employee Performance Management incorporates the following aspects. Master Transaction Reports

Master:
In this module it has the information of the Manager, Employee, Task and it will be stored in to the database.

Transaction:
This module is used to capture the effort spend by the employee for the particular task and to produce which of the skills been utilized and which are not utilized.

Reports:
Reports are viewed whenever the bank user wants to know the information. Reports need to be created with good care. Reports are generated from the Employee list, Authorizer list, login list, Task list.

2.2 SYSTEM SPECIFICATION

2.2.1 APPLICATION SPECIFICATION

Three Tier Architecture Three-tier architecture introduces a server (or an "agent") between the client and the server. The role of the agent is manifold. It can provide translation services (as in adapting a legacy application on a mainframe to a client/server environment), metering services (as in acting as a transaction monitor to limit the number of simultaneous requests to a given server), or intelligent agent services as in mapping a request to a number of different servers, collating the results, and returning a single response to the client.

Employee Performance Management System uses the 3-tier application is a program, which is organized into three major disjunctive layers. These layers are,

Presentation layer (Front end) Business layer (Logical) Data layer (Backend)

Three Tier Architecture

Application layer Application layer is the form which provides the user interface to either programmer of end user. Programmer uses this layer for designing purpose and to get or set the data back and forth. Business layer This layer is a class which we use to write the function which works as a mediator to transfer the data from Application or presentation layer data layer. In the three tier architecture we never let the data access layer to interact with the presentation layer. Data Access Layer This layer is also a class which we use to get or set the data to the database back and forth. This layer only interacts with the database. We write the database queries or use stored procedures to access the data from the database or to perform any operation to the database.

2.3.2 NETWORK SPECIFICATION

The development and availability of Internet technology has resulted in an upsurge of Intranets within these Organizations. It is now relatively easy for someone with an

understanding of the technology and HTML to create web pages, and implement a server to host them. As their experience increases they may also become able to produce graphics to enhance the site, and more complicated and functional navigation.

2.2.3 Hardware specification

Processor RAM Hard Disk : Intel Pentium Dual Core : 1GB : 40GB

2.2.4 Software Environment

Operating System Database Server Frame Work : Linux, Windows XP : Oracle 10g : Eclipse

Introduction to Frame Work

A software framework, in computer programming, is an abstraction in which common code providing generic functionality can be selectively overridden or specialized by user code providing specific functionality. Frameworks are a special case of software libraries in that they are reusable abstractions of code wrapped in a well-defined API, yet they contain some key distinguishing features that separate them from normal libraries.

Introduction to Eclipse Framework

Eclipse is a software originally designed by International Business Machines Corporation also known as IBM which has been offered by this latter to the open source community in 2001. Since, the main project (the Eclipse Platform) and many other subprojects (improvements of the Eclipse platform) are managed by the Eclipse Foundation (www.eclipse.org). 8

ECLIPSE Eclipse is a framework for delivering what the project calls "rich-client applications" whose main aim is to provide a framework intended to implement Integrated Development Environments (IDEs) which are environments dedicated for programming. Eclipse is a platformindependent software, it means that you can execute it on several operating systems like Windows, Linux, Mac OS etc, due to the fact it has been written in Java. It has been designed in such a way that all functionalities of the software come from the adjunction of plug-ins to the runtime application. This allows Eclipse to be what you want it to be by adding or deleting plugins. By default the Eclipse software is provided with a Java IDE called JDT (Java Development Tool) but if you need it you are able to add IDEs such as C/C++, PHP etc according to your needs. Also, Eclipse can do things totally different from programming. For example the software Azureus, a very well known and used bittorrent client, is based on the Eclipse framework.

Oracle Features Oracle was primary a database company with little or no services. In addition, Oracle has no canned applications. Today, the picture is quite different. This multibillion-dollar company has lots of products, lots of services and even more applications.

Open Connectivity Oracle provides for uninterrupted access to the database 24 hours a day. Oracle provides open connectivity to and from other vendors software. Using add-ons to the Oracle database, you can work with information that resides in other data repositories, such as IBMs DB2, Sybase or Microsoft Access if from other software, such as Microsoft Visual Basic, Power softs, Power Builder, Guptas SQL * Windows development tools.

CSS: Cascading Style Sheets (CSS) is a style sheet language used to describe the presentation of a document written in a markup language. CSS is a breakthrough in Web design because it allows developers to control the style and layout of multiple Web pages all at once. To make a global change, simply change the style, and all elements in the Web are updated automatically.

2.3 COST ESTIMATION AND SCHEDULING

Software cost is related to many variables such as Human, Technical, Environment and Effort applied to develop it. The estimates of cost depend, on our ability to estimate and evaluate several factors, given below.

Number of user inputs Number of user output Number of files Number of inquiries Experience and ability of the project personnel The quality of software development environment The degree to which software components can be reused

The productivity of a CMM Level 4 company is 2.0 and we assumed the productivity of our team as 2.0. Based on the size and Productivity the man days and man hours are calculated as shown below,

Man Days

= =

180.0 Function Points / 2.0 90days 90 * 8 = 720 hr

Man Hours

Let us see how to compute the man power estimation and the cost estimation of the project Employee Performance Management is. The computation is described briefly below.

10

Man Power Estimation

Phase User Requirement Specification Project Planning System Requirement Specification Architectural Design Document Detailed Design Document Coding Unit Testing Integration Testing System Testing User Acceptance Testing Installation Total

Time Taken 50 45 50 70 95 200 40 40 40 40 50 720

Cost Estimation

Cost for 1 Hour Total Cost Cost

= = =

200.00 Indian Rupees (Rs) 720 Hrs * 200.00 1, 44,000 Rupees

11

2.4 Final Outline of the Proposed System

The proposed system overcomes all the drawbacks of the existing system. A system study help to analyze the present system in its full dimension, it recommends the need for a new system, at it put handle the inefficiencies of a present system. The proposed system can be easy to view, easy to modify, easy to see the process of each stage. Some of the significant accrued benefits of the Interest calculation system include, Enhanced information delivery and improved result. Greater security and improved performance. Flexible solution capable of evolving quickly changing requirements. Minimal conflicts among data. Cheaper cost of management.

12

3. DESIGN AND DEVELOPMENT PROCESS

3.1 Fundamental design concepts
Although the degree of interest in each concept has varied over the year, each has stood the test of time. Each provides the software designer with a foundation from which more sophisticated design methods can be applied. Fundamental design concepts provide the necessary framework for getting it right. A software design is a meaningful engineering representation of some Software product that is to be built. A design can be traced to the customers requirements and can be assessed for quality against predefined criteria. During the design process the software requirements model is transformed into design models that describe the details of the data structures, system architecture, interface, and components. Each design product is reviewed for quality before moving to the next phase of software development.

3.2 Design Notations

3.2.1 Data flow diagram Analysis model help us to understand the relationship between different components in the system design. Analysis model shows user more clearly, how a system will function. This is the first technical representation of a system. The analysis is modeling must achieve three primary objectives. To establish a basis for creation of software design. To describe what the user requires. To define a set of requirement that can be validated once the software is built Data Flow Diagram.

13

A Data Flow Diagram is a graphical technique that depicts information flow and transforms that are applied as data move from input to output. The DFD is used to represent increasing information flow and functional details. A level 0 DFD, also called a fundamental system model or a Context Model, represents the entire software elements as a bubble with input and output indicated by incoming and outgoing arrows respectively. Additional process and information flow parts are represented in the next level i.e., Level 1 DFD. Each of the processes represented at Level 1 are sub functions of overall system depicted in the Context Model. Any processes, which are complex in Level 1, will be further represented into sub functions in the next Level, i.e., in level 2. Basic DFD symbols: To Construct a Data Flow Diagram, we use Arrow Circles Open End Box Squares Arrow An arrow identifies the data flow in motion. It is a pipeline through which information is flown like the rectangle in the Flow Chart.

Data may flow a source to a processor and from a data store or process. An arrow line depicts the flow, with the arrowhead pointing in the direction of flow.

Circle Circle stands for process that converts the data into information

A process represents transformation where incoming data flow is changed into outgoing flows.

14

Rectangle A Rectangle defines a source or destination of system data. A source is a person or a part of organization, which enters or receives information from the system but is considered to be outside the context of the data flow model.

Open End Box An Open End Box represents a data store, data at rest or temporary reposition of data.

A graphical picture of the logical steps and sequence involved in a procedure or a program is called a flow chart. Unlike detailed flow chart, Data Flow Diagram does not supply detailed description of the modules but graphically describes a systems data how the data interact with the system.

Six rules for considering the Data flow Diagram Arrows should not cross each other Squares, circles and Data Store must have names Decomposed data flow squares and circles can have the same names. Choose meaningful names for data flow Draw all data flows around the outside of the diagram.

15

LEVEL-0 (CONTEXT DIAGRAM):

Self-assessment

Manager Selected

Employee

Employee Performance Management

Review Manager

Reports User rights

Task Allotment

HR User

Figure 3.2.1 LEVEL-0 (CONTEXT DIAGRAM):

16

LEVEL: 1 (EMPLOYEE AND MANAGER)

Register Employee/Manager Invalid login

Employee table

Login Process

Login table

Views Employee Skill set

Valid Manager

Valid Employee

Selects and Allots task

Task Viewing

Selects task

Allots the task

Views task

Captures the effort

Task Details

Task Allotted

Task Record Tracks the effort

Assigns Task

Employee

Manager

Effort estimation Skills Report sent to employee Skills Analyzed Manager Skill Analyzed record

Figure: 3.2.2 LEVEL: 1 (EMPLOYEE AND MANAGER)

17

LEVEL 1(MANAGER - HR USER)

Manager

Request to update employee details Request Through Comments

Update Login Table

HR User

Login Process

Login Table

Updates the employee table

Update Employee Table Employee

Figure: 3.2.3 LEVEL 1(MANAGER - HR USER)

18

LEVEL-2:

Register

Employee/Manager Manager

Request to update employee details

Administrator

New user Employee table Login Process Login table Views Employee Skill set Valid Manager Valid Employee

Updates employee details

Employee table

Selects and Allots task

Task Viewing

Selects task

Allots the task

Views task

Captures t he effort

Task Details

Task Allotted

Task Record Table Tracks the effort

Employee Assigns Task Views Skills Report

Manager

Effort estimation

Skill Analyzed record Manager

Skills Analyzed

Figure: 3.2.4 LEVEL-2

19

3.2.2. Structure Chart

Structure Chart is used to show the hierarchical arrangement of the modules in a Skill and Activity Tracker System. Each rectangular box in the structure chart represents a form and module. The names of the forms are written inside the box. An arrow joins two forms that have an invocation relationship. The module and forms in the Employee Performance Management represents in the below structure chart

EMPLOYEE PERFORMANCE MANAGENT SYSTEM

LOGIN

HR USER

EMPLOYEE

MANAGER

USER PRIVILEGES

PERFORMANCE ANALYSIS

WORK FOR THE ASSIGNED TASK

CAPTURES EFFORT SPEND ON THE TASK

REQUEST CHANGE MANAGER

ANALYZE EFFORT REPORTS

ASSIGNS TASK DETAILS

ALLOTS TASK TO THE EMPLOYEE

REPORT GENERATION

EMPLOYEE PERFORMANCE MANAGEMENT

20

3.3 Design process

The design phase focuses on the detailed implementations of the system recommended in the feasibility study. Emphasis is on translating performance specification into design specification. The design phase is a translation from user-oriented document to a document to a document oriented to the programmers or database personnel.

3.3.1 Data Structure Design

To design an application it is necessary to design a database file. These files are called tables. After designing the output and input, tables must be organized according to the storage needs of the back end used. Normalization procedure is used to avoid duplication of data and to produce feasibility necessary to support different functional requirements. In this project some fields are assigned as primary key. The repeating data are removed and are placed in the corresponding entity. In the master table primary key is assigned and this is referenced by the same field in the transaction table which is assigned there as foreign key. Every non key attribute in this system are nontransitively dependent on primary key. The records are retrieved by selecting the primary key.

Normalization It is a technique for designing relational database tables to minimize duplication of information. The goals of normalization are, Eliminating redundant data Ensuring data dependencies make sense.

Types of Normalization are, 1. 1st Normal form 2. 2nd Normal form 3. 3rd Normal form

21

 1st Normal form A relation to be in 1NF, each column must contain only a single value and each row must contain the same columns. 2nd Normal form In order to be in Second Normal Form, a relation must first fulfill the requirements to be in First Normal Form. Additionally, each non key attribute in the relation must be functionally dependent upon the primary key. 3rd Normal form In order to be in Third Normal Form, a relation must first fulfill the requirements to be in Second Normal Form. Additionally, all attributes that are not dependent upon the primary key must be eliminated.

TABLE DESIGN: Tb_Employee

Primary Key - Emp_id Field Name Emp_id Emp_name Emp_job Emp_Experience Emp_dept Emp_join date Emp_add Emp_sal Emp_skill level Emp_skilltype Emp_manager Type Number Varchar Varchar Varchar Varchar Date Varchar Number Varchar Varchar Varchar Size 5 30 15 10 15 50 5 20 20 30 Description Employee id Employee name Employee job Employee experience Employee department Date of joining job Employee address Employee salary Employee skill level Employee skill type Employee manager allotted

22

Tb_Task Details
Primary Key Task_id Field Name Task_id Task name Task start date Task end date Duration Skill set Type Number Varchar Date Date Varchar Varchar Size 5 20 20 20 Description Task Detail id Task name Task start date Task end date Task duration Skill required for the task

Tb_TaskAllotment
Primary Key - Taskallot_id Foreign Key - Taskid , Emp_id Field Name Taskallot_id Task_id Emp_id Allotted date Comments Type Number Number Number Date Varchar Size 5 5 5 20 Description Task allotted id Task detail id Employee id Task allotted date Task comments

Tb_Login
Primary Key - Emp_id Field Name Emp_id Username Password Login time Type Number Varchar Varchar Timestamp Size 5 30 20 Description Employee id User name Password Login Time

23

Tb_TaskRecord
Priamry Key Taskrec_id Foreign Key Emp_id , Task_id Field Name Taskrec_id Task_id Emp_id Date Duration Comments From To Status Type Number Number Number Date Varchar Varchar Varchar Varchar Varchar Size 5 5 5 20 30 10 10 20 Description Taskrecord id Task detail id Employee id Effort captured date Effort duration Comments of effort Start time of work End time of work Status of the Task

Tb_PerformanceAnalyze and Record

Primary Key Skillrec_id Foreign Key Emp_id , Taskrec_id Field Name Skillrec_id Emp_id Taskrec_id Recorded date Type Comments Skills utilized Skill not utilized Effort for the task Type Number Number Number Date Varchar Varchar Varchar Varchar Varchar Size 5 5 5 15 30 20 20 20 Description Skillrecord id Employee id Taskrecord id Recorded date Type of analyze Comments Skill utilized Skill not utilized Effort for the task

24

3.3.2 Module Design

The project Design and development of skill and activity tracker system is divided into 3modules. They are as follows

Manager Module Employee Module. HR Module.

Manager Module The manager assigns the task to the employee in the organization who works under his guidance. He tracks the effort spent by the employee for the particular task. The managers analyze which are those skills by employee are utilized and those which are not utilized. This module can help managers for effort estimation per task.

Employee Module The Employee views the assigned to him and works to complete the task. The effort spent for each task been recorded by the employee in the database. The employee self estimates his efforts spend for the task. Views the report as what level the employee is at present.

Administrator Module The HR gives the privileges to employee as per the request of the manager. The username and password are given to the employee and if any changes in the employee database can be updated only by the HR.

25

3.3.3 Input Design

The input design is the process of converting the user-oriented inputs in to the computerbased format. For providing a good input design for the application easy data input and selection features are adopted. The input design requirements are user friendliness and consistent format. The input form comprises of Login form, which play a major role in the project that screens the unauthorized user entering into the system. The user name and password are given as input to login into the system. The given below the Input screens. Login User Task Details Registration Task Allotment Analyzing efforts Effort capture

Login Form Description: This form is used to login the users. The security has to enters the username and the password. Input: Enter the username and password. Process: Check the role based authentication for user. Table: Tb_login. Ref: ANNEXURE-INPUT DESIGN Fig1.0

Registration Description: New employees use this registration to enroll them and to select the manager to work under them. Input: Enter the Name, Address, mobile no, email-id, skillset and manager to work under. Process: Store the data in the table Table: Tb_employee Ref: ANNEXURE-INPUT DESIGN Fig1.1

26

Task Details Description: Manager stores the task with one skill set. Input: select the task_id and enters the task name, duration. Process: Forward task detail to task assigning. Table: Tb_Task details. Ref: ANNEXURE-INPUT DESIGN Fig 1.2

Task Allotment Description: Manager assigns the task to the employee who works under his guidance. Input: Select the Taskallot_id,taskid emp_id and enters the comments. Process: Forward to the employee. Table: Tb_Task allotment. Ref: ANNEXURE-INPUT DESIGN Fig 1.3

Analyzing efforts Input: Select the taskrec_id and Enter the skill utilized,skill not utilized by the employee. Process: Forward the skills to be improved to Internal Employee. Table: Tb_skillanalyze and record Ref: ANNEXURE-INPUT DESIGN Fig 1.4

3.3.4 Output Design

The output design presents the manipulated data to the end user. The output design acts as medium of communication to the user by providing the desired data that may be either a stored data fetched from the database or may be manipulated result displayed to the user for confirmation before it is stored into the database. The quality output is one, which meets the requirements of the end user and presents the information clarity. In any system results of processing are communicated to the users and to other systems through outputs. The output design deals with determining how the information is to be displayed for immediate need and also for the hard copy output. The given below the output screens.

27

 Performance analyzed Record view Task Details view. Internal Employee Details View Skill analyzed Record view Description: The manager can send the analyzed record to the Top Management. Input: Select the date from Date Picker. Table: Tb_skill analyze and record Ref: ANNEXURE-INPUT DESIGN Fig 2.0

Task Details view Description: The task allotted by the manager to the employee. Input: Select the date from Date Picker Table: Tb_Taskrecord Ref: ANNEXURE-INPUT DESIGN Fig 2.1 Internal Employee Details View Description: View the Internal Employee Details From the database. Input: Select the Skill Set, Experience Process: View the Internal Employee Details and Project. Table: Tb_employee Ref: ANNEXURE-INPUT DESIGN Fig 2.2

3.4 Development Approach:

Employee Performance Management was designed and developed based on the Waterfall Model. This model particularly expresses the interaction between subsequent phases. Testing software is not an activity, which strictly follows the implementation phase. In each phase of the software development process, we have to compare the results obtained against that which is required. In all phases quality has to be assessed and controlled.

28

System Requirements Completed Review Software Requirements Analysis Preliminary Design Completed Review Detail Design

Completed

Review

Completed

Review Coding and Unit Testing Review Output Testing Review Maintain Software Completed Completed

Fig 6 SDLC Phases

1.

In the Requirements Analysis phase

(a) The problem is specified along with the desired service objectives (goals) (b) The constraints are identified 2. In the specification phase the system specification is produced from the detailed

definitions of (a) and (b) above. This document should clearly define the product function. 3. In the system and software design phase, the system specifications are translated into a Data structure Software architecture Algorithmic detail and Interface representations 29

software representation. The software engineer at this stage is concerned with:

The hardware requirements are also determined at this stage along with a picture of the overall system architecture. By the end of this stage the software engineer should be able to identify the relationship between the hardware, software and the associated interfaces. Any faults in the specification should ideally not be passed down stream. 4. In the implementation and testing phase stage the designs are translated into the software Detailed documentation from the design phase can significantly reduce coding effort. Testing at this stage focuses on making sure that any errors are identified and that the software meets its required specification. 5. In the integration and system testing phase all the program units are integrated and tested

domain

to ensure that the complete system meets the software requirements. After this stage the software is delivered to the customer. 6. The maintenance phase the usually the longest stage of the software. In this phase the Meet the changing customer needs Adapted to accommodate changes in the external environment

software is updated to:

4. TESTING AND IMPLEMENTATION

4.1 System Testing
It is the process of exercising software with the intent of finding and ultimately correcting errors. This fundamental philosophy does not change for web applications, because web based system and applications reside on network and inter-operate with many different operating systems, browsers, hardware platforms and communication protocols. Thus searching for errors is significant challenge for web applications.

4.1.1 Testing and Methodologies

System testing is the state of implementation, which is aimed at ensuring that the system works accurately and efficiently as expect before live operation, commences. It certifies that the 30

whole set of programs hang together System testing requires a test plan that consists of several key activities and steps for run program, string, system and user acceptance testing. The implementation of newly design package is important in adopting a successful new system. Our software testing methodology is applied in four distinct phases: Unit testing System testing Integration testing Validation testing 4.1.1.1 Unit Testing The unit testing was conducted during the development phase. we test their specific functionality individually or with other units. However, unit testing is designed to test small pieces of functionality rather than the system as a whole. This allows us to conduct the first round of testing to eliminate bugs before the other major tests.

Login form

Test Case ID 1

Test Case Description

Expected Results

Actual Results

Pass /Fail

Click login button

Enter username and Please Enter user password name and password Pass by message by text box Password character should display like (*) Displaying character * password Pass

Enter password

Enter invalid username and Error message password should displayed Enter without password Enter password displayed by message box Home page should be display with user roles

Display invalid username / password by message box Displaying Enter password by message box Home page was displayed with user roles

Pass

Pass

Enter Username and password then click login button

Pass

31

Registration form Test Case ID 6 Click Submit Button Without Entering Any Fields. 7 Select the Date of joining Less than to system Date. Selected Date is Selected Invalid Invalid Date is Pass Enter the Require Field Necessary Enter the Require Field Necessary Pass Test Case Description Expected Results Actual Results Pass/Fail

4.1.1.2 Integration Testing Incremental integration testing involves continuous testing of an application as new functionality is added. This requires that aspects of an application's functionality be able to work separately before all parts of the application are completed. Full integration testing tests combined parts of an application to determine if they function together correctly. Integration Testing Test Case ID Select the Employee id by selecting the Technology in 9 the dropdown list Box. Available Employee id in the Dropdown list Box is loaded. Available Employee id in the Dropdown list Box is loaded. Pass Test Case Description Expected Results Actual results Pass/ Fail

Select the Task ID by 10 selecting the ID in the Dropdown list Box. .

Available Task ID in the Dropdown list Box is loaded.

Available Task ID in the Dropdown list Box is loaded. Pass

32

Validation Testing: Tests to determine whether an implemented system fulfills its requirements. The checking of data for correctness or for compliance with applicable standards, rules, and conventions. The process of applying specialized security test and evaluation procedures, tools, and equipment needed to establish acceptance for joint usage of an AIS by one or more departments or agencies and their contractors.

Test Case ID

Test Case Description

Expected Results

Actual Results

Pass/Fail

12

Enter the alphabetical characters It wont allow in the mobile number Field you to enter the alphabetical characters. 13 Enter the Task Id in the Emp_id It wont allow Dropdown list Box. you to Enter Task ID.

It wont allow you to enter the alphabetical characters. It wont allow you to Enter Task ID.

Pass

Pass

4.2 Quality Assurance

Quality assurance consists of the auditing and reporting functions of management. The goal of quality assurance is to provide management with the data entries necessary to be informed about the product quality thereby gaining the goal of insight and confidence that the product quality is meeting. Greater emphasis on quality in organization requires quality assurance. To be an integral part of the information system development .The development process must include checks throughout the process to ensure that the final product meets the original user requirements. Its included in the industry standard (IEEE 1993) On the development process quality assurance process is integrated into a linear development cycle through validation and verification performed at crucial system development steps .The goals of the management is to institute and monitor a quality assurance program with in the development process Quality assurance includes, 33

 Validation of the system against requirements. Checks for errors in design documents and in the system itself. Quality assurance for usability.

4.2.1 Generic Risks

A risk is a potential event with negative consequences that has not happened yet. However a risk could also be defined as the event with unforeseen positive consequences. By identifying the risks we can avoid failures and increase the success rate of our system. During the risk management process, the following things were discussed. They are: What are the risks in my project? What can go wrong in my project? What are important risks? What shall we do to reduce severity or avoid risk? What is the risk status? What has to be changed?

4.2.2 Security Technologies & Policies

Security is necessary in today's environment because data processing represents a concentration of valuable assets in the form of information, equipment, and personnel. Security and privacy must focus on controlling unauthorized access. The following security policies are implemented in our system. They are Form-based login authentication. Authorization and Access Control. Session Management. Data and Resource access.

34

4.3 System Implementation

Implementation is the stage of the project where the theoretical design is turned into a working system. At this stage the main work load, the greatest upheaval and the major impact on the existing system shifts to the user department. If the implementation is not carefully planned a controlled it can cause and confusion. Implementation includes all those activities that take place to convert from the old system to the new one. The new system may be totally new, replacing an existing manual or automated system or it may be a major modification to an existing system. Proper implementation is essential to provide a reliable system to meet the organization requirements. Successful implementation may not guarantee improvement in the organization using the new system, but improper installation will prevent it. The process of putting the developed system in actual use is called system implementation. This includes all those activities that take place to convert from the old system to the new system. The system can be implemented only after thorough testing is done and if it is found to be working according to the specifications. The system personnel check the feasibility of the system. The system implementation has three main aspects. They are education and training, system testing and changeover. The method of implementation and the time scale to be adopted are found out initially. Next the system is tested properly and the same time users are trained the new procedures.

4.3.1 Implementation Procedures

Implementation of software refers to the final installation of the package in its real environment, to the satisfaction of the intended users and the operation of the system. The active user must be aware of the benefits of using the system Their confidence in the software is built up. Proper guidance is imparted to the user so that he is comfortable in using the application. The user must know that for viewing the result, the server program should be running in the server. If the server object is not up running on the server, the actual processes wont take place. 35

4.3.2 User Training

Our entire system was developed very user friendly. No extra training was required to use our system. Our system automatically guides (fully user guided) the user to give input and to produce the output.

4.3.3 Operational Documentation

An online help which gives the clear idea about our system was attached with our system. Whenever the user needs guidance he can get help from the help manual.

4.4 System Maintenance

The maintenance phase of the software cycle is the time in which a software product performs useful work. After a system is successfully implemented, it should be maintained in a proper manner. System maintenance is an important aspect in the software development life cycle. The need for system maintenance is for it to make adaptable to the changes in the system environment. There may be social, technical and other environmental changes, which affect a system, which is being implemented. Software product enhancements may involve providing new functional capabilities, improving user displays and mode of interaction, upgrading the performance characteristics of the system. Maintenance is actually implementation of the review plan as important as it is programmers and analyst is to perform or identify with him or herself with the maintenance. There are psychologically personality and professional reasons for this. Analyst and programmers spend fair more time maintaining programmer then they do writing them Maintenances account for 50-80% of total system development.

36

5. CONCLUSION
The project report entitled Employee Performance Management" has come to its final stage. The System is designed to meet all the requirements of the user. EPM gives the facility to define the tasks in the organization and also allows the managers to track the efforts spent by the employee for that particular task. The system has been developed with much care that it is free of errors and at the same time it is efficient and less time consuming. A good amount of user- friendly features have been incorporated in this software Employee Performance Management and it is possible for any of the candidates to exploit features to get the maximum benefit.

Some special features of this project are: It reduces the manpower to some extent It reduces the time cost. To provide an easy and efficient environment To provide an easy user interactive area To reduce the report generation required time To provide intra mail process .

37

SCOPE FOR FURTHER ENHANCEMENT

The software is left without proper and frequent maintenance will have to put in the bin after a small duration of usage. In order to avoid this timely enhancement will be made to this project so as keep the system update according to the user needs. In teams of technological updating, steps will be taken to make this current developed Skill and Activity Tracker System compatible with the new versions of the software tools used so as to avoid the maximum possible usage out of the system. Time will make changes .. its true. EPM is so flexible to change according to the needs. Since the software is reusable and the modules are well formed it is easy to make any changes easily. We are planning to add the facility for providing different levels of Performance tracking of employee services based on this performance.

38

BIBLIOGRAPHY
BOOKS
The Zen of CSS Design, Dave Shea, OReilly Publications, Gold Edition JavaScript: A Beginners Guide, John Pollock, TATA McGraw Hill, Gold Edition JavaScript Programmer's Reference, Cliff Wootton, Wrox Publications, Har/Cdr edition (April 13, 2009)

WEBSITES http://www.fiftyfoureleven.com/resources/programming/xmlhttprequest/examples http://eclipse-tutorials.com/ http://www.ibmtools.com/

39

ANNEXURES

1. INPUT DESIGN

Home Page

40

Login Form

Fig: 1.0

41

Registration form

Fig: 1.1

42

Task details form

Fig: 1.2

43

Task Allotment form

Fig:1.3

44

Analyze efforts

Fig:1.4

45

2. OUTPUT DESIGN
Performance analyzed record view

Fig:2.0

46

Task Details view

Fig:2.1

47

Internal Employee Details view

Fig:2.2

48

3. SAMPLE SOURCE CODE

Registration Form
<%@ page language="java" contentType="text/html; charset=ISO-8859-1" pageEncoding="ISO-8859-1"%> <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html> <head> <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"> <title>Insert title here</title> </head> <script type="text/javascript"> function fun() { if(document.f2.username.value=="") { alert("enter the username") } if (document.f2.passwd.value=="") { alert("enter the password"); return false; } if(document.f2.confirmpwd.value=="") { alert("enter the Confirm-password"); return false; } if(document.f2.name.value=="") { alert("enter the Name"); return false; } if(document.f2.address.value=="") { alert("enter the address"); return false; } if(document.f2.phone.value=="") { alert("enter the phone number"); return false; } if(document.f2.mobile.value=="") { alert("enter the mobile"); return false; } if(document.f2.email.value=="") return true; } </script>

49

<body> <!-- Add the below code where you wish the text to appear on the page: --> <b> <font size="5"> <script> var text=" Employee - Registration Form " // YOUR TEXT var speed=80 // SPEED OF FADE - Higher=faster/Lower=slower if (document.all||document.getElementById){ document.write('<span id="highlight">' + text + '</span>') var storetext=document.getElementById? document.getElementById("highlight") : document.all.highlight } else document.write(text) var hex=new Array("00","14","28","3C","50","64","78","8C","A0","B4","C8","DC","F0") var r=1 var g=1 var b=1 var seq=1 function changetext(){ rainbow="#"+hex[r]+hex[g]+hex[b] storetext.style.color=rainbow } function change(){ if (seq==6){ b-if (b==0) seq=1 } if (seq==5){ r++ if (r==12) seq=6 } if (seq==4){ g-if (g==0) seq=5 } if (seq==3){ b++ if (b==12) seq=4 } if (seq==2){ r-if (r==0) seq=3 } if (seq==1){ g++

50

if (g==12) seq=2 } changetext() } function starteffect(){ if (document.all||document.getElementById) flash=setInterval("change()",speed) } starteffect() </script> </font></b>&nbsp;&nbsp;&nbsp;&nbsp; <form name="f2" action="taskdetails.jsp" onsubmit="return fun()" > <table align="Center"> <td width="155"> <tr> <img src="employee-engagment.jpg" width="850" height="142" > </tr> <tr> <td><strong><font face="verdana,arial" size=-1>Employee Name</strong></td> <td width="271"> <input type="text" name="uname"></td></tr> <tr> <td><font face="verdana,arial" size=-1> <div align="justify"><strong> Employee ID</strong></div></td> <td> <input type="text" name="pass"></td></tr> <tr> <td><strong><font face="verdana,arial" size=-1> Hire Date </strong></td> <td> <input type="text" name="conpwd"></td></tr> <tr> <td><font face="verdana,arial" size=-1> <div align="justify"><strong>Experience </strong></div></td> <td> <input type="text" name="name"></td></tr> <tr><td><strong><font face="verdana,arial" size=1>Address</strong></td> <td> <textarea name="address" cols="15" rows="1"> </textarea><br></td></tr> <tr> <td><font face="verdana,arial" size=-1><strong> Job </strong></td> <td> <input type="text" name="phone"></td></tr> <tr><td><strong><font face="verdana,arial" size=1>Mobile No</strong></td> <td> <input type="text" name="mobile"></td></tr>

51

<tr><td><strong><font face="verdana,arial" size=1>DOB</strong></td> <td> <select name="date"> <option value="">- Select -</option> <option value="1">1</option> <option value="2">2</option> <option value="3">3</option> <option value="4">4</option> <option value="5">5</option> <option value="6">6</option> <option value="7">7</option> <option value="8">8</option> <option value="9">9</option> <option value="10">10</option> <option value="11">11</option> <option value="12">12</option> <option value="13">13</option> <option value="14">14</option> <option value="15">15</option> <option value="16">16</option> <option value="17">17</option> <option value="18">18</option> <option value="19">19</option> <option value="20">20</option> <option value="21">21</option> <option value="22">22</option> <option value="23">23</option> <option value="24">24</option> <option value="25">25</option> <option value="26">26</option> <option value="27">27</option> <option value="28">28</option> <option value="29">29</option> <option value="30">30</option> <option value="31">31</option> </select> <select name="month"> <option value="">- Select -</option> <option value="1">1</option> <option value="2">2</option> <option value="3">3</option> <option value="4">4</option> <option value="5">5</option> <option value="6">6</option> <option value="7">7</option> <option value="8">8</option> <option value="9">9</option> <option value="10">10</option> <option value="11">11</option> <option value="12">12</option> </select> <select name="year"> <option value="">- Select -</option> <option value="1970">1970</option> <option value="1971">1971</option> <option value="1972">1972</option>

52

<option value="1973">1973</option> <option value="1974">1974</option> <option value="1975">1975</option> <option value="1976">1976</option> <option value="1977">1977</option> <option value="1978">1978</option> <option value="1979">1979</option> <option value="1980">1980</option> <option value="1981">1981</option> <option value="1982">1982</option> <option value="1983">1983</option> <option value="1984">1984</option> <option value="1985">1985</option> <option value="1986">1986</option> <option value="1987">1987</option> <option value="1988">1988</option> <option value="1989">1989</option> <option value="1990">1990</option> <option value="1991">1991</option> <option value="1992">1992</option> <option value="1993">1993</option> <option value="1994">1994</option> <option value="1995">1995</option> <option value="1996">1996</option> <option value="1997">1997</option> <option value="2000">2000</option> </select> </td></tr> <tr><td><font face="verdana,arial" size=-1><strong>Email</strong></td> <td> <input type="text" name="email"></td></tr> <tr><td><font face="verdana,arial" size=1><strong>Sex</strong></td> <td> <select name="sex"> <option value="">- Select -</option> <option value="Male">Male</option> <option value="Female">Female</option> </select> </td></tr>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <tr><td><font face="verdana,arial" size=-1></font> </td><td><font face="verdana,arial" size=1></font><br><br><br> <input type="submit" value="SUBMIT" name=chkform onclick="chk_onclick()"> <input name="RESET" type="reset" value="RESET"/></td></tr> </table> </form> </body> </html>

53

Task Details form

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml-transitional//EN"> <html xmlns='http://www.w3.org/1999/xhtml' xml:lang='en'> <head> <script type="text/javascript"> function fun() { if(document.f2.fname.value=="") { alert("enter the first name") } if (document.f2.lname.value=="") { alert("enter the Address"); return false; } if(document.f2.dob.value=="") { alert("enter the date of birth"); return false; } if(document.f2.address.value=="") { alert("enter the address"); return false; } if(document.f2.dob.value=="") return true; } </script> </head> <style type="text/css"> <!-body,td,th { font-family: Times New Roman, Times, serif; color: #000000; } body { background-color: #fffff; } --> </style></head> <body background="motivational-131h.jpg "> <!-- Add the below code where you wish the text to appear on the page: --> <b> <font size="5"> <script>

54

var text="Public - Registration Form" // YOUR TEXT var speed=80 // SPEED OF FADE - Higher=faster/Lower=slower if (document.all||document.getElementById){ document.write('<span id="highlight">' + text + '</span>') var storetext=document.getElementById? document.getElementById("highlight") : document.all.highlight } else document.write(text) var hex=new Array("00","14","28","3C","50","64","78","8C","A0","B4","C8","DC","F0") var r=1 var g=1 var b=1 var seq=1 function changetext(){ rainbow="#"+hex[r]+hex[g]+hex[b] storetext.style.color=rainbow } function change(){ if (seq==6){ b--if (b==0) seq=1 } if (seq==5){ r++ if (r==12) seq=6 } if (seq==4){ g-if (g==0) seq=5 } if (seq==3){ b++ if (b==12) seq=4 } if (seq==2){ r-if (r==0) seq=3 } if (seq==1){ g++ if (g==12) seq=2 } changetext() } function starteffect(){ if (document.all||document.getElementById) flash=setInterval("change()",speed) }

55

starteffect() </script> </font></b>

<form

name="f2" action="allot.jsp" onsubmit="return fun()" >

<fieldset> <center> <table align="left"> <img src="1.jpg" width="850" height="142" > <tr> <td><div align="justify"><b> Task ID </b></div></td> <td><input type="text" size="30" name="fname"/></td> </tr> <tr> <td><div align="justify"><b> Task Name</b></div></td> <td><input type="text" size="30" name="lname"/></td> </tr> <tr> <td> <div align="justify"><b>Skill Set</b></div></td> <td> <p> <select name="select" size="1"> <option>- select the Skill type -</option> <option>Technical</option> <option>Analytical</option> </select> </p> </td> </tr> <tr> <td><div align="justify"><b>Task Start date</b></div></td> <td> <input type="text" name="dob" size="30"/></td> </tr> <tr> <td><div align="justify"><b>Task End Date</b></div></td> <td><input type="text" name="address" size="30"/></td> </tr> <tr>

56

<td><div align="justify"><b>Task Duration</b></div></td><br><br> <td><input type="text" name="address1" size="30"/></td> </tr> <tr> <td><div align="justify"><b>Email_ID</b></div></td> <td><input type="text" name="address2" size="30"/></td> </tr>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <tr><td><font face="verdana,arial" size=-1></font> </td><td><font face="verdana,arial" size=1></font><br><br><br> <input type="submit" value="SUBMIT" name=chkform onclick="chk_onclick()"> <input name="RESET" type="reset" value="RESET"/></td></tr> </table> </center> </fieldset> </form> </body> </html>

4. ABBREVIATIONS
EPM GUI DFD LAN HR Employee Performance Management Graphical User Interface Data Flow Diagram Local Ares Network Human Resource

57