MBA Notes Personnel Management or Human Resource Management
sap hr
Full description
sap hr
reviewer
sap hr
Guidance Personnel
La formation du personnel est un investissement. Elle permet aux entreprises d'accroître les compétences et la productivité de leur main-d’œuvre tout en augmentant la qualité de leurs produi…Description complète
comment evaluer le personnel pour etablir un plan de formation
Wonderlic Personnel TestDeskripsi lengkap
SAP HCM
ssssssssssssssxxxxxxxxxxxxxxxx
personal test for merchandiser
Description complète
Description complète
personal test for merchandiserDeskripsi lengkap
Audit Interne - Paiement du personnelDescription complète
Message Personnel (Michel Berger)
Ce document a été uploadé via Beebac, le réseau social gratuit de partage de savoirs scolaires et professionnels. Beebac apporte un service ouvert et personnalisé pour tous ceux qui souhaitent appr...Full description
Description complète
7. EMPLOYEE MANAGEMENT SYSTEM AIM
To develop a project employee management system using the Rational Rose Software from the UML diagram and to implement the software in Visual Visual Basic. PROJECT ANALYSIS AND PROJECT PLANNING The employee management system is used to manage our personnel things such as maintaining dataases in offices etc. this project is easy for the !"# to handle the details. This is personally used for !"#. PROBLEM STATEMENT The !"# must enter the name and password to login the form and select the particular employee to view the details aout that employee and maintaining the employee details personally. This process of employee management system are descried se$uentially through following steps%
& The !"# login to the employee management system. & 'e(she search for the list of employees. & Then select the particular employee. & Then view the details of that employee. & )fter displaying the employee details then logout. SOFT REQUIREMENT SPECIFICATION: SPECIFICATION: 1. INTRODUCTION 2. OBJECTIVE 3. OVERVIEW 4. PURPOSE
The main purpose of creating the document aout the software is to *now aout the list of re$uirements that is to e developed. 5. SCOPE: +t specifies the re$uirements to develop a processing software part that complete the set of re$uirements. +n this specification% we define aout the system re$uirements that are apart from the functionality of system . FUNCTIONALITY: Many memers of the process live to chec* for the occurrence and transaction% we all have to carry over at sometime. 7. USABILITY
The User interface ma*es the employee Management System to e efficient. !. PERFORMANCE +t is the capaility aout which it can perform function for many users at the same time for the efficiency ,i.e.- without any error occurrences. ". RELIABILITY The system should e ale to the user through the day to day transactions. 1#. FUNCTIONAL REQUIREMENTS 11. E$TERNAL INTERFACE REQUIREMANTS SOFTWARE REQUIREMENTS • • •
T%%& '% () *+),: Rational rose F-%' ),: ava B/0 ),: MS )ccess
ARDWARE REQUIREMENTS • • • •
P-%0)++%- : pentium /. RAM : 25 m O)-/' +6/') : Microsoft windows 0p. F-)) ,+ +/0) : 1 g
12. UML DIAGRAMS: USE CASE DIAGRAM
The use cases are a set of scenarios to guide together y a common user goal. ) scenario is the se$uence of steps descriing an interaction etween a user and their system.
DOCUMENTATION OF USE CASE DIAGRAM The use case diagram in the employee management system illustrates the se$uence of se$uencing and descriing an interaction etween a !"# and a system. •
•
•
L%1 This use case gives as entry to the !"# and the dataase. L+' %8 )&%6)): This will create the situation for the !"# to select particular employee from the availale list. E&%6)) ,)'/&+: The !"# can ale to view the details of the employee using this use case.
ACTIVITY DIAGRAM The )ctivity diagram descries the se$uencing of activity will support for oth conditional and parallel. )n activity is a variant of state diagram.
DOCUMENTATION OF ACTIVITY DIAGRAM The !"# Logins to the employee management system. 'e(she selects a particular employee from the list of availale employee. The !"# can view the details of the particular employee y clic*ing the respective utton. )fter viewing the details he is logout from the system.
CLASS DIAGRAM
The !lass diagram the types of oject in the system a various *inds of static relation ships that e0ists among them.
DOCUMENTATION OF CLASS DIAGRAM The !lasses used in this project are CEO: The !"# has to login the form y specifying the name and password of him. • D/'/(/+): The dataase chec*s whether the !"# has given the name and password • accordingly if not the error message will e displayed. A9/&/(&) )&%6))+: The dataase is connects to the list of availale employees and the • !"# if wants then select the employee from it. SEQUENCE DIAGRAM: +t is a *ind of interaction diagram in which an oject is shown as a o0 at the top of the dash vertical line. This vertical line is called oject life time. The life time represent the oject2s life during interaction oject deletion is shown with a large 0.
DOCUMENTATION OF SEQUENCE DIAGRAM
The !"# must enter his name and password to login the employee management system. The verification process is undergone y the dataase .+f the details are correct he can enter to the system otherwise error is displayed. )fter login the details of the particular employee is viewed y the !"#. 3inally he is logged out from the system.
COLLABORATION DIAGRAM +n a collaoration diagram oject are shown as icons as on. ) collaoration diagram arrow indicates the message send within the given use case. The se$uence is indicated y numering the messages.
DOCUMENTATION OF COLLABORATION DIAGRAM
+t is same as the se$uence diagram that involves the oject of the project with the only differences that we give the se$uence no to the each process
The !"# must enter his name and password to login the employee management system. The verification process is undergone y the dataase .+f the details are correct he can enter to the system otherwise error is displayed. )fter login the detail of the particular employee is viewed y the !"#. 3inally he is logged out from the system. STATE CART DIAGRAM
+t is a techni$ue to descrie the ehavior of the system.+t determines all the possile states as that of particular oject gets into the oject oriented techni$ue.State diagrams are drawn for a single class so status to the lifetime ehavior of a single ojector.
DOCUMENTATION OF TE STATE CART DIAGRAM:
The various states are the login% lists of employees% selects a employee% display the information aout the employee% logout. The state chart diagram descries the ehavior of the system. The main purpose of the system is to maintain an employee details personally. 3or that the !"# Login to the employee management system. 'e(she selects a particular employee from the list of availale employee. The !"# has to view the details of the particular employee y clic*ing the respective utton. The !"# views the details then finally he is logout from the system. PACAGE DIAGRAM ) pac*age is represented as folder among shown as large rectangle with a ta attached its upper left corner. ) pac*age may contain oth suordinated pac*age oth ordinary model can e organi4ed into pac*ages. There are three types of layers%
a. User interface layer . 5omain layer c. Technical layer
DOCUMENTATION OF PACAGE DIAGRAM The three layers in the online recruitment system are T;) U+)- ')-8/0) &/6)- 6 consists of the we and login. This layer descries how the applicant logins to the wesite and apply for the jo. T;) D%/ &/6)- 7 shows the activities that are performed in the online recruitment system. The activities are register% attend test and select talented applicant. T;) T)0;0/& +)-90) &/6)- < the applicant details% verification details and the selected applicant details are stored in the dataase.
COMPONENT DIAGRAM !omponents are a slightly fu44y concept in the UML% ecause oth classes and components can e used to model the same thing. ) component represents a modular part of a system that encapsulates its contents and whose manifestation is replaceale within its environment. ) component defines its ehavior in terms of provided and re$uired interfaces. )s such% a component serves as a type% whose conformance is defined y these provided and re$uired interfaces.
DOCUMENTATION OF COMPONENT DIAGRAM
+n this diagram there lin* etween the actors is present in the S8MS that could e shown in diagrammatically way in the component diagram. "ach every actor is having a directional lin* to process further details present in the system. DEPLOYMENT DIAGRAM ) deployment diagram shows the assignment of concrete software artifacts ,such as e0ecutale files- to computational nodes ,something with processing services-. +t shows the deployment of software elements to the physical architecture and the communication ,usually on a networ* etween physical elements. ) deployment diagram usually shows an e0ample set of instances ,rather than classes
RESULT Thus the project to develop an "mployee Management System using the Rational Rose Software and to implement the system using ava is done successfully.
