Professional Documents
Culture Documents
A Human Resource Management System (HRMS) or Human Resource Information System (HRIS), refers to the systems and processes at the intersection between human resource management (HRM) and information technology. It merges HRM as a discipline and in particular its basic HR activities and processes with the information technology field, whereas the programming of data processing systems evolved into standardized routines and packages of enterprise resource planning (ERP) software. On the whole, these ERP systems have their origin on software that integrates information from different applications into one universal database. The linkage of its financial and human resource modules through one database is the most important distinction to the individually and proprietary developed predecessors, which makes this software application both rigid and flexible.
Chapter 1 Introduction
Chapter 1 : Introduction
The first view of human resources management, it was a routine active interested in recording, classifying and saving data related to workers. Those data that will enable them to execute manager responsibilities in running rules and laws of system and billboards that will organize labor usage and .employment, salaries and wages paymentetc However the modern view for Human Resource Management (HRM) was reforming where its one of the main departments in an organization, which will cooperate in gaining the production efficiency, .plus gaining the main purposes of the organization In real life if you want to view or get some services from any organization you must go to that organization and search through documents to find results and make them manually, this has a big chance to get loss or .harmed and you may lose your effort and time Our system aims to make this operation in computerized form, to insure working in precise and get .employees satisfaction We claim this system from scratch and we claim that we included all functionalities to make the .system applicable and easy to use even for non-technical staff We start doing our project step by step involving all the phases in system development life cycle, .starting with identification and selection, initiation and planning, analysis, design, and implementation
1.1.
The manual work in human resource department in any organization may produce errors, loss of documents, difficult to determine the wrong and need more time .
Objectives: 1. Minimize data-entry errors 2. Provide accurate information. 3. Cost reduction. 4. Increase the flexibility. 5. Increase the speed of performing activities. 6. Improvement of management planning and controls.
Phases of work :
The following tasks and deliverables reflect the current understanding of the project:
Analysis :
1. Determining system requirement. 2. Structuring system requirements (process modeling, logic modeling, Conceptual Data modeling).
Design :
1. 2. 3. Designing Databases, forms and reports. Designing interfaces and Dialogs. Finalizing Design specifications.
Implementation :
System implementation (coding).
2.4.
Project scope :
This project will cover the organization and all corporations that contain department of human resource and maintain all operations that perform manually. The main purpose that we will achieve is to make operations performed easily and quickly, and to save resources. Actors are interacting and using this system:
Administrators: who are responsible to give username and password, and in our system have the -1 following responsibilities: login to the system, create accounts, change passwords, send messages, .modify databases and get reports .Employee: A person, who uses the system and views some documents -2 Receive reports and fill important data, and in our system have the following responsibilities: log in to .the system, modify documents, view states, change passwords, send messages and get reports Data entry: who is responsible for making some operations and process documents on computers -3 .and complete his work and send the report to system Administrator And in our system, he has the following responsibilities: log in to the system, modify documents, .create documents, change passwords, view document states, send messages and get reports .And for each of them there is a log in screen to allow interacting with the system
10
:Our team examined some feasibility areas; these areas are as the following :Tangible benefits
Error reduction , increase speed of activity and interactions , improve management planning and control and save resource.
:Intangible benefits
Availability of new , better or more information , improve planning , increase productivity and efficiency and increase flexibility in doing the jobs , since the process of retrieving documents and updating them will be faster. :Cost Organization cost including Cost for buying software, training employees and pcs and network and .for developer cost maintaining and updating software and adding additional tool
staff may change at any time situation of canceling a predefined requirement or the need for stating a new requirement is possible.
11
Risk Requirements change: There will be a large number of changes to the requirements than anticipated. Inconsistent or incomplete requirements. Time out: The expected time may not be enough to perform each task. Different parts may not integrate and software installation may not succeed. Not enough experience in working projects and poor skills in programming and little knowledge of database concepts and development software. Database Creation or retrieving in an inefficient way
Risk Type
Probability
Effects
Strategy
Reviewing Requirements High Serious requirements and update them as they change.
Requirements
Estimation
High
Serious
Tools
Moderate
Serious
Learn more about Technology Moderate tolerable database concepts and efficient data retrieval. Types of Risk
12
2.7.
Project organization :
HRMS
Services
13
14
Requirement:3.3 .
:User requirement 3.3.1
:Functional requirements
.The system shall have employee who has account created by administrator .1 .The system shall have manager who has special account with additional privileges .2 .The system shall have administrators with their account who have priority to control the system .3 The administrators of the system shall be the only ones who are responsible for adding, .4 .modifying, or deleting employees accounts The administrator shall be able to add news, events, changes depends on manager .5 .recommendation .The employee shall be able to access the system via LAN network only .6 .The data entry shall be only responsible of receiving information to create the document .7 .(The system shall allow the employee to change his profiles (Like change the account password .8 15
: Non-Functional requirements
1Security issue : the system must be secured that forbid unauthorized people or staff cant gain access to the system . Every subsystem shouldnt allow staff from other subsystem to modify its data . 2- User friendly: the system must be simple and clear for the users to help them do what they want. 3- Effectiveness: we must keep a backup for all the information in the server . 4- The quick access and Provision of the required services. 5- Reliability: The application must validate user entries in order to ensure that no errors are encountered. If a certain error shows up, the error must be displayed in a well structured way in order to allow the users to easily understand it. 6- Evolution: The application must be designed and constructed in a way which makes it open to expansion.
16
17
Data entry
Employee
:Level 0
Adminstrato r
0.1 Log in
Human resource
0.1
0.1 Log in 18
Employee
Log in
Data Entry
: Level 1
19
Level 2 :
Employee Database
Data Entry
0.3.6 0.3.0 Display page Crating new document
D1
System Database
D2
Employee Database
20
:Level 3
0.4.4 Send message 0.4.1 Modify document 0.4.2 Get report 0.4.3 View state
D2
Employee Database
21
Employee:
.Login to the system.Modify document.View status.Change password.Send message.Get report-
Data entry
.Login to the system.Modify document.Get report.Change password.View document status.Send message.Create event-
22
4.2.
System Models :
user password
log in
end user
23
lo g in
s y s te m a d m i n i s tr s to r
24
lo g in
< < i n c l u d< e< >i n> c l u d e > > < < in c lu d e > >
m o d i fy d o c u m e n t c h a n g e p a s s v i eo w d s t s t u s w r g e t r e p o r ts e n d m e s s a g e
e m p lo y e e
25
26
log in
Create event
Data Entry
27
log in
<<include>>
processing document
employee
adminstrstor
end user
28
Figure (4.5): shows Use case for modifying document for all actors
29
system administrator
user database
broadcasting event
system employee
2.login
3.username&pass
4.verfiying
5.success
6.viewing
7.display
11.success message
13.select event
14.broadcast
15.success message
Figure (4.6): shows Sequence diagram for some actions that are performed by system administrator
30
employee
viewing document
process document
document database
2.login
3.username&pass
4.verfiying
5.success
10.info request
11.info
12.process
13.info reques
14.success message
Figure (4.7): shows Sequence diagram for some actions that are performed by employee
31
enduser viewing.1
enduser page
processing
document database
login.2
username&pass.3
verfiying.4
success.5
viewing.6
display.7
modifying document. 8
requested document.9
view document.10
processing.11
update document.12
success message.13
Figure (4.8): shows Sequence diagram for some actions that are performed by data entry
4.3.
32
33
This Project is intended to convert all paper based companies to computer based ones , and do some jobs that are more accurate and more reliable by computers than hand job . There is a lot of modification can be done on this system like 1- Adding a hardware to register attendance of employees . 2- Connect this system to the internet and allow it to send emails to employees that alert them about their leaves and vacations . 3- Develop a web application and connect it with this system to allow all employees to explore their salaries , leaves , attendance ,etc
34
References :
1- Gennick Jonathan, Oracle SQL Plus; The Definitive guide , OReilly , 2006 . 2- Kevin Loney, Bob Bryla , Oracle Database 10g Handbook , McGraw-Hill , 2005 . 3- Curtis HK Tsang , Clarence SW Lau , Ying K Leung , Object-Oriented Technology , McGrawHill , 2005. 4- Ian Sommerville , Software Engineering , Pearson, 2010 , Edition 9th . 5- Wikipedia , http://en.wikipedia.org/wiki/Wikipedia .
35