HUMAN RESOURCE MANAGEMENT SYSTEM BY -1-

ACKNOWLEDGMENT I express thanks and gratitude to Mr. H.O.D computer science department, encoura ging support and guidance in carrying out the project. I would like to express g ratitude and indebtedness to , for his valuable advice and guidance without whic h this project would not have seen the light of the day. I thank , Project guide , for , for his providing us with an excellent project and guiding me in completing our project successfully. I would like to thank all the staff members of for their kind co-o peration. I would like to thank my parents for being supportive all the time, an d I am very much obliged to them. -2-

ABSTRACT -3-

CONTENTS -4-

CONTENTS Page nos. *Acknowledgement *Abstract 1. INTRODUCTION 1.1 HRMS 2. SYSTEM ANALYSIS 2.1 2.2 2.3 Existing System Proposed System Feasibility Study 3. MODULE DESCRIPTION 3.1 Employee Info Module 3.2 Administration Module 3.3 Pro ject Management Module 3.4 Training Management Module 4. SYSTEM REQUIREMENTS 4.1 4.2 Software Requirements Hardware Requirements -5-

5. LITERATURE SURVEY 6. SYSTEM DESIGN 6.1 6.2 Detailed Design 6.1.1 UML Diagrams Database Design 6.2.1 Dataflow Diagrams 6.2.2 Database Tables 6.2.3 E-R Diagram s 6.2.4 Screens. 7. TESTING 8. IMPLEMENTATION 9. CONCLUSION 10.BIBLIOGRAPHY -6-

-7-

INTRODUCTION -8-

HUMAN RESOURCE MANAGEMENT SYSTEM -9-

1.2 HUMAN RESOURCE MANAGEMENT SYSTEM SYSTEM ANANLYSIS - 10 -

EXISTING SYSTEM - 11 -

2.1 EXISTING SYSTEM The HR Administration falls short of controlling the employees activities in anal yzing his/her strengths and weakness. The decision for appraisal of assigning ne xt project to the employee or to train him/her to enhance the skills where lies with proper projection. He is not provided with the detailed project information done or to be assigned based on Application / Verticals. . 2.1.1 DRAWBACKS IN EXISTING SYSTEM: Need of extra manual effort. It used to take much time to find any employee very much accurate. Danger of losing the files in some cases. - 12 Not

PROPOSED SYSTEM - 13 -

2.2 PROPOSED SYSTEM Decision in assigning proper skillful hands for the project is an important issu e in HR Module. The HR Administrator should report with the personal holding the necessary skills required for the project assignment. The decision in making an alysis about the employees skills is a prime important before booting in. The pro posed system of HR Module is the right software to be incorporated into the Auto mation of HR Software for helping the organization needs with respect to skilful Human Resource. The proposed system provides detail general information about t he employee along with Educational, Certification, Skill and Project details. It enhances the HR Management in adding, viewing and updating employees details and generates various reports regarding employees skill and experience. Suggestions and Grievances posted by the employees are upheld for taking care of the necessa ry steps in forwarding companys obligation. . 2.2.1 ADVANTAGES OF PROPOSED SYSTEM : Very fast and accurate. - 14 No need of any extra manual effort.

No fever of data loss. Just need a little knowledge to operate the system. require any extra hardware device. At last very easy to find the employees. FEASIBILITY STUDY - 15 -

Doesnt

2.3 FEASIBILITY STUDY Once the problem is clearly understood, the next step is to conduct feasibility study, which is high-level capsule version of the entered systems and design pro cess. The objective is to determine whether or not the proposed system is feasib le. The three tests of feasibility have been carried out. Technical Feasibility Economical Feasibility Operational Feasibility TECHNICAL FEASIBILITY In Technical Feasibility study, one has to test Whether the proposed system can be developed using existing technology or not. It is planned to implement the pr oposed system using java technology. It is evident that the necessary hardware a nd software are available for development and implementation of the proposed sys tem. Hence, the solution is technically feasible. ECONOMICAL FEASIBILITY - 16 -

As part of this, the costs and benefits associated With the proposed system comp ared and the project is economically feasible only if tangible or intangible ben efits outweigh costs. The system development costs will be significant. So the p roposed system is economically feasible. OPERATIONAL FEASIBILITY It is a standard that ensures interoperability Without s tifling competition and innovation among users, to the benefit of the public bot h in terms of cost and service quality. The proposed system is acceptable to use rs. So the proposed system is operationally feasible. - 17 -

MODULE DESCRIPTION - 18 -

MODULE DISCRIPTION: The list of modules incorporated with Human Resource Management System is Employee Info Module Administration Module Project Management Module Training Management Module HR Reports This module deals with the management of information such as the the employee details-his personal name,qualification,skill,experience,login id,password,etc., Importance of module s in any software development side is we can easily understand what the system w e are developing and what its main uses are. At the time of project we may creat e many modules and finally we combine them to form a system. 3.1 Employee Info Module - 19 -

This module deals with the management of the employee information such as the pe rsonal details-his name,qualification,skill,experience,login id,password,etc., I mportance of modules in any software development side is we can easily understan d what the system we are developing and what its main uses are. At the time of p roject we may create many modules and finally we combine them to form a system. person, so that it can be easily added to the database with any duplication of t he data. 3.2 Administration Module: This module deals with the management of the employee information such as the hi ring of the eligible candidate, payments criteria, his personal information main tenance etc. 3.3 Project Management Module: This module deals with the management of the proj ects related with the employee like-projects that were past dealt, current proje cts in his account etc. 3.4 Training Management Module: This module deals with the training of the emplo yee based on his experience and attendance monitoring. Also the information of t he projects that need to be trained for the employees based on their experience and skills and the like. 3.5 HR Reports Module: - 20 -

This module is specified for the purpose of the report generation for the HR on his desired requests. SYSTEM REQUIREMENTS - 21 -

HARDWARE AND SOFTWARE REQUIREMENTS Hard ware Specification: Processor Processor Speed RAM Hard Disk Key Board : : : : : Intel P-III based system 250 MHz to 833MHz 64MB to 256MB 2GB to 30GB 104 ke ys Software Specification - 22 -

Language Database Operating System RAM : : : : JDK 1.4 Oracle 9i WindowsNT/95/98/2000 256MB LITERATURE SURVEY - 23 -

JAVA Java was conceived by James Gosling, Patrick Naughton, Chris Warth, Ed Frank and Mike Sheridan at Sun Microsystems Inc.in 1991. It took 18 months to develop the first working version. This language was initially called Oak but was renamed as J ava in 1995. Between the initial implementation of Oak in the fall of 1992 and th e public announcement of Java in the spring of 1995, many more people contribute d to the design and evolution of the language. The main properties of the Java, which made Java so popular, are as follows: 1. Simple 2. Secure 3. Portable 4. O bject-Oriented 5. Robust 6. Multithreaded 7. Architecture-Neutral 8. Interpreted 9. High performance 10.Distributed 11.Dynamic - 24 -

THE KEY FEATURES OF JAVA IS BYTE CODE: The key that allows Java to solve both the security and the portability problems just described is that the output of a Java compiler is not executable code. Ra ther, it is Byte code. Byte code is a highly optimized set of instructions desig ned to be executed by the Java runtime systems, which is called the Java Virtual Machine (JVM). That is, in its standard form, the JVM is an interpreter for Byt e code. This may come has a bit of surprise. Translating a Java program into a b yte code helps and makes it much easier to run a program in a wide variety of en vironments. The reason is straightforward only the JVM needs to be implemented f or each platform. Once the runtime package exists for a given system, any Java p rogram can run on it. Remember, although the details of the JVM will differ from platform to platform, all interpret the same Java Byte code. JAVA ENVIRONMENT: Java environment includes a large number of development tools and hundreds of classes and methods. The development tools are the part of the system known as Java Development Kit (JDK) and the classes are methods are part of - 25 -

the Java standard library (JSL), also known as the Application Programming Inter face (API). JAVA DEVELOPMENT KIT: The Java development kit comes with a collection of tools that are used for deve loping and running Java programs. They include: 1.Applet Viewer (for viewing Jav a Applets) 2.Javac (Java Compiler) 3.Java (Java interpreter) 4.Javap (Java Disas sembler) 5.Javah (for C header files) 6.Javadoc (for creating HTML documents) 7. Jdb (Java Debugger) APPLICATION PROGRAMMING INTERFACE: The Java standard library includes hundreds of classes and methods grouped into several functional packages. Most commonly used packages are: Language support p ackage: A collection of classes and methods required for implementing basic feat ures of java. Utilities package: A collection of classes to provide utility func tions such as date and time functions. Input/Output package: A collection of cla sses required for input & output manipulations. - 26 -

Networking package: A collection of classes for communication with other computers via Internet. AWT package: The abstract windo w toolkit package contains classes that implements platform independent graphica l user interface. Applet package: This includes a set of classes that allows us to create Java applets. JAVA DATABASE CONNECTIVITY (JDBC) The Java database connectivity Application Programming Interface (API) is an API currently being designed by Sun Microsyste ms that provides a Java language interface with SQL Call Level Interface standar d. This standard provides a DBMS independent interface to relational databases t hat defines a generic SQL database access framework. The most visible implementa tion of the SQL CLI is Microsofts ODBC (Open Database Connectivity). This API def ines a common SQL syntax and function calls that can be used by developers to se nd SQL commands to and retrieve data from SQL databases. ODBC - enabled applicat ions make use of database drivers (similar to other device drivers) installed on the system that allows applications to talk to a vendors database. Using this me thodology, all of the DBMS specific code is placed inside the ODBC driver and th e application developer is - 27 -

shielded from implementation specific problems in theory. Practically speaking, it is sometimes difficult to completely remove vendors specific syntax from all O DBC operations, but in most cases, it is relatively simple task to port ODBC to run on a new database server. ODBCs primary drawback is that it is written in C. Because of the limitations inherent in the use of native methods, the JDBC desig ners have designed the JDBC specification to most easily use ODBC in short-term, but they have provided the capability long-term for JDBC to be implemented in o ther ways. The JDBC API is expressed as a series of abstract Java interfaces wit hin the java.sql package. Here are the most commonly used interfaces: java.sql.D riverManager unloading systems. java.sql.Connection Handles the connections to a specific database. java.sql.Statement contains an SQL statement to be passed to the database: two sub-types in this interface are the PreparedStatement (for ex ecuting a Pre-Compiled SQL statement) and the CallableStatement (for executing a database stored procedure). java.sql.ResultSet contains the record result set f rom the SQL statement passed to the database. of database manages drivers the lo ading and from the underlying - 28 -

STEPS REQUIRED TO ACCESS A JDBC DATABASE The steps required to access a JDBC database should be familiar. JDBC uses the c oncept of a Connection handle to manage a programs connection to a database. ESTABLISING A CONNECTION The first thing we need to do is establish a connection with the DBMS you want t o use. This involves two steps : 1. Loading the driver: If, we want to use the J DBC-ODBC bridge driver, the following code will load it : Class.forName ("sun.jd bc.odbc.JdbcOdbcDrive) Our driver documentation will give us the class name to us e. For instance, if the class name is jdbc.Driverxyz, you would load the driver with the following line of code: Class.forName (jdbc.Driverxyz); 2. Making the con nection: the second step in establishing a connection is to have the appropriate driver connect to the DBMS. The following line of code illustrates the general Syntax: Class.forName ("sun.jdbc.odbc.JdbcOdbcDrive Connection con=DriverManager .getConnection ("Jdbc: Odbc: hrmsdsn"); - 29 -

CREATING A STATEMENT A statement needs to be created so that it can be passed to the database for pro cessing. This is done by calling the connection class createStatement () method. Syntax: Java.sql.Statement st=connection.createStatement (); RETREIVING VALUES FROM RESULT SET JDBC returns results in a ResultSet object, so we need to declare in instance of the class ResultSet to hold our result. The following code demonstrates declari ng the ResultSet object RS and assigning the results to query: ResultSet rs=st.e xecuteQuery ("select * from EMPDEATILS where user_name="+user_name+""); DATABASE DATABASE A database is a set of data, organized for easy access. The database is an actua l data; it is the database that you will be accessing when you need to retrieve data. DATA DICTIONARY The data dictionary is a set of tables Oracle uses to maintain information about the database. The data dictionary contains information about tables, indexes, c lusters and so on. DBA (DATABASE ADMINISTRATOR) - 30 -

The DBA is the person responsible for the operation, configuration and performan ce of the database. charged backups with keeping and the database operating The DBA is smoothly, Other ensuring that backups are done on regular basis (and that work), installing new software. responsibilities might include planning for future expansion and disk space needs, creating databases and table spaces, adding users and maintaining s ecurity, and monitoring the database and retuning it as necessary. Large install ations might have teams of DBAs to keep the system running smoothly; alternativel y, the task might be segmented among the DBAs. ORACLE Oracle is a relational database management system, it provides a platform for cl ient server computing i.e., it supports distributed database and distributed pro cessing. - 31 -

SYSTEM DESIGN - 32 -

DETAILED DESIGN - 33 -

UML DIAGRAMS - 34 -

UNIFIED MODELING LANGUAGE UML is the international standard notation for object-oriented analysis and desi gn. The Object Management Group defines it. The heart of object-oriented problem solving is the construction of a model. The model abstracts the essential detai ls of the underlying problem from its usually complicated real world. Several mo deling tools are wrapped under the heading of the UML, which stands for Unified M odeling Language. AN OVERVIEW OF UML: The UML is a language for Visualizing Specifying Constructing Documenting These are the artifacts of a software-intensive system. The three major elements of UM L are The UMLs basic building blocks put together. Some common mechanisms that ap ply throughout the UML. The rules that dictate how those building blocks may be BASIC BUILDING BLOCKS OF THE UML: - 35 -

The vocabulary of UML encompasses three kinds of building blocks: nships Diagrams

Things

Relatio

THINGS IN THE UML: They are the abstractions that are first-class citizens in a model. There are fo ur kinds of things in the UML 1. Structural things 2. Behavioral things. 3. Grou ping things. 4. Annotational things. These things are the basic object oriented building blocks of the UML. They are used to write well-formed models. STRUCTURAL THINGS: Structural things are the nouns of the UML models. These are mostly static parts of the model, representing elements that are either conceptual or physical. In all, there are seven kinds of Structural things. Class: - 36 -

A class is a description of a set of objects that share the same attributes, ope rations, relationships, and semantics. A class implements one or more interfaces . Graphically a class is rendered as a rectangle, usually including its name, at tributes and operations, as shown below. Interface: An interface is a collection of operations that specify a service of a class or component. Graphically the interface is rendered as a circle together with its n ame. ISpelling Collaboration: Collaboration defines an interaction and is a society of roles and other element s that work together to provide some cooperative behavior thats bigger than the s um of all the elements. Chain of Responsibili ty - 37 -

Graphically, collaboration is rendered as an ellipse with dashed lines, usually including only its name as shown below. Chain Use Case: Use case is a description of a set of sequence of actions that a system performs that yields an observable result of value to a particular thing in a model. Gra phically, Use Case is rendered as an ellipse with dashed lines, usually includin g only its name as shown below. Place Order Active Class: An active class is a class whose objects own one or more processes or threads an d therefore can initiate control activity. Graphically, an active class is rende red just like a class, but with heavy lines usually including its name, attribut es and operations as shown below. HRMS EMPLOYEE DEATILS Suspend () Flush () Component: - 38 -

Component is a physical and replaceable part of a system that conforms to and pr ovides the realization of a set of interfaces. Graphically, a component is rende red as a rectangle with tabs, usually including only its name, as shown below. orderform.jav a Node: A Node is a physical element that exists at run time and represents a computatio nal resource, generally having at least some memory and often, processing capabi lity. Graphically, a node is rendered as a cube, usually including only its name , as shown below. server BEHAVIORAL THINGS: Behavioural Things are the dynamic parts of UML models. These are the verbs of a model, representing behaviour over time and space. Interaction: An interaction is a behavior that comprises a set of messages exchanged among a set of objects within a particular context to - 39 -

accomplish a specific purpose. Graphically, a message is rendered as a direct li ne, almost always including the name if its operation, as shown below. Display State Machine: A state machine is a behavior that specifies the sequence of states an object ar e an interaction goes through during its lifetime on response to events, togethe r with its responses to those events. Graphically, a state is rendered as a roun ded rectangle usually including its name and its sub-states, if any, as shown be low. Waiting GROUPING THINGS: Grouping things are the organizational parts of the UML models. These are the bo xes into which a model can be decomposed. RELATIONSHIPS IN THE UML: - 40 -

There are four kinds of relationships in the UML: 1. Dependency 2. Association 3 . Generalization 4. Realization 1.Dependency: whenever This is relationship between two classes one class is completely dependent on the other class. Graphically the dashed line represents it with arrow pointing to the clas s that it is being depended on. 2. Association: It is a relationship between instances of the two classes. There is an association between two classes if an instance of one c lass must know about the other in order to perform its work. In a diagram, an as sociation is a link connecting two classes. Graphically it is represented by lin e as shown. 3. Generalization: An inheritance is a link indicating one class is a super class of the other. A generalization has a triangle pointing to the super class. Graphically it is represented by line with a triangle at end a s shown. - 41 -

4. Realization: DIAGRAMS IN UML: Diagrams play a very important role in the UML. There are nine kind of modeling diagrams as follows: Use Case Diagram Class Diagram Object Diagram Sequence Diagram Collaboration Dia gram State Chart Diagram Activity Diagram Component Diagram Deployment Diagram CLASS DIAGRAM: Class diagrams are the most common diagrams found in modeling object-oriented sy stems. A class diagram shows a set of classes, interfaces, and collaborations an d their relationships. Graphically, a class diagram is a collection of vertices and arcs. - 42 -

USE CASES DIAGRAM: Use Case diagrams are one of the five diagrams in the UML for modeling the dynam ic aspects of systems(activity diagrams, sequence diagrams, state chart diagrams and collaboration diagrams are the four other kinds of diagrams in the UML for modeling the dynamic aspects of systems). INTERACTION DIAGRAMS An Interaction diagram shows an interaction, consisting of a set of objects and their relationships, including the messages that may be dispatched among them. I nteraction diagrams are used for modeling the dynamic aspects of the system. A s equence diagram is an interaction diagram that emphasizes the time ordering of t he messages. Graphically, a sequence diagram is a table that shows objects arran ged along the X-axis and messages, ordered in increasing time, along the Y-axis and messages, ordered in increasing time, along the Y-axis. SEQUENCE DIAGRAMS: A sequence diagram is an interaction diagram that emphasizes the time ordering o f the messages. Graphically, a sequence diagram is a table that shows objects ar ranged along the X-axis and messages, ordered in increasing time, along the Y-ax is. Sequence diagrams have two interesting features: - 43 -

ACTIVITY DIAGRAM An Activity Diagram is essentially a flow chart showing flow of control from activity to activity. They are used to model the dynamic aspects o f as system. They can also be used to model the flow of an object as it moves fr om state to state at different points in the flow of control. Contents Activity diagrams commonly contain: Fork Start & End Symbol STATE CHART DIAGRAMS A state chart diagram shows a state machine. State chart diagrams are used to mo del the dynamic aspects of the system. For the most part this involves modeling the behavior of the reactive objects. A reactive object is one whose behavior is best characterized by its response to events dispatched from outside its contex t. A reactive object has a clear lifeline whose current behavior is affected by its past. Graphically a state chart diagram is a collection of vertices and arcs . - 44 -

Contents: State chart diagram commonly contain: Simple states and Composite states. Transi tions, including events and actions. CLASS DIAGRAM - 45 -

E m p lo g in L o g in () C h e c k T r a in in g D e t a il s () C h e c k C o m p e n s a t io n () C h e c k E m p lo y e e () E m p l o y e e D e t a i ls D ept D a te Emp Emp A s s ig n e d () o f J o in in g ( ) D e t a i ls () C o m p o n e n t() H R A d m i n is t r a t i o n Hr Nam e H r ID A d d D e t a il s A d d E m p D e t a ils () A d d T r a in in g D e t a ils () A d d C o m p e n s a t io n () T ra in in g d e a t ils Dept L o c a t io n E m p Nam e S k il l D e t a ils S k il l C o n t e n t ( ) T ra i n in g A s s ig n ( ) D u r a t io n ( ) C o m p e n s a t io n C o m p e n s a t i o n A m t () Y e a r o f w o rk ( ) S k il l R e p o rt () USE CASE DIAGRAM - 46 -

L o g in A d m in is t ra t o r C h e c k E m p D e t a ils E m p lo y e e A d d E m p d e t a i ls C h e c k T r a i n i n g D e t a i ls A d d t ra in in g d e t a ils C h e c k C o m p e n s a tio n A d d C o m p e n s a t io n d e t a ils Logout SEQUENCE DIAGRAM - 47 -

H R A d m in E m p lo y e e T ra i n in g C o m p e n s a t i o n P la c e m e n t 1 . lo g in S k ill E m p d e a t ils 2 . ve r ify 3 . A d d e m p d e t a ils 4 . A d d s k il ls R e p o r t 5 . A d d P la c e m e n t re p o r t 6 . A d d T r a in in g R e p o r t 7 d e a . e m t A d d C o m p e n s a t io n R e p o r t 8 . lo g o u t 9 . C h e c k e m p a t ils 1 0 . C h e c k e m p lo y e e s k ills r e p o r t 1 1 . C h e c k p lo y e e p la c e m e n t r e p o r t 1 2 . c h e c k e m p c o m p e n s io n re p o r t

1 3 . c h e c k e m p l o y e e t ra in in g re p o rt 1 4 .L o g o u t COLLABORATION DIAGRAM - 48 -

E m p lo g in Check T ra in in g H r A d m in Check E m p D e t a il C heck C o m p e n s a tio p n A dd T ra in in g A dd c o m p e n s a tio n A dd E m p D e t a ils ACTIVITY DIAGRAM - 49 -

Receive Emp Details Emp Login Open Tarining List Open Emp Details Check Training List Emp Details - 50 -

Class Diagram Emp login Login() Check Training Details() Check Compensation() Check Employee() Employee Details Dept Assigned() Date of Joining() Emp Details() Emp Component( ) HR Administration Hr Name Hr ID Add Details Add Emp Details() Add Training Detai ls() Add Compensation() Training deatils Dept Location Emp Name Skill Details Skill Content() Training A ssign() Duration() Compensation Compensation Amt() Year of work() Skill Report() - 51 -

DATABASE DESIGN - 52 -

DATA FLOW DIAGRAMS - 53 -

DATA FLOW DIAGRAMS DATA FLOW DIAGRAMS: A graphical tool used to describe and analyze the moment of data through a syste m manual or automated including the process, stores of data, and delays in the s ystem. Data Flow Diagrams are the central tool and the basis from which other co mponents are developed. The transformation of data from input to output, through processes, may be described logically and independently of the physical compone nts associated with the system. The DFD is also know as a data flow graph or a b ubble chart. CONTEXT DIAGRAM: The top-level diagram is often called a context diagram. It contains a single process, but it plays a very important role in studying the cu rrent system. The context diagram defines the system that will be studied in the sense that it determines the boundaries. Anything that is not inside the proces s identified in the context diagram will not be part of the system study. It rep resents the entire software element as a single bubble with input and output dat a indicated by incoming and outgoing arrows respectively. - 54 -

TYPES OF DATA FLOW DIAGRAMS: Data Flow Diagrams are of two types as follows: (a) Physical DFD (b) Logical DFD 1. PHYSICAL DFD: Structured analysis states that the current system should be first understand co rrectly. The physical DFD is the model of the current system and is used to ensu re that the current system has been clearly understood. Physical DFDs shows actu al devices, departments, and people etc., involved in the current system 2. LOGICAL DFD: Logical DFDs are the model of the proposed system. They clearly should show the requirements on which the new system should be built. Later during design activi ty this is taken as the basis for drawing the systems structure charts. BASIC NOTATION: - 55 -

The Basic Notation used to create a DFDs are as follows: DATAFLOW: Data move in a specific direction from an origin to a destination. PROCESS: People, procedures, or devices that use or produce (Transform) Data. identified. The physical component is not SOURCE: External sources or destination of data, which may be People, programs, organizations or other entities. DATA STORE: Here data are stored or referenced by a process in the System DESIGN: - 56 -

Design is the first step in moving from problem domain to the solution domain. D esign is essentially the bridge between requirements specification and the final solution. The goal of design process is to produce a model or representation of a system, which can be used later to build that system. The produced model is c alled the Design of the System. It is a plan for a solution for the system. PROCESS FLOW DIAGRAM Create Is Create s Create an Employee Manag es HR manager s Details s Placement - 57 Training Compensation Employees Administration ReportsReport Skil l Reports Details Reports

1 1 1 Context Flow Diagram - 58 -

Description: Context Flow Diagram gives us the complete details about the inputs and outputs for a given system. In the above system the main task is to identify a criminal face. So, the operator and eyewitness are t he inputs to our system and criminal face is desired output. LOGIN PROCESS LOGIN User Id Password PROCESS SCREEN ERROR IN INPUT Level-1 Description: The inputs to the process are User Id and Password given by the developer to allow the software available for the Admin en vironment. After giving the inputs the details, checks whether the entered ones are valid are not. It displays screen if match occurs otherwise error message if they are not matched. - 59 -

MAIN SCREEN PROCESS ADMIN MAIN SCREEN Add Emp Add Skill Reports Add Placement Add Training Report Add Compensation Level -2 Description: This process mainly explains the different that are available for the admin. Here the selection of e admin and he can select whatever screen he wants. The re available are Add Emp details, Add skill Report, Add aining Report, Add Compensation Report. - 60 screens the screen depends on th different screens that a placement report, Add Tr

Add Employee Details Administrator Creat e Employee Report Level-3 Description: This process clearly illustrates adding the details of the Employee such as name, age, gender, location, address, state and city alo ng with his EMP Id. These details are being added to the database, if any error is generated then it will be prompted to the admin otherwise we get message data is successfully added. Add Skill Report - 61 -

DATABASE Admin ADD Skill Report DATA IS ADDED Level-4 Description: This process clearly illustrates adding the details of the Employees skill Report such as name, qualification, experience, departmen t, projects handled, current projects and skills along with his EMP Id. These de tails are being added to the database, if any error is generated then it will be prompted to the admin otherwise we get message data is successfully added. Add Placement Report - 62 -

DATABASE Admin Add Placement Report DATA UPDATED Level-5 Description: This process clearly illustrates adding the details of the Employees placement Report such as name, employee status, reporting date, regulatory region, country, company control unit, department, supervisor id, lo cation and along with his EMP Id. These details are being added to the database, if any error is generated then it will be prompted to the admin otherwise we ge t message data is successfully added. - 63 -

TRAINING REPORTS DATABASE Admin Add Training Report DATA UPDATED Level-6 Description: This process clearly illustrates adding the details of the Employees Training Report such as name, project name, training department , skill report, start date, end date, department, and remarks and along with his EMP Id. These details are being added to the database, if any error is generate d then it will be prompted to the admin otherwise we get message data is success fully added. - 64 -

COMPARISON PROCESS DATABASE Admin Add Compensation Report DATA UPDATED Level-7 Description: This process clearly illustrates adding the details of the Employees Compensation Report such as name, salary range, and annual inco me, tax of income, loans, present annual income, facilities, and insurance and a long with his EMP name. These details are being added to the database, if any er ror is generated then it will be prompted to the admin otherwise we get message data is successfully added. - 65 -

DATABASE TABLES DATABASE TABLES Login Table - 66 -

user_login user_name admin kishore sree tarun vamsi password admin kishore sree tarun vamsi employee employee employee user_type Administrator Add Employee Details add_emp user_name password kishore sree tarun vamsi kishore sree tarun vamsi id first_na me last_name qualification department kumar kumar kumar Krishna MBA mca B.Tech B .Tech FINANCE computers computers computers date_ of age sex birth 18-April addr ess 1004 kishore 1001 sree 1003 tarun 1002 vamsi 21 male yousfguda 20/10/1984 21 male DSNR 15/03/1985 20 male yousfguda 20/05/1984 21 male chandanaga Add Skill Report skill_report45 user_name sree vamsi kishore fname sree vamsi kishore qua mca B.Tech MBA dept co mputers IT FINANCE proj_hand IPMS OCRS Tally curr_hand hrms Finger Print ID Acco unts exp 2 2 5 skil Java,Jsp java,jsp,jdbc CA Add Placement Report - 67 -

pLACEMENT54 username emp_stat effe_dat sree Active 01march2005 2/feb region coun comp cont_u nit dept loc super_id Maharastra AUSTRALIA B.H.E.L production Production Campus employee vamsi kishore Active Active Maharastra GERMANY GE USA IT Networking Campus employee Campus employee 16 june Delhi brekely FINANCE Financing Add Training Report trai user_name vamsi emp_id 1002 projn Finger Print ID dept Administration skill sdat edat 01-07-2005 reas good RGM 01-04-2005 sree 1001 HRMS Financing DFS 01-02-2005 01-02-2005 good - 68 -

trai user_name kishore emp_id 1004 Tally projn dept Financing skill Tally sdat 01-052005 edat 01-09-2005 reas good Add Compensation Report compensation username empid sal_rang kishore 1004 1000015000 annul_in 180000240000 tax 3% loa ns pre_annul faci bus facilities ins health insurance personal loans 180000240000 Sree 1001 500010000 60000120000 1% home loans 60000120000 bus facilities life insurance vamsi 1002 500010000 120000180000 2% vehical loans 120000180000 travelling health insurance - 69 -

SCREENS - 70 -

LOGIN SCREEN LOGIN PROCESS USER ID PASSWORD - 71 -

MAIN SCREEN View employee details - 72 -

View employee skill report - 73 -

View employee placement report - 74 -

View employee training report - 75 -

View employee compensation report - 76 -

Employee logout page - 77 -

TESTING - 78 -

TESTING PHASE The completion of a system is achieved only after it has been thoroughly tested. Though this gives a feel the project is completed, there cannot be any project without going though this stage. Hence in this stage it is decided whether the p roject can under go the real time environment execution without any break downs, therefore a package can be rejected even at this stage. SYSTEM TESTING Testing is a set of activities that can be planned in advance and conducted syst ematically. The proposed system is tested in parallel with the software that con sists of its own phases of analysis, implementation, testing and maintenance. Fo llowing are the tests conducted on the system. UNIT TESTING During the implementation of the system each module of the system was tested sep arately to uncover errors with in its boundaries. User interface was used as a g uide in the process. MODULE TESTING A module is composed of various programs related to that module. Module testing is done to check the module functionality and interaction between units within a module. - 79 -

It checks the functionality of each program with relation to other programs with in the same module. It then tests the overall functionality of each module. INTEGRATION TESTING Integration testing is a systematic technique for constructing the program structure while conducting tests to uncover errors asso ciated with interfacing. The objective is to take unit-tested module and build a program structure that has been dictated by design. ACCEPTANCE TESTING The software has been tested with the realistic data given by the client and pro duced fruitful results. The client satisfying all the requirements specified by them has also developed the software within the time limitation specified. A dem onstration has been given to the client and the end-user giving all the operatio nal features. - 80 -

IMPLEMENTATION - 81 -

IMPLEMENTATION PHASE The implementation is the final and important phase. It involves User training, system testing and successful running of the developed system. The users test th e developed system when changes are made according to the needs. The testing pha se involves the testing of the developed system using various kinds of data. An elaborate testing of data is prepared and system is tested using the tests data. Implementation is the stage where theoretical design turned into a working syst em. Implementation is planed carefully to propose system to avoid unanticipated problems. Many preparations involved before and during the implementation of pro posed system. The system needed to be plugged in to the organizations network the n it could be accessed from anywhere, after a user logins into the portal. The t asks that had to be done to implement the system were to create the database tab les in the organization database domain. Then the administrator was granted his role so that the system could be accessed. The next phase in the implementation was to educate the system. A demonstration of all the functions that can be carr ied out by the system was given to examination department person, who will make extensive use of the system. - 82 -

CONCLUSION - 83 -

- 84 -

BIBLIOGRAPHY - 85 -

BIBLIOGRAPHY BOOKS REFERRED The following books were used extensively for the project development and implem entation. 1.The Complete Reference Java2 Tata McGraw-Hill publishing Company Limit ed. By Herbert Schildt. 2. Software Engineering, A Practitioners Approach Tata McGr aw-Hill Pressman. 3. PL/SQL. By Ivan Bayross. Publishing Company Limited. By Roger S. WEBSITES REFERRED The following links were searched and exploited extensively for the project deve lopment and implementation. 1. http://www.java.sun.com/products\java 2. http://www.jakarta.apache.org 3. htt p://www.javaworld.com/ 4. http://www.java2s.com/ - 86 -