KARNATAK UNIVERSITY, DHARWAD

C.S.I COLLEGE OF COMMERCE

DHARWAD

DEPARTMENT OF B.C.A (BACHELOR OF

COMPUTER APPLICATIONS)
2021-2024

INTERNSHIP REPORT ON
“Online Job Portal”

UNDER THE GUIDANCE OF:

MR. STEPHEN WILLIAMS

SUBMITTED BY
Shelton Victor Coutinho
UUCMS No: U02AR21S0049
 C.S.I COLLEGE OF COMMERCE
DHARWAD

DEPARTMENT OF B.C.A (BACHELOR OF

COMPUTER APPLICATIONS)
2021-2024

INTERNSHIP REPORT ON
“Online Job Portal”

UNDER THE GUIDANCE OF:

MR. STEPHEN WILLIAMS

SUBMITTED BY
Shelton Victor Coutinho
UUCMS No: U02AR21S0049
 C.S.I., K.N.D., B.M.H.E.S. C’S
CSI COLLEGE OF COMMERECE, DHARWAD

DEPARTMENT OF B.C.A
(BACHELOR OF COMPUTER APPLICATIONS)
2021-2024

CERTIFICATE

This is to certify that Mr. Shelton Victor Coutinho has Satisfactorily

completed the internship work entitle “ONLINE JOB PORTAL” for the partial
fulfillment of degree in Bachelor of Computer Applications of Karnataka University,
Dharwad for the year 2018-2019.

Internship associate: Internship guide:

Shelton Coutinho Mr. Stephen Williams

Examiners
1………………..
2……………….. Co-Ordinator
 ACKNOWLEDGEMENT

We would like express our special gratitude to our principal Dr. Kamala Dhawale,
C.S.I College of Commerce, Dharwad, for her support and co-operation to take up this project.

Furthermore, we would also like to acknowledge with much appreciation the crucial role
of the staff who is also the head of the project Mr. Stephen Williams whose contribution in
stimulating suggestions and encouragement, helped us to coordinate and guiding us throughout
the internship which is on “ONLINE JOB PORTAL” and especially in this report.

We have to appreciate the guidance given by other supervisor as well as the panels
especially in our project presentation that has improved our presentation skills thanks to their
comment and advices.

We would like to express our deepest appreciation to all the staff of BCA department
who provided us the possibility to complete this report.

Date: Signature

Place: Dharwad SHELTON COUTINHO

 ABSTRACT

The purpose of “Online Job Portal System” is to automate the existing manual system by
the help of computerized equipment’s and full-fledge computer software, fulfilling their
requirements, so that their valuable data/information can be stored for a longer period with easy
accessing and manipulation of the same. The required software and hardware are easily available
and easy to work with.

“Online Job Portal System” is secure, reliable and fast management system. It can assist
the user to concentrate on their activities rather to concentrate on the record keeping. Thus, it will
help organization in better utilization of resources. The organization can maintain computerized
records without redundant entries. That means that one need not be distracted by information that
is not relevant, while being able to reach the information.

The aim is to automate its existing system by the help of computerized equipment’s and
full-fledge computer software, fulfilling their requirements, so that their valuable data/information
can be stored for a longer period with easy accessing and manipulation of the same. Basically, the
project describes how to manage for good performance and better services for the clients.
 Table Of Contents

1 Introduction…………………………………………………………………01
1.1. Problem Definition
1.2. Project Overview
1.3. Hardware Specification
1.4. Software Specification
2 Literature Survey…………………………………………………………...05
2.1. Existing System
2.2. Proposed System
2.3. Feasibility Study
3 System Analysis & Design…………………………………………………..06
3.1. Analysis
3.2. Disadvantage of present system
3.3. Design Introduction
3.4. UML Diagrams
3.5. Usecase Diagrams
3.6. Class Diagram
3.7. Data Flow Diagram’s
3.8. ER Diagram’s
3.9. MYSQL Database tables
4 Implementation………………………………………………………………24
4.1. Weekly Summary
4.2. Languages used
4.3. PHP—DETAILs
4.4. Software Used (server, database etc)
4.5. Code
5 Testing………………………………………………………………………...33
5.1. Details of testing methodoliges.
5.2. Sample Testing used.
6 Results/Screenshots…………………………………………………………..34
6.1. Home Page
6.2. About Us
6.3. Contact Us
6.4. Admin Panel
7 CONCLUSIONS/RECOMMENDATIONS/FUTURE SCOPE…………...44
8 REFERENCES……………………………………………………………….45
 1. Introduction

1. 1 Problem Definition
Computerized online Job Search System is developed to facilitate the General administration
system to manage the various information of the Job Seeker and Employer and the processes
involved in a placement company. So, that organization can access accurate information
quickly and easily as and when required, thereby improving its operational efficiency &
effectiveness

In today’s competitive environment, where everybody wants to be on the top, Information

plays very crucial role. As fast as information is accessed and processed, it can give good
results.

Online Job portal system is an application which connects employer and job seekers where
employers are the source of the resources and the job seeker can find and apply for their
targeted job.

In Online Job portal system, we use PHP and MySQL database. This is the project which
keeps records of the employer, jobseeker and administrator. Online Job portal system has
three modules i.e. Jobseeker, Employer and Admin.

Admin Modules:
This module provides administrator related functionalities. Administrator manages entire
application and maintains the profiles of applicants and employers.
Dashboard: In these sections, admin can briefly view the total job category, total employer,
total candidates and total job.
Job Category: In this section, admin can manage job category (add/update/delete).
List of Employer: In this section, admin can view the list of employers and see the detail of
individual employer.
Reg Jobseeker: In this section, admin can view the list of candidates(jobseeker) and see the
detail of individual candidates(jobseeker).
Pages: In this section, admin can manage the about us and contact us pages.

Reports: In this section admin can generate report of how many employers and candidates
register between two dates.
Search: In this section, admin can search a particular employer and candidates by company
name and mobile number respectively.
Admin can also update his profile, change the password and recover the password.

1|Page
Employer Module
This module provides functionalities related to employers. Employers can post vacancy
details and update the details as and when necessary. Employers can search through applicant
resumes based on different criteria.
Jobs: In this section, employer can post the job and manage the jobs.
Candidates List: In this section employer can view the list of applied candidates and send
message to selected candidates.
Reports: In this section employer can view how many candidates apply for a job in
particular periods.
Employer can also update his profile, change the password and recover the password.

Candidates (Jobseeker) Modules

Home: In this section, candidates can view job which is posted by employer and apply those
jobs.
Applied Jobs: In this section, candidates can a view response of applied job.
About Us: In this section, candidates can view the about us page of website.
Contact Us: In this section, candidates can view the contact us page of website.
Candidates (Jobseeker) can also update his profile, change the password and recover the
password.

1. 2 Project Overview
Brief summary of home page
This is the home page of the website in which admin, registered employer and candidates can
login their account. Visitor user can sign up for employer and candidates as per their needs.

Scope: It may help collecting perfect management in details. In a very short time, the
collection will be obvious, simple and sensible. It will help a person to know the
management of past years perfectly and vividly. It also helps in current all works relative to
job portal system. It will be also reduced the cost of collecting the management & collection
procedure will go on smoothly.
Our project aims are to automate the existing manual system by the help of computerized
equipment’s and full-fledge computer software, fulfilling their requirements, so that their
valuable data/information can be stored for a longer period with easy accessing and
manipulation of the same. The required software and hardware are easily available and easy
to work with.

2|Page
1. 3 Hardware Specification.

Client Side:
RAM 512 MB

Hard disk 10 GB

Processor 1.0 GHz

Server side:
RAM 1 GB

Hard disk 20 GB

Processor 2.0 GHz

1. 4 Software Specification
Client Side:
Web Browser Google Chrome or any compatible browser

Operating System Windows or any equivalent OS

Server Side:

Web Server APACHE

Server-side Language PHP5.6 or above version

Database Server MYSQL

Web Browser Google Chrome or any compatible browser

Operating System Windows or any equivalent OS

3|Page
APACHE

The Apache HTTP Server Project is an effort to develop and maintain an open-source
HTTP server for modern operating systems including UNIX and Windows. The goal of this
project is to provide a secure, efficient and extensible server that provides HTTP services in sync
with the current HTTP standards.
The Apache HTTP Server ("httpd") was launched in 1995 and it has been the most
popular web server on the Internet since April 1996. It has celebrated its 20th birthday as a
project in February 2015.

PHP
•PHP stands for PHP: Hypertext Preprocessor.
•PHP is a server-side scripting language, like ASP.
•PHP scripts are executed on the server.
•PHP supports many databases (MYSQL, Informix, Oracle, Sybase, Solid, Generic
ODBC, etc.).
• PHP is an open-source software.
• PHP is free to download and use.
MYSQL

• MYSQL is a database server

• MYSQL is ideal for both small and large applications
• MYSQL supports standard SQL
• MYSQL compiles on a number of platforms
• MYSQL is free to download and use
• How to access MySQL:
http://localhost/phpmyadmin

4|Page
 2. Literature Survey

2.1. Existing System:

The present system requires applicants to search through print and visual media for job
opportunities. Applicants need to apply for jobs using conventional methods and appear
for interview on a specified date at a specified location. Employers need to advertise the
vacancies and sort all applicant details, conduct selection procedures and complete the
formalities. This approach is tedious and requires much effort and resources.

2.2. Propoed System:

The proposed system is a web-based application which allows applicants and employers
to register their details. Applicants can browse through the vacancy details that are posted
and can apply for the jobs online. Employers can browse through the posted resumes and
select suitable candidates.

2.3. Feasibility Study:

It may help collecting perfect management in details. In a very short time, the collection
will be obvious, simple and sensible. It will help a person to know the management of
passed years perfectly and vividly. It also helps in current all works relative to job portal
system. It will be also reduced the cost of collecting the management & collection
procedure will go on smoothly.
Our project aims is to automate the existing manual system by the help of computerized
equipments and full-fledge computer software, fulfilling their requirements, so that their
valuable data/information can be stored for a longer period with easy accessing and
manipulation of the same. The required software and hardware are easily available and
easy to work with.

5|Page
 3. System Analysis & Design

3.1. Analysis:
In present all visitor parking work done on the paper. The whole year visitor parking
record is stored in the registers. We can’t generate reports as per our requirements
because it take more time to calculate the visitors parking report.

3.2. Disadvantage of present system:

• Not user friendly: The present system not user friendly because data is not stored in
structure and proper format.
• Manual Control: All report calculation is done manually so there is a chance of
error.
• Lots of paper work: Visitors maintain in the register so lots of paper require storing
details.
• Time consuming

3.3. Design Introduction:

Design is the first step in the development phase for any techniques and principles for the
purpose of defining a device, a process or system in sufficient detail to permit its physical
realization.

Once the software requirements have been analyzed and specified the software design
involves three technical activities - design, coding, implementation and testing that are
required to build and verify the software.

The design activities are of main importance in this phase, because in this activity,
decisions ultimately affecting the success of the software implementation and its ease of
maintenance are made. These decisions have the final bearing upon reliability and
maintainability of the system. Design is the only way to accurately translate the
customer’s requirements into finished software or a system.

Design is the place where quality is fostered in development. Software design is a process
through which requirements are translated into a representation of software. Software
design is conducted in two steps. Preliminary design is concerned with the transformation
of requirements into data

6|Page
3.4. UML Diagrams

Actor: A coherent set of roles that users of use cases play when interacting with the use
cases.

Use case: A description of sequence of actions, including variants, that a system

performs that yields an observable result of value of an actor.

UML stands for Unified Modeling Language. UML is a language for specifying,
visualizing and documenting the system. This is the step while developing any product
after analysis. The goal from this is to produce a model of the entities involved in the
project which later need to be built. The representation of the entities that are to be used
in the product being developed need to be designed.

3.5. Usecase Diagrams

Use case diagrams model behavior within a system and helps the developers understand
of what the user require. The stick man represents what’s called an actor.

Use case diagram can be useful for getting an overall view of the system and clarifying
who can do and more importantly what they can’t do.

Use case diagram consists of use cases and actors and shows the interaction between the
use case and actors.

• The purpose is to show the interactions between the use case and actor.
• To represent the system requirements from user’s perspective.
• An actor could be the end-user of the system or an external system.
A Use case is a description of set of sequence of actions. Graphically it is rendered as an
ellipse with solid line including only its name. Use case diagram is a behavioral diagram
that shows a set of use cases and actors and their relationship. It is an association
between the use cases and actors. An actor represents a real-world object. Primary Actor
– Sender, Secondary Actor Receiver.

7|Page
Use Case Diagrams:
Sign in
Admin

Dashboard

Add Job Category

Manage Job Category

(Update/Del Details)

ViewAd
Employer

View Jobseeker

View Employer

Update Contact Us/About

Us

Generate Reports

Update Profile

Change Password

Password Recovery

Search

8|Page
Employer

Sign Up

Sign in

Post Jobs

Manage Jobs

Manage Candidates

Generate Report

Update Profile

Change Password

Password Recovery

Search

9|Page
Candidates (Jobseeker)

Sign Up

Sign in

Visit Home Page

View Applied Jobs

View About us

View Contact Us

Update Profile

Change Password

Password Recovery

Search

10 | P a g e
3.6. Class Diagram
A description of set of objects that share the same attributes operations, relationships,
and semantics

11 | P a g e
3.7. Data Flow Diagram’s

A Data Flow Diagram (DFD) is a traditional visual representation of the information flows
within a system. A neat and clear DFD can depict the right amount of the system requirement
graphically. It can be manual, automated, or a combination of both.

It shows how data enters and leaves the system, what changes the information, and where
data is stored.

The objective of a DFD is to show the scope and boundaries of a system as a whole. It may
be used as a communication tool between a system analyst and any person who plays a part
in the order that acts as a starting point for redesigning a system. The DFD is also called as a
data flow graph or bubble chart.

The following observations about DFDs are essential:

1. All names should be unique. This makes it easier to refer to elements in the DFD.
2. Remember that DFD is not a flow chart. Arrows is a flow chart that represents the
order of events; arrows in DFD represents flowing data. A DFD does not involve any
order of events.
3. Suppress logical decisions. If we ever have the urge to draw a diamond-shaped box in
a DFD, suppress that urge! A diamond-shaped box is used in flow charts to represents
decision points with multiple exists paths of which the only one is taken. This implies
an ordering of events, which makes no sense in a DFD.
4. Do not become bogged down with details. Defer error conditions and error handling
until the end of the analysis.

Standard symbols for DFDs are derived from the electric circuit diagram analysis
and are shown in fig:

12 | P a g e
Circle: A circle (bubble) shows a process that transforms data inputs into data outputs.

Data Flow: A curved line shows the flow of data into or out of a process or data store.

Data Store: A set of parallel lines shows a place for the collection of data items. A data store
indicates that the data is stored which can be used at a later stage or by the other processes in a
different order. The data store can have an element or group of elements.

Source or Sink: Source or Sink is an external entity and acts as a source of system inputs or sink
of system outputs.

13 | P a g e
Zero Level

First Level

14 | P a g e
Second Level

15 | P a g e
3.8. ER Diagram’s
The Entity-Relationship (ER) model was originally proposed by Peter in 1976 [Chen76]
as a way to unify the network and relational database views. Simply stated the ER model
is a conceptual data model that views the real world as entities and relationships. A basic
component of the model is the Entity-Relationship diagram which is used to visually
represent data objects. Since Chen wrote his paper the model has been extended and
today it is commonly used for database design for the database designer, the utility of the
ER model is:
• It maps well to the relational model. The constructs used in the ER model can
easily be transformed into relational tables.
• It is simple and easy to understand with a minimum of training. Therefore, the
model can be used by the database designer to communicate the design to the end
user.
• In addition, the model can be used as a design plan by the database developer to
implement a data model in specific database management software.

ER Notation
There is no standard for representing data objects in ER diagrams. Each modeling
methodology uses its own notation. The original notation used by Chen is widely used in
academics texts and journals but rarely seen in either CASE tools or publications by non-
academics. Today, there are a number of notations used; among the more common are
Bachman, crow's foot, and IDEFIX.
All notational styles represent entities as rectangular boxes and relationships as lines
connecting boxes. Each style uses a special set of symbols to represent the cardinality of
a connection. The notation used in this document is from Martin. The symbols used for
the basic ER constructs are:
• Entities are represented by labeled rectangles. The label is the name of the entity.
Entity names should be singular nouns.
• Relationships are represented by a solid line connecting two entities. The name
of the relationship is written above the line. Relationship names should be verbs
• Attributes, when included, are listed inside the entity rectangle. Attributes which
are identifiers are underlined. Attribute names should be singular nouns.
• Cardinality of many is represented by a line ending in a crow's foot. If the crow's
foot is omitted, the cardinality is one.
Existence is represented by placing a circle or a perpendicular bar on the line. Mandatory
existence is shown by the bar (looks like a 1) next to the entity for an instance is required.
Optional existence is shown by placing a circle next to the entity that is optional.

16 | P a g e
ER Diagram

17 | P a g e
3.9 MYSQL Database tables

Admin Table:(Table name is admin)

This store admin personal and login details.

Category Table(Table name is tblcategory)

This table store category of jobs.

Apply Job Table: (Table name is tblapplyjob)

This table store the details of apply jobs.

18 | P a g e
Education Table: (Table name is tbleducation)

This table stores the education details of candidates.

Experience Table: (Table name is tblexperience)

This table stores the experience details of candidates.

19 | P a g e
Employers Table: (Table name is tblemployers)

This table stores details of employers.

Jobs Table: (Table name is tbljobs)

This table stores details of jobs which are posted by employers.

20 | P a g e
Jobseekers Table: (Table name is tbljobseekers)

This table stores details of jobseeker.

Message Table: (Table name is tblmessage)

This table stores message detail which is send by employer to jobseeker.

21 | P a g e
Pages Table: (Table name is tblpages)

This table stores about us and contact us details.

22 | P a g e
Schema Diagram

23 | P a g e
 4. Implementation
4.1. Weekly Summary
Week 1: Introduction and Project Setup
• Objective: Understand the basics of HTML.
• Tasks Completed:
o Set up the development environment with a code editor (e.g., Visual Studio
Code).
o Created an initial project folder structure.
o Explored HTML tags and their attributes.
o Styled a simple webpage using HTML.
o Created a Simple HTML webpage with Forms.
• Codes Used:
o HTML Syntax:
HTML syntax is the set of rules and conventions used to write HTML documents.
It includes:

• Elements: Basic building blocks defined by tags.

• Tags: Keywords enclosed in angle brackets, like, and
• Attributes: Provide additional information about elements, written within
the opening tag, such as class, id, and herf.
• Content: The text or other elements nested between opening and closing
tags.
o HTML Tags define the structure and layout of a web document. Some common HTML
tags include:
• Root element that wraps the entire document.
• Contains meta-information like
o Syntax for from tag:
<form>
.
form elements
.
</form>
The <form> element is a container for different types of input elements, such as: text
fields, checkboxes, radio buttons, submit buttons, etc.

The HTML <input> element is the most used form element.

24 | P a g e
 An <input> element can be displayed in many ways, depending on the type of attribute.
Type Description
<input type="text"> Displays a single-line text input field
<input type="radio"> Displays a radio button (for selecting one of many choices)
<input type="checkbox"> Displays a checkbox (for selecting zero or more of many choices)
<input type="submit"> Displays a submit button (for submitting the form)
<input type="button"> Displays a clickable button

Week 2: Styling with CSS

• Objective: Apply CSS styles to enhance the visual appearance of the webpage.
• Tasks Completed:
o Designed a cohesive layout for the contact form.
o Used CSS selectors to target specific elements.
o Applied colors, fonts, and margins to improve aesthetics.
o Explored CSS properties like margin, padding, and border.
• Codes Used:
o File name: style.css
CSS Syntax

selector { Property: value; }

A CSS Syntax rule consists of a selector, property, and its value. The selector points to
the HTML element where the CSS style is to be applied. The CSS property is separated
by semicolons. It is a combination of the selector name followed by the property:
value pair that is defined for the specific selector.

25 | P a g e
Week 3: Adding JavaScript Functionality
Enhancing Forms with JavaScript:
• Implemented JavaScript to enhance the functionality of HTML forms.
• Added client-side validation to ensure data integrity before submission.
• Used event listeners to handle user interactions such as clicking buttons and submitting
forms.
• Applied JavaScript to provide real-time feedback and error messages to users.
Tools and Resources:
• Utilized browser developer tools (e.g., Chrome DevTools) to debug JavaScript code.
• Explored online resources and documentation to understand best practices for writing
efficient and secure JavaScript.
Duties Performed:
• Studied and practiced fundamental JavaScript concepts.
• Applied JavaScript to improve form functionality and user experience.

Week 4: Working with Databases

1. MySQL and phpMyAdmin
• Objective: Learn database management.
• Tasks Completed:
o Explored phpMyAdmin, a web-based tool for managing MySQL databases.
o Browsed tables, viewed data, and understood table structure.
o Inserted records and learned about SQL queries.
o Explored features like searching data and emptying tables.

2. Database Design
• Designed database schemas for various projects.
• Learned about normalization, indexing, and relationships (e.g., one-to-many, many-
to-many).
• Implemented CRUD operations (Create, Read, Update, Delete) in SQL.

3. Challenges Faced
• Understanding CSS specificity and inheritance.
• Ensuring cross-browser compatibility.
Handling complex database queries efficiently.

26 | P a g e
Week 5: Working with the assigned application and database.
1. Project details:
I. A job portal is an online job board where applicants can find job listings, and
employers can search for ideal candidates.
II. These portals simplify the hiring process by allowing recruiters to post job
advertisements, customize application questions, and efficiently search for
resumes.

2. Features of a Job Portal Website:

I. Job Listings: Employers can post job openings, specifying details like job title,
description, location, and qualifications.
II. Job Search: Job seekers can search for relevant positions based on keywords,
location, and other filters.
III. Resume Upload: Job seekers can upload their resumes to apply for jobs.
IV. Application Tracking: Employers can manage applications, track candidate
progress, and communicate with applicants.
V. User Profiles: Both job seekers and employers can create profiles with relevant
information.
VI. Notifications: Automated alerts for new job postings or application status
changes.
Advanced Search: Refine searches based on specific criteria (e.g., experience level,
industry, salary range).

Week 6: Worked with the development of the project

1. Project details:
a. Created an Admin login page
b. features such as password resetting, email and password validation, password
encryption.
c. Establishing Connection with the server.
d. Sending SQL Queries to the MySQL database.
e. Creation of table for login page in MYSQL database.
f. Updating existing values.
g. Retrieving the current values for password validation.
2. Tasks Completed:
a. Frontend Development: I dedicated time to frontend development tasks,
including implementing user interfaces, designing layouts, and enhancing user
interactions using HTML, CSS, and JavaScript. This involved coding responsive
designs, interactive elements, and dynamic content presentation to optimize the
user experience.

27 | P a g e
 b. Database Integration: I focused on integrating databases into the project to store
user data, content information, and system configurations. This involved
designing database schemas, writing SQL queries, and implementing database.
c. Feature Implementation: I collaborated with the development team to
implement various features and functionalities requested by stakeholders. This
included features such as user authentication, content management, progress
tracking, and collaborative tools to facilitate effective teaching and learning
experiences.
Week7: Worked with development of the project
Worked on developing Jobportal modules aimed at enhancing the services for Job
applicants. My responsibilities primarily involved coding functionalities using HTML, CSS, and
PHP to create interactive elements and ensure seamless user experience.

Coding Tasks Completed:

1. HTML: Developed the structure of the education modules, including layouts for different
sections and interactive components.
2. CSS: Styled the HTML elements to enhance visual appeal and ensure consistency across
the modules.
3. PHP: Implemented backend functionalities such as user authentication, data processing,
and dynamic content generation based on user inputs.

Duties Performed:
1. Collaborated with the development team to brainstorm ideas and contribute to the overall
project roadmap.
2. Participated in code reviews and provided feedback to improve code quality and
maintainability.
3. Assisted in troubleshooting and resolving technical issues encountered during
development.
Conducted research on emerging technologies and best practices in smart education to
incorporate innovative features into the modules.

Week 8: Module integration of the project

1. User Authentication and Registration:
o Implement user registration and login functionality.
o Use PHP sessions or tokens to manage user authentication.
o Integrate with the database to store user credentials securely.
2. Job Listings and Search:
o Create modules for job listings and search.
o Allow employers to post job openings and job seekers to search for relevant
positions.

28 | P a g e
 o Integrate with the database to store job details and search criteria.
3. User Profiles and Resumes:
o Develop user profile pages where job seekers can upload their resumes.
o Integrate with file upload functionality to store resumes.
o Allow users to update their profiles and manage their information.
4. Company Profiles and Job Postings:
o Create modules for company profiles.
o Employers should be able to create and manage job postings.
o Integrate with the database to store company details and job postings.
5. Application Tracking System (ATS):
o Implement an ATS module to track job applications.
o Connect job seekers’ applications to specific job postings.
o Notify employers about new applications.
6. Admin Panel:
o Develop an admin module for managing users, job listings, and company profiles.
o Admins can verify companies, review applications, and handle user-related tasks.
7. Advanced Search and Filters:
o Enhance the job search module with advanced filters (e.g., location, salary,
industry).
o Integrate search algorithms to improve search accuracy.
8. Responsive Design:
o Ensure that all modules are responsive and work well on different devices
(desktop, tablet, mobile).
9. Testing and Debugging:
o Regularly test each module for functionality, security, and performance.
o Debug any issues and optimize code as needed.

Week 9: Module integration of the project and testing

Weekly Activities
Module Integration
1. User Authentication Module:
o Integrated user login and registration functionality.
o Ensured that user credentials are securely stored and validated during login.
2. Job Listings Module:
oIntegrated the job listings feature.
o Collaborated with frontend developers to display job openings, including details
such as job title, description, and location.
3. Search Functionality Module:
29 | P a g e
 o Integrated job search functionality.
o Users can now search for jobs based on criteria like location, industry, and job
type.
Testing
1. Unit Testing:
oConducted unit tests for individual modules.
o Verified that each module functions correctly in isolation.
2. Integration Testing:
o
Tested the interaction between integrated modules.
o
Ensured seamless communication between user authentication, job listings, and
search features.
3. User Acceptance Testing (UAT):
o Collaborated with QA engineers to simulate real-world scenarios.
o Validated end-to-end functionality from a user’s perspective.

4.2. Languages used

PHP, MYSQL, HTML, CSS, Javascript
4.3. PHP—DETAILs
4.4. Software Used (server, database etc)
Code editor: VS Code
Web server: Xampp

30 | P a g e
 4.5. Code
<?php include('database.php')?>

<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="UTF-8">
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<link rel="stylesheet" href="style.css">
<script src="events.js" defer></script>
<title>Login</title>
</head>
<body>
<div class="container" id="container">
<div class="form-container sign-up-container">
<form action="regitration.php" method="post">
<h1>Create Account</h1>
<span>or use your email for registration</span>
<input type="text" placeholder="Name" name="name" required/>
<input type="email" placeholder="Email" name="email" required/>
<input type="password" placeholder="Password" name="password" required/>
<button>Sign Up</button>
</form>
</div>
<div class="form-container sign-in-container">
<form action="signin.php" method="post">
<h1>Sign in</h1>
<span>Using your Email id and Password</span>
<input type="email" placeholder="Email" name="email" required/>
<input type="password" placeholder="Password" name = "password"required/>
<a href="forgotpwd.php">Forgot your password?</a>

31 | P a g e
 <button type = "submit" name="submit">Sign In</button>
</form>
</div>
<div class="overlay-container">
<div class="overlay">
<div class="overlay-panel overlay-left">
<h1>Welcome Back!</h1>
<p>To keep connected with us please login with your personal info</p>
<button class="ghost" id="signIn">Sign In</button>
</div>
<div class="overlay-panel overlay-right">
<h1>Hello, Friend!</h1>
<p>Enter your personal details and start journey with us</p>
<button class="ghost" id="signUp">Sign Up</button>
</div>
</div>
</div>
</div>
</body>
</html>

<?php mysqli_close($conn);?>

32 | P a g e
 5. Testing
5.1. Details of testing methodoliges.
System Testing
The goal of the system testing process was to determine all faults in our project. The program was
subjected to a set of test inputs and many explanations were made and based on these explanations it
will be decided whether the program behaves as expected or not. Our Project went through two levels
of testing

5.2. Sample Testing used

1. Unit testing

2. Integration testing

UNIT TESTING
Unit testing is commenced when a unit has been created and effectively reviewed. In order
to test a single module, we need to provide a complete environment i.e. besides the section
we would require

• The procedures belonging to other units that the unit under test calls
• Non local data structures that module accesses
• A procedure to call the functions of the unit under test with appropriate
parameters

1. Test for the admin module

• Testing admin login form-This form is used for log in of administrator of the
system. In this form we enter the username and password if both are correct
administration page will open otherwise if any of data is wrong it will get redirected
back to the login page and again ask the details.
• Report Generation: admin can generate report from the main database.

INTEGRATION TESTING
• In the Integration testing we test various combination of the project module by
providing the input.
• The primary objective is to test the module interfaces in order to confirm that no
errors are occurring when one module invokes the other module.

33 | P a g e
 6. Results/Screenshots

6.1. Home Page

34 | P a g e
6.2. About Us

6.3. Contact Us

35 | P a g e
6.4. Admin Panel
6.4.1. Login Page

6.4.2. Forgot Password Page

36 | P a g e
6.4.3. Dashboard

6.4.4. Profile

37 | P a g e
6.4.5. Change Password

6.4.6. Add Job Category

38 | P a g e
6.4.7. Manage Job Category

6.4.8. Update Job Category

39 | P a g e
6.4.9. Forgot Password

6.4.10. Profile Details

40 | P a g e
6.4.11. Update Profile

6.4.12. Add Education Details

41 | P a g e
6.4.13. Add Experience Details

6.4.14. History of Applied Job

42 | P a g e
6.4.15. View Job Details

43 | P a g e
7. CONCLUSIONS/RECOMMENDATIONS/FUTURE SCOPE

The Application was designed in such a way that future changes can be done easily. The
following conclusions can be deduced from the development of the project.

• Automation of the entire system improves the productivity.

• It provides a friendly graphical user interface which proves to be better when
compared to the existing system.
• It gives appropriate access to the authorized users depending on their permissions.
• It effectively overcomes the delay in communications.
• Updating of information becomes so easier.
• System security, data security and reliability are the striking features.
• The System has adequate scope for modification in future if it is necessary.

44 | P a g e
 8. REFERENCES

For PHP
• https://www.w3schools.com/php/default.asp
• https://www.sitepoint.com/php/
• https://www.php.net/

For MySQL
• https://www.mysql.com/
• http://www.mysqltutorial.org

For XAMPP
• https://www.apachefriends.org/download.html

45 | P a g e