RECRUITMENT SYSTEM

1. OBJECTIVE:
 The objective of the Recruitment system is to increase the number of
applicant to apply in the organization.
 If the entire process of ‘Recruitment' is done in a manual manner then it
would takes several days for the recruitment.
 To attract and engage people it needs to achieve its overall organizational
objectives.
 It determines the current and future requirements of the organization in
conjunction with its personnel planning and job analysis activities.
2. SCOPE:
 The System provides an online interface to the user where they can fill in
their personal details and apply for the job.
 The Organization (HR-Department) concerned with the recruitment
process can make use of this system to reduce their workload and process
the application in a speedy manner.
 Provide a communication platform between the Applicant and the
Organization.
3. PROJECT DESCRIPTION:
Problem statement:
The recruitment system allows the job seekers to view the job
opportunity through Advertisement and helps to apply for the job. The
organization shortlist the applicants for the interview. The shortlisted
applicants undergo through a process of Test and Interview. The HR
department selects the Applicant based on the performance in the Test and
Interview. Finally the recruited applicants are informed. This system makes
the task of the job seeker easier rather than waiting in queue for enrollment.
This also reduces the time consumption for both for the job seeker and
organization.
4. REQUIREMENT:
4.1. Functional requirement:
4.1.1. Analysis:

 The job analysis is a formal system develop to determine what tasks

people actually perform in their jobs.
 The purpose of a job analysis is to ensure creation of the right fit
between the job and the employee and to determine how employee
performance will be assessed.
 It source the candidate with the abilities and attitude, which are
required for achieving the objectives of an organization.
 Recruitment process is a process of identifying the jobs vacancy,
analyzing the job requirements, reviewing applications, screening,
shortlisting and selecting the right candidate.

4.1.2. Design:

 A recruitment system is a software application that employers use to

effectively manage their recruitment processes and candidate flow.
 It allows you to create and store a database of candidates, manage
and publish vacancies, process applications, invite and reject
applicants, and more.

4.1.3. Implementation:

 This automated personnel recruitment system (APRS) has been

designed to be user friendly and easy to navigate.
 If the viewer needs to communicate with the website, all has to do is
to click on any of the link and he can communicate with the site.
 The module has been packaged and installed on the testing server.
The various are integrated together through as single website
interface.

4.2. HARDWARE REQUIREMENT:

Processor: Pentium III

Hard disk drive: 40 GB
RAM: 128 MB
 Cache: 512 KB.

4.3 . SOFTWARE REQUIREMENT:

 Any window based operating system with DOS support are

primary requirement for software development. Window XP,
FrontPage and dumps are required. The system must be connected
via LAN and connection to internet is mandatory.

4.4. Merits:
 Provides convenience.
 Easily understandable.
 User friendliness.
4.5. Demerits:
 Need computer knowledge.
 It is complex for large scale products.
5. OVERALL DESCRIPTION:
5.1. PRODUCT PERSPECTIVE:
It enables us to maintain the railway train details like their timings,
number of seat available and reservation billing and cancelling the tickets.
5.2 SOFTWARE INTERFACE:
Any window based operating system with DOS support are primary
requirement for software development. Window XP, FrontPage and dumps
are required. The system must be connected via LAN and connection to
internet is mandatory.
5.3 HARDWARE INTERFACE :
Printer
Normal PC SOFTWARE INTERFACE:
Front end -> Visual Basic
Back end -> MS-Access
 5.4. USER INTERFACE:
Keyboard and Mouse.
5.5 CONSTRAINTS:
 The recruiting efforts are the hindrances faced during the
recruitment process.
 The qualification for the job is more important and they should be
unique from others.
 An enterprise may not be able to recruit the persons freely even
though it offers better salaries and other amenities.
6. DOMAIN MODEL:
A domain is a visual representation of conceptual classes or real
situation object in a domain.
 In object-oriented analysis, the domain model is the most
important.
 It illustrates the concept in the domain.
 It acts as a source of inspiration for designing some software
objects.

In our project, when we are enter into the webpage we can check the
customer details such as his personal details and also work related details.
7. LOGICAL ARCHITECTURE :
The logical architecture is the large-scale organization of software
classes into packages, sub classes and layers. This is called logical
architecture.
8. RISK ARCHITECTURE:
It defines that some process loss, or any problem can be faced while
creating the project.
8.1 SOFTWARE RISK:
If the software is affected by virus it may cause problems or too
many users logging at same time can cause a lag. It can be rectified by
many ways.
 8.2 HARDWARE RISK:
If the hardware component is suddenly burn or broke down due to
over burden, while creating the project.
8.3 NON-FUNCTION RISK:
Due to failure of Hardware and software, then it can’t be completed
within the time schedule and budget schedule.
9. GANTT CHART:
It describes the time schedule for the plan to complete the core
product what is the time taken for the project action of core project.
10. OVERALL DESCRIPTION :
10.1. Product perspective:
The RS acts as an interface between the ''Applicant and the
'Organization'. This system tries to make the interface as simple as possible
and at the same time not risking the security of data stored in. This
minimizes the time duration for recruitment process.
10.2. System Interface:
Front End Client –The Applicants and Organization online interface is
built using JSP and HTML. The Administrators’ local interface is built
using Java. • Web Server - Glassfish application server (SQL Corporation). •
Back End - SQL database.
10.3. Hardware interface:
The server is directly connected to the client systems. The client
systems have access to the database in the server.
10.4. System Interface:
 The applicant views the jobs through Advertisement.
 Applicants apply for the job.
 Test and Interview are conducted.
 Recruited Applicants are informed.
 HR Manager can generate reports from the information and he/she is
the only authorized personnel to add the eligible application information to
the database.
Applicant these are the persons who desire to apply for the job.
Organization these are the person with certain privileges to announce
recruitment depending upon the organization need. He/ She may contain a
group of persons under him/her to publish advertisement and give
suggestion whether or not to approve the recruitment. HR He/ She is the
person who upon receiving intimation from the RS, perform a personal
verification of the applicants and see if he/she has eligibility for the
advertised job through a process of Test and Interview.

10.5. Constraints:
The Applicants require a computer to submit their information.

11. PRE-FUNCTION AND POST-FUNCTION:

Login:
Pre-function: Posting a job wiling form to the company and
enclosing the qualification.
Post-function: Resume and their experience.
Work Details:
Pre-function: Receiving a call letter and getting ready for an
interview.
Post-function: Facing to the interview room.
Payroll Calculation:
Pre-function: perfectly answering to the questions.
Post-function: Discussing the salary packages and the working
details.
Assumption and Depended
  The Applicants and HR must have basic knowledge of computers and
English Language.

12. TECHINCAL SERVICE LAYER:

This shows the interaction between the actor and object in sequence
diagram.
13. DOMAIN MODEL LAYER:
After composing the technical service layer from partial layer
architecture. Since we are going to generate the coding in java/VB the
project domain is experienced in java/VB using rational rose
14. USER INTERFACE LAYER:
This layer shows the interface with sequence diagram by changing
the sequence symbol. The sequence symbol is replaced by an actor symbol,
which shows interface between use case and
15. UML PACKAGE DIAGRAM :
 An UML package diagram provides a way to group elements.
 A UML package can group anything.

15.1 UML DAIGRAM:

1. use case diagram
2. class diagram
3. sequence diagram
4. collaboration diagram
5. state chart diagram
6. activity diagram
7. component diagram
8. deployment diagram

15.1.1 Use case diagram:

 A use case diagram in the Unified Modeling Language (UML) is a
type of behavioral diagram defined by and created from a Use-case
analysis. Its purpose is to present a graphical overview of the functionality
provided by a system in terms of actors, their goals, and any dependencies
between those use cases. The main purpose of a use case diagram is to
show what system function are performed for which actor. Alternatively,
interaction among actors can be part of the assumptions used in the use
case.
Actors:
 An actor is a person, organization, or external system that plays a role in
one or more interactions with the system
 The representation of the actor is

The Recruitment system use cases are:

1. Advertisement
2. Apply for job
3. Test
4. Interview
5. Recruit
Applicants ACTORS INVOLVED: Actors are as follows:
1. Applicant
2. Organization
3. HR
Actors Documentation:
 Applicant is an actor who applies for the job vacancy. If he/she gets
selected then HR department sends the Interview call letter.
  HR is an actor who informs about the vacancy to their Organization.
HR recruits the applicants based on the required skill for the vacant
position and shortlist them. HR is also responsible for Interview
Scheduling.
 Organization is an actor who announces the Advertisement for
vacancy.
Use case:
Select applicant for reviews:
Description: This Use Case is initiated by HR. The lists of selected
Applicants are Informed .The Test and Interviews are conducted by the HR
of the region that has the vacancy. Flow of Events:
1. HR schedules the interview process.
2. HR conducts test and interview for the applicant via online system.
3. Who clear the interview process are selected.
Pre-Condition: Applicants must meet eligibility criteria. Post-Condition:
Applicants clears interview process OR doesn’t clear interview process.

Use case: test.

Description: This Use Case is initiated by the HR. A test will be conducted
by the HR Flow of Events 1. The applicants undergo the Test process. 2.
He/ She clear or not clear the Test. Pre-Condition: Applicant is selected for
the Test. Post-Condition: Applicant clear or not clear the Test.

Use case: Interview

Description: This Use Case is initiated by the HR. An Interview will be
conducted by the HR Flow of Events
1. The applicants undergo the Interview process.
2. He/ She clear or not clear the Interview.
Pre-Condition: Applicant is selected for the Interview. Post-Condition:
Applicant clear or not clear the Interview. USE CASE: RECRUITED
APPLICANTS
Description: This Use Case is initiated by the HR. The selected applicants
are recruited by HR. Flow of Events
1. The applicants clear the Test.
2. The applicants clear the Interview.
Pre-Condition: Applicant is selected for the Test and Interview. Post-
Condition: Applicant clears Test and Interview.
USE CASE: Recruitment applicant.
Description: This Use Case is initiated by the HR. The selected applicants
are recruited by HR. Flow of Events
1. The applicants clear the Test.
2. The applicants clear the Interview.
Pre-Condition: Applicant is selected for the Test and Interview.
Post-Condition: Applicant clears Test and Interview.
15.1.2. ACTIVITY DIAGRAM:
The activity diagram represents the series of activities that are
occurring between the objects. Following is activity diagram which
represents the recruitment process. An activity diagram is a variation or
special case of a state machine in which the states or activity representing
the performance of operation and transitions are triggered by the
completion of operation. The purpose is to provide view of close and what
is going on inside a use case or among several classes. An activity is shown
as rounded box containing the name of operation.

15.1.3. CLASS DIAGRAM:

The UML class diagram illustrates class interfaces and their actions.
They are used for static object modeling. The problem domain describes the
structure and the relationships among objects.
The Recruitment system class diagram consists of five classes
1. Applicant class
2. Organization class
3. HR Department class
4. Advertisement class
5. Recruitment class
1) APPLICANT CLASS:
It consists of eight attributes and two operations. The attributes are
Applicant-id, Applicant -name, Applicant -DOB, Applicant -Gender,
Applicant -Qualification, Applicant-phone, Applicant –email id, Applicant
addr. The operation of this class are view jobs ( ) and Apply ( ).
2) ORGANIZATION CLASS:
The attributes of this class are Org-name, Org-Ph-No, and Org-Addr.
The operation of this class are HR-Dept( ), Mkt-Dept( ) and Account-Dept(
).
3) HR DEPARTMENT CLASS:
The attributes of this class are Emp-id, Emp-name, Emp-DOB, Emp-
Gender, Emp-Phone, Empemailid, Emp-addr. The operation are Planning( ),
Policies( ),Strategies( )
4) ADVERTISEMENT CLASS:
The attributes of this class are Adv-No, Adv-Name and Adv-description.
The operation is display ( ).
5) RECRUITMENT CLASS:
The attributes are Rec-Designation and Rec-Total candidate. The
operation is recruit ( ).
CLASS DIAGRAM:
15.1.4. INTERACTION DIAGRAM:
A sequence diagram illustrates a kind of format in which each object
interacts via message. It is generalize between two or more specialized
diagram.
Applicant: Applicant
Advertisement Organization
Recruitment Committee: HR Recruitment Committee: HR
Applicant advertisement
Organisations recruitment committee HR
1: view jobs
2: apply for jobs
3: forward applicants
4: Analyses applicant resume
5: send interview call letter/email
7: applicant passed test & interview informed 8: salary fixed/received
6: attend interviews.
15.1.5. STATE CHART DIAGRAM:
Every object undergoes through some state and on receiving some
event the state gets changed. This transition of the state can be represented
by the state transition diagram.

State chart diagram:

15.1.6. DEPLOYMENT DIAGRAM:
Deployment diagrams are used to visualize the topology of the
physical components of a system where the software components are
deployed. It is a graph of nodes connected by communication association.
It is represented by a three dimensional box. A deployment diagram in the
unified modeling language serves to model the physical deployment of
artifacts on deployment targets. Deployment diagrams show "the allocation
of artifacts to nodes according to the Deployments defined between them.
It is represented by 3-dimentional box. Dependencies are represented by
communication association. The basic element of a deployment diagram is
a node of two
Deployment Diagram:
15.1.6. COMPONENT DIAGRAM:
The component diagram is represented by figure dependency and it
is a graph of design of figure dependency. The component diagram's main
purpose is to show the structural relationships between the components of a
systems. It is represented by boxed figure. Dependencies are represented
by communication association. Component diagrams are used to visualize
the organization and relationships among components in a system.
Component diagram:

16. Device node:

A physical computing resource with processing and memory service
to execute software, such as a typical computer or a mobile phone.
17. Execution Environment Node:
This is a software computing resource that runs within an outer node
and which itself provides a service to host execute other executable
software element.
18. Implementation:
After completing the 8 diagrams we have to select the respective
programming language domain from the tool menu for each diagram we
have to select main class and generate code for
19. Testing:
After completing the code generation for each diagram. Select the
tool menu under quality architect performs unit testing and scenario testing
for each code. Testing activities are made several types of testing is carried
on.
20. Conclusion:
Thus, the above project for Recruitment system has been successfully
executed and codes are generated.

---------The End----------