Group No7 Campus Recruitment System PDF

Campus Recruitment System
Submitted in partial fulfillment of the
requirements of the degree of
B. E. Information Technology
By
Kalyani Jadhav 151260
Priyanka Kate 141061
Neha Kotian 141090
Jayesh Sawant 141056
Supervisor(s):
Dr. Joanne Gomes
Head of Department
Department of Information Technology
St. Francis Institute of Technology (Engineering College)
University of Mumbai
2017-2018
CERTIFICATE
Principal
I
Project Rep
II
Declaration
III
Abstract
Campus Recruitment System (CRS) is web-based tool to reduce communication gap
between Job providers and Job seekers.The Main objective of this project is to make easy
the recruitment process of any organization. This CRS is designed by keeping in mind
both parties Job providers and Job seekers. CRS allows Job seekers to register their details
like skills and experience with the system, and then on the other hand even it allows job
providers to post their requirements with the system. Campus Recruitment Management
system is helpful for the job providers i.e. companies which are in need of employees, job
seekers who are in need of job, (for both Experienced and fresher's). This portal's main
aim is to provide the vacancies available for the job seekers in IT technologies. CRS will
automatically send mails to all job seekers whose skills are matched with the requirement.
IV
Contents
1 Introduction 1
1.1 Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
1.2 Problem Formulation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
1.3 Motivation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
1.4 Proposed Solution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.5 Scope of the Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
2 Review of Literature 4
3 System Analysis 6
3.1 Functional Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
3.2 Non Functional Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . 6
3.3 Speci c Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
3.3.1 Hardware Requirements . . . . . . . . . . . . . . . . . . . . . . . . . 6
3.3.2 Software Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . 7
3.4 Use Case . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
4 Analysis Modeling 9
4.1 Data Modeling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
4.2 Activity Diagram....................................................................................................... 10
4.3 Functional Modeling ....................................................................................................... 11
4.3.1 Level 0 DFD ....................................................................................................... 11
4.3.2 Level 1 DFD ....................................................................................................... 11
4.3.3 Level 2 DFD ....................................................................................................... 12
4.4 Timeline Chart .......................................................................................................... 13
5 Design 14
5.1 Architectural Design ................................................................................................. 14
5.2 User Interface Design ..................................................................................................... 15
6 Implementation 19
6.1 Technologies Used .......................................................................................................... 19
6.2 Working of Project .......................................................................................................... 20
6.2.1 PHP Codes .................................................................................................... 21
6.2.1.1 1.About.php.................................................................................... 21
6.2.1.2 Add event.php ................................................................................ 22
6.2.1.3 Add notice.php ............................................................................... 22
6.2.1.4 Adlogout.php ...................................................................................... 23
V
CONTENTS
6.2.1.5 Adminlogin.php .................................................................................. 23

6.2.1.6 Adminpanel.php.................................................................................. 23
6.2.1.7 Banner.php ...................................................................................... 23
6.2.1.8 Companydetails .................................................................................. 24
6.2.1.9 Company panel ............................................................................... 24
6.2.1.10 Company register ............................................................................ 24
6.2.1.11 Company login................................................................................... 25
6.2.1.12 Connect.php .................................................................................... 26
6.2.1.13 Db_con.php ..................................................................................... 26
6.2.1.14 Mainpage.php ..................................................................................... 26
6.2.2 Database: SQL Files ...................................................................................... 27
6.2.2.1 Campus ........................................................................................... 27
6.2.2.2 Calendar .......................................................................................... 29
7 Testing 30
7.1 Test Cases ...................................................................................................................30
7.2 Type of Testing used .................................................................................................. 30
8 Results and Discussions 32
9 Conclusion and Future Scope 33

9.1 Conclusion....................................................................................................................... 33
9.2 Future Scope ............................................................................................................... 33
VI
List of Figures
3.1 Use-Case diagram for CRS . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
4.1 Entity-Relationship diagram for CRS . . . . . . . . . . . . . . . . . . . . . . 9

4.2 Activity diagram for CRS .......................................................................................... 10
4.3 Level 0 DFD ................................................................................................................... 11
4.4 Level 1 DFD ................................................................................................................... 11
4.5 Level 2 DFD ................................................................................................................... 12
4.6 Timeline Chart ........................................................................................................... 13
5.1 Project ow of Campus Recruitment System ........................................................14

5.2 Homepage of CRS.......................................................................................................... 15
5.3 Admin login of CRS ...................................................................................................... 15
5.4 Student login of CRS .................................................................................................... 16
5.5 Company login of CRS ................................................................................................. 17
5.6 CV format of CRS ..................................................................................................... 17
5.7 Chatbox of CRS ......................................................................................................... 18
VII
List of Tables
7.1 Test case for login page .................................................................................................. 30

7.2 Test case for home page ................................................................................................. 30
VIII
Chapter 1
Introduction
Campus Recruitment Website provides online help to the users all over the world. Using
web recruitment systems like recruitment websites or jobsites also play a role in simplifying
the recruitment process.
1.1 Description
The Project titled Campus Recruitment System (CRS) is one which helps out the HR
Personal in the recruitment of new candidates to the company and helps the recruitment
process as a whole. A college CRS consists of a student login, company login and an admin
login. This project is bene cial for college students, various companies visiting the campus
for recruitment and even the college placement o cer. The said software system allows the
students to create their pro les and upload all their details including their marks onto the
system.The admin can check each student details and can remove faulty accounts. This
system also consists of a company login where various companies visiting the college can
view a list of students in that college and also their respective resumes. This software system
allows students to view a list of companies who have posted for vacancy. The admin has
overall rights over the system and can moderate and delete any details not pertaining to
college placement rules. This system handles student as well as company data and e ciently
displays all this data to respective sides. This system also contains discussion page where
many people could discuss or chat on multiple topics.
1.2 Problem Formulation

In an earlier times CRS processes were used to be manual . The administrator has to refer
all the records kept for years ago to simply know the details. This is very tedious. There
are many limitations for the existing systems. In manual campus placement, all the work
1
CHAPTER 1. INTRODUCTION
done manually so there were many chances of getting errors. The interface of student and
administer is maximum which makes the system time consuming. Students created and
submitted their CVs early in the year, leaving them frozen in time. Lists were produced
for each company, and students had to regularly travel in to review the notice board. The
process is to slow and consumes valuable academic time that was diverted from activity which
is more useful. The college records are stored and modi ed in excel sheets hence sorting is
a problem. Searching were used to done manually based on the company criteria Training
and Placement O cers (TPO) will identify the eligible student by ltering the excel sheet.
TPO has to see each and every student marks and their eligibility. No searching method is
provided.The student will get notify through traditional notice board only. There may be
chances of loss of opportunity. The students were not being made aware of the TPO activity.
For communication ,one has to go to TPO personally to obtain relevant information such as
company question paper,job details,which is not available with the student.
1.3 Motivation
Computer based information system is designed to improve existing system. The information
that TPO has to pass to the students can be conveyed online.Such compuer based system
provides following features:
• Improves accuracy in result.
• It has user-friendly interface having quick authenticated access to documents.
• It provides the facility of maintaining the details of the students.
• It will reduce the paper work and utilize the maximum capabilities of the setup and
organization as well as it will save time and money, which are spending in making
reports and collecting data.
• It can be access throughout the organization and outside as well with proper login
provided.
• This system can be used as an application for college to manage the student information
concerning placement.
• Helps company coming for campus recruitment to see student details. Before coming
for campus, company can get information about eligible students along with interested
students.
• This project can be used very easily in the process of decision making in new recruit-
ments.
• E ective way of providing communication between job providers and job seekers.
• Reliable and consistent way of searching jobs.
• Conducting secured and restricted online exam for screened employees.
2
1.4. PROPOSED SOLUTION
1.4 Proposed Solution

The proposed CRS meant to give more easiness to the users that they can add and re-
trieve information so quickly. Once you open this web application at the front end all the
schedule/events are available to everyone. Also in the every current student login this sched-
ule/events are available. There are mainly three types of users they are Student, TPO of the
college, and Companies. The administrator is the master user; he gets the most number of
priorities than the other users. The di erent functions involve the case of an administrator
are updating, approval. The administrator can view and approve the various application
forms.
Students can review and enter information around the clock and from any location. Students
can register themselves and ll up general details with academic scores, and update them
constantly. Students can very exibly search for and View Company and vacancy details,
and apply to vacancies by attaching. Students on placement will also use the system to
read important announcements, to obtain information on assessment, to see the results of
assessments recorded in the system.
When TPO rst login, they see all the recently changed / created companies and vacancies.
Like other users, they can examine any vacancy on the system. Of course, they can also
search for vacancies via exible forms. Strict policy based security de nes an upper limit
on the allowed activities of a given admin user like TPO. TPO can gather information on
all students for which they have appropriate permissions; this can be on an individual or
group basis, they can also export a spreadsheet of important statistics on a group for further
or detailed analysis. At a glance the system status page reveals a great deal of information
about the most recent usage of the system.
1.5 Scope of the Project

This system is useful for the college campus recruitment process. The system will be helpful
for training and placement department to shortlist students in advance and prepare students
for placements. The system will be helpful to the students to get a rough idea about their
CV. This system will help students to get an idea of placement process from past reviews.
3
Chapter 2
Review of Literature
Earlier recruitment was done manually and it was all at a time consuming work. Now it is all
possible in a fraction of second. It is all done online without much time consuming. Today's
recruitment applications are designed to do a whole lot more than just reduce paperwork.
They can make a signi cant contribution to a company's marketing and sales activity. Re-
cruitment websites and software make possible for managers to access information that is
crucial to managing their sta , which they can use for promotion decisions, payroll consid-
erations and succession planning. Campus Recruitment Website provides online help to the
users all over the world. Using web recruitment systems like recruitment websites or jobsites
also play a role in simplifying the recruitment process. Such websites have facilities where
prospective candidaes can upload their CV's and apply for jobs suited to them. Such sites
also make it possible for recuiters and companies to post their sta requirements and view
pro les of interested candidates[1].
Recruitment is done manually. These tasks are time consuming. It may take one month
or long. People around the world cannot apply. Online Recruitment system very convenient
because in the manual system there are lot of di culties in conducting and managing a
recruitment exam, short listing, maintaining sta etc. Campus Management system (CRS)
project which relates to HRMS department will maintain entire recruitment service and
provide services for job vacancies. This website allows companies to post job vacancies with
respect to the subject on which they are looking for employs and job seekers need to log in
to their account with given login and password and check job vacancies[2]. Job seekers can
check there job application status from their account. This project will provide scope for
future development[3].
PHP supports a large number of major protocols such as POP3, IMAP, and LDAP. PHP4
added support for Java and distributed object architectures (COM and CORBA), making n-
tier development a possibility for the rst time. PHP performs system functions, i.e. from
les on a system it can create, open, read, write, and close them. The other uses of PHP
are: PHP can handle forms, i.e. gather data from les, save data to a le, thru email you
can send data, return data to the user. You add, delete and modify elements within your
4
database thru PHP. Access cookies variables and set cookies.Using PHP, you can restrict
users to access some pages of your website.It can encrypt data. In order to develop and run
PHP Web pages, three vital components need to be installed on your computer system.
• Web Server - PHP will work with virtually all Web Server software, including Mi-
crosoft's Internet Information Server (IIS) but then most often used is freely available
Apache Server.
• Database - PHP will work with virtually all database software, including Oracle and
Sybase but most commonly used is freely available MySQL database.
• PHP Parser - In order to process PHP script instructions, a parser must be installed
to generate HTML output that can be sent to the Web Browser.
5
Chapter 3
System Analysis
3.1 Functional Requirements

• Administrator should have access to all details of the system.
• Administrator will train the system and generate rules-set.
• User can register into the system.
• User can login into system any time and give input to system.
3.2 Non Functional Requirements

• The system should provide the accurate estimated output to the user.
• The system should be able to increase the e ciency and performance of prediction
results.
• The system should allow user to access information in anywhere with anytime.
3.3 Speci c Requirements

3.3.1 Hardware Requirements
• i3 Processor Based Computer
• 1 GB RAM
• 50 GB Hard Disk
• Monitor
• Internet Connection
6
3.3. SPECIFIC REQUIREMENTS
3.3.2 Software Requirements

• Windows 7 or higher.
• WAMP Server
• Notepad++.
• My SQL 5.6.
7
CHAPTER 3. SYSTEM ANALYSIS
3.4 Use Case
Figure 3.1: Use-Case diagram for CRS
Description: In this use-case, shown in Figure 3.1, there are three actors- Admin, Company,
Student. Admin will be able to Login to system, send noti cations, Manage students, reply
queries, manage company details, View student details. Student will be able to post queries,
manage pro le, view company details. Company will be able to post vacancies and post
eligibility criteria.
8
Chapter 4
Analysis Modeling
4.1 Data Modeling
Figure 4.1: Entity-Relationship diagram for CRS
Description: The Entity-Relationship diagram shown in Figure 4.1 shows the relationship
between the main components and features of CRS. Student, company and admin can login
into the system. New user needs to register rst and then they can login using their user id
and password.
9
CHAPTER 4. ANALYSIS MODELING
4.2 Activity Diagram
Figure 4.2: Activity diagram for CRS
Description: In this activity diagram, shown in Figure 4.2, there are three main roles- Ad-
min, Student and company. Admin will be able to Login in to the system. After login, Admin
can send noti cations and acknowledgements. Students can ll details, receive acknowledge-
ment, view company details, view vacancies, select companies. After lling up data, admin
can display study material, display schedule, generate company speci c CV. Companies can
receive CV of students, conduct test, admin updates the database.
10
4.3. FUNCTIONAL MODELING
4.3 Functional Modeling

4.3.1 Level 0 DFD
Figure 4.3: Level 0 DFD
Description: The DFD, shown in Figure 4.3, gives an overview of information sharing
between the user and the database. The required information is fetched from the database
and returned back to the user.
4.3.2 Level 1 DFD
Description: The above Figure 4.4 shows the Level 1 DFD for the CRS. It gives a detailed
information of data sharing between user and database. User requests a query to the CRS
11
CHAPTER 4. ANALYSIS MODELING
database, database checks for relevant data and if present , returns it back to the user.
4.3.3 Level 2 DFD
Description: The above Figure 4.5 shows the Level 2 DFD for the CRS. User requests a
query to the database. System accepts user query and checks in the database for availability
of information in the database and processes the query and data is returned back to the user.
12
4.4. TIMELINE CHART
4.4 Timeline Chart
Figure 4.6: Timeline Chart
Description: The above Figure 4.6 shows the timeline chart of our project. It shows a
series of events in chronological order over a linear timescale. It makes it easy to understand
critical milestones, such as the progress of a project schedule with the help of timeline chart.
13
Chapter 5
Design
5.1 Architectural Design
Figure 5.1: Project ow of Campus Recruitment System
Description: The above Figure 5.1 shows the owchart of the CRS. In our project, there are
three actors- Admin, Company and Student. Each actor need to register themselves in the
system. After that, each will be able to login with their unique login IDs. After Admin logs
in, he will be able to view all the registered students, view company details, insert eligibility
criteria of the companies, display the list of eligible students and send noti cations about
interview schedules, etc. After Students login, they will be able to insert or update pro le
data, view details of company, view noti cations sent by the Admin, post queries related to
placements.
14
5.2. USER INTERFACE DESIGN
5.2 User Interface Design
Figure 5.2: Homepage of CRS
Description: The homepage shown in Figure 5.2 is the main page of the CRS. It consist of
three buttons: Admin login, Student login, Company login, TnP Schedule and FAQ.
Figure 5.3: Admin login of CRS

15
CHAPTER 5. DESIGN
Description: The admin login page shown in Figure 5.3 allows the administrator or the
TPO to login and manage student and company data. We can redirect it to home page
also.
Figure 5.4: Student login of CRS
Description: The student login page shown in Figure 5.4 allows the student to login and
view company details and generate their CV. If student has not register they can register
the portal. this page can redirect to main page.
16
5.2. USER INTERFACE DESIGN
Figure 5.5: Company login of CRS
Description:The company login page shown in Figure 5.5 allows the company to login and
view student details and view their CV.If student has not register they can register the portal.
this page can redirect to main page.
Figure 5.6: CV format of CRS
Description: The above Figure 5.6 shows the format of the CV of CRS. The CV has a
standard format.
17
CHAPTER 5. DESIGN
Figure 5.7: Chatbox of CRS
Description: The above Figure 5.7 shows the chatbox of CRS. Chatbox allows us to ask
queries or doubts to other users who are logged in.
18
Chapter 6
Implementation
6.1 Technologies Used

PHP:
• PHP can handle forms, i.e. gather data from les, save data to a le, thru email you
can send data, return data to the user.
• You add, delete and modify elements within your database thru PHP.
• Access cookies variables and set cookies.
• Using PHP, you can restrict users to access some pages of your website.
• It can encrypt data.
Environment Setup
In order to develop and run PHP Web pages, three vital components need to be installed
on your computer system.
Web Server - PHP will work with virtually all Web Server software, including Microsoft's
Internet Information Server (IIS) but then most often used is freely available Apache Server.
Database - PHP will work with virtually all database software, including Oracle and
Sybase but most commonly used is freely available MySQL database.
PHP Parser - In order to process PHP script instructions, a parser must be installed
to generate HTML output that can be sent to the Web Browser.
WAMP is a Windows OS based program that installs and con gures Apache web server,
MySQL database server, PHP scripting language, phpMyAdmin (to manage MySQL database's),
and SQLiteManager (to manage SQLite database's). WAMP is designed to o er an easy way
to install Apache, PHP and MySQL package with an easy to use installation program instead
of having to install and con gure everything yourself. WAMP is so easy because once it is
installed it is ready to go. You don't have to do any additional con guring or tweaking of
19
CHAPTER 6. IMPLEMENTATION
any con guration les to get it running. There are usually two reasons why someone chooses
to install WAMP. They are looking to install WAMP for development purposes or to run
their own server.
PHP Admin
Allows you to change or add users and for making new databases phpMyAdmin is a free
software tool written in PHP, intended to handle the administration of MySQL the World
Wide Web. phpMyAdmin supports a wide range of operations with MySQL.
SQL Server and Database System
SQL Server is a relational database management system from Microsoft that's designed
for the enterprise environment. SQL Server runs on T-SQL (Transact -SQL), a set of pro-
gramming extensions from Sybase and Microsoft that add several features to standard SQL,
including transaction control, exception and error handling, row processing, and declared
variables.
Using WAMP as a Development Server
You can use WAMP to develop and test websites locally on their own computer instead
of having to get a web hosting account to develop with. Most people will be using WAMP
for development purposes such as learning how to create websites with HTML, PHP, and
MySQL.
Using WAMP as a Production Server
WAMP was designed to be a testing and development server, not an actual production
server. WAMP does not come with any real security in place so it o ers no protection from
any kind of attack. Any 10 year old with access to the internet can easily hack your WAMP
server. If your website(s) have highly sensitive data (such as credit card numbers, social
security numbers, user ids, passwords, etc.), you need to take this in consideration before
your put this information online. Unless you are an experienced system administrator and
can con gure WAMP to be more secure, you should never user WAMP for a production
server.
6.2 Working of Project
• Admin Login: Here, the admin of the Campus Recruitment website put his credentials
in the Login page.
• Student Login: Here, the student of the Campus Recruitment website put his cre-
dentials in the Login page.
20
6.2. WORKING OF PROJECT
• Company Login: Here, the company of the Campus Recruitment website put their
credentials in the Login page.
• Company views student data: Here, various company's views data of students to
recruit them.
• Student can view company data: Here, various students views data of companies
and apply accordingly.
• Forum: Here, people could discuss on multiple topic and share their views or chat
with other people.
• Admin dashboard: Here, admin has overall functional rights to modify data &
manage it.
• Appropriate data processing and handling: After ring any of the query by
admin/students/companies, appropriate data is processed and handled.
• Chatbox: In chatbox, anyone can ask question to admin. Anyone can answer the
query.
6.2.1 PHP Codes
6.2.1.1 1.About.php
<html>
<head>
<body background="images\b.png"> <link rel="stylesheet" href="style1.css">
<title>Main Page</title> </head> <?php include("banner.php")?>
<form>
<table width="90%" border="1" height="60%" align="center" cellpadding="0" cellspac-
ing="0">
<tr><td width="25%"><table align="center" border="0" width="90%" height="60%">
<tr align="center"> <td> <label><a href="about.php" class="sty3"> About us </la-
bel></br>
<a href="faq.php" class="sty3">FAQ</label></td></tr> </table> </td> <td class="style4">
</table>
</form>
</body>
<?php include("footer.php")?> </html>
21
6.2.1.2 Add event.php

<?php
require_once('bdd.php');
if (isset($_POST['title']) && isset($_POST['start']) && isset($_POST['end']) && is-
set($_POST['color'])){
$title = $_POST['title']; $start = $_POST['start']; $end = $_POST['end']; $color =
$_POST['color'];
$sql = "INSERT INTO events(title, start, end, color) values ('$title', '$start', '$end',
'$color')";
//$req = $bdd->prepare($sql); //$req->execute(); echo $sql;
$query = $bdd->prepare( $sql ); if ($query == false) { print_r($bdd->errorInfo()); die
('Erreur prepare');
} $sth = $query->execute(); if ($sth == false) { print_r($query->errorInfo()); die ('Er-
reur execute'); }
} header('Location: '.$_SERVER['HTTP_REFERER']);
?>
6.2.1.3 Add notice.php

<html>
<link rel="stylesheet" href="style1.css"> <body background="images\adbg.png">
<?php include("banner.php"); include("menu2.php"); include("connect.php"); ?>
<body background="images\b.png"> <form method="post" enctype="multipart/form-
data"> </br></br>
<table align="center" border="0" width="30%" height="30%" cellspacing="0" cell-
padding="0">
<tr><td colspan="2" class="carth" ><center><h2><u>Add Internship Notice</u></h2>
<td class=" style1" align="right">Title </td> <td><input type="text" name="title"
></td>
</tr> <tr> <td class=" style1" align="right"> Notice </td> <td><input
type=" le" name="image">
<tr align="center"> <center><td align="center" colspan="2"><input type="submit"
class="bulk5" value="Submit"
</center> </tr> </table> <?php if(isset($_POST['subm'])) { $var="select max(nid)
as max from notice";
$nid=""; if(mysqli_num_rows($res)== 0) { $nid="101"; } else { $nid = $row['max'] +
1; }
$ le=$_FILES['image']['tmp_name']; echo $iname=$_FILES['image']['name']; if(isset($iname))
if(move_uploaded_ le($ le, $location.$iname)) { //echo 'uploaded'; } } } else { //echo
'please upload'; }
$sql="Insert into notice values('$nid','$title','$iname','$date')"; if(mysqli_query($con,$sql))
else { echo"<script>alert('Not Added')</script>"; } }
?> <?php include("footer.php")?></form></body></html>
22
6.2.1.4 Adlogout.php
<?php session_start(); session_destroy(); header("Location:mainpage.php"); ?>
6.2.1.5 Adminlogin.php
<html> <link rel="stylesheet" href="style1.css"> <?php include("banner.php");?> <body
background="images\adbg.png">
<table border="0" align="center" cellspacing="0" cellpadding="0" width="20%" height="20%">
<h2><u>ADMIN LOGIN</u></h2></td></tr> <tr> <td class=" style1" align="right">
<input type="text" name="uname" required></br></br></td> </tr><tr align="center">
<td class=" style1" align="right">Password </br></br></td> <td align="left">
<input type="password" name="pass" required></br></br></td> </tr>
<tr align="center"> <td colspan="2"><input class="bulk5" type="submit" value="LOGIN"
name="login">
</br></br></br></br> <?php include("footer.php")?> </body> </html>
<?php if(isset($_POST['login'])) { include("connect.php"); $uname=$_POST['uname'];
$pass=$_POST['pass'];
$sel="select username,password from admin where username='$uname' and password='$pass'";
$result=$con->query($sel);
if($row=mysqli_fetch_array($result))
{ header("Location:adminpanel.php"); session_start(); $_SESSION['ad']='Admin'; $ad=
$_SESSION['ad']; }
else { echo "<script>alert('Invalid Username or Password');</script>";
} }?></body> </html>
6.2.1.6 Adminpanel.php
<form> <table align="center" width="70%" height="40%"> <tr align="center" class="carth">
<td><h2>Welcome to Admin Panel
</form> </body> <?php include("footer.php")?></html>
6.2.1.7 Banner.php
<html> <link rel="stylesheet" href="style1.css">
<script id="cid0020000181875088747" data-cfasync="false" async src="//st.chatango.com/js/gz/emb.js"
{"handle":"campusplacements","arch":"js",
"styles":{"a":"CC0000","b":100,"c":"FFFFFF","d":"FFFFFF"
"n":"FFFFFF","p":"10","q":"CC0000","r":100,
"pos":"br","cv":1,"cvbg":"CC0000","cvw":75,"cvh":30,"fwtickm":
<table align="center" width="90%" height="20%">
<tr> <td width="100%" height="100%"> <center>
23
6.2.1.8 Companydetails
<html> <link rel="stylesheet" href="style1.css"> <body background="images\adbg.png">
<?php include("banner.php"); include("menu.php");
include("connect.php"); include("searchcmp.php");
$rel=$con->query($sel); if(mysqli_num_rows($rel)== 0) {
echo "<script>alert('No data found');</script>"; } else
{ echo " <label class='carth' ><center><h2><u>
Company Details</u></h2></center></label>
align='center' width='70%' height='15%'> <th class='style2'>Company Id</th> <th
class='style2'>
<th class='style2'>HR Name</th> <th class='style2'>
Contact</th> <th class='style2'>Email</th> ";
<td class='style1' width='15%'>".$data['id']."</td>
<td class='style1' width='15%'>".$data['hr']."</td>
</td> <td class='style1' width='15%'>".
</table></br></br></br></br> <center> <form action="cmpdet.php" method="post">
<input type="text" name="search">
<input type="submit" value=">>"/>
6.2.1.9 Company panel

<html> <link rel="stylesheet" href="style1.css"> <body background="images\adbg.png">
<?php include("banner.php"); include("menu1.php"); include("connect.php"); session_start();
$cid= $_SESSION['cid'];
$sel="select cname from cmpreg where id='$cid'"; $rel=$con->query($sel); $data=$rel-
>fetch_assoc(); echo "
<table align='center' width='70%' height='40%'> <tr class='carth'> <td><h1>Welcome
To ".$data['cname']."
<?php include("footer.php"); ?> </body> </html>
6.2.1.10 Company register

<html> <link rel="stylesheet" href="style1.css"> <body>
<?php include("banner.php"); include("connect.php"); $var="select max(id) as max
from cmpreg"; $res=$con->query($var);
$row = mysqli_fetch_assoc($res);$cid = $row['max'] + 1;
?> <body background="images\b.png"> <form method="Post" >
<table align="center" border="0" width="60%" height="60%" cellspacing="0" cell-
padding="0">
<tr><td colspan="2" class="carth" ><center><h2><u>Company Register</u></h2>
<tr> <td align="right" class="style1">Company Name    </td>
<td align="left">
<input type="text" name="cname" pattern="[a-zA-Z' ']*$" title="Plz Enter Charac-
ters Only" required></td> </tr>
24
<tr> <td align="right" class="style1">Established Year    </td>

<td align="left">
<input type="text" name="est" pattern="[0-9]{4}" title="Plz Enter Valid year" re-
quired></td> </tr>
<tr> <td align="right" class="style1">EmailId    </td> <td align="left">
<tr> <td align="right" class="style1">Contact No    </td> <td
align="left">
<input type="text" name="cont" pattern="[0-9]{10}" title="Plz Enter Valid Contact
No" required></td> </tr>
<tr> <td align="right" class="style1">HR Name    </td> <td align="left">
<input type="text" name="hr" pattern="[a-zA-Z' ']*$" title="Plz Enter Characters
Only" required></td> </tr>
<tr> <td align="right" class="style1">Company Id    </td> <td
align="left">
<input type="text" style="background-color:lightgrey; font-weight:bold" name="id" value="<?php
echo $cid ?>" disabled></td> </tr>
<tr align="center"> <center><td align="center" colspan="2"><input type="submit"
class="bulk5" value="Register" name="reg">
</td></center> </tr> </table></br></br> <?php include("footer.php");?>
<?php if(isset($_POST['reg'])) {
$cname=$_POST['cname']; $est=$_POST['est']; $cont=$_POST['cont']; $email=$_POST['email'];
$hr=$_POST['hr'];
$username=$_POST['username']; $pass=$_POST['pass'];
$sql="Insert into cmpreg values('$cname','$est','$email','$cont','$hr','$cid','$username','$pass')";
if(mysqli_query($con,$sql))
{ echo "<script>alert('Register succesfully');</script>"; echo "<script>
location.replace('companylogin.php')</script>" ; } else { echo"<script>
alert('Plz Try Again')</script>"; } }?></form></body></html>
6.2.1.11 Company login

<html> <link rel="stylesheet" href="style1.css"> <?php include("banner.php");?> <body
background="images\adbg.png">
<form method="POST"><table border="0" align="center" cellspacing="0" cellpadding="0"
width="25%" height="20%">
<tr><td colspan="2" class="carth" ><center><h2><u>COMPANY LOGIN</u></h2>
<td class=" style1" align="right">Username </br></br></td> <td>
<tr align="center"> <td class=" style1" align="right">Password </br></br></td>
<td>
<input type="password" name="pass" required>
<tr align="center"> <td colspan="2"><input type="submit" class="bulk5" value="LOGIN"
<td colspan="2" style="text-align:center; color:white;font-size:17px">Not a Member?
<a href="cmpreg.php">Register Now</a>/<a href="mainpage.php">Go back</td>
</tr></table> </br></br>
</br></br> <?php include("footer.php");?><?php if(isset($_POST['login']))
{ $uname=$_POST['uname']; $pass=$_POST['pass']; include("connect.php");
25
$sel="select username,pass,id,cname from cmpreg where username='$uname' and pass='$pass'";

$result=$con->query($sel);
if($row=mysqli_fetch_array($result))
{header("Location:cmppanel.php");session_start();$_SESSION['cid']=$row['id'];$cid= $_SES-
SION['cid'];
$_SESSION['cname']=$row['cname']; $cname= $_SESSION['cname']; }
6.2.1.12 Connect.php
<?php $con=mysqli_connect("localhost","root","","campus")or die("could not connect");?>
6.2.1.13 Db_con.php
<?php
$DB_host = "localhost"; $DB_user = "root"; $DB_pass = ""; $DB_name = "campus";
try { $db_con = new PDO("mysql:host={$DB_host};dbname={$DB_name}",$DB_user,$DB_pass);
$db_con->setAttribute(PDO::ATTR_ERRMODE, PDO::ERRMODE_EXCEPTION);
}
catch(PDOException $e) { echo "ERROR : ".$e->getMessage(); } ?>
6.2.1.14 Mainpage.php
<html> <head> <link rel="stylesheet" href="style1.css"> <title>Main Page</title> </head>
<?php include("banner.php")?>
<body background="images\backg.png"> <form>
<table width="90%" border="0" height="60%" align="center" cellpadding="0" cellspac-
ing="0">
<td><td width="25%"> <table align="center" border="0" width="90%" height="60%">
<a href="index.php" class="sty3">TnP Schedule</label></br></br></br> <label>
<a href="faq.php" class="sty3">FAQ</label></td></tr> </table> </td> <td>
<table align="center" border="0" width="60%"> <tr align="center"><td class="style4">Welcome
To The Campus</td>
<tr align="center"><td style="text-align:center; color:white;font-size:20px">Get Your
DreamJob Today</td>
<table border="0" align="center" width="70%" height="50%" cellspacing="0" cell-
padding="0"> <tr> <td>
<center><a href="adminlogin.php" class="style3">Admin Login</a></center>
</td> <td class="style3"> <center> <a href="studentlogin.php" class="style3">Student
Login</a>
<center> <a href="companylogin.php" class="style3">Company Login</a> </cen-
ter> </td>
</form> </body> <?php include("footer.php")?> </html>
26
6.2.2 Database: SQL Files
6.2.2.1 Campus
-- phpMyAdmin SQL Dump
-- version 4.6.4
-- https://www.phpmyadmin.net/
--
-- Host: 127.0.0.1
-- Generation Time: Feb 21, 2018 at 08:56 AM
-- Server version: 5.7.14
-- PHP Version: 5.6.25
SET SQL_MODE = "NO_AUTO_VALUE_ON_ZERO";
SET time_zone = "+00:00";
/*!40101 SET @OLD_CHARACTER_SET_CLIENT=@@CHARACTER_SET_CLIENT
*/;
/*!40101 SET @OLD_CHARACTER_SET_RESULTS=@@CHARACTER_SET_RESULTS
*/;
/*!40101 SET @OLD_COLLATION_CONNECTION=@@COLLATION_CONNECTION
*/;
/*!40101 SET NAMES utf8mb4 */;
--
-- Database: `campus`
--
-- -- Table structure for table àdmin` --
CREATE TABLE àdmin` ( ùsername` varchar(50) NOT NULL, `password` varchar(50)
NOT NULL ) ENGINE=InnoDB DEFAULT CHARSET=latin1;
-- -- Dumping data for table àdmin` --
INSERT INTO àdmin` (ùsername`, `password`) VALUES ('123', '123');
-- --------------------------------------------------------
-- -- Table structure for table `cmpreg` --
CREATE TABLE `cmpreg` ( `cname` varchar(40) NOT NULL, èst` varchar(30) NOT
NULL, èmail` varchar(30) NOT NULL, `contact` varchar(10) NOT NULL,
`hr` varchar(40) NOT NULL, ìd` varchar(10) NOT NULL, ùsername` varchar(40) NOT
NULL, `pass` varchar(40) NOT NULL ) ENGINE=InnoDB DEFAULT CHARSET=latin1;
-- -- Dumping data for table `cmpreg` --
INSERT INTO `cmpreg` (`cname`, èst`, èmail`, `contact`, `hr`, ìd`, ùsername`, `pass`)
VALUES ('Infosys', '1990', 'info@gmail.com', '9892823644', 'abc', '101', 'abc', 'abc'),
('Accenture', '1980', 'accenture@gmail.com', '9898231234', 'heena', '102', '567', '567'),
('Techm', '1998', 'Techm@gmail.com', '9892823641', 'Leena', '103', 'tech', 'tech');
-- --------------------------------------------------------
-- -- Table structure for table `comments` --
CREATE TABLE `comments` ( `cmid` varchar(50) NOT NULL, `cid` varchar(50) NOT
NULL, ùid` varchar(50) NOT NULL, `comm` varchar(500) NOT NULL,
`date` varchar(50) NOT NULL ) ENGINE=MyISAM DEFAULT CHARSET=latin1;
-- -- Dumping data for table `comments` --
27
INSERT INTO `comments` (`cmid`, `cid`, ùid`, `comm`, `date`) VALUES ('101', '101', '1',
'Study Basic Oops concepts and Sql queries', '30-1-2018'),
('101', '102', '2', 'Study Data Structures also along with basic Oops concepts', '30-1-
2018'), ('101', '103', '3', 'dfdfs', '2018-01-30'), ('101', '104', '3', 'afdg', '2018-01-30'),
('101', '105', '3', 'dfgdfg', '2018-02-17');
-- --------------------------------------------------------
-- -- Table structure for table `notice` --
CREATE TABLE `notice` ( `nid` varchar(20) NOT NULL, `title` varchar(300) NOT
NULL, ` le` varchar(200) NOT NULL,
`date` varchar(30) NOT NULL ) ENGINE=MyISAM DEFAULT CHARSET=latin1;
-- -- Dumping data for table `notice` --
INSERT INTO `notice` (`nid`, `title`, ` le`, `date`) VALUES ('101', 'sdas', 'Project-synopsis.pdf',
'2018/01/27'), ('102', 'sfsdf', 'Project-synopsis.pdf', '2018/01/30'),
('103', 'dfgdf', 'Project-synopsis.pdf', '2018/01/30'), ('104', 'fgdg', 'Project-synopsis.pdf',
'2018/01/30'), ('105', , , '2018/01/30');
-- --------------------------------------------------------
-- -- Table structure for table `stureg` --
CREATE TABLE `stureg` ( `sid` int(10) NOT NULL, `fname` varchar(40) NOT NULL,
`mname` varchar(40) NOT NULL, `lname` varchar(40) NOT NULL,
`gender` varchar(40) NOT NULL, èmail` varchar(40) NOT NULL, `contact` varchar(10)
NOT NULL, `city` varchar(40) NOT NULL,
àddress` varchar(100) NOT NULL, ìmage` varchar(40) NOT NULL, `dob` varchar(20)
NOT NULL, àge` varchar(10) NOT NULL,
`school` varchar(40) NOT NULL, `ssc` oat NOT NULL, `yr1` varchar(11) NOT NULL,
ùni1` varchar(40) NOT NULL, `jclg` varchar(40) NOT NULL,
`hsc` oat NOT NULL, `yr2` varchar(11) NOT NULL, ùni2` varchar(40) NOT NULL,`dclg`
varchar(40) NOT NULL, `dep` varchar(40) NOT NULL,
àgg` oat NOT NULL, `yr3` varchar(11) NOT NULL, ùni3` varchar(40) NOT NULL,
èxtra` varchar(60) NOT NULL, `quali` varchar(40) NOT NULL, ùsername` varchar(40)
NOT NULL,
`password` varchar(40) NOT NULL ) ENGINE=InnoDB DEFAULT CHARSET=latin1;
-- -- Dumping data for table `stureg` --
INSERT INTO `stureg` (`sid`, `fname`, `mname`, `lname`, `gender`, èmail`, `contact`, `city`,
àddress`, ìmage`, `dob`, àge`, `school`, `ssc`, `yr1`, ùni1`,
`jclg`, `hsc`, `yr2`, ùni2`, `dclg`, `dep`, àgg`, `yr3`, ùni3`, èxtra`, `quali`, ùsername`,
`password`) VALUES (3, 'Mandar', 'P', 'Sawant', 'Male', 'mandar@gmail.com',
'9892823644', 'goregaon', 'mumbai', 'i1.png', '1990-01-10', '26', 'suvidya', 60, '2006', 'Uni-
versity of Mumbai', 'yojana', 67, '2008', 'University of Mumbai', 'sathaye',
'BSC.IT', 70, '2011', 'University of Mumbai', 'sports', 'computers', 'md', 'md'), (2, 'Poonam',
'P', 'Yadav', 'Female', 'abcd@gmail.com', '9892823612', 'mumbai', 'mumbai', 'i1.jpg',
'1992-10-01', '24', 'vidyamandir', 70, '2007', 'University of Mumbai', 'vivek', 76, '2009',
'University of Mumbai', 'vivek', 'BSC.IT', 65, '2015', 'University of Mumbai', 'coding', 'no',
'poonam', 'poonam'), (1, 'jyotsna', 't', 'desai', 'Female', 'abc@gmail.com', '9892823644',
'MUMBAI', 'mumbai', 'user.png', '1993-06-09', '22', 'abc', 88, '2008',
'mumbai', 'annn', 70, '2010', 'mumbai', 'aaaaa', 'MCA', 75, '2016', 'mumbai', 'qq', 'aaaa',
'username', 'pqr');
-- --------------------------------------------------------
28
-- -- Table structure for table `vacancy` --

CREATE TABLE `vacancy` ( `cid` varchar(10) NOT NULL, `cname` varchar(40) NOT
NULL, `job` varchar(40) NOT NULL, `salary` varchar(40) NOT NULL,
`criteria` varchar(100) NOT NULL, `bond` varchar(100) NOT NULL, èmail` varchar(40)
NOT NULL ) ENGINE=InnoDB DEFAULT CHARSET=latin1;
-- -- Dumping data for table `vacancy` --
INSERT INTO `vacancy` (`cid`, `cname`, `job`, `salary`, `criteria`, `bond`, èmail`) VALUES
('101', 'Infosys', 'Technical Support', '10000', '60', '1yr', 'infosys@gmail.com'),
('102', 'Accenture', 'Electrical Engineer', '30000', '50', '1yr', 'accenture@gmail.com');
-- -- Indexes for dumped tables --
-- -- Indexes for table `cmpreg` -- ALTER TABLE `cmpreg` ADD PRIMARY KEY (ìd`);
-- -- Indexes for table `comments` -- ALTER TABLE `comments` ADD PRIMARY KEY
(`cid`);
-- -- Indexes for table `notice` -- ALTER TABLE `notice` ADD PRIMARY KEY (`nid`);
-- -- Indexes for table `stureg` -- ALTER TABLE `stureg` ADD PRIMARY KEY (ùser-
name`);
-- -- Indexes for table `vacancy` -- ALTER TABLE `vacancy` ADD PRIMARY KEY (`cid`);
/*!40101 SET CHARACTER_SET_CLIENT=@OLD_CHARACTER_SET_CLIENT
*/;
/*!40101 SET CHARACTER_SET_RESULTS=@OLD_CHARACTER_SET_RESULTS
*/;
/*!40101 SET COLLATION_CONNECTION=@OLD_COLLATION_CONNECTION
*/;
6.2.2.2 Calendar
CREATE TABLE IF NOT EXISTS èvents` ( ìd` int(11) NOT NULL AUTO_INCREMENT,
`title` varchar(255) NOT NULL,
`color` varchar(7) DEFAULT NULL, `start` datetime NOT NULL, ènd` datetime DE-
FAULT NULL,
PRIMARY KEY (ìd`) ) ENGINE=InnoDB DEFAULT CHARSET=utf8 AUTO_INCREMENT=15
;
INSERT INTO èvents` (ìd`, `title`, `color`, `start`, ènd`) VALUES (1, 'All Day Event',
'#40E0D0', '2016-01-01 00:00:00', '0000-00-00 00:00:00'),
(2, 'Long Event', '#FF0000', '2016-01-07 00:00:00', '2016-01-10 00:00:00'), (3, 'Repeating
Event', '#0071c5', '2016-01-09 16:00:00', '0000-00-00 00:00:00')
(4, 'Conference', '#40E0D0', '2016-01-11 00:00:00', '2016-01-13 00:00:00'), (5, 'Meeting',
'#000', '2016-01-12 10:30:00', '2016-01-12 12:30:00'),
(6, 'Lunch', '#0071c5', '2016-01-12 12:00:00', '0000-00-00 00:00:00'), (7, 'Happy Hour',
'#0071c5', '2016-01-12 17:30:00', '0000-00-00 00:00:00'),
(8, 'Dinner', '#0071c5', '2016-01-12 20:00:00', '0000-00-00 00:00:00'), (9, 'Birthday Party',
'#FFD700', '2016-01-14 07:00:00', '2016-01-14 07:00:00'), (10, 'Double click to change',
'#008000', '2016-01-28 00:00:00', '0000-00-00 00:00:00')
29
Chapter 7
Testing
7.1 Test Cases
Table 7.1: Test case for login page

Test Description Expected Output Pass/Fail
1 Valid Login Id and Password Successful Login Pass
2 Invalid Login Id and Password Unsuccessful Login Pass
Table 7.2: Test case for home page

Test Description Expected Output Pass/Fail
1 Shortcut hyperlinks - Home and Logout Home will redirect to the home page Pass
2 Add user details User details added Pass
3 Account details Parameters added Pass
7.2 Type of Testing used

Since we are concerned with nal results (i.e. results and preventive measures) for that, we
have used black box testing methodology. The bene t of black box testing is that we do not
to worry about how code is running, but testing is done only for obtaining the correct output.
In our case, an input is given to system and the system presents us with the output. If the
system generates correct output we conclude that the system testing has passed.
Black Box Testing: Black box testing is a method of software testing that examines the
functionality of an application without peering into its internal structures or workings. This
method of test can be applied to virtually every level of software testing; unit, integration,
system and acceptance.
The steps involved in Testing are:
Unit Testing Unit testing focuses veri cation e orts on the smallest unit of the software
design, the module. This is also known as Module Testing . The modules are tested sepa-
rately. This testing carried out during programming stage itself. In this testing each module
is found to be working satisfactorily as regards to the expected output from the module.
30
7.2. TYPE OF TESTING USED
Integration Testing Data can be grossed across an interface; one module can have adverse
e orts on another. Integration testing is systematic testing for construction the program
structure while at the same time conducting tests to uncover errors associated with in the
interface. The objective is to take unit tested modules and build a program structure. All the
modules are combined and tested as a whole. Here correction is di cult because the isolation
of cause is complicate by the vast expense of the entire program. Thus in the integration
testing stop, all the errors uncovered are corrected for the text testing steps.
System Testing System testing is the stage of implementation that is aimed at ensuring
that the system works accurately and e ciently for live operation commences. Testing is
vital to the success of the system. System testing makes a logical assumption that if all the
parts of the system are correct, then goal will be successfully achieved.
Validation Testing At the conclusion of integration testing software is completely assem-

bled as a package, interfacing errors have been uncovered and corrected and a nal series of
software tests begins, validation test begins. Validation test can be de ned in many ways.
But the simple de nition is that validation succeeds when the software function in a manner
that can reasonably expected by the customer. After validation test has been conducted one
of two possible conditions exists.
31
Chapter 8
Results and Discussions
Result:
• Admin - The admin of the CRS put his credentials in the Login page. Admin can add
the details of company and student. Admin can have whole access of the system.so
that he can handle all the database and revert towards the query of the student and
company.
• Student -The student of the CRS put his credentials in the Login page. Student
can generate the CV and can take the print of the CV. Student can view the com-
pany details. If student have any query regarding placement, he or she can ask the
query through the chatbox.Student will get the noti cation of the events i.e. Campus
placement or Seminars regarding placement,etc. held in the college.
• Company - The company of the CRS put their credentials in the Login page.Company
can view the CV's of the students and shortlist them for the interview.
Discussion:
• The student panel allows the students to create their pro les and upload all their details
including their marks onto the system.
• The admin can check each student details and can remove faulty accounts.
• The system also consists of a company login where various companies visiting the college
can view a list of students in that college and also their respective resumes.
• The software system allows students to view a list of companies who have posted for
vacancy.
• The admin has overall rights over the system and can moderate and delete any details
not pertaining to college placement rules.
• The system handles student as well as company data and e ciently displays all this
data to respective sides.
• This system also contains forum page where many people could discuss or chat on
multiple topics.
32
Chapter 9
Conclusion and Future Scope
9.1 Conclusion
From a proper analysis of positive points and constraints on the CRS, it can be safely
concluded that the project CRS is a highly e cient GUI based component. This application
is working properly and meeting user requirements. This component can be easily plugged
in many other systems. Nowadays manual process of searching a job of one's choice as well
as searching the appropriate candidate for a speci c job has become a huge task and so
realizing the need for easy management of this process, the site has been developed. It is
very easy to update and maintain information through this site. The main features of this
site include exibility, ease of manipulation of information, easy access searching, storage,
reduction of manual work in an e cient manner, a quick, convenient, reliable, timely and
e ective way to reach recruiting, search and employment professionals worldwide and it is also
very economical. The project could very well be enhanced further as per the requirements.
9.2 Future Scope

This system is helpful for the college campus recruitment process for training and placement
department to shortlist students in advance and prepares students for placements. The
system will be helpful to the students to get a rough idea about their CV.
Goals:
• Reduced entry work.
• Easy retrieval of information
• Reduced errors due to human intervention
• User friendly screens to enter the data
• Portable and exible for further enhancement

33
CHAPTER 9. CONCLUSION AND FUTURE SCOPE
• Web enabled.
• Fast nding of information requested
34
Bibliography
[1] K.N.Prakash, N.Shwetha Lakshmi, K.Akshay, Mobile Operated Campus Application for
Retrival Of College Server Data Using Wi-Fi Connection , Advances in Computer Science
and its Applications, vol. 1, pp.104-110, 2012
[2] Mansi Gera, Shivani Goel, A Model for Predicting the Eligibility for Placement of Stu-
dents Using Data Mining Technique , International Conference on Computing, Commu-
nication and Automation, pp.114-117, 2015
[3] Praveen Rani, Dr. Rajan Vohra, Generating Placement Intelligence In Higher Educta-
tion Using Data mining , International Journal of Computer Science and Information
Technologies, vol.6(3), pg.2298-2302, 2015
35
BIBLIOGRAPHY
Acknowledgements
We hereby take the privilege to present our project report on Campus Recruitment
System . We are very grateful to our Project Supervisor Dr. Joanne Gomes and Ms.
Vandana Patil for contributing their valuable insight into the Project by taking the time
out from their busy and hectic schedule right from the project's inception, being after us like
true mentor and great academic parents. We are thankful to them for having instilled an
entrepreneurial zest within us so as to bring up this innovative idea and make it possible for
us to work on it.
We are very thankful to Project Coordinators Ms. Shree Jaswal & Ms. Amrita
Mathur whose guidance and support was an immense motivation for us to carry on with
our project. They have been a constant source of inspiration to us. Their suggestions have
greatly contributed for the betterment of our project.
We extend our hearty thanks to the sta members both teaching and non-teaching and
the Learning & Information Resource Center (LIRC) for their unconditional co-operation at
all times
36

Group No7 Campus Recruitment System PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Group No7 Campus Recruitment System PDF

Uploaded by

Copyright:

Available Formats

Campus Recruitment System

Submitted in partial fulfillment of the

requirements of the degree of

Kalyani Jadhav 151260

Priyanka Kate 141061

Neha Kotian 141090

Jayesh Sawant 141056

Dr. Joanne Gomes

Department of Information Technology

St. Francis Institute of Technology (Engineering College)

6.2.1.5 Adminlogin.php .................................................................................. 23

8 Results and Discussions 32

9 Conclusion and Future Scope 33

3.1 Use-Case diagram for CRS . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

4.1 Entity-Relationship diagram for CRS . . . . . . . . . . . . . . . . . . . . . . 9

5.1 Project ow of Campus Recruitment System ........................................................14

7.1 Test case for login page .................................................................................................. 30

1.2 Problem Formulation

1.4 Proposed Solution

1.5 Scope of the Project

3.1 Functional Requirements

• Administrator will train the system and generate rules-set.

• User can register into the system.

3.2 Non Functional Requirements

3.3 Speci c Requirements

3.3.2 Software Requirements

3.4 Use Case

Figure 3.1: Use-Case diagram for CRS

4.1 Data Modeling

Figure 4.1: Entity-Relationship diagram for CRS

4.2 Activity Diagram

Figure 4.2: Activity diagram for CRS

4.3 Functional Modeling

Figure 4.3: Level 0 DFD

4.3.2 Level 1 DFD

Figure 4.4: Level 1 DFD

4.3.3 Level 2 DFD

Figure 4.5: Level 2 DFD

4.4 Timeline Chart

Figure 4.6: Timeline Chart

5.1 Architectural Design

Figure 5.1: Project ow of Campus Recruitment System

5.2 User Interface Design

Figure 5.2: Homepage of CRS

Figure 5.3: Admin login of CRS

Figure 5.4: Student login of CRS

Figure 5.5: Company login of CRS

Figure 5.6: CV format of CRS

Figure 5.7: Chatbox of CRS

6.1 Technologies Used

• Access cookies variables and set cookies.

• It can encrypt data.

6.2 Working of Project

6.2.1 PHP Codes

6.2.1.2 Add event.php

6.2.1.3 Add notice.php

6.2.1.9 Company panel

6.2.1.10 Company register

<tr> <td align="right" class="style1">Established Year &nbsp;&nbsp;&nbsp;</td>

6.2.1.11 Company login

$sel="select username,pass,id,cname from cmpreg where username='$uname' and pass='$pass'";

6.2.2 Database: SQL Files

-- -- Table structure for table `vacancy` --

<tr> <td align="right" class="style1">Established Year </td>