Professional Documents
Culture Documents
INTRODUCTION. MODULE DESCRIPTION. SYSTEM REQUIREMENTS. SYSTEM ANALYSIS. FEASIBILITYSTUDY. PROJECT PLANNING. DATABASE DESIGN. DATA DICTIONARY. DATA FLOW DIAGRAM. UML DIAGRAMS. FEATURE ENHANCEMENTS. BIBLIOGRAPHY.
1.0 Introduction
1.1 What is Hrms:
The Human Resource Management System (HRMS) is an on-line computerized system which stores, processes and reports employment and payroll records. The functions of HRMS are: Security (management of on-line view and update capabilities) Registration process. Leave application process.
Registration process:
This module provides instruction for completing the new hire process. It is important that these components accurately reflect an employees history because Human Resources data is used in both the Universitys management and government reporting for various purposes.
Address Information
Use this page to change existing home or business addresses or to record other addresses. The system automatically records the home and mailing address here when first entered under Personal Data. To change one of these addresses, follow the steps below. To enter a new address type, follow the steps on the next page.
Practical use of the different leave types e.g. Annual, Accumulated, Family Responsibility, Sick, Maternity etc. The capture of transactions and accessing Leave History.
MODULE DESCRIPTION:
The list of modules incorporated with Human Resource Management System is
personal details-his name, qualification, skill, experience, login id, password, etc.,
Importance of modules in any software development side is we can easily understand what the system we are developing and what its main uses are. At the time of project we may create many modules and finally we combine them to form a system. so that it can be easily added to the database with any duplication of the data.
employee leave application process is approved or rejected to team leader. When we have
HR MODULE:
employee leave information details monitoring. When we have team leader approved new employee information details see hr will be activated leader approved or rejected. When we have team
SYSTEM REQUIREMENTS :
Software Specification :
Software : Struts. JDBC. My SQL Windows N T / 98/ 2000/XP/7 64MB to 256MB.
System Analysis:
The HRMS application is based on relational database technology and web architecture. The application stores information in tables. In this we will discuss the way HRMS utilizes these tables to enable efficient storage and retrieval of data. We will discuss the impact of Effective Dates and Actions, as they relate to the business information you maintain using the HRMS application.
Objectives
By the end of this module, you will be able to: Illustrate effective dating within HRMS. Describe the four Actions and their purpose when accessing a page.
EXISTING SYSTEM :
The HR Administration falls short of controlling the employees activities in analyzing his/her strengths and weakness. The decision for appraisal of assigning next project to the employee or to train him/her to enhance the skills where lies with proper projection. He is not provided with the detailed project information done or to be assigned based on Application / Verticals.
DRAWBACKS IN EXISTINGSYSTEM:
Need of extra manual effort. It used to take much time to find any employee.
PROPOSED SYSTEM:
Decision in assigning proper skillful hands for the project is an important issue in HR Module. The HR Administrator should report with the personal holding the necessary skills required for the project assignment. The decision in making analysis about the employees skills is a prime important before booting in. The proposed system of HR Module is the right software to be incorporated into the Automation of HR Software for helping the organization needs with respect to skilful Human Resource. The proposed system provides detail general information about the employee along with Educational, Certification, Skill and Project details. It enhances the HR Management in adding, viewing and updating employees details and generates various reports regarding employees skill and experience. Suggestions and Grievances posted by the employees are upheld for taking care of the necessary steps in forwarding companys obligation.
Very fast and accurate. No need of any extra manual effort. No fever of data loss. Just need a little knowledge to operate the system. Doesnt require any extra hardware device.
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 process. The objective is to determine whether or not the proposed system is feasible. The three tests of feasibility have been carried out.
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 proposed system using java technology. It is evident that the necessary hardware and software are available for development and implementation of the proposed system. Hence, the solution is technically feasible.
ECONOMICAL FEASIBILITY :
As part of this, the costs and benefits associated With the proposed system compared and the project is economically feasible only if tangible or intangible benefits outweigh
OPERATION FEASIBILITY :
It is a standard that ensures interoperability Without stifling competition and innovation among users, to the benefit of the public both in terms of cost and service quality. The proposed system is acceptable to users. So the proposed system is operationally feasible.
PROJECT PLANNING
The material covered so far has addressed the concepts, tools, and technology for building systems. Developing a system requires planning and coordinating resources within a given time. More important, effective project management is needed to organize the available resources, schedule the events, and establish standards. A project manager is expected to have managerial and technical skills along with management support for system success. The process of planning, designing, and implementing computer system is called a project. A project manager who uses available resources to produce systems for the organization directs it. In large firms, installing a system may take years and involve hundreds of people. Planning and installing smaller projects on schedule also take time to and require control and coordination of resources. It takes an effective manager to organize the available resources, schedule the events, and establish standards. A project manager is expected to have managerial and technical skills along with management support for system success.
Time Scheduling:
Gantt chart:
The following chart shows our typical plan of the time scheduling in the form of Gantt chart. A Gantt chart is a horizontal bar chart developed as a production control tool in 1917 by Henry L. Gantt, an American engineer and social scientist.
Week
Activity 0 2 4 6 8 10 12 14 16 18 20
PERT Chart: Gantt chart has one drawback: They do not show precedence relationships among the
tasks and the milestones of a project. PERT charts have overcome this. The following chart shows our typical plan of the time scheduling in the form of PERT chart.
Task ID:
1 7 2
21 28
5 49
7 14 6
21
Precedence relationships:
Part of the process of building a project schedule involves breaking down the work into smaller activities (the Work Breakdown Structure) and then sequencing the activities. When you sequence the activities you should make sure that every activity is related to at least one other activity. In many cases, the relationships will involve two or more activities.
There are a couple of ways to represent these relationships. Perhaps the most common technique is called Precedence Diagramming Method (PDM). (This technique is sometimes called Activity on Node (AON).) In the PDM technique, the activities themselves are placed in boxes and the boxes are connected with arrows that show the precedence relationship.
The most common precedence relationship is when one activity cannot start until another activity has finished. In most schedules this is the relationship that exists in almost all (if not all) cases. This is referred to as a Finish-to-Start relationship. However, there are three
First, let's assume we have two activities--"A" and "B". It does not matter what the exact activities are. It only matters that there is a relationship between them. There are four possible relationships.
Finish-to-Start :
This means that Activity B cannot start until Activity A has completed. This is by far the most common relationship between multiple activities. In most schedules, all relationships will be finish-to-start.
Example:
Activity A is "Create the Project Charter." Activity B is "Obtain Project Charter approval from the Project Sponsor." This finish-to-start relationship would say that we must create the Project Charter before we obtain Project Charter approval from the Project Sponsor.
Start-to-Finish:
Start-to-finish means that Activity A must start before Activity B can finish. This is a very rare relationship.
Example: Let's assume that you want to fertilize your garden, but the plants must all be wet when the fertilizer is applied.
Start-to-Start:
This means Activity A must start before Activity B can start.
Example: Assume that you are having your walls painted in one room and wallpaper is being hung in another room. You want to minimize the total disruption and so you want to make sure both activities happen at the same time.
Activity A is "Paint the walls." Activity B is "Hang the wallpaper." The wallpaper hangers may be ready to go (activity B). However, the start-to-start relationship says that they cannot start until the painting starts (activity A). This relationship is based on the activity start times. The end times of each activity are not related and, in fact, one activity could end at a much later time than the other.
Finish-to-Finish:
This means Activity A must finish before Activity B can finish.
Example: Assume you're cooking dinner and you want the turkey to finish cooking before the potatoes.
Database Design:
Database design is the process of developing database structures to hold data to cater to user requirements. The final design must satisfy user needs in terms of completeness, integrity, performance and other factors. For a large enterprise, the database design will turn out to be an extremely complex task leaving a lot to the skill and experience of the designer. A number of tools and techniques, including computer-assisted techniques, are available to facilitate database design. The primary input to the database design process is the organizations statement of requirements. Poor definition of these requirements is a major cause of poor database design, resulting in databases of limited scope and utilities which are unable to adopt to changes. The major step in database design is to identify the entities and relationships that reflect the organizations data, naturally. The objective of this step is to specify conceptual structure of the data and is often referred to as data modeling. There are several methodologies to model the data logically. We adopted ER modeling as our data modeling technique. ER model is technique for analysis and logical
Entity:
Entity is a distinguishable object. These entities are classified into regular entities and weak entities. A weak entity is an entity that is existence dependent on some other entity i.e. it does not exist if that other entity does not exist. A regular entity is that it is not weak. The graphical notation of entity is shown below.
Regular Entity
Weak Entity
Attribute:
Entities have properties known as attributes. All entities of a given type have certain kinds of properties in common. Each kind of property draws its value from a corresponding value set. Properties can be of various types: Simple or composite, key, single or multi, missing, and base or derived. Attributes are graphically represented as shown below.
Attribute
Relation:
Relationship defines an association among entities. The entities involved in a given relationship are said to be participants in tat relationship. The number of participants in a given relationship is called the degree of that relationship. An ER relationship can be one one, one many, and many - many. Cardinality of a relationship refers to representing the number of occurrences of entities in a given relationship. The graphical notation of relation is represented as shown below.
Relationshi p
In our project we have identified entities, attributes for those entities, and relationships between those entities from data collected at analysis phase. These are listed below:
Entities:
Registration Registration Status Registration Experience Employee Department. Department Details Employee Leave Details. Employee Utilities.
Attributes:
Entity
Registration
Attributes REGISTRATION_ID,FIRSTNAME ,LASTNAME,DOB, AGE, SEX, CONTACT NUMBER, ALTERNATIVE NUMBER , EMAIL_ID, ADDRESS, SCHOOL_DETAILS,INTERMEDIATE_DETAILS,GRADUATION_ DETAILS, POSTGRADUATION_DETAILS, DEPARTMENT, REGISTRATIONSTATUS , TYPEOFREGISTRATION, SOFTSKILLS, TECHNICALSKILLS, REGISTERED DATE,APPROVEDDATE,ACTIVATIONDATE. EMPLOYEE_ID,DEPARTMENT_ID,FIRSTNAME,LASTNAME,DO CUMENTS_SUBMITTED,OFFERLETTER_CREATED,OPPOINTM ENT_CREATED,EMPLOYEE_ID_CREATED,ACCESSCARD_ISS USED. REGISTRATION_ID,ORGANIZATIONNAME,TOTAL_EXPERIEN CE (In Months) ,DESIGNATION, REFFERAL_NAME, REFFERAL_NUMBER,REFFERAL _DESIGNATION. EMPLOYEE_ID,FIRSTNAME,LASTNAME,DOB,AGE,CONTACT NUMBER,ALTERNATIVENUMBER,EMAIL_ID,ADDERSS, SCHOOL_DETAILS,INTERMEDATE_DETAILS, GRADUTION_DETAILS,POSTGRADUTION_DETAILS,SKILLS,S EX,LANGUAGEKNOWN,PASSWORD,STATUS,DATEOFJOININ G.
Registration Status
Registration Experience
Employee
DEPARTMENT_ID,DEPARTMENTNAME,LOCATION,DOMAIN. EMPLOYEE_ID,DESIGNATION,SALARY,ROLE,DESCRIPTION, DEPARTMENT_ID,IDCARD_NO,GRADE,TEAMLEADER,MANAG ER,ANNUAL_LEAVES. LEAVE_ID,EMPLOYEE_ID,EMPLOYEENAME,SUBJECT, LEAVE_FROMDATE,LEAVE_TODATE, DESCRIPTION, LEAVESTATUS,LEAVEREQUESTEDDATE,LEAVEAPPROVEDDA TE,TL_LEAVEAPPROVEDDATE,HR_LEAVEACTIVEDATE. EMPLOYEE_ID,FIRSTNAME,LASTNAME,EMPLOYEE_DESK, PERIPHERLS,DESCRIPTION,IPADDRESS,ASSESSCARDNO, DATEOFJOINING,
Employee Utilities
Data Dictionary:
A data dictionary is a catalogue a repository of the elements in a system. As the name suggests, these elements center around data the way they are structured to meet user requirements and organization needs. In a data dictionary you will find a list of all the elements composing the data flow through a system.
REGISTRATION:
Name REGISTRATION_ID FIRSTNAME LASTNAME DOB AGE SEX CONTACTNUMBER ALTERNATIVE NUMBER EMAIL_ID ADDRESS SCHOOL_DETAILS INTERMEDIATE_DET AILS GRADUTION_DETAIL S POSTGRADUATION_ DETAILS DEPARTMENT REGISTRATIONSTAT US TYPEOFREGISTRATI Type Varchar(20) Varchar (45) Varchar (45) Varchar (32) INT(6) Varchar(20) Varchar(12) Varchar(12) Varchar(50) Varchar(150) Varchar(150) Varchar(150) Varchar(150) Varchar(150) Varchar(32) Varchar(32) Varchar(32) Not null Not null Not null Constraints Primary key Not null Not null Not null Not null Not null Not null Description REGISTRATION_ID FIRSTNAME LASTNAME DOB AGE SEX MALE/FEMALE CONTACTNUMBER ALTERNATIVE NUMBER EMAIL_ID ADDRESS SCHOOL_DETAILS INTERMEDIATE_DET AILS GRADUTION_DETAIL S POSTGRADUATION_ DETAILS DEPARTMENT REGISTRATIONSTAT US TYPEOFREGISTRATI
REGISTRATION_STATUS:
Name EMPLOYEE_ID DEPARTMENT_ID FIRSTNAME LASTNAME DOCUMENTS_SUBMITTED OFFERLETTER_CREATED OPPOINTMENT_CREATED EMPLOYEE_ID_CREATED ACCESSCARD_ISSUSED Type Varchar(20) INT(11) Varchar (45) Varchar (45) Varchar (45) Varchar (45) Varchar (45) Varchar (45) Varchar (45) Constraints Primary key NOTNULL Not null Not null Description EMPLOYEE_ID DEPARTMENT_ID FIRSTNAME LASTNAME DOCUMENTS_SUBMITTED OFFERLETTER_CREATED OPPOINTMENT_CREATED EMPLOYEE_ID_CREATED ACCESSCARD_ISSUSED
REGISTRATION_EXPERIENCE:
Name REGISTRATION_ID ORGANIZATIONNAME TOTAL_EXPERIENCE (In Type Varchar(20) Varchar(45) Varchar (45) Constraints Not null Not null Not null Description EMPLOYEE_ID ORGANIZATIONNAME TOTAL_EXPERIENCE (In
EMPLOYEE:
Name EMPLOYEE_ID FIRSTNAME LASTNAME DOB AGE SEX CONTACTNUMBER ALTERNATIVE NUMBER EMAIL_ID ADDRESS SCHOOL_DETAILS INTERMEDIATE_DET AILS GRADUTION_DETAIL S Type Varchar(20) Varchar (45) Varchar (45) Varchar (32) INT(6) Varchar(20) Varchar(12) Varchar(12) Varchar(50) Varchar(150) Varchar(150) Varchar(150) Varchar(150) Not null Constraints Primary key Not null Not null Not null Not null Not null Not null Description EMPLOYEE_ID FIRSTNAME LASTNAME DOB AGE SEX MALE/FEMALE CONTACTNUMBER ALTERNATIVE NUMBER EMAIL_ID ADDRESS SCHOOL_DETAILS INTERMEDIATE_DET AILS GRADUTION_DETAIL S
SKILLS LANGUAGEKNOWN
PASSWORD STATUS
SKILLS LANGUAGEKNOWN
PASSWORD STATUS
DATEOFJOINING
DATEOFJOINING
ER Diagram:
UML Diagrams:
Sequence Diagram:
Collaboration Diagram:
FEATURE ENHANCEMENTS:
Bibliography
SOFTWARES HTML: HTML In a Nut Shell Using HTML 4.0 Java: Java In a Nut Shell Using Java 2 Platform The Complete Reference Java 1.2 Core Java Introduction To Java Servlets Java Servlet Programming Java Database Programming System Development: Fundamentals Of System Concepts System Analysis And Design Software Engineering: Uml References: Learning Uml
REFERENCES ORielly Joseph Weber ORielly Joseph Weber Herbert Schildt Kenneth Paul James Good Will ORielly Matthew Siple Jerry Fitz Gerald Elias M. Awad Roger P Pressman ORielly