Professional Documents
Culture Documents
Specification
for
“Recruitment Process
Management System”
25 Feb,2021
Table of Contents
Table of Contents .......................................................................................................................... ii
Table of Figures………………………………………………………………………………….ii
List of Tables…………………………………………………………………………………….ii
Revision History ........................................................................................................................... iii
1. Introduction ..............................................................................................................................1
1.1 Purpose ............................................................................................................................................ 1
1.2 Document Conventions.................................................................................................................... 2
1.3 Intended Audience and Reading Suggestions .................................................................................. 2
1.4 Product Scope .................................................................................................................................. 3
1.5 References...................................................................................... Error! Bookmark not defined.
2. Overall Description ..................................................................................................................3
2.1 Product Perspective ......................................................................................................................... 3
2.2 Product Functions ............................................................................................................................ 3
2.3 User Classes and Characteristics ..................................................................................................... 4
2.4 Operating Environment.................................................................................................................... 5
2.5 Design and Implementation Constraints .......................................................................................... 5
2.6 User Documentation ........................................................................................................................ 6
2.7 Assumptions and Dependencies ...................................................................................................... 6
3. External Interface Requirements ...........................................................................................6
3.1 User Interfaces ................................................................................................................................. 6
3.2 Hardware Interfaces ......................................................................................................................... 6
3.3 Software Interfaces .......................................................................................................................... 6
3.4 Communications Interfaces ............................................................................................................. 6
4. System Features........................................................................................................................6
4.1 System Feature 1 ............................................................................ Error! Bookmark not defined.
4.2 System Feature 2 (and so on) ......................................................... Error! Bookmark not defined.
5. Other Nonfunctional Requirements ......................................... Error! Bookmark not defined.
5.1 Performance Requirements ............................................................ Error! Bookmark not defined.
5.2 Safety Requirements ...................................................................... Error! Bookmark not defined.
5.3 Security Requirements ................................................................... Error! Bookmark not defined.
5.4 Software Quality Attributes ........................................................... Error! Bookmark not defined.
5.5 Business Rules ............................................................................... Error! Bookmark not defined.
6. Other Requirements .................................................................. Error! Bookmark not defined.
Appendix A: Glossary...................................................................... Error! Bookmark not defined.
Appendix B: Analysis Models ......................................................... Error! Bookmark not defined.
Appendix C: To Be Determined List .............................................. Error! Bookmark not defined.
Software Requirements Specification for <Project> Page iii
Revision History
Name Date Reason for Changes Version
Recruitment Process 14 Dec, Function Requirements not defined properly. 1.0
Management System 2020
Recruitment Process 21 Function Requirements and use cases are not 1.1
Management System Dec,2020 defined properly.
Recruitment Process 4 Use cases are not defined properly. 1.2
Management System Jan,2021
Recruitment Process 11 Project modules are not defined properly. 1.3
Management System Jan,2021
Recruitment Process 19, Wireframe and Screen are not added in 1.4
Management System Jan 2021 document.
Recruitment Process 25 Jan, Wireframe is not added properly in document. 1.5
Management System 2021
Recruitment Process 29 Jan, Wireframe is not added properly in document 1.6
Management System 2021
Recruitment Process 1 Feb, ERD is not properly defined in document. 1.7
Management System 2021
Recruitment Process 12 Gantt Chart is not defined properly. 1.8
Management System Feb,2021
Recruitment Process 25 Gantt Chart is not defined properly 1.9
Management System Feb,2021 in a document.
Software Requirements Specification for <Project> Page 1
1. Introduction
Before employee recruitment system the applicants have to search for jobs by visiting different
institutes moreover they have to visit different cities for the jobs. For that they have to use their
money and resources. And there is no guarantee that he/she will get the job or not.
I have designed this system to benefit the applicants, they do not have to go to other cities. They just
need to open their browser and search for the website. There they can apply for the job and they will
even get their appointment letter on the website.
Employee Recruitment System by overall is aims to facilitate the applicant to apply for the job
online. Indirectly, it is also to facilitate the managerial department of an organization for an
optimized and systematic employee recruitment process.
A quick look at the overall trends in Online recruiting shows the rise in the importance of recruiting
on the web site, online training, dawn of video interviews and emergence of professional Internet
Recruiters. Online recruiting systems, with its emphasis on a more strategic decision making process
is fast gaining ground as a popular outsourced function.
The system also provides the global platform for both jobseekers and the organization, where the
jobseekers can find their dream jobs and organization can find the right candidate to fulfill staff
requirements. This system has web-forms like registration form, login form and account pages like
user applicant page, admin account page etc. An administrator can be a manager who has full
authority over the whole system. The administrator is able to update and retrieve data from the
account of candidate. The candidate is a center of this system. He has to register himself to use the
services of the system.
1.1 Purpose
The primary purpose to develop this system is to optimize the recruitment process for an
organization. Besides, the qualified applicants could be sort by this system based on their
qualifications and company requirements. The system has been designed to do a whole lot more
than just reduce paperwork. It can make a significant contribution for the organization.
The applicants can give their CV online.
Software Requirements Specification for <Project> Page 2
Augmented Reality:
Augmented reality is the vision of a physical environment by means of a device (Web Browsers like
Google Chrome) so that this real-world physical environment is shown in real time with an
additional layer of virtual elements.
HTML: HTML stands for Hyper Text Mark-up Language HTML is the standard mark-up language
for Web pages HTML elements are the building blocks of HTML pages HTML elements are
represented by <> tags.
SQL: SQL stands for structure Query Language. It is a standard language for accessing and
manipulating databases.
HR: Human resources are used to describe all the working of organization which is responsible for
managing all matters related to employees.
Online Recruitment System enables the users to have the typical recruitment facilities and features
at their disposal. It resolves typical issues of manual staffing processes and activities into a
controlled and closely monitored work flow in the architecture of the application. This multi -
platform solution brings in by default, the basic intelligence and immense possibilities for further
extension of the application as required by the user. The system makes it simpler to share and
manage the organization’s human resource requirements with higher efficiency and easiness. The
objective of these websites is to serve as a common meeting ground for jobseekers and organization,
both locally and globally. This kind of systems is specifically designed for organization to help in
solving staffing problems.
2. Overall Description
My system is based on the recruiting process, using the concept of recruiting we have automated all
the processes that are used in new recruiting for hire. This will help us find the right job for the right
person. This system aims to develop a centralized, web-based recruitment process system for HR
groups in the organization. Some features of this system will be creating vaccines, storing
application data and initiating the interview process, scheduling interviews, storing interview results
for the candidate and finally hiring the candidate.
The first HR module has full authority over the candidate. It can display all registered users and
have the power to delete them. He can edit and update job titles and post new jobs. He can also see
all the candidate's details.
Software Requirements Specification for <Project> Page 4
In the second module, a candidate applies for the position himself. After registering, they will be
directed to their home page. Here he can update his profile, change password and view exam details
and all.
In the third module, the administrator has access to the whole process. The administrator is a
supervisor of the entire program and processes.
Create account
Sign in
Structure and systematically organize the entire recruitment processes.
It facilitates faster, unbiased, accurate and reliable processing of applications from various
applications.
Helps to reduce the time-per-hire and cost-per-hire.
It maintains an automated active database of the applicants facilitating the talent
management and increasing the efficiency of the recruitment processes.
It provides a flexible, automated and interactive interface between the application system,
the recruitment department of the company and the job seeker.
It helps to communicate and create healthy relationships with the candidates through the
entire recruitment process.
This product has three types of users based on different levels of functionality i.e. applicant, HR and
admin. Applicant can use this application to apply for a job by uploading their CV. HR use this
application to recruit best persons for their job and know about their skills. All users require only
general knowledge of using touch screen of Web Application.
Software Requirements Specification for <Project> Page 5
Device Performance:
Need adequate performance from the device to operate the application efficiently.
Input/ Output ports:
This application will use Keyboard for input and display screens for the output. Also needs storage
permission to upload CV.
Software Requirements Specification for <Project> Page 6
At the completion of development, a user manual will be made available to help users. Hints may
be provided in the application to assist with the ease of use of the program.
Web application is assumed to have good condition with all functions working properly.
All interaction with the user is via keyboard. Once the application has started, the user can interact
through icons on the screen by mouse. If the user clicks the icon then specific function performs.
Since this application is developed as a Web App, operating system is the most important required
software for this application to work.
4. System Features
for the user to accomplish their task, thereby satisfying the business needs. Functional
Requirements are also called Functional Specification. Functional Requirement can range from
the high-level abstract statement of the sender’s necessity to detailed functional requirement
specifications. Functional software requirements help you to capture the intended behavior of the
system. So, functional requirements talk about a particular system outcome when a task is
performed on them by the user.
Identifier Requirements
Req-1 The system shall have options from which the applicant can apply for all the
vacant positions, apply for one vacant position or apply for some job only.
Req-2 The system shall include feature to check the applicant information or status.
Req-3 The system shall allow applicants to enter the necessary information (first
name, last name and address), upload curriculum vitae,from which the
system can calculate grading and made the first screening.
Req-4 The system shall display all list of applicants awaited along with their position
interest and application.
Req-5 The system shall provide the step-by-step wizard that ensures applicants
provide all the information the company needs.
Req-6 The system should rank candidates based on the criteria set.
Req-7 The system should be flexible to set criteria’s based on the company
interest.
Req-8 The system should provide candidates information to update the assessment
result.
Req-9 The system should save the data filled by the recruitment unit.
Req-10 The system shall add results based on the recruitment unit interest and rank
applicants in ordered manner.
Req-12 The system should accept criteria as an input to make the final ranking.
Req-14 The system should have a way to identify which person specification is for
which job type.
Req-15 The system should have a way to check the validity of the data to be saved.
Req-16 The system should display detail job description when an applicant wants to
see.
Req-17 The system shall notify all candidates by generating automatic e-mail.
Req-19 The system shall provide list of candidates together with the respective full
information.
Req-20 The system shall display report for all jobs posted if user prefers to see.
Req-21 The system shall provide a means to send list of candidates for approval.
Req-22 The system should have a view option for the user to see any notifications
sent.
Req-23 The system shall display list of jobs.
Req-24 The system shall provide all jobs requirement before the user applies for that
specific job type.
Req-25 The system shall provide applicants status info when a user requests status
info.
Use case diagram refer to diagrammatic view of showing out what the actions that external actors
and internal actors (users involve with the system) who take part in performing the system. The
opportunities that can be gained by designing of this use case diagram are that it will help in
identifying who the users of the system which is being implemented.
Furthermore, by preparing use case it will help in identifying the goals associated with each actor
involved with the system as well. Following provided use case diagrams was prepared upon the
requirements and system functionalities that will be included within the recruitment management
system.
4.3.1 UC-1:
Software Requirements Specification for <Project> Page 10
4.3.2 UC-2:
4.3.3 UC-3:
Software Requirements Specification for <Project> Page 12
Sequence Diagram represents object collaboration and is used to define event sequences between
objects for a certain outcome. Using UML sequence diagrams, it represents the flow of messages as
well as events and actions between objects of the system. Therefore, the opportunities that can be
gained by creating the sequence diagram are that it will help in identifying the architecture as well as
the interface and logical problems beforehand. A sequence diagram is an interaction diagram.
Interaction among the components of a system is very important from implementation and execution
perspective. Sequence diagram is used to visualize the sequence of calls in a system to perform a
specific functionality.
Software Requirements Specification for <Project> Page 14
Sequence diagram of application is displayed which explains the sequence of each and every
activity of application.
A non-functional requirement is a specification that describes the system's operation capabilities and
constraints that enhance its functionality. These may be speed, security, reliability, etc.
Table 3: Non-Functional Requirements:
Identifier Requirements
NFR 1 This application is secure for every kind of its users, because here is facility of
session management. If any user logout from any session, then nobody will be able to
access his profile without knowing his confidential password.
NFR 2 The database used here is robust, reliable and fast. So, users will have to wait for the
output very short time.
NFR 3 This application can be accessed from any type of platform.
NFR 4 There is no case of redundancy in the database so it will not take extra memory
space.
7. Development Model
It is based on iterative and incremental development, where requirements and solutions evolve
through collaboration between cross-functional teams. I t can be used with any type of project, but it
needs more engagement from the customer and to be interactive. Also, we can use it when the
customer needs to have some functional requirement ready in less than three weeks and the
Software Requirements Specification for <Project> Page 22
requirements are not clear enough. This will enable more valuable and workable piece for software
Figure:12 Wireframe
9 Giant Chart:
Software Requirements Specification for <Project> Page 24