Project Synopsis Format

Name Roll No Project Undertaken Estimated Duration Name and Address of Organization Ravinder Kaur RD1903A32 Smart Hiring System 4 months Techno Campus SCF 8 New Jawahar Nagar, Jalandhar External Supervisor Name External Supervisor Designation External Supervisor Phone no External Supervisor Email Nature of Project Project Description Functional Requirements / System features Following are the identified functional requirements of the Smarter Hiring System 1. Candidate profile management: Create a new profile Update an existing profile Delete a profile Neeraj Tandan Faculty 0181-2242408 manjit@technocampus@co.in Web

2. Support for uploading a profile in an accepted format 3. Provide role based access to the system ( Authentication and Authorization) Administrators / HR personnel Hiring Manager Employee

4. Manage the resume lifecycle. 5. Enforce eligibility criteria including blacklisting of a profile. 6. Generate reports based on required filters

Functional requirements details 1. Candidate profile management An employee can create a new profile. Each profile should be uniquely identified by a primary key which can be the unique identification number (proposed), mobile number or email. At any given point of time, there should be one and only one profile of a single person should exist. If the profile already exists, then the employee should be allowed to update the profile. 2. Support for uploading a profile in an accepted format While creating/updating the profile, the employee should be allowed to upload the resume as a document and the system should allow the retrieval of this document whenever an authorized person accessed the profile. 3. Provide role based access to the system (Authentication and Authorization) The identified user roles are: a. Administrator/HR Is allowed to create, update, view all and delete a profile b. Hiring Manager Is allowed to create, update and view all profiles c. Employee Is allowed to create new profiles (refer a candidate) and to update the profiles he has created. 4. Manage the resume lifecycle The system should have a resume life cycle so that the following issues are addressed. No two hiring managers can start the hiring process on the same candidate

Once interviewed, the findings are to be recorded such as for which position the candidate has been interviewed, did the skill set match, reason for rejection or selection etc.

5. Enforce eligibility criteria including blacklisting of a profile Whenever a candidate undergoes a selection process, the candidate might be rejected because he might not suit the exact competency/level expected for that role. Hence the candidate will be rejected. This candidate history will help other managers to easily look for candidates and if their requirements suits then to proceed with the selection process. During the selection process if the candidate was found to be mischievous such as fake identity, cooked certificate etc, then the candidate must be blacklisted in the system. 6. Generate candidate/profile report The system should generate reports based on various filters such as skill set, years of experience, domain experience etc. Through this report an interested person can identify the availability/eligibility of the candidate, or if the candidate is being interviewed by other team or the candidate has interviewed for a similar role and rejected etc.

Use Case Diagram

Database Schema The proposed DB schema is given below. 1. Organization Name ID Location Address 2. Department Name ID Manager 3. Employee

 Name DOB EMP ID IsManager IsAdmin Department Location Address PhonePrimary PhoneSecondary MailID 4. CandidateProfile Name DOB Domain Technologies YearsOfExperience MailID PhonePrimary PhoneSecondary LifeCycleState ( contacted/interviewedd/offered/joined/blacklisted) University Qualification

Internal Faculty Advisor Scope of Project

Parul Khurana This software is used by the organizations to recruit employees with a robust recruitment process.

Ravinder Kaur Signature

7 February 2012 Date

Comments/Observation by Faculty Advisor _________________________________________________________________________ _________________________________________________________________________ _________________________________________________________________________ Recommended Yes No

Signature of Faculty Advisor Date: Approved Yes No

Signature of HOD/HOI Date