JOB SEARCH PORTAL SYSTEM

STUDENT NAME : NYONGESA W. COSMAS

INDEX NO : 5032100727

CENTRE CODE : 503210

CENTRE NAME: KITALE NATIONAL POLYTECHNIC

COURSE CODE: 2920

SUBMITTED TO: THE KENYA NATIONAL EXAMINATION

COUNCIL IN PARTIAL FULFILMENT OF THE
REQUIREMENTS FOR THE AWARD OF DIPLOMA IN
INFORMATION COMMUNICATION TECHNOLOGY

SUPERVISOR: MR. ABUTI

SERIES: JULY 2024

PAGE \* MERGEFORMAT iii

DECLARATION
I declare that this project is my original work and has been submitted to Kitale National
Polytechnic for examination or award of a diploma.
Name: NYONGESA W COSMAS

Signed………………………… Date……………..

Supervisor’s Name: MR SAMUEL ABUTI

Signed………………………… Date…………….

PAGE \* MERGEFORMAT iii

DEDICATION
I dedicate this work to the Almighty and to my family for their constant support both
spiritually and financially. I also dedicate this project work to my friends more so our
classmates for the support love and encouragement they showed us during this period.

PAGE \* MERGEFORMAT iii

ACKNOWLEDGEMENT
I am indebted to The Kitale National Polytechnic for giving me the chance to pursue
Diploma in Information and Communication Technology. I wish to thank all my classmates
for having contributed in formulation of ideas and for providing a suitable working
environment towards the completion of this proposed work. I would also like to thank our
supervisor Mr Samuel Abuti for his constant guidance towards the development of this
project idea.

PAGE \* MERGEFORMAT iii

ABSTRACT
Unemployment is one of the serious social issues faced by both developing and developed
countries. The main reason for this problem is the unfair distribution or lack of information
on job opportunities so people are unable to know the new job vacancies. It means that there
are some jobs available, but jobseekers do not have access to that information. An efficient
search of the internet might help to jobseekers in their job hunt. The main aim of this job
portal is to connect the industries and act as an online recruitment platform to support the job
seekers to find the right jobs advertised by companies or individuals with job opportunities.
Furthermore, this system enhances the understanding concept and importance of the job
portal..

PAGE \* MERGEFORMAT iii

ACRONYMS AND ABBREVIATIONS
SIIS - School of Informatics and Innovative System ASD - Adaptive
Software Development life cycle

DFD - Data flow diagram

ISO - International Organization for Standardization

RAM - Random Access Memory

RAD - Rapid Application Development

SDLC - Systems Development Life Cycle

GUI - Graphical User Interface

T.C NO -Test Case Number

PAGE \* MERGEFORMAT iii

 Table of Contents
DECLARATION....................................................................................................................i
DEDICATION.......................................................................................................................ii
ACKNOWLEDGEMENT....................................................................................................iii
ABSTRACT..........................................................................................................................iv
ACRONYMS AND ABBREVIATIONS..............................................................................v
CHAPTER ONE.........................................................................................................................2
1.0 INTRODUCTION............................................................................................................2
1.1 Background Information..................................................................................................2
1.2. Problem Statement..........................................................................................................2
1.4 Why Job Search Portal?...................................................................................................3
1.5 Assumptions.....................................................................................................................3
1.6 Advantages of the New System........................................................................................3
1.7 Scope................................................................................................................................3
1.8 Limitations of the system.................................................................................................3
1.9 Proposed system...............................................................................................................4
CHAPTER TWO........................................................................................................................5
2.0 LITERATURE REVIEW.................................................................................................5
CHAPTER THREE....................................................................................................................6
3.0 METHODOLOGY...........................................................................................................6
3.1 Predictive Life Cycle Models...........................................................................................6
3.2. Adaptive Software Development life cycle models........................................................6
3.2.1. Agile System Development Methodology...............................................................6
3.2.2. Advantages of Agile.................................................................................................7
3.2.3. Disadvantages of Agile............................................................................................7
3.2.3.1. System Planning....................................................................................................7
3.2.3.2. System Analysis....................................................................................................7
3.2.3.3. System Design.......................................................................................................8
3.2.3.4. System Coding and Implementation.....................................................................8
3.2.3.5. System Testing......................................................................................................8
5.7. SYSTEM IMPLEMENTATION AND TESTING.........................................................9
5.7.1Testing Methodologies:..............................................................................................9
5.7.2. Levels of Testing......................................................................................................9
5.7.3. Types of Testing.....................................................................................................10
5.7.4. TCD (Test Case Document):..................................................................................11

vi
 SYSTEM IMPLEMENTATION.........................................................................................13
CHAPTER FOUR....................................................................................................................14
4.0 SYSTEM DESIGN....................................................................................................14
4.1 DESIGN TOOLS.......................................................................................................14
4.2 ENTITY RELLATIONSHIP DIAGRAM (ERD).....................................................15
4.3 DATA FLOWCHAT.................................................................................................16
4.4 PHYSICAL DESIGN................................................................................................17
SYSTEM’S DATABASE....................................................................................................19
FINDINGS...........................................................................................................................19
RECCOMENDATIONS......................................................................................................19
CONCLUSIONS..................................................................................................................20
REFERENCES.....................................................................................................................20
Appendix..................................................................................................................................21

vii
 CHAPTER ONE
1.0 INTRODUCTION
Online job portals use internet as a platform for job advertisements, posting of job vacancies
and job applications by job seekers. Job Search Portal allows Job seekers to apply for a job
online by viewing jobs Posted by companies. It allows online job posting for companies and
sending interview letter to selected candidates by e-mail. Quick and advanced search facility
for both Job seeker and Companies is the main advantage of this application.

1.1 Background Information

Job Search Portal involves a user (job seeker) creating an account by registering and
uploading his/her curriculum vitae. The company(s) also registers and publishes the job
vacancies and job requirements on the portal. The candidate can then apply for the job and
the company will vet the applications upon which the candidate can be recruited or turned
down. A candidate will be able to access career guidance or advice that will be available in
the portal
1.2. Problem Statement
The successful implementation of Automatic job Application Software in different
organizations warrants careful planning and depends largely on how well policy makers
understand and appreciate the dynamics of such implementation
With the proposed system it requires very low system resources and it will work in almost all
configuration and organizations to cater for job vacancies. All individuals with all the
qualifications required will be able to be placed at different workplaces in different
organizations.
1.3. OBJECTIVE
Main Objective
The goal of the project is to develop a software that will enable automatic job employment
hence cubbing lack of employment opportunities.
OTHER OBJECTIVES:
 To provide within the software the ability to place individuals rightfully in accordance to their
level of study.
 To cub idleness and poverty for economic development as employment rate increases
 To create the function of assigning jobs to many people as possible depending on their level of
study

viii
 1.4 Why Job Search Portal?
The Objective of this project is to develop an e-recruitment site, which is a modern way for
the employers to advertise the latest job openings in their organization over the internet. This
project also facilitates the jobseekers to apply for these jobs online. This project will provide
the employers with low budget cost effective resume search and job posting options for the
companies to best fit their job requirements. This job portal is able to capture job
requirements based on industry needs. Job Search Portal also tends to offer career advice to
job seekers.
Most companies lack a website. They can therefore use Job Search portal to advertise
their job vacancies.
1.5 Assumptions
The system users (job seekers and companies/ individuals with job opportunities) have access
to internet services.
1.6 Advantages of the New System
i. The new system should be cost effective.
ii. To augment management, improve productivity and services iii. To
enhance user / system interface. iv. To improve information quality and
usability.
v. To upgrade systems reliability, availability, flexibility and growth potential.
1.7 Scope
The project will be developed from project conception and initiation to project close which
will run from 17th October 2021 to 4th December 2021. The stakeholders will be the
companies/individual who will post or advertise a job vacancy on the platform, the platform
administrators who form the team monitors and manages the platform, the candidates (job
seekers) who will apply for the advertised job vacancies based on the described qualifications
and job requirements.

1.8 Limitations of the system

i. Delay in processing admission.
ii. Takes a lot of time to retrieve a particular application form.
iii. Lose of vital document as filling system is manual.

ix
1.9 Proposed system
Users must have access to the internet.
i. Applying for jobs through online
ii. Maintaining records of job opportunities with its company details
iii. Maintaining records of candidates’ profile with their experience
iv. To access the different companies for opportunities
v. Offering the best services for job seekers and company users
vi. User(s) can edit and delete the information in their profile.
vii. Company user can view suitable candidates profile
viii. Administrator can add and delete the users on the basis of their performance ix.
Candidate can view and apply the opportunities available in the companies
x. Admin user can add or delete the company user from the system.

x
 CHAPTER TWO

2.0 LITERATURE REVIEW

The digital world has brought a new dimension to the world of recruiting. The World Wide
Web, or Web 1.0, shortened the search time, costs and offered a transparent method of
information for candidates (Salmen, 2012). E-Recruitment is an easiest and convincing way
to hire people from any part of the world and promotes opportunity, it benefits the company
to be recognized globally, and E-HRM helps in conveying any kind of HR policies, training
program, and pay slip sheets easily. E-HRM is based on more systematic & technology
theorem, which helps the HR department to scrutinize employee performance carefully &
accurately.
It helps in imparting any HR policy; keep a track on employees’ daily activity report (DAR),
efficiently helps the employees in promotion & transfers. E-recruitment, also known within
the literature as online recruitment, cyber recruiting, or internet recruiting are synonymous.
They imply formal sourcing of jobs online (Ganalaki, 2002). It is a complete process which
includes job advertisements, receiving resumes and building human resource database with
candidates and incumbents.
The findings from Holm’s (2012) thesis were that there was a difference between the
paperbased and the electronic-based recruitment process. From the findings, Holm’s found
that the electronic-based recruitment process began with few electronic tools for line
managers to commence the recruitment process, e.g., line managers were putting their hiring
needs into a Word document and sending it to the responsible recruiter. The recruiter then
had to read each applicant and rate the order. In some cases, this is handled through filter
programs bringing top applicants to the forefront. Holm’s (2012) study was conducted
between the years 2008 to 2010 in three companies in Denmark, which could have limited
the validity of the recruitment process today as electronic technology has been developed for
the evolving topic of recruitment.

xi
 CHAPTER THREE
3.0 METHODOLOGY
The Systems Development Life Cycle (SDLC) is a framework for describing the phases
involved in developing and maintaining information systems
Systems development projects can follow;
3.1 Predictive Life Cycle Models
Waterfall modelhas well-defined, linear stages of systems
development and support

Spiral model
Shows that software is developed using an iterative or spiral approach rather than a linear
approach

Incremental build model provides for progressive

development of operational software

Prototyping model used for developing prototypes to

clarify user requirements

Rapid Application Development (RAD) model

used to produce systems quickly without sacrificing quality

3.2. Adaptive Software Development life cycle models

Scrum; According to the Scrum Alliance, Scrum is the leading agile development method for
completing projects with a complex, innovative scope of work.
Agile; Agile today means using a method based on iterative and incremental development, in
which requirements and solutions evolve through collaboration.

3.2.1. Agile System Development Methodology

Agile is a software development methodology to build a software incrementally using short
iterations of 1 to 4 weeks so that the development process is aligned with the changing
business needs. Instead of a single-pass development of 6 to 18 months where all the
requirements and risks are predicted upfront, Agile adopts a process of frequent feedback
where a workable product is delivered after 1 to 4-week iteration. The aim of agile methods

xii
is to reduce overheads in the software process (e.g., by limiting documentation) and to be
able to respond quickly to changing requirements without excessive rework.

3.2.2. Advantages of Agile

i. Customer satisfaction
ii. Allows for changes to be made.
iii. Deliver a working software frequently, ranging from a few weeks to a few months,
considering shorter time-scale.
iv. Promotes collaboration
v. Provides motivation between individual team members.

3.2.3. Disadvantages of Agile

i. Limited support for distributed development environments.
ii. Limited support for subcontracting. iii.Limited support for
developing large, complex software.
iv Limited support for development involving large teams.
Agile follows the phases of software development life cycle which include;
 Project planning: initiate, ensure feasibility, plan schedule, and obtain approval.
 Analysis: understand computer lab needs and processing requirements
 Design: define solution system based on requirements and analysis decisions
 Implementation: construction, testing, user training, and installation of new system
Support: keep system running and improve

3.2.3.1. System Planning

In planning phase, we identified the system requirements for the Job Search Portal project.
This was first phase of the system and it entailed determining the necessary information that
was required for the system to be fully operational and functional. The requirements that we
captured was subjected to thorough scrutiny to determine the level of essence of it as well as
eliminate the unwanted requirements. We did this based on the fact that though the
requirements might have been raised by the target users, they might not be realistic or might
not be so much important.

3.2.3.2. System Analysis

Here, we analyzed and considered the current systems and investigated any problems
associated with it. Other sources of information about system and the new requirements were
also investigated at this time. The important information from the planning phase was highly

xiii
used in this phase, and the valid information gathered from the users was analyzed for the
design stage.

3.2.3.3. System Design

After the requirements having already been captured and analyzed, the design of the
information flow was done here. It is in this phase that the flow charts, data flow diagrams
and entity relationship diagrams were drawn to show flow of information and the activity
diagrams were developed to show the connection that will exist between one information and
another.

3.2.3.4. System Coding and Implementation

After the design of the interfaces as well as the indication of the information flow through the
Sequence diagrams and the flowcharts algorithms, the next step was to develop code that
performed the hidden functionality of the system to realize the already set objectives. The
code was developed highly depending on the information flow and therefore the flowcharts
developed earlier were now applied here. The requirements documentation was referred
throughout the rest of the system development process to ensure the developing project
aligns with the needs and requirements or scope. A proper execution of the previous stages
ensured an easier realization of this phase in the course of our development. Upon
completion of the coding, the various components of the system were then integrated in to
one system in order to function collectively as a single component.

3.2.3.5. System Testing

Last phase is system testing done when development is complete and the system is ready for
deployment. The testing phase come next to determine if the earlier intended objective have
been realized by then. Testing was done based on whether completeness will have been
realized or functional testing that determined whether the software is doing what it is
expected correctly and in the right way. User testing was then carried out to ascertain that the
users will be contented with what will have been achieved then.

xiv
5.7. SYSTEM IMPLEMENTATION AND TESTING
Testing:
The process of executing asystem with the intent of finding an error.
Testing is defined as the process in which defects are identified, isolated, subjected for
rectification and ensured that product is defect free in order to produce the quality product
and hence customer satisfaction.

Quality is defined as justification of the

requirements Defect is nothing but deviation
from the requirements Defect is nothing but bug.
Testing --- The presence of bugs
Testing can demonstrate the presence of bugs, but not their absence
Testing is a systematic attempt to break a program or the AUT
Debugging is the art or method of uncovering why the script /program did not execute
properly.

5.7.1Testing Methodologies:
5.7.1.1. Black box Testing: is the testing process in which tester can perform testing on an
application without having any internal structural knowledge of application.
Usually Test Engineers are involved in the black box testing.
5.7.1.2. White box Testing: is the testing process in which tester can perform testing
on an application with having internal structural knowledge. Usually, The Developers
are involved in white box testing.
5.7.1.3. Gray Box Testing: is the process in which the combination of black box and white
box techniques are used.
5.7.2. Levels of Testing
5.7.2.1. STLC (Software Testing Life Cycle)
5.7.2.2. Test Planning: Test Plan is defined as a strategic document which describes the
procedure how to perform various testing.
• Objective of testing,
• Areas that need to be tested,
• Areas that should not be tested,
• Scheduling Resource Planning,

xv
Test Development:
Test case Development (check list)
Test Procedure preparation. (Description of the test cases)
Test Execution Implementation of test cases.
Result Analysis:
Expected value: is nothing but expected behavior of application.
Actual value: is nothing but actual behavior of the application Bug Tracing:
Collect all the failed cases, prepare documents. Reporting:
Prepare document (status of the application)

5.7.3. Types of Testing

Smoke Testing: is the process of initial testing in which tester looks for the availability of
all the functionality of the application in order to perform detailed testing on them. (Main
check is for available forms)
Sanity Testing: is a type of testing that is conducted on an application initially to check for
the proper behavior of an application that is to check all the functionality are available before
the detailed testing is conducted by on them.

Regression Testing: is one of the best and important testing. Regression testing is the process
in which the functionality, which is already tested before, is once again tested whenever
some new change is added in order to check whether the existing functionality remains same.

Re-Testing: is the process in which testing is performed on some functionality which is

already tested before to make sure that the defects are reproducible and to rule out the
environment’s issues if at all any defects are there.
Static Testing: is the testing, which is performed on an application when it is not been
executed.
ex: GUI, Document Testing

Dynamic Testing: is the testing which is performed on an application when it is being

executed. Ex: Functional testing.

Alpha Testing: it is a type of user acceptance testing, which is conducted on an application

when it is just before released to the customer.

xvi
Beta-Testing: it is a type of UAT that is conducted on an application when it is released to
the customer, when deployed in to the real time environment and being accessed by the real
time users.
Monkey Testing: is the process in which abnormal operations, beyond capacity operations
are done on the application to check the stability of it in spite of the user’s abnormal
behavior. Compatibility testing: it is the testing process in which usually the products are
tested on the environments with different combinations of databases (application servers,
browsers…etc.) In order to check how far the product is compatible with all these
environments platform combination.
Installation Testing: it is the process of testing in which the tester tries to install or try to
deploy the module into the corresponding environment by following the guidelines
produced in the deployment document and check whether the installation is successful or
not.
Adhoc Testing: Adhoc Testing is the process of testing in which unlike the formal testing
where in test case document is used, without that test case document testing can be done of
an application, to cover that testing of the future which are not covered in that test case
document. Also, it is intended to perform GUI testing which may involve the cosmetic
issues.

5.7.4. TCD (Test Case Document):

Test Case Document Contains
• Test Scope (or) Test objective
• Test Scenario
• Test Procedure
• Test case

The procedure for testing this screen is planned in such a way that the data entry, status
calculation functionality, saving and quitting operations are tested in terms of Gui testing,
Positive testing, Negative testing using the corresponding Gui test cases, Positive test cases,
Negative test cases respectively

xvii
Test Cases:

Table 1 below shows Template for Test Case

T.C.No Description Exp Act Result

Table 1: Template for Test Case

5.7.5. Guidelines for Test Cases:

a)GUI Test Cases:
i. Total no of features that need to be check
ii. Look & Feel
iii. Look for Default values if at all any (date & Time, if at all any require)
iv. Look for spell check

Table 2 below shows Example for GUI Test cases:

T.C. Actual
No Description Expected value value Result
Check for all the features in the The screen must contain
1 screen all the features
Check for the alignment of the The alignment should be
2 objects as per the validations in proper way
Table 2: Example of GUI Test Case

b)Positive Test Cases:

i. The positive flow of the functionality must be considered
ii. Valid inputs must be used for testing
iii. Must have the positive perception to verify whether the requirements are justified.

Table 3 below shows Example for Positive Test cases:

T.C. Description Expected value Actual Result
No value

1 Check for date left for The date and time of

advertised job vacancy closure the advertised job must
be displayed

xviii
2 Enter the valid username and It should accept
password for job seeker
Table 3: example of positive test case

c)Negative Test Cases:

i. Must have negative perception.
ii. Invalid inputs must be used for test.

Table 4 below shows Example for Negative Test cases:

T.C. Description Expected value Actual Result
No value
1 Try to modify the information Modification should not
in date and time beallowed
2 Enter invalid data in to the job It should not accept
seeker login form invalid data, save should
not allow
Table 4: example of a negative test case

SYSTEM IMPLEMENTATION
It is the process of ensuring that the information system is operational, and then allowing
users to take over its operation for use and evaluation. Implementation of Job Search portal
includes activities such as:
i. Training of end users how the whole system operates and the functionalities of the system
ii. Evaluation of the system on regular intervals.
iii. Completion of user documentation system changeover

xix
 CHAPTER FOUR
4.0 SYSTEM DESIGN
System design is the process of planning to develop a new system or to make changes to the
existing system to come up with a newly proposed system. Design entails selection of
development tools and production of detailed procedures that states how design process will
be carried and implementation of the proposed system
4.1 DESIGN TOOLS
External Entry

Data flow

Process/operation
Data store

Tables

xx
4.2 ENTITY RELLATIONSHIP DIAGRAM (ERD)
id
Job title

id name

relate gender
s
name

age registration age

statuss

has

LOGIN

USERNAME PASSWORD

xxi
4.3 DATA FLOWCHAT

STAR
T

LOGIN

CON
DITI

MENU

Registration workers

STOP

xxii
4.4 PHYSICAL DESIGN
LOGIN FORM

MENU FORM

xxiii
REGISTRATION

xxiv
SYSTEM’S DATABASE
REGISTRATION

FINDINGS
Most companies do not have their own Job Portals for advertising job vacancies.
Most existing job portals do provide platform for hiring of Casual job seekers
Most job sites are prone to phishing, hence lack of data confidentiality, integrity, availability.

RECCOMENDATIONS
Job Search portal provides a platform where companies that lack their own website can
advertise their Job vacancies.
Encrypting user data and ensuring multiple layers of security to avoid phishing hence helps
to maintain Confidentiality, Integrity and Availability
Job Search portal caters for the casual job seekers

xxv
CONCLUSIONS
In conclusion, we intended to solve some problems that job seekers and companies are facing
today. The main aim of this work was to develop a web job portal, which caters for various
types of users and is easy to use. The advantages of the new portal are as follows:
i. Achieve the main targets of the Project
ii. Standard content, services and display
iii. High level management and flexibility
This work has focused on improving the online job portals and tried to reduce some problems
that existed in them by developing a knowledge system that also acts as a job portal. Thus,
this portal can be more beneficial with further enhancements the services and features. We
divided the future enhancement of this system into three areas of improvements, as follows:
i. Graphic improvements
ii. Contents improvements
iii. Technical improvements

REFERENCES
H. Sylva, and S. T. Mol, “E-recruitment: A study into applicant perceptions of an online
application system”, International Journal of Selection and Assessment, Vol. 17, No. 3.,
2009, pp. 311-323.
M. Haroon, and M. Zia-ur-Rehman, “E-recruitment: Across the small and large firms in
Pakistan”, Interdisciplinary Journal of Contemporary Research in Business, Vol. 2, No. 1,
2010, pp. 179-191.
A. B. Holm, “E-recruitment: Towards an ubiquitous recruitment process and candidate
relationship management”, ZeitschriftfürPersonalforschung , Vol. 26, No. 3, 2012, pp. 241-
25.
N. Mo. A. Munassar, and A. Govardhan, “A comparison between five models of software
engineering”, International Journal of Computer Science Issues, Vol. 7, Issue 5, 2010, pp.
94101.

xxvi
 Appendix
CODING
LOG IN
Private Sub cmdexit_Click()
Unload Me
End Sub

Private Sub cmdlogin_Click()

Dim user As String
Dim pass As String
user = "admin"
pass = "12345"
If (user = username.Text And pass = password.Text) Then
MsgBox "login successful"
menu.Show
Else
MsgBox "login failed"
End If
End Sub

MENU

Private Sub cmdadmin_Click()

registration.Show
End Sub

Private Sub cmdexit_Click()

Unload Me
login.Show
End Sub

REGISTRATION

Private Sub cmdexit_Click()

Unload Me
menu.Show
End Sub

Private Sub cmddelete_Click()

Set rs = New Recordset
Call connect
rs.Open "delete from registration where id = '" & txtid & "'", cn
MsgBox "YOU WANT TO DELETE RECORD", vbInformation
txtid = ""
txtname = ""
cmbage = ""
txtnationality = ""
txtdate1 = ""
cmbstatus = ""
cmbgender = ""

xxvii
End Sub

Private Sub cmdok_Click()

Set rs = New Recordset
Call connect
rs.Open "insert into registration(id,name,age,nationality,date1,status,gender)values('" & txtid & "','" &
txtname & "','" & cmbage & "','" & txtnationality & "','" & txtdate1 & "','" & cmbstatus & "','" &
cmbgender & "')", cn
MsgBox "YOU WANT TO ADD RECORD", vbInformation
txtid = ""
txtname = ""
cmbage = ""
txtnationality = ""
txtdate1 = ""
cmbstatus = ""
cmbgender = ""
End Sub

Private Sub cmdsearch_Click()

Set rs = New Recordset
Call connect
rs.Open "select * from registration where id = '" & txtid & "'", cn
If Not rs.EOF Then
txtid = rs!id
txtname = rs!Name
cmbage = rs!age
txtnationality = rs!nationality
txtdate1 = rs!date1
cmbstatus = rs!Status
cmbgender = rs!gender
Else
MsgBox "ID NOT FOUND", vbInformation
End If
End Sub

xxviii