ONLINE PLACEMENT MANAGEMENT 0

N
0 SYSTEM L
N
I
L
N
I
E
N

E
P

L
P
A
L
C
A
E
C
M
E
E
M
N
E
T
N

T
M

A
M
N
A
A
N
G
A
E
G
M
E
E
M
N
E
T
N

T ONLINE PLACEMENT MANAGEMENT

SYSTEM
 ONLINE PLACEMENT
MANAGEMENT SYSTEM

UNDER THE GUIDENCE

MR.

SUBMITTED BY
 Abstract
Online placement management system is an online job portal
which brings makes the right recruiters and right Job-seeker
meet.

It gets the whole job done, very simply and without hassles.

Easy to use interface makes job much easier for the Job-
provider as well as the Job-Seeker.

A user wanting to use the facilities of Job portal has to first

register.

The registration process for Job-seeker is a step by step easy

method which also includes a unique “CV” upload process.

Student’s registration is a one step procedure.

 Introduction to Project
Online Placement portal is a web application. It provides candidates, ability to
register to this application and search for placement, and manage their accounts.
Each candidate will have an account with their own home page.

On the other hand employers those are willing to publish the job for their company to
candidates, can register to the placement portal and get their own account created
and can post jobs to the portal’s database.

Registered Employers can add or remove jobs and these jobs can be seen by
various candidates and they can contact the concern person for the jobs. Main of this
web application is to make a user friendly platform where, applicant can search jobs
easily and is accessible to everyone who is interested. The purpose of the
application is to provide Placement portal for Job Seekers, to submit their CV and
apply for the jobs, where Employer can select best Students from available
candidate profile.

Number of Modules:
Admin: The authorized person who controls the entire network.

Login: A Student, Company and Admin has to login to the site using his unique user
id and password.

Student: The person who applies for job.

Company: Creates vacancies.

Search Job: A Student can search for the jobs and then get the details for the
Company.

Search Resume: A Company can search for resume with prospective candidate and
then get the details for the candidate as well as download the CV of the candidate.

Generate CV: The sites provide the Job Seeker with preformatted CV which can be
downloaded.

Post Job: A Company can post a new job opening.

Delete Job: A Company should be able to delete the posted jobs.

Problem Statement
1. Login: A Student and Company login
after registration and Admin can login
to the site using his unique user id and
password for security.
2. Send Mail: A Student, Company and
Admin send mail to each other for
sharing their views for job and
answers to the job requirements or
candidate.
3. Register: A Student and Company
register themselves before Login as
they are register to the new account of
placement portal.
4. Post Job: A Company post new Job for
some duration and then delete the
post and again post next job for the
student.
5. Apply Job: A student applies for job
that is liked by them if not then it can
response cancel.
6. Report Generated: After all the details
student list are seen.
7. CV Generation: After search for a job we
need to generate CV.
8. Profile Match: After CV generated and
CV downloaded we find for a profile
match according to our resume.
9. Update/ Manage Account: Updating and
Manage of account is must to update time to
time for the information.
10. Search Job: Searching a Job by student
and uploading CV.
11. Manage Placement Account: Admin
manages for Placement account, any
changes made or job provided.
12. Search Resume: Search for a candidate
we should have a resume for that person
and downloading CV to match profile of
student.
13. View Update Profile: If profile match is
done we upload Profile.
14. View Delete Profile: If profile is not
matched we delete Profile.
 USE CASES
1. Login

1.1. Brief Description

This use case describes how a user logs into the online placement
management system.

1.2. Actors
The following actor interacts and participates in this use case Admin,
Student and Company.

1.3. Flow of events

1.3.1. Basic Flow
This use case starts when the actor wishes to login to the online
placement management system:
The system requests that the actor enter his name, password and role.
The role can be any of Student, Company or Admin.
The actor enters his/her name, password and role.
The system validates the entered name, password, and role and logs
the actor into the system.

1.3.2. Alternative Flow

Invalid user id/password: If in the basic flow, the actor enters user id,
password or role wrong, the system displays an error message. The
actor can choose to either return to the beginning of the basic flow or
cancel the login.

1.4. Special Requirements

None

1.5. Pre conditions

All users must have a user account created for them in the system,
prior to executing the use cases.

1.6. Post condition

If the use case was successful, the actor is logged in to the system. If
not, the system state is unchanged.

1.7. Extension Points

None
2. Registration:

2.1. Brief Description

This use case describes how to register into the
online placement management system.

2.2. Actors
The following actor interacts and participates in this
use case Student and Company.

2.3. Flow of events

2.3.1. Basic Flow

This use case starts when the actor wishes to

register the Online Placement management system:

The system requests that the actor register the role.

2.3.2. Alternative Flow

In this use case if registration is failed then we have

to again go back and register.

2.4. Special Requirements

None

2.5. Pre conditions

All users should register themselves before login.

2.6. Post condition

If the use case was successful, the actor registers in
the system. If not, the system state is unchanged.

2.7. Extension Points

None
3. Manage Job Response:

3.1. Brief Description

This use case describes how the Company response
the online placement management system.

3.2. Actor
Only the Company interacts and participates in this
use case.

3.3. Flow of events

3.3.1. Basic Flow

This use case starts when the actor wishes to

manage the placement system. The system requests
that the Company manage the job response after
apply and post for job. The system validates the
available changes for the respective they send mail
to generate job.

3.3.2. Alternative Flow

None

3.4. Special Requirements

None

3.5. Pre conditions

Company must be Login and any job response
they get then only it can be managed.

3.6. Post condition

If he use case was successful, the actor has to
manage the job in the system. If not, the
system state is unchanged.

3.7. Extension Points

None
4. Manage account:

4.1. Brief Description

This use case describes how the Admin Manage
account in the online placement management
system.

4.2. Actor
The admin interacts and participates in this use case.

4.3. Flow of events

4.3.1. Basic Flow
This use case starts when the actor wishes to
manage the job. The system requests that the
admin manage the account after any response
for job. The system validates the available
changes for the respective to view a system.
4.3.2. Alternative Flow
None

4.4. Special Requirements

None

4.5. Pre conditions

Admin must be Login and can manage the
account.

4.6. Post condition

If he use case was successful, the actor has to
manage the account in the system. If not, the
system state is unchanged.

4.7. Extension Points

None
5. Search Resume:

5.1. Brief Description

This use case describes the Company search for a
resume or candidate.

5.2. Actors
The Company is the actor to search for a resume.

5.3. Flow of events

5.3.1. Basic Flow
This use case starts when the actor login and start
searching for the resume. The system downloads the
resume or CV generated by the Student and then
matches his/ her profile.
5.3.2. Alternative Flow
None

5.4. Special Requirements

None

5.5. Pre conditions

All the users must have a user login in the system,
prior to executing the use cases.

5.6. Post condition

If use case was successfully, the actor logged into
the system. If not the system state is unchanged.

5.7. Extension Points

None
6. Search Job:

6.1. Brief Description

This use case describes the Student to search for a
job.

6.2. Actors
The Student is the actor to search for a job.

6.3. Flow of events

6.3.1. Basic Flow
This use case starts when the actor login and start
searching for job. The student Upload his/ her CV.
6.3.2. Alternative Flow: If no Jobs are post or
applied for job there is no CV.

6.4. Special Requirements

None

6.5. Pre conditions

All the users must have a user login in the system,
and can search job, prior to executing the use cases.

6.6. Post condition

If use case was successfully, the actor logged into
the system. If not the system state is unchanged.

6.7. Extension Points

None
7. Apply for Job:

7.1. Brief Description

This use case describes the student apply for the job
after uploading CV.

7.2. Actors
The Student interacts and participates in this use
case for jobs apply.

7.3. Flow of events

7.3.1. Basic Flow
This use case starts when the actor apply for job and
7.3.2. Alternative Flow
This use case start when student applies for
job, if no job are post then return and cancel.

7.4. Special Requirements

None

7.5. Pre conditions

The student must have to register and generate CV
before jobs apply.

7.6. Post condition

If the use case was successful, the actor has
cancelled the job apply in the system. If not, the
system state is unchanged.
7.7. Extension Points

None
8. Post for Job:

8.1. Brief Description

This use case describes the Company who post new
job and download CV of job seeker.

8.2. Actors

The company interacts and participates in this use

case post for job.

8.3. Flow of events

8.3.1. Basic Flow
This use case starts when the actor post for job.
8.3.2. Alternative Flow
This use case start when company post for
job, if no jobs is to be post then return and
cancel.

8.4. Special Requirements

None

8.5. Pre conditions

The student must have to register and generate CV
before jobs apply.

8.6. Post condition

If the use case was successful, the actor has
cancelled the post job in the system. If not, the
system state is unchanged.
8.7. Extension Points

None
9. Profile Match:

9.1. Brief Description

This use case describes that company and student
matches the job profile according to their needs.

9.2. Actors

The student and company interact and participate in

this use case

9.3. Flow of events

9.3.1. Basic Flow
This use case is to find the profile matches or
not for either student and company.
9.3.2. Alternative Flow
This use case describes that if company does
not post job or student cannot upload CV
then it returns back and no profile match.

9.4. Special Requirements

None

9.5. Pre conditions

All the users should check or match their profile
according to the job.

9.6. Post condition

If the use case was successful, the actor checked the
profile match. If not, the system state is unchanged.

9.7. Extension Points

None
10. Send Mail:

10.1. Brief Description

In this use case company or student and admin
can send mail.

10.2. Actors
The Admin, student and company interact and
participate in this use case.

10.3. Flow of events

10.3.1. Basic Flow
This use case or flow is to send the mail if we upload
CV or download CV and find the job or student.

10.3.2. Alternative Flow

If we are not able to find job or student then no need

of sending mail, return back and cancel.

10.4. Special Requirements

None

10.5. Pre conditions

All the users must check the profile matches or not.

10.6. Post condition

If the use case was successful, then actor check mail
send or not otherwise state is unchanged.

10.7. Extension Points

None
11. View upload profile:

11.1. Brief Description

In this use case student and company can view
upload profile.

11.2. Actors
The company and student interact and participate in
this use case.

11.3. Flow of events

11.3.1. Basic Flow
In this flow a student and company can
upload their profile after profile match.
11.3.2. Alternative Flow
In this flow student and company
matches the profile but does not match
then they cancel.

11.4. Special Requirements

None

11.5. Pre conditions

All the users must check profile carefully to view the
details.

11.6. Post condition

If the use case was successful, the actor checked the
profile matches, if not then return and no changes
done.

11.7. Extension Points

None
12. View delete profile:

12.1. Brief Description

In this use case student and company can view
delete profile.

12.2. Actors
The company and student interact and participate in
this use case.

12.3. Flow of events

12.3.1. Basic Flow
In this flow a student and company can
delete their profile after profile match.
12.3.2. Alternative Flow
In this flow student and company
matches the profile but does not match
then they cancel.

12.4. Special Requirements

None

12.5. Pre conditions

All the users must check profile carefully to view the
details.

12.6. Post condition

If the use case was successful, the actor checked the
profile matches, if not then return and no changes
done.

12.7. Extension Points

None
13. CV generated:

13.1. Brief Description

This use case describes the generation of CV
uploaded by student.

13.2. Actor
In this actor student participate and interact with the
use case.

13.3. Flow of events

13.3.1. Basic Flow
This use case starts when apply for job after
CV generated.
13.3.2. Alternative Flow
In this use case CV generated if profile match
otherwise cancel login.

13.4. Special Requirements

None

13.5. Pre conditions

All the users must have login or register the job
management system.

13.6. Post condition

If this use case was successful, the actor check the
job to be searched after CV upload.

13.7. Extension Points

None
14. Report generated:

14.1. Brief Description

This use case describes the details are generated
after all the process.

14.2. Actors
In this actor company and admin interact and
participate in this use case and generate the reports.

14.3. Flow of events

14.3.1. Basic Flow
This use case starts when the actor complete
the process.
14.3.2. Alternative Flow
In this use case if no job process done then it
does not reply or report generate.

14.4. Special Requirements

None

14.5. Pre conditions

All the users must have a user login in the system,
before view upload profile or delete profile.

14.6. Post condition

If the use case was successful, the actor checked the
report generated by admin and job provider.

14.7. Extension Points

None
 CONTEXT DIAGRAM (LEVEL - 0 DFD)

The Context Diagram is given below:

ADMIN

STUDENT COMPANY

ONLINE

PLACEMENT

MANAGEMENT

SYSTEM

View Update Response View Delete Response

Report Generated

The following persons are interacting with the “ONLINE

PLACEMENT MANAGEMENT SYSTEM”

(i) ADMIN
(ii) STUDENT
(iii) COMPANY
LEVEL-1 DFD Send mail

Send mail
Send View Student List
Mail

User id, password

View
View Delete
Upload Profile
Manage
Profile
Job
Response
Report
Generated Match No Match
Upload profile

Manage job Delete profile

resp resp
Data store
COMPANY Profile
Report Match
Post job opening

Search candidate

Post
Apply
Job Search
Job Candidate profile
Resume

Download CV

Apply for job Job profile

STUDENT Search
Upload CV
Job

LOGIN
Register CV
Generation
Post CV

User id, password

Send mail

ADMIN
User information
User
Account
Update/ User entry
Manage
Account Update / manage account
Login and Registration:

Job Seeker
Enter user id, password
Registration

Enter user id, password

LOGIN

Enter user id, password

Job Provider
Admin
User information

Admin:

Admin User information

Enter user id, password

User
account

Send Mail:

Job Seeker
Admin
Send
mail Job Provider

Mail Information
Manage Job Response:

Job Provider Manage

Job
Response

Manages Job response

Manage Account:

View Managed information

Admin Manage
Account

Profile Match:

Job Provider

Profile
Job Provider Match

Profile Details
View Upload Profile:

Job Provider

View Employee List

View
Upload
Profile
Retrieve User Information Validate/ Process User Info

View Delete Profile:

View Employee List

Job Provider

Validate/ Process User Info

View
Delete
Retrieve User Information
Profile
Search Job:

Job Seeker
Search
Job Job Details

Search Resume:

Job Provider
Search
Resume
Resume
generate

Post Job:
Job Details

Job Provider Search

Resume

Apply Job:

Job Details info

Apply
Job Seeker
Job
 Report Generated:

Job Provider

Report
Generated

Report Generated

Admin

CV generated:

Job Provider Job Seeker

CV Download
Display
CV CV info
Generated
CV Upload generate
Use Case CV GENERATION
Diagram
SEARCH JOB

APPLY JOB

UPDATE / MANAGE
ACCOUNT

LOGIN

SEND MAIL

ADMIN
REGISTER

VIEW DELETE
PROFILE

VIEW UPLOAD
PROFILE STUDENT

POST JOB

REPORT
GENERATED

PROFILE MATCH

COMPANY
MANAGE JOB
RESPONSE

SEARCH RESUME
 Entity Relationship Diagrams

Username Company

Experience Address
Resume Contact

D. O. B.
Salary
STUDENT Job
Searches

User ID Company_ID
Job_ID

Password Experience
Contact
Address

Post
Deletes Seeks

Username Address

Contact

COMPANY
Industry

Company_ID Company

Password
Experience
 SRS (Software System Requirements)
1. Introduction
1.1 . Purpose
1.2 . Objective & Scope
1.3 . Definitions, Acronyms and
Abbreviations
2. Specific requirements
2.1. User interfaces:
Login
Registration
Post Job
Apply Job
Search Job
Search Resume
CV generated
Profile Match
View Upload Profile
View Delete Profile
Send Mail
Report generated
Manage Job Response
Manage Account
2.2. Client Side Requirements
 2.2.1. Hardware interfaces
2.2.2. Software interfaces
2.2.3. Operating system
2.3. Server Side Requirements
2.3.1. Hardware interfaces
2.3.2. Software interfaces
2.3.3. Operating system
2.4. Tools and Language Used
2.5. Report generation
3. Software system architecture
3.1. Security
3.2. Maintainability
3.3. Reliability
3.4. Availability
 1. Introduction

1.1. Purpose
This system can be used as an online job portal for the
placements providing to the un- employees who are
seeking for a job placement. Job seeker logging into
the system and he is able to upload their information
in the form of a CV. Visitors/ company representatives
logging in may also access/ search any information put
by job seeker.

1.2. Objective & Scope

The main objective of Job Portal is to provide an
essence of online job portal. Job Portal has been
designed to make the suitable recruiters find
prospective candidates, and vice versa. Job Portal has
been designed to make the process of online job
hunting much easier.

1.3. Definitions, Acronyms and Abbreviations

Admin: The authorized person who controls all the
network

Job Provider: Who Creates vacancies

Job Seeker: The person who apply for job

2. Specific Requirements

2.1. User Interfaces

 Login: Login search for Id, Password
 Registration: Registration search for the user
information
 Post Job: Job provider post new job
 Apply Job: Job Seeker apply for job
 Search Job: Job Seeker search for job
 Search Resume: Job Provider search for resume or
candidate
 CV generated: CV is generated by Job seeker
 Profile Match: After uploading CV Profile is matched
 View Upload Profile: If profile is matched then it is
uploaded
 View Delete Profile: If profile is not matched then it is
deleted
 Send Mail: Mail is send by Job seeker, Job provider and
Admin to provide information
 Report generated: After all the information of Online
Job portal Report is generated
 Manage Job Response: Job provider manage job
responses
 Manage Account: Admin manage the account if any
problem occurs

2.2. Client Side Requirements

2.2.1. Hardware Interfaces
 512 MB of RAM
 P-IV processor or higher
2.2.2. Software Interfaces
 Web Browser like Internet Explorer 8.0,
Mozilla Firefox, Opera 10.60, Google
Chrome or others.
 Apache Tomcat 6.0

2.2.3. Operating System

Any OS

2.3. Server Side Requirements

2.3.1. Hardware Interfaces
 512 MB of RAM
 P-IV processor or higher

2.3.2. Software Interfaces

 Web Browser like Internet Explorer 8.0, Mozilla
Firefox, Opera 10.60, Google Chrome or others.
 Apache Tomcat 6.0

2.3.3. Operating System

Any OS
 2.4. Tools and Language Used
Tools used:
 Wamp Server
 Dreamweaver
Languages:
 PHP
 SQL
 HTML
 CSS

2.5. Report Generation

After Job registration to profile match
Report is generated.

3. Software system architecture

 Security: The application software
should be secure
 Maintainability: Software must be
designed in a way that can be
maintained in future.
 Reliability: The system should be
reliable. This software should not crash
frequently.
 Availability: The system should be
available to all users 24/7.
THANK YOU