Table of Contents

1. Introduction

1.1 Purpose

1.2 Scope

1.3 Definition and abbreviation

1.4 References

1.5 Overview

2. Overall Description

2.1 Product Perspective

2.1.1 System Interface

2.1.2 User Interface

2.1.3 Hardware Interface

2.1.4 Software Interface

2.1.5 Communication Interface

2.1.6 Memory Constraints

2.1.7 Operations

2.1.8 Site Adaption Requirement

2.2 Product Functions

2.3 User Characteristics

2.4 Constraints

2.5 Assumptions and Dependencies

3. Specific Requirements

3.1 External Interface Requirements

3.1.1 User Interfaces

3.1.2 Hardware Interfaces

3.1.3 Software Interfaces

3.1.4 Communications Interfaces

3.2 Specific Requirements

3.2.1 Sequence Diagram

3.2.2 Classes and classification of specific requirements

3.3 Performance Requirement

3.4 Design Constraints

3.5 Software system Attributes

3.5.1 Reliability

3.5.2 Availability

1
3.5.3 Security

3.5.4 Maintainability

4. Supporting Information

4.1 Table of Content and Index

4.2 Appendixes

2
 INTRODUCTION

1.1 Purpose

The primary purpose to develop this system is to optimize the recruitment process for college. Besides, the qualified
applicants could be sort by this system based on their qualifications and company requirements. Based on the applicants’
skills and areas of interest, the company suitable or the company in which he/she is going to place can be predicted. Another
purpose of the software is to facilitate the student (in the college) and the company to register and communicate with
placement office.

1.2 Product Scope

Campus Recruitment System enables the user to have the typical recruitment facilities and features at their disposal. It
resolves the typical issue of manual staffing processes and activities into a controlled and closely monitored work flow in the
architecture of the application. The objective of this application is to serve as a common meeting ground for jobseekers and
company, locally. This kind of system is specifically designed for organization to help in solving staffing problems and
managing human resource department activities at higher degree of optimization.

1.3 Definition & Abbreviation

A Campus Recruitment System is a platform or software solution designed to facilitate the process of recruiting students
from educational institutions for job opportunities. It typically includes features such as candidate management, job posting
and management, scheduling and coordination, communication management, event management, assessment and evaluation
tools, analytics and reporting, integration with HR systems, feedback mechanisms, and security measures.

1.4 Overview

The Campus Recruitment System (CRS) is a comprehensive software solution designed to streamline and optimize the
recruitment process within educational institutions. It facilitates seamless interaction between students, employers, and the
college's placement office. The system aims to efficiently match qualified students with job opportunities based on their
skills, qualifications, and interests, while also meeting the requirements of recruiting companies. Key features include
student and employer registration, job posting and application management, interview scheduling, communication tools, and
predictive analytics for suggesting suitable company placements. The CRS enhances efficiency, transparency, and
collaboration, ultimately improving the overall campus recruitment experience

3
 Overall Description

2.1 Product Perspective

In the “Campus Recruitment System,” We will be having a user interface for the admin, student, and company. The user can
log in to their account. Depending on the user, the utilities will be decided. The student can login to their respective account
and can apply for the respective

post available. If the user does not have an account, then he/she can create an account and can apply or the jobs. The
company can login to their account and can update the details of the jobs available. If the company do not have an account
the they can create and account and can update the job details. Admin will already be having an ID and password. The admin
will login and manage the student and companies’ activities. After the creation or the login of the user, a successful message
will be displayed to the user

2.2 Product Functions

The above DFD clearly shows various various process associated with the project and how the data flows between the
entities and database. The student can create the account. If the account is already present then he/she can search for the
available jobs, can view the jobs, and apply for the jobs. Further he/she can update the details, can change the password etc.

4
The company can create the account. If the company already have an account, then the company can post the job and can
also view how many candidates have applied for the jobs of that company. The admin can manage the student and the
company. Admin validates the account of the

student. Admin validates the account of the company. Admin can also remove company and the student if found any
discrepancy. Admin manages all activities of company and student.

2.3 User Classes and Characteristics

The actors and use cases are clearly shown in below use-case diagram

In software and systems engineering, a use case is a list of actions or event steps typically defining the interactions between a
role (known in the Unified Modelling Language as an actor) and a system to achieve a goal. The actor can be a human or
other external system. In systems engineering use cases are used at a higher level than within software engineering often
representing missions or stakeholder goals.

S. No Actor Name Description / Actor’s Role

1 ADMIN Manage students & companies
2 STUDENT Apply for jobs, view job status & search jobs.
3 COMPANY Post jobs & view applications of students.

5
The following section describes the Use Cases with Pre and Post Conditions

S. No Use case Name Description Pre-condition Post condition

1 Perform Login User (admin, student, or company) User having account Login successful
can perform login
2 Perform Logout User (admin, student, or company) User logged in Successfully logged out
can perform logout
3 Update Details User (admin, student, or company) User logged in View details
can update their details.
4 Change Password User (admin, student, or company) User having password. Password is reset.
can change passwords.
5 Manage Admin can manage companies Existing admin & at least one Validated by admin &
Company company company can continue
with its account
6 Manage Students Admin can manage students Existing admin & at least one Validated by admin &
student student can continue
with its account
7 Apply for jobs Student can apply for job Job should be there posted by Applied for job
company & student must be successfully & wait for
eligible for job response from
company
8 View Job Status Student can view job status Student must have successfully Viewed job status &
applied for job. can accept job if
selected else can apply
for other job
9 Search jobs Student can search for job Student must have account & Can find a job or not.
logged in
10 Post Jobs Company can post jobs Company must have account & Student can now apply
logged in for jobs.
11 View Applications Company can view applications of At least one student must have Company can react to
students applied. applications
12 Get Help User can get help for login User should have tried for it or User will now login
just get help if does not know using this help.
how to login

2.5 Constraints

The following Design and Implementation Constraints are applicable for the Campus Recruitment System:

1. The system is designed to be the cross platform supportable. The system is supported on a wide range of hardware and
any android platform which is having any version of android built into the system. This application is being developed using
android studio; hence it is extremely portable

2. To prevent multiple students of the same speciality to log-in onto same company portal. Request, a workflow system
needs to be designed which routes the company vacancy Requests to students.

3. System is expected to store maximum 64GB of data.

4. Initially system will be available on android system with versions greater than

5. Then the system will be available for even iOS mobiles and even on PCs and Laptops.

6. To assist students for selecting a company and preparing for interview for that company, a machine learning algorithm
will be designed and trained on a training data-set to predict which skills will be required for students and if student is
eligible for company, this algorithm will continue to be trained on previous recorded data sets of students to improve the
quality of predictions.

7. The database shall be maintained by admin and who have not logged in for last 1 year would get archived onto a parallel
database. Restoring of student’s data is beyond the scope of the project and would need to be managed by admin.

8. As the system is supposed to be used by students and company as well, care needs to be taken from a usability perspective
in terms of font sizes and ease of system usage.

6
9. Also UI is made with animations so that company can find it good for uploading jobs and interact with students. Even
more and more companies and students use this app is the aim.

2.7 Assumptions and Dependencies

The Key Assumptions are:

1.The whole system is designed based on only one college.

2. There will be one authorised student for a particular id. So, id will be unique.

3. There will be one authorised company for a particular id. So, all ids will be unique.

4. Student can fill maximum 30 application form for jobs in a company.

5. A Machine Learning Algorithm to assist students for selecting a company and preparing for interview for that company
will be implemented to predict which skills will be required for students and if student is eligible for that company

SPECIFIC REQUIREMENTS

3.1 External Interface Requirements

3.1.1 User Interfaces

The user interface section defines the way various stakeholders interact with the system. All the screens will be developed to
work on android mobile. Error messages will appear as a popup on the screen. The maximum size of error message will be
40 characters. Buttons will there to make the navigation simpler. A first-time user of the mobile should see the login screen
when he/she will open the android application. If the user has not registered to the, then he/she should be able to redirect to
the sign-up page from login screen. Every user should have the profile where he/she can apply for the job. After the creation
of account, the user can login to the application and will be able to apply for the jobs.

7
Similarly, here will be the same option for the login of the company where the company can sign up and login. An Admin
should also be log in to the web portal where he/she can administer the system by managing the student and company using

the application. After performing

login, the user will be able to

see the side menu as shown in the figure below. After performing login by the company, the company will be able to see side
menu shown in the second figure below.

User can select the section and can perform the respective task. There is an option to add the jobs for the company where the
companies can add the vacancies for their companies they have.

3.1.2 Hardware Interfaces

8
 Since the mobile application does not have designated hardware, it does not have any hardware interface. The hardware
connection between the database server and application is managed by the underlying operating system on the mobile phone.

3.1.3 Software Interfaces

The system is self-contained and no data is supposed to share with the third party. The communication of the mobile
application between the database consist of both reading and modifying the data, while the communication between the
database and the mobile application consists of only reading operation.

3.1.4 Communications Interfaces

The communication between the different parts of the system is important since they depend on each other. However, in
what way the communication is achieved is not important for the system and is therefore handled by the underlying
operating system for the mobile application.

3.2 Specific Requirements

3.2.1 Sequence Diagram

3.2.2 Performance Requirements

1. The separate business logic at admin side from the student interface ensures good performance.

2. The system exhibits high performance because it is well optimized. The business logic is clearly separate from the UI.

3. System should be able to scale to many users concurrently.

4. The response time of processes is as follows: Student Registration max 10 seconds Company Registration max 15
seconds Company Job posting max 15 seconds Student applying for job max 20 seconds

5. System is available 24 by 7

9
3.2.3 Design Constraints

The following Design and Implementation Constraints are applicable for the Campus Recruitment System:

1. The system is designed to be the cross platform supportable. The system is supported on a wide range of hardware and
any android platform which is having any version of android built into the system. This application is being developed using
android studio; hence it is extremely portable

2. To prevent multiple students of the same speciality to log-in onto same company portal. Request, a workflow system
needs to be designed which routes the company vacancy Requests to students.

3. System is expected to store maximum 64GB of data.

4. Initially system will be available on android system with versions greater than

5. Then the system will be available for even iOS mobiles and even on PCs and Laptops.

6. To assist students for selecting a company and preparing for interview for that company, a machine learning algorithm
will be designed and trained on a training data-set to predict which skills will be required for students and if student is
eligible for company, this algorithm will continue to be trained on previous recorded data sets of students to improve the
quality of predictions.

7. The database shall be maintained by admin and who have not logged in for last 1 year would get archived onto a parallel
database. Restoring of student’s data is beyond the scope of the project and would need to be managed by admin.

8. As the system is supposed to be used by students and company as well, care needs to be taken from a usability perspective
in terms of font sizes and ease of system usage.

9. Also UI is made with animations so that company can find it good for uploading jobs and interact with students. Even
more and more companies and students use this app is the aim.

3.4 Software System Attributes

3.4.1 Reliability

Reliability in a campus recruitment system denotes consistent performance without failures, ensuring accurate data handling,
minimal downtime, and swift error recovery. It encompasses dependable availability, robust error handling, and efficient data
management to maintain system integrity. Scalability ensures seamless operation with growing demands, while proactive
monitoring and maintenance sustain reliability over time. Ultimately, reliability fosters trust among users, enabling smooth
recruitment processes and bolstering organizational efficiency.

3.4.2 Availability

It refers to its accessibility and usability whenever required. It ensures that recruiters, students, and administrators can
access the system without interruption or delay, enabling them to perform their tasks efficiently. High availability is achieved
through measures such as redundant hardware, load balancing, and failover mechanisms to mitigate downtime. Monitoring
tools and proactive maintenance further contribute to ensuring continuous availability, enhancing user satisfaction, and
optimizing the recruitment process.

3.4.3 Security

1. The system is provided a high level of security and integrity of the data held by the system.

2. only authorized personnel such as admin can gain access to the to the private data and only the user with valid username
and password is allowed to view its user page.

3.4.4 Maintainability

Maintainability in a campus recruitment system refers to its ease of maintenance and modification over time. It involves
designing the system in a way that allows for efficient updates, bug fixes, and enhancements without disrupting its
functionality. Key aspects include well-organized code structure, clear documentation, and modular design, enabling
developers to understand and modify the system effectively. Implementing best practices such as version control, automated
testing, and code reviews streamlines maintenance efforts and reduces the risk of introducing errors.

10