Libyan International Medical University

Faculty of Information Technology

Developing a Job seeker website for Benghazi

City

Name: Aya Tawfig Eltawil

Number: 1662

Supervisor: Bilal Aljabour

Submitted in partial fulfillment of the requirements of B.Sc. Degree in

Information Technology

Spring 2020-2021
 DECLARATION

This is to declare that the graduation project report produced under the supervision of:

Having the title:

Is a contribution of the student below and no part of this report has been reproduced illegally.
All referenced parts have been used in this report have been cited properly. I will be
responsible for any consequences if violation of this declaration is proven.

Date:

Project Student:

Name: Signature :

i
 CERTIFICATION

This project entitled “ ”

prepared by “ ” and “ ”,

under the supervision of “ ”, Has been approved

for submission to the department of “

”,

Faculty of Information technology in a partial fulfilment for the certification of bachelor’s

degree in information technology.

Supervisor:

Libyan International Medical University

Signature:

Candidate:

Signature:

Candidate:

Signature:

ii
 Acknowledgement

The success of this project required guidance and assistance from many people and I am

extremely privileged to have this all along the completion of my project. All that I have done

is only due to such supervision and assistance and I would not forget to thank them.

In starter I would like to gift this success to my family who were my strength and a massive

support in the whole journey of life not only their support and encouragement through this

project.

I respect and thank my supervisor and my mentor Mr. Bilal Al Jabour, for all the support and

guidance which made me complete the project duly. I am extremely thankful to him for all the

scientific and practical advices in our field of study.

It is a pleasure to be mentored by such great teachers through my path in university and I would

like to express my gratitude specially for:

o Dr. Mohammad Abdullah.

o Alla Barakat.

Lastly, I am thankful for having amazing friends, they stood by me in all situations and they

were the most supportive people and I wish them success in their upcoming life.

iii
 Abstract

The purpose of this project is to provide an idea of a job search website, and to demonstrate

all the stages of software development life cycle to build the system. This essence of the project

idea has a business and a social side as well, and this was the real motive for adopting and

developing the idea. The main goal of the web project is to help people find work in an easier

way and in less time.

The incremental model, which is a software development method, has been adopted as a

development process methodology and made the process simple and less complicated. After

selecting the appropriate methodology, the following PHP, HTML and CSS are used in the

implementation stage in order to obtain a working website.

In the last stage, many test cases have been carried out to ensure that all functions the web

application works as intended and the user receives the output as desirable.

The challenges faced during building this application with the chosen techniques and

methodologies have benefits, it led to the construction of an easy to use, maintainable and

practical website that can help a lot of people to find workers, and much more of people to find

jobs.

iv
Table of contents

Chapter 1 Introduction

1.1 Background …………………………………………………………………….. 2

1.2 The Problem Statement ……………………………………………………….... 3

1.3 Aim and Objectives …………………………………………………………….. 4

1.4 Scope and Limitations ………………………………………………………….. 4

1.5 Methodology …………………………………………………………………..... 5

1.6 Project Structure ………………………………………………………………… 6

Chapter 2 Requirements

2.1 Introduction………………………………………………………………………… 8

2.2 Feasibility Study…………………………………………………………………… 8

2.2.1 Operational Feasibility study…………………………………………………….... 8

2.2.2 Technical Feasibility Study………………………………………………………… 9

2.3 Requirements Elicitation…………………………………………………………... 10

2.3.1 Requirements Elicitation Techniques……………………………………………… 10

2.4 Scenarios…………………………………………………………………………… 11

2.5 Use Case Diagram………………………………………………………………….. 15

2.6 Use Cases…………………………………………………………………………... 11

2.7 Software Requirements specifications document…………………………………... 24

2.7.1 Overview of Software requirements specification…………………………………………. 24

v
2.7.2 Purpose……………………………………………………………………………………… 24

2.7.3 Intended audience…………………………………………………………………………... 25

2.7.4 Scope of the web application……………………………………………………………….. 25

2.7.5 Glossary……………………………………………………………………………………... 25

2.7.6 Outline……………………………………………………………………………….. 25

2.7.7 Overall Description………………………………………………………………………….. 26

2.7.8 Product Perspective………………………………………………………………………….. 26

2.7.9 Product Functions…………………………………………………………………………… 26

2.7.10 User Characteristics…………………………………………………………………. 26

2.7.11 Constraints…………………………………………………………………………………… 27

2.7.12 Assumption and Limitation………………………………………………………………….. 27

2.7.13 Specific Requirements………………………………………………………………………. 27

2.7.14 External Interface Requirements…………………………………………………………….. 28

2.7.15 Hardware Interfaces…………………………………………………………………………. 32

2.7.16 Communications Interfaces…………………………………………………………………. 32

2.7.17 Functional requirements and non-functional requirements………………………………….. 32

2.7.18 Design Constrains…………………………………………………………………………… 37

2.7.19 Prioritization and Release Plan……………………………………………………………… 37

2.7.20 Requirements Validation…………………………………………………………… 38

Chapter 3 Design

3.1 Overview…………………………………………………………………………………… 40

3.2 Software Design……………………………………………………………………. 40

3.2.1 UML Activity Diagram…………………………………………………………….. 40

vi
 3.2.2 UML Sequence Diagram………………………………………………………….. 44

3.2.3 UML Class Diagram……………………………………………………………….. 49

3.2.4 UML Component Diagram………………………………………………………… 50

3.2.5 Database Structure…………………………………………………………………. 51

Chapter 4 Implementation

4.1 Implementation Phase…………………………………………………………….. 57

4.2 Technologies used………………………………………………………………… 57

4.3 Challenges………………………………………………………………………… 58

4.4 Increments delivery……………………………………………………………….. 59

4.5 Gantt chart for implementation stage……………………………………………... 61

Chapter 5 Testing

5.1 Testing Phase……………………………………………………………………. 67

5.1.1 Test cases………………………………………………………………………… 67

5.2 Test matrix………………………………………………………………………. 75

Chapter 6 Conclusion

6.1 Summary…………………………………………………………………………... 78

6.2 Future Work………………………………………………………………………. 79

Reference………………………………………………………………………..…. 80

vii
 List of tables

Table 2. 1 Use case table explain the creation of the user account …………………………… 15

Table 2. 2 Use case table explain user logging in to website………………………………….. 16

Table 2.3 Use case table concerned of how the seeker and the visitor search jobs…………… 17

Table 2. 4 Use case table concerned of how the company user searches for seeker………….. 18

Table 2. 5 Use case table concerned of how the company user view applicants list………….. 19

Table 2. 6 Use case table concerned of how the company user Manage Job List…………….. 20

Table 2.7 Use case table concerned of how the visitor view recent jobs……………………… 20

Table 2. 8 Use case table concerned of how the visitor view recent job………………………. 21

Table 2. 9 Use case table concerned of how the admin Manage Company Account…………. 22

Table 2.10 Use case table concerned of how the admin Manage Seekers Accounts…………… 23

Table 2.11 Use case table concerned of how the admin View reports and statistics…………… 23

Table 2.12 Terms used in this project are described in this table………………………………. 25

Table 2.13 describe the functional requirements required in this project………………………. 33

Table 2.14 Traceability matrix matching the functional requirements and use cases………….. 36

Table 2.15 non-functional requirements ………………………………………………………. 37

Table 2.16 shows the increments of the project………………………………………………... 38

Table 3.1 Seeker table in database and its datatype…………………………………………… 52

Table 3.2 Job table in database and its datatype………………………………………………. 53

Table 3.3 Company table in database and its datatype………………………………………... 54

Table 3.4 Admin table in database and its datatype…………………………………………… 55

Table 4. 1 Increments and their time planned…………………………………………………. 60

Table4. 2 Increments and their actual time to implement……………………………………... 60

Table 5.1 test case for register a Company…………………………………………………… 67

viii
Table 5.2 test case for user login……………………………………………………………… 69

Table 5.3 test case for search for jobs………………………………………………………… 70

Table 5.4 test case for Company post a job…………………………………………………… 71

Table 5. 5 test matrix………………………………………………………………………….. 76

ix
 Table of figures

Figure 1.1 shows incremental model phases…………………………………………………... 6

Figure 2. 1 percentage of responses of the questioner…………………………………………. 9

Figure 2. 2 use case diagram illustrates the interaction in the web application………………… 14

Figure 2. 3 shows searching for jobs interface…………………………………………………. 28

Figure 2. 4 shows creating account for company interface…………………………………….. 29

Figure 2. 5 shows creating account for Seekers interface……………………………………… 30

Figure 2. 6 shows report and statistics interface……………………………………………….. 31

Figure 3. 1 shows UML Activity Diagram for Seeker creates account…………………………. 41

Figure 3. 2 shows UML Activity Diagram for Seeker creates account………………………… 42

Figure 3. 3 shows UML Activity Diagram for Seeker and visitor search for jobs……………… 43

Figure 3.4 Shows UML Sequence Diagram for Seeker creates account………………………. 44

Figure 3.5 Shows UML Sequence Diagram for Company User creates account……………….. 45

Figure 3. 6 shows UML Sequence Diagram for Company User searching for seeker…………… 46

Figure 3. 7 shows UML Sequence Diagram for Seeker searching for Jobs………………………. 47

Figure 3. 8 shows UML Sequence Diagram for Visitor searching for Public Jobs………………. 48

Figure 3. 9 shows UML Class Diagram………………………………………………………….. 49

Figure 3.10 shows UML Component Diagram…………………………………………………… 50

Figure 3.11 Shows the Database Diagram………………………………………………………… 51

Figure 4. 1 Gantt chart for the project……………………………………………………………. 61

Figure 4.2 home page interface of the website………………………………………………….. 62

Figure 4.3 Login interface……………………………………………………………………….. 63

Figure 4.4 Register a Company interface of the website………………………………………… 64

Figure 4.5 The database of the website………………………………………………………….. 65

x
Figure 5.1 Shows register a Company test………………………………………………………. 73

Figure 5.2 Shows a login test……………………………………………………………………. 74

Figure 5.3 Shows a search test…………………………………………………………………… 74

Figure 5.4 Shows a Company post a job test…………………………………………………….. 75

xi
 Chapter 1

Introduction

1
1.1 Background:

According to several studies, unemployment in Libya is in forms and types, and

between complete unemployment, which means complete cessation of work, lack of

opportunities to engage in labor activities, and partial unemployment, Libya suffers

from Compelling unemployment, which is the result of the exit of international

companies from the country, which led to the stoppage The worker is out of work due

to the security situation and the collapse of the economy and development wheel in the

country. [1]

Like each other part of live, the internet has revolutionized the way to find work. For a

job seeker, this may be useful as there are numerous ways that online tools and

resources can help them find what they are searching for. Today, a job seeker can search

for jobs in a myriad of places and make an online presence to be discovered on the web.

[2]

A job website acts as an open job search engine and database. Job sites can help

applicants find employment in any industry with any level of education and experience.

In order to locate and apply for as many appropriate jobs as possible, anyone actively

pursuing a career should strongly consider using a job website. [3]

Most employment sites are free to browse. Users just type in their desired job title and

search for opportunities in their area. However, some work sites require upfront

payment to unlock full browsing and application privileges. Once the user applies to a

job through a job site, the hiring manager will review their information and reach out

2
to them if interested. Certain platforms allow employers to reach out to qualified

candidates whether or not they’ve applied for an open position with the company. [4]

With job websites, companies have specifically identified their open positions and often

accept job applications directly through the job websites. Employers usually pay a fee

to the job websites to list their jobs on the site. [5]

1.2 Problem statement:

Finding a job is not as easy as many people think. Most people find themselves firing

lots of applications a day in the hopes that they’ll get called for at least one of them.

There are many ways that may seem promising to a job seeker, such as TV and radio

advertisements, applying for a job through recruiters and by referrals. However, most

of the people who apply for jobs using these techniques often end up with little to no

results.

Companies and business organizations are on the constant lookout for new employees.

These organizations usually put out job opportunity advertisements on broadcast news

and on print media like newspapers and magazines.

Their main goal is to find the right person with the right qualifications for a specific

job. Surprisingly, even though big amounts of money are invested in these ads, these

organizations still find it non-viable to find the specialized person they are searching

for.

Not all job seekers want a full time job. Some seekers, like university students for

instance, desire a part time job that can fit just right in their schedule.

This is a problem, as it is inconvenient and highly unlikely for them to not find what

they are searching for.

3
1.3 Aims and Objectives:

The aim of this project is to develop a website for Job Seekers.

Project objectives:

1. To provide the advantage of being able to communicate with professionals in

different fields of work.

2. To help in facilitating the process of searching for candidates.

3. To provide the advantage of being able to submit an employment website or an

individual's CV online.

4. To help people looking for jobs to save effort and money and to help job seekers to

find jobs more easily.

5. To help applicants to choose the appropriate work time for them and provide the

ease of differentiation among job applicants.

6. To attract people with multi-dimensional skills and experience that are suitable for

organizations.

7. To provides a wider spread of companies.

8. To provide the Speed in posting jobs.

9. To provide the access to applicants 24 hours a day.

1.4 Project Scope and limitation:

A website to provide jobseekers in the city of Benghazi with different jobs information

like online applying for jobs and search for jobs by enter applicants information and

attaching Curriculum Vitae (CV), it also provides the organizations and companies that

needs an employees the ability to sign up and enter the employee data that the company
4
needs. The companies can find the appropriate employee from the employee’s data.

Also, the admin can view reports and statistics.

The website will not provide the facilities for direct contact between seekers and

companies. Also, the availability of internet connection is a must to use the system.

1.5 Methodology:

The project will be implemented using the incremental model because it’s more

adaptable and fewer exorbitant to adjust scope and requirements, simpler to check and

debug during a smaller iteration, easier to manage risk because risky parts are

defined and treated during its iteration and every iteration is an easily managed

milestone, Error Reduction (core components are used by the customer from the

start of the process and then extensively tested),

divide and conquer uses for task breakdown, lowers initial cost of delivery.[6]

5
 Figure 1.1 shows incremental model phases. [6]

1.6 project structure:

The rest chapters of this report are:

• Chapter 2 Requirement

• Chapter 3 Design

• Chapter 4 Implementation

• Chapter 5 Testing

• Chapter 6 Conclusion

6
 Chapter 2

Requirements

7
2.1 Introduction

This chapter shows how the requirement have been collected, describe the types of

feasibility study have been used to evaluate the project, explains the elicitation of

requirements, describe the flow of the web application scenario, explains in details the

scenario in use cases, illustrate the use case diagram, and the overall description of

Software Requirements specifications.

2.2 Feasibility Study

A feasibility study is a way to evaluate the practicality and desirability of a project and

to determine whether a particular project is feasible or not.

2.2.1 Operational Feasibility Study

A questionnaire was published on the Internet and it was responded to in a random way

by people in Libya, and the response was the acceptance of the idea of creating a

website for job seekers.

101 responses were collected by different people, ages and genders. The questionnaire

contains a set of important questions, including:

• Have you ever had difficulty searching for a job?

• Have you tried using a job search website before?

• Have you ever heard of sites to search and apply for jobs online?

8
 • Do you support the existence of a specialized site to search for jobs in the city

of Benghazi?

Figure2. 1 percentage of responses of the questioner

The most important question was:

• Do you support the existence of a specialized website to search for jobs in the

city of Benghazi?

The percentage of the response to this question was 90.1% of people answered

with yes, then a lot of people support the idea of creating the website so this

project is operationally feasible.

2.2.2 Technical Feasibility Study

The required techniques for web development for this project are the HTML (Hyper

Text Markup Language), CSS (Cascading Style Sheets), PHP (Hypertext

9
Preprocessor), and MYSQL Database and all of these techniques are known and any

other techniques required in this project will be learned.

2.3 Requirements Elicitation

Requirements elicitation is a complex process that consists of gathering, researching,

defining, structuring, and clarifying a product's requirements.

2.3.1 Requirements Elicitation Techniques

The success of an elicitation technique used depends on the maturity of the analyst,

developers, users, and the customer involved. The techniques used in this project are:

i. Brainstorming

In order to agree on the idea of this project, four brainstorming sessions were held with

the supervisor of the graduation project, and many ideas were generated to create the

website.

ii. Similar Products

1. In Wazfna.com, the list of available jobs appears after entering the home page.

In this list, a user can create an account, log in. Both companies and seekers can

create accounts. Furthermore, there are options available that allow users to

upload their picture, C.V, and report any problems that they may face during

their visit to the website.

2. In Indeed.com, the user can search for a job and the location then appears a list

of jobs, the user can create an account and can search for jobs by Date Posted,

10
 Remote, Salary Estimate, Job Type, Location, Company and Experience Level.

The employers can contact with each other’s.

iii. Survey/Questionnaire

To gather information and to create a feasibility study, an online questionnaire was

created and it was answered by many people.

2.4 Scenario:

A website for any seeker looking for a Job, the user enters the website the homepage

appears, containing options and information about the site.

The admin can login to the site and modify the information. The applicants can create

an account and search for a job by enter their information and attaching Curriculum

Vitae (CV), the organizations and companies can create account on the website and

enter the employee data that the company needs.

The user can create an account and choose whether it is for a seeker or a company

• Create Account for the seeker:

The seeker enters information (name – phone number- age- gender- address- Email-

career – attaches C.V (Pdf- word)) and then it will be chosen by the seeker if it appears

for public or private (only for the users who have accounts) then the seeker enters

verification characters to make sure is a person and not a robot.

• Create Account for the company:

The company user enters information (name- address- Employment - Attach the logo-

phone numbers- Email – the company website – Facebook page) and then it will be

chosen by the company if it appears for public or private (only for the users who have

11
accounts) then the company user enters verification characters to make sure is a person

and not a robot.

• Login:

The user who has an account can login by entering the username and password. The

user can recover the password in case he forgot it.

• Search for Jobs:

The seeker can search for a job by (Career- age – gender-city) and if the seeker chose a

job the seeker can applies for it.

• Search for Seekers:

A company user can search for seekers by (Career- age- gender-city) and can view

applicants list for a specific job which means the list of seekers who apply for a specific

job.

• Manage Job List:

A company user can Manage Job list which means post a job and delete a post.

• The visitor:

The visitor can view recent jobs which means see the last jobs uploaded to site and the

visitor has the right to see the public jobs only, and can search for Jobs by (Career- age-

gender-city).

12
 • The Admin Login:

The admin can log into the site by entering the username and password previously

entered into the database, and can change the password.

• Manage Company Accounts:

The admin can manage company accounts which means activate and deactivate the

accounts.

• Manage Seekers Accounts:

The admin can manage seekers accounts which means activate and deactivate the

accounts.

• View reports and statistics:

The admin can display statistics and reports by searching for it based on a specific

request.

13
 2.5 Use Case Diagram

Login

Create Account

Apply for Job

Manage Job List

Manage company
Accounts

Manage Seekers Accounts

Seeker View Applicants List Admin

n

View recent Jobs

View reports and

Statistics

Search for Jobs

Extension point: the user is visitor Company
Visitor
<<extend>>

Search for public Jobs only

Search for seekers

Figure 2. 2 use case diagram illustrates the interaction in the web

application

14
2.6 Use Cases

A use case is a written description of how users will perform tasks on your website. It

outlines, from a user’s point of view, a system’s behavior as it responds to a request.

Table 2. 1 Use case table explain the creation of the user account.

ID UC1

Title Create Account

Description The user creates an account

Primary actor The seeker and the company user

Precondition The user enters the website

1. The seeker enters information

(name – phone number- age-

Main success scenario gender- address- Email- career –

attaches C.V (Pdf- word))’

2. 2. Then it will be chosen by the

seeker if it appears for public or

private (only for the users who

have accounts)

3. Then the seeker enters

verification characters to make

sure is a person and not a robot.

A1

15
 A1: 1. The company user enters

information (name- address-

Employment - Attach the logo- phone

numbers- Email – the company website –

Facebook page).

2. Then it will be chosen by the company

Alternative scenario user if it appears for public or private

(only for the users who have accounts).

iv. Then the company user enters

verification characters to

make sure is a person and not

a robot.

Success post condition The seeker or the company user created

an account

Priorty of Implementation 1

Table 2. 2 Use case table explain user logging in to website.

ID

UC2

Title User Login

Description The seeker and company user can Log

into the website

16
 Primary actor The seeker and the company user

Precondition The user has an account

1. The user can login by entering the

username and password.

Main success scenario 2. The user can recover the password in

case he forgot it.

Success post condition The user logged into successfully the

website

Exceptional scenario 5 wrong attempts the session will be

closed and the user can try again in 15

minutes.

Priorty of Implementation 7

Table 2. 3 Use case table concerned of how the seeker and the visitor search for

jobs.

ID UC3

Title Search for Jobs

Description The seeker and the visitor can search for

Jobs

Primary actor The seeker

Precondition The seeker logged into the website or

the visitor enters the website.

17
 1. The seeker can search for a jobs by

(Career- age – gender- city).

Main success scenario 2. The seeker can applies for a job.A1

Alternative scenario • A1: The visitor can search for the

public jobs only by (Career- age –

gender-city).

Success post condition The user found the jobs

Priorty of Implementation 2

Table 2. 4 Use case table concerned of how the company user searches for

seekers.

ID UC4

Title Search for Seekers

Description The company user can search for

Seekers

Primary actor The company user

Precondition The company user logged in

successfully to the website.

18
 • A company user can search for
seekers by (Career- age- gender-

Main success scenario city).

Success post condition The company found the Seekers

Priorty of Implementation 3

Table 2. 5 Use case table concerned of how the company user view applicants list.

ID UC5

Title View Applicants List

Description The company can view applicants list

Primary actor The company user

Precondition The company user logged in

successfully to the website.

• The Company user can view

applicants list for a specific job

Main success scenario which means the list of seekers

who apply for a specific job.

Success post condition The company user view applicants list

Priorty of Implementation 5

19
Table 2. 6 Use case table concerned of how the company user Manage Job List.

ID UC6

Title Manage Job List

Description The company can Manage Job List

Primary actor The company

Precondition The company user logged in

successfully to the website.

• The Company user can Manage

Job list which means post a job

Main success scenario and delete a post.

Success post condition The company user Managed Job List

Priorty of Implementation 6

Table 2. 7 Use case table concerned of how the visitor view recent jobs.

ID UC7

Title view recent jobs

Description The visitor can view recent jobs

Primary actor The visitor

Precondition The visitor enters the website

20
 • The visitor can view recent jobs

which means see the last jobs

Main success scenario uploaded to site and the visitor

has the right to see the public jobs

only

Success post condition The visitor view recent jobs

Priorty of Implementation 4

Table 2. 8 Use case table concerned of how the visitor view recent jobs.

ID UC8

Title Admin Login

Description The admin can log into the website

Primary actor The admin

Precondition The admin has an account

1. The admin can log into the site by

entering the username and

Main success scenario password previously entered into

the database.

2. The admin can change the

password.

Success post condition The admin logged in successfully to the

website

21
 Priorty of Implementation 11

Table 2. 9 Use case table concerned of how the admin Manage Company

Accounts.

ID UC9

Title Manage Company Accounts

Description The admin can Manage Company

Accounts

Primary actor The admin

Precondition The admin logged in successfully to the

website

• The admin can manage company

accounts which means activate and

Main success scenario deactivate the accounts.

Success post condition The admin Managed Company

Accounts

Priorty of Implementation 8

22
Table 2. 10 Use case table concerned of how the admin Manage Seekers

Accounts.

ID UC10

Title Manage Seekers Accounts

Description The admin can Manage Seekers

Accounts

Primary actor The admin

Precondition The admin logged in successfully to the

website

• The admin can manage seekers

accounts which means activate and

Main success scenario deactivate the accounts.

Success post condition The admin Managed Seekers Accounts

Priorty of Implementation 9

Table 2. 11 Use case table concerned of how the admin View reports and

statistics.

ID UC11

Title View reports and statistics

23
 Description The admin can View reports and

statistics

Primary actor The admin

Precondition The admin has an account

• The admin can display statistics

and reports by searching for it

Main success scenario based on a specific request.

Success post condition The admin View reports and statistics

Priorty of Implementation 10

2.7 Software Requirements specifications document

This section describes the requirements based on the previous stage of eliciting and

analyzing of the requirements using the standard of IEEE (830).

2.7.1 Overview of Software requirements specification

A software requirements specification (SRS) is a comprehensive description of the

intended purpose and environment for software under development. The SRS fully

describes what the software will do and how it will be expected to perform.

2.7.2 Purpose

The purpose of this document is to provide a detailed description of the requirements

of job seeker website. Also, it illustrates and explain the user interfaces and functions.

This document offers the idea of an undergraduate project to be implement in order to

graduate.

24
2.7.3 Intended audience

• Supervisor of the undergraduate project

• Discussion Committee of the university.

2.7.4 Scope of the web application

A website to provide jobseekers in the city of Benghazi with different jobs

information like online applying for jobs and search for jobs by enter applicants

information and attaching Curriculum Vitae (CV), it also provides the

organizations and companies that needs an employees the ability to sign up and

enter the employee data that the company needs. The companies can find the

appropriate employee from the employee’s data. Also, the admin can view

reports and statistics.

2.7.5 Glossary

Table 2. 12 Terms used in this project are described in this table

Term Definition

Seeker The person who looks for a job

Applicants The people who apply for a job

2.7.6 Outline

The following of this document include:

25
 • The first section shows system functionality, the user characteristics the

people who interact with the system, system constraints, and the

limitations of the system concerned about this website.

• The second section describe the Specific requirements. Also, it

illustrates the interfaces of the system.

• The third section explain the functional requirement and non-functional

requirement, Design constraints and requirement validation.

2.7.7 Overall description

An overall description of the requirement document of Job Seeker website.

2.7.8 Product Perspective

The website is not connected to other system, and it hosted on a web server.

2.7.9 Product Functions

The visitor of the website has the ability to search for public jobs only, the

seeker has the ability to create an account and search for jobs, the company user

has the ability to create an account and search for seekers and post a job and

delete it, and the admin have the ability to create an account and activate and

deactivate seekers and company accounts.

2.7.10 User Characteristics

People who interact with the system divided into:

26
 • The visitor who visits the website without creating an account and can search

for public jobs only.

• The seeker who creates an account and search for jobs and apply for jobs.

• The company user who creates an account and search for seekers and post a job

and delete it and view applicants list.

• The administrator of the website who creates an account and manage company

accounts and seekers accounts and can view reports and statistics.

2.7.11 Constraints

The administrator of the website is the only one responsible for activate and

deactivate seeker and accompany accounts, the company user is the only one

responsible for post a job and delete it, and the visitor is the one who can see

and search for public jobs only.

2.7.12 Assumptions and Limitations

The website will not provide the facilities for direct contact between seekers

and companies. Also, the availability of internet connection is a must to use the

website.

2.7.13 Specific requirements

All the specific requirements and functional requirements which describe the

system in details are included in this section.

27
2.7.14 External Interface Requirements
A wireframe is a schematic or blueprint that is useful for helping the

programmers and the designers think and communicate about the structure of

the software or website you're building. The wireframes give the designer the

visualization of the system and it provide the basic prototype and the description

of the user interfaces.

This section includes user interfaces of the system:

Figure 2. 3 shows searching for jobs interface

28
Figure 2. 4 shows creating account for company interface

29
Figure 2. 5 shows creating account for Seekers interface

30
Figure 2. 6 shows report and statistics interface

31
2.7.15 Hardware Interfaces

None.

2.7.16 Communications Interfaces

None.

2.7.17 Functional Requirements and non-functional requirements

This section contains the requirements that specify all the functions of the web

application.

32
 Table 2. 13 describe the functional requirements required in

this project.

FR ID Requirement description Use Priority

case of

implemen

tation

The system shall allow the seeker to create an account

FR 1 by entering the information (name – phone number-

age- gender- address- Email- career – attaches C.V UC1 1

(Pdf- word))

The system shall allow the company user to create an

FR2 account by entering the information (name- address- UC1

Employment - Attach the logo- phone numbers- Email 1

– the company website – Facebook page).

The system shall allow the user after creating the

FR3 account to choose the information if it appears for UC1 1

public or private.

The system shall allow the user enters verification

FR4 characters to make sure is a person and not a robot. UC1 1

The system shall allow the user to login by entering

FR5 username and password UC2 7

33
 The system shall allow the user to recover the

FR6 password. UC2 7

The system shall allow the seeker to search for jobs by

FR7 (Career- age- gender- city). UC3 2

FR8 The system shall allow the seeker to apply for a job. UC3 2

The system shall allow the visitor to search for the

FR9 public jobs only by (Career- age – gender-city). UC3 2

The system shall allow the company user to search for

FR10 seekers by (Career- age-gender-city). UC4 3

The system shall allow the company user to view

FR11 applicants list for a specific job. UC5 5

The system shall allow the Company user to Manage

FR12 Job list which means post a job and delete a post. UC6 6

The system shall allow the visitor to view recent jobs

FR13 which means see the last jobs uploaded to site and the UC7 4

visitor has the right to see the public jobs only

The system shall allow the admin can log into the site

FR14 by entering the username and password previously UC8 11

entered into the database.

34
 The system shall allow the admin to manage company

FR15 accounts which means activate and deactivate the UC9 8

accounts.

The system shall allow the admin to manage seekers

FR16 accounts which means activate and deactivate the UC10 9

accounts.

The system shall allow the admin to display statistics

FR17 and reports by searching for it based on a specific UC11 10

request.

35
 Table 2. 14 Traceability matrix matching the functional
requirements and use cases:
UC1 UC2 UC UC4 UC5 UC6 U UC U UC UC
3 C7 8 C 10 11
9
FR1 ✓

FR2 ✓

FR3 ✓

FR4 ✓

FR5 ✓

FR6 ✓

FR7 ✓

FR8 ✓

FR9 ✓

FR10 ✓

FR11 ✓

FR12 ✓

FR13 ✓

FR14 ✓

FR15 ✓

FR16 ✓

FR17 ✓

36
Table 2. 15 non-functional requirements

NRF ID Requirement Description

NFR1 The system must be understandable to users and easy to use.

NFR2 The system must have high performance and quick response and

reports must be ready in 20 second at most.

NFR3 The system must have high level of security.

NFR4 The design colors must be Comfortable to the eyes.

NFR5 The system must be available 24/7.

2.7.18 Design constrains

• The user interface must be in Arabic language to make sure the user understand

it.

2.7.19 Prioritization and Release Plan

This section includes the requirements and its priority of implementation and

assign it to increments where in each increment the requirement must be

designed, implemented, and tested.

37
Table 2. 16 shows the increments of the project.

Increment ID Requirement ID’s Time Planned to implement

Inc1 Fr1, Fr2, Fr3, Fr4 13 days

Inc2 Fr7, Fr8, Fr9, Fr10 14 days

Inc3 Fr11, Fr12, Fr13 15days

Inc4 Fr5, Fr6, Fr13, Fr14 17 days

Inc5 Fr15, Fr16, Fr17 12 days

2.7.20 Requirements Validation

Meetings have been conducted with the supervisor of the graduation project to approve

and validate the Requirements.

38
Chapter 3

Design

39
3.1Overview:

This chapter displays the software design phase of the software lifecycle. This

phase is considered the software’s blueprint that will lead to a functioning web

application when completed. Software design, both as a concept and as a

process are clarified in this chapter. Furthermore, unified modeling language

UML diagrams and the structure of the database created during this project will

be summarized in this chapter.

Unified modeling language UML is a modeling language in the field of

software engineering which aims to set standard ways to visualize the design

of a system. UML guides the creation of multiple types of diagrams such as

interaction, structure and behavior diagrams. [7]

3.2 Software Design:

The design phase of software development deals with transforming the customer

requirements as described in the SRS documents into a form implementable using a

programming language.

3.2.1 UML Activity Diagram

Activity diagram is an important diagram in UML to describe the dynamic aspects

of the system.

Activity diagram is basically a flowchart to represent the flow from one activity to

another activity. The activity can be described as an operation of the system.

The control flow is drawn from one operation to another. This flow can be

sequential, branched, or concurrent. [8]

40
• This activity diagram shows the steps of seeker registration

Figure 3. 1: shows UML Activity Diagram for Seeker creates account

41
• This activity diagram shows the steps of company registration

Figure 3. 2: shows UML Activity Diagram for Company creates account

42
 • This activity diagram shows the steps of searching for jobs

Figure 3. 3: shows UML Activity Diagram for Seeker and visitor search for jobs

43
3.2.2 UML Sequence Diagram

A sequence diagram is a type of interaction diagram because it describes

how—and in what order—a group of objects works together. These

diagrams are used by software developers and business professionals to

understand requirements for a new system or to document an existing

process.[9]

• This sequence diagram shows the steps of seeker registration

Figure 3.4: Shows UML Sequence Diagram for Seeker creates account

44
 • This sequence diagram shows the steps of company registration

Figure 3.5: Shows UML Sequence Diagram for Company User creates account

45
 • This sequence diagram shows the steps of company user searching for seekers

Figure 3. 6: shows UML Sequence Diagram for Company User searching for

seekers

46
• This sequence diagram shows the steps of seeker searching for jobs

Figure 3. 7: shows UML Sequence Diagram for Seeker searching for Jobs

47
 • This sequence diagram shows the steps of visitor searching for public jobs

Figure 3. 8: shows UML Sequence Diagram for Visitor searching for Public Jobs

48
 3.2.3 UML Class Diagram

The UML Class diagram is a graphical notation used to construct and visualize

object-oriented systems. A class diagram in the Unified Modeling Language (UML)

is a type of static structure diagram that describes the structure of a system by showing

the system's:[10]

Classes, their attributes, operations (or methods), and the relationships among objects.

Figure 3. 9: shows UML Class Diagram

49
3.2.4 UML Component Diagram

A component diagram is used to break down a large object-oriented system into the

smaller components, so as to make them more manageable. It visualizes the

relationships as well as the organization between the components present in the

system. [11]

Figure 3. 10: shows UML Component Diagram

50
 3.2.5 Database Structure:

Database design illustrates a detailed data model of a database also known

as the database schema. It shows the various tables that are in the system

and the relationships between the tables.

Seeker Job
Seeker_ID Job_ID
Name Comp_ID*
PhoneNo Job_title
Age Reg_Date
Reg_Date Req_skills
Gender City
Address Has_car
Email Gender
Career Age
CV_file Work_type
Allowed_for_public Salary
username Notes
password Allowed_for_public
user_status Show_in_HomePage

Company Admin
Comp_ID Username
CompName Password
Address 1
PhoneNo
Email
LogoImg
Website
FacebookPage
Employment
Allowed_for_public
username
password
user_status

Figure 3.11 Shows the Database Diagram

51
Table 3.1 Seeker table in database and its datatype

Seeker

Field Description Datatype and Notes

DataLength

Unique number of the seeker

SeekerID Int(11) Primary
Key

Name The name of the seeker Varchar(30)

The number of the seeker

PhoneNo Varchar(10)

Age Age of the seeker Varchar(30)

Reg_Date Seeker Registration date Date

Gender Gender of the seeker Varchar(8)

Address Address of the seeker Varchar(10)

Seekers
Email Email Varchar(30)

Type of Career that seeker

Career search for Varchar(10)

CV_file File name Varchar(255)

Seeker information shows for

Allowed_for_public public or private Boolean

Show_in_HomePage Seeker information shows in

homepage or not Boolean

username The username of the user Varchar(20) Unique

password The password of the user Varchar(10)

User_status Status of the user Varchar(5)

52
Table 3.2 Job table in database and its datatype

Job

Field Description Datatype and Notes

DataLength
Unique number of the job
JobID Int(11) Primary
Key
Unique number of the
CompanyID company Int(11) Foreign
Key

Job_title The title of the job Varchar(10)

Reg_Date job Registration date Date

The required skills in the job

Req_skills Varchar(15)

City City required in the job Varchar(10)

Does the required person own

Has_car a car or not Varchar(8)

Gender of required person

Gender Varchar(8)

Type of Career that seeker

Age search for Varchar(30)

Work_Type Type of work if its part time Varchar(15)

or full time

Salary Job salary Int(5)

Notes If any notes about the job Varchar(255)

Job information shows for

Allowed_for_public public or private Boolean

Show_in_HomePage Job information shows in

homepage or not Boolean

53
Table 3.3 Company table in database and its datatype

Company

Field Description Datatype and Notes

DataLength
Unique number of the
CompanyID company Int(11) Primary Key

Reg_date Registration date Date

Comp_name The name of the company Varchar(50)

Address Company address Varchar(10)

PhoneNo Numbers of Company Varchar(20)

Email Company Email Varhar(25)

Logo Image of the

LogoImg company Blob

Website Company website Varchar(25)

Facebook Page of
Facebook Page The company Varchar(25)

Employment Type of work if its part Varchar(10)

time or full time

Allowed_for_public Company information Boolean

shows for public or private

Show_in_HomePage Company information

shows in homepage or not Boolean

username The username of the user Varchar(20) Unique

Password The password of the user Varchar(10)

User_status Status of the user Varchar(5)

54
Table 3.4 Admin table in database and its datatype

Admin

Field Description Datatype and Note

DataLength
id The unique number of the admin Int(11)
Username The username of the admin Varchar(30) unique

Password The password of the admin Varchar(10)

55
 Chapter 4

Implementation

56
4.1 Implementation Phase

Implementation phase is one of the phases of Software Engineering Life Cycle, it

includes the actual creation of the project (the execution phase).

The implementation phase involves putting the project plan into action. This phase

involves the actual installation of the newly-developed system. This step puts the

project into production by moving the data and components from the old system and

placing them in the new system via a direct cutover. The software design is translated

into source code. All the components of the software are implemented in this phase.

[12]

4.2 Technologies used

The technologies used in order to implement and developing this website:

• Hypertext Markup Language (HTML)

HTML is the language used to create webpages. "Hypertext" refers to

the hyperlinks that an HTML page may contain. "Markup language" refers to the

way tags are used to define the page layout and elements within the page, it’s a

standardized system for tagging text files to achieve font, color, graphic, and

hyperlink effects on World Wide Web pages. [13]

• Cascading Style Sheet (CSS)

Cascading style sheets are used to format the layout of Web pages. They can be

used to define text styles, table sizes, and other aspects of Web pages that previously

57
could only be defined in a page's HTML. CSS helps Web developers create a

uniform look across several pages of a Web site. [14]

• Hypertext Preprocessor (PHP)

Hypertext Preprocessor, a scripting language used to create dynamic and

interactive HTML Web pages. A server processes PHP commands when a

website visitor opens a page, then sends results to the visitor’s browser. [15]

• Bootstrap

Bootstrap is a framework to help you design websites faster and easier.

• MY SQL Database

MySQL is a freely available open-source Relational Database Management

System (RDBMS) that uses Structured Query Language (SQL). A single

MySQL database can contain many tables at ones and store thousands of

individual records. [16]

4.3 Challenges

This section explains the difficulties faced while implementing the website

Which leads to a delay in the project

• Time management

The time is an important factor in any project, one of the main challenges that

faced this project is the limitation of time and many tasks to achieve.

58
 • New functionality learning

Learning new functionality consumes a lot of time and effort which is cause to

a delay in the project.

• Complexity of some requirements.

Some requirements of this project appear as it has been more complicated to

implement and difficult than expected.

• Covid 19

Because of the virus and the spread of the disease, it led to a delay in the process

of establishing and discussing the project.

4.4 Increments delivery

Based on the project’s plan of release, each release includes specific

requirements that has to be designed, implemented, tested and shown to

customer.

This section illustrates the increments and their delivery time.

The following table shows description of each increment and which date it

should be delivered in.

59
Table 4. 1 Increments and their planned time

Increment Requirement ID’s Required Time

ID

Inc1 Fr1, Fr2, Fr3, Fr4 13 days

Inc2 Fr7, Fr8, Fr9, Fr10 14 days

Inc3 Fr11, Fr12, Fr13 15days

Inc4 Fr5, Fr6, Fr13, Fr14 17 days

Inc5 Fr15, Fr16, Fr17 12 days

Table4. 2 Increments and their actual time to implement

Increment Requirement ID’s Date of submission

ID

Inc1 Fr1, Fr2, Fr3, Fr4 17 days

Inc2 Fr7, Fr9, Fr10 15 days

Inc3 Fr12, Fr13 9 days

Inc4 Fr5, Fr13, Fr14 13 days

Inc5 Fr15, Fr16, Fr17 11 days

60
 4.5 Gantt chart for implementation stage

A Gantt chart is a useful graphical tool which shows activities or tasks performed

against time. [19]

Each increment includes activities such as implementation and testing, the following

figure represents a time schedule that demonstrates the activities of this project.

Figure 4. 1 Gantt chart for the project

61
4.6 Implementing the design pattern:

Figure 4.2 home page interface of the website

62
Figure 4.3 Login interface

63
Figure 4.4 Register a Company interface of the website

64
Figure 4.5 The database of the website

65
Chapter 5

Testing

66
5.1 Testing Phase

The testing phase of the software development lifecycle (SDLC)

is wherever you concentrate on investigation and discovery. Throughout the

testing part, developers ascertain whether or not their code and programming work in

line with client needs. [17]

5.1.1 Test cases

A test case is a set of actions performed on a system to determine if it satisfies software

requirements and functions correctly. The purpose of a test case is to determine if

different features within a system are performing as expected and to confirm that the

system satisfies all related standards, guidelines and customer requirements. [18]. this

section illustrates the important test cases in the application.

Table 5.1 test case for register a Company

Test Case ID TC01

Description check company registration with valid

data

Requirement ID FR2

Go to site

Test Steps http://localhost/job/signincom.php/

enter (name- address- Employment -

Attach the logo- phone numbers- Email –

the company website – Facebook page-

Allowed_for_public -

67
 show_in_HomePage - username

password) and verification characters

then click register.

Company name = Al tatweer Company

Address = Benghazi

Employment = Full-time

Test Data Logo = image

Phone numbers = 0925116729

Email = tatweer@gmail.com

Facebook Page = Tatweer Company

Allowed_for_public = yes

show_in_HomePage = yes

username = tatweer

password = 1234

After admin activate the account the user

Expected Results should have the account created for him

and can see the website and have the

access for further functionalities

Actual Results Account is created successfully and

saved in the database

Type of test Black box testing

Pass/Fail Pass

68
 Date of Creation 5-9-2021

Executed By Rania Kablan

Table 5.2 test case for user login

Test Case ID TC02

Description check user login with valid data

Requirement ID FR5

Test Steps Go to site http://localhost/job/login.php/

enter (username password) and then

click login.

Test Data username = tatweer

password = 1234

Expected Results After admin activate the account the

user can login to the website and have

the access for further functionalities

Actual Results The user logged in successfully

Type of test Black box testing

Pass/Fail Pass

Date of Creation 5-9-2021

Executed By Rania Kablan

69
Table 5.3 test case for search for jobs

Test Case ID TC03

Description check search for jobs with valid data

Requirement ID FR7

Test Steps Go to site

http://localhost/job/jobsearch.php/

The user can search with (Gender –

address- age – career - notes).

Test Data Gender = male

Address = Benghazi

Age = from 25 to 35

Career = Math teacher

Notes = must has a master degree

Expected Results the results appear to the user

Actual Results the results appear to the user

Type of test Black box testing

Pass/Fail Pass

Date of Creation 6-9-2021

Executed By Rania Kablan

70
Table 5.4 test case for Company post a job

Test Case ID TC04

Description check company post a job with valid data

Requirement ID FR12

Test Steps Go to site

http://localhost/job/CreateJobs.php/

The company enter (Job_title – Required

skills - city – has car – gender - age –

work_type – salary - notes – Allowed for

public – show in home page).

Test Data Job_title = Math teacher

Required skills = a good communication

skills

City = Benghazi

has car = yes

Gender = male

Age = from 25 to 35

work_type = Full-time

salary = 1200

Notes = must has a Master degree

Allowed for public = yes

show in home page = yes

71
Expected Results the company post a job

Actual Results the company posted a job

Type of test Black box testing

Pass/Fail pass

Date of Creation 6-9-2021

Executed By Rania Kablan

72
5.2 Screenshots of tests:

Figure 5.1 Shows register a Company test

73
Figure 5.2 Shows a login test

Figure 5.3 Shows a search test

74
 Figure 5.4 Shows a Company post a job test

5.3 Test Matrix

Test matrix is used to capture actual quality, effort, the plan, resources and time

required to capture all phases of software testing.[19] This section present the test

matrix to ensure that all functional requirements are tested and passed the test.

75
Table 5. 5 Test Matrix

Functional

requirement Tested First test Last test

ID

FR1 ✓ Pass Pass

FR2 ✓ Pass Pass

FR3 ✓ Fail Pass

FR4 ✓ Pass Pass

FR5 ✓ Pass Pass

FR7 ✓ Pass Pass

FR9 ✓ Pass Pass

FR10 ✓ Pass Pass

FR12 ✓ Pass Pass

FR13 ✓ Fail Pass

FR14 ✓ Pass Pass

FR15 ✓ Pass Pass

FR16 ✓ Pass Pass

FR17 ✓ Pass Pass

76
Chapter 6

Conclusion

77
6.1 Summary

The spread of the Internet around the world and its development has led to the ease of

many parts of our lives, in addition to the increase in web applications, which has led

to an increase in the opportunities for searching online, and this is a solution to many

of the problems that most people face today, including the problem of searching for a

job.

The problem stated that is job search is a complex and demanding effort and it may take

a lot of time to find a job, long with the difficulties faced during the job search process,

and the effective job search involving important self-regulatory activities, such as goal-

directed effort and appropriate information gathering.

In the analyzing phase the solution proposed for this problem is developing such an

application to provide the jobseekers the ability to find a job more easily and in less

time.

The next stage in the process of building this application is to define the requirements

of the application and then design the appropriate solution in the design stage which

includes schemas, constraints, techniques and designs such as UML diagrams, database

design, user interfaces and many more guides in order to create a diagram for this

application.

Getting to the implementation stage in which many concepts are gradually

implemented, Requirements and designs turn into a working software application.

To ensure that the application works as intended, several test cases are conducted in the

testing phase to finally get the web app working in the right way like is expected.

78
6.2 Future Work

The future vision of this website makes it deal with online payment when registering

to the website, with the ability of payment when doing advertisements on the site.

79
References:

[1] Borzaga, C., Salvatori, G., & Bodini, R. (2019). Social and Solidarity Economy

and the Future of Work* This paper draws on a work that was previously published by

the ILO and is available at: http://www.ilo.org/wcmsp5/groups/public/—ed_emp/—

emp_ent/—coop/documents/publication/wcms_573160.pdf (Copyright © International

Labour Organization 2017.). Journal of Entrepreneurship and Innovation in Emerging

Economies, 5(1), 37–57. https://doi.org/10.1177/2393957518815300

[2] Smith, A. (2015, November 19). 1. The internet and job seeking. Pew Research

Center: Internet, Science & Tech. https://www.pewresearch.org/internet/2015/11/19/1-

the-internet-and-job-seeking/

[3] The 6 Best Sites for Job Seekers With Disabilities of 2021. (n.d.). The Balance

Careers. Retrieved September 9, 2021, from

https://www.thebalancecareers.com/best-sites-for-job-seekers-with-

disabilities-4768164

[4] The 10 Best Job Search Websites of 2021. (n.d.). The Balance Careers. Retrieved

September 9, 2021, from https://www.thebalancecareers.com/top-best-job-

websites-2064080

[5] Difference Between a Job Board and Search Engine. (n.d.-b). The Balance

Careers. Retrieved September 9, 2021, from

https://www.thebalancecareers.com/difference-between-a-job-board-and-a-

job-search-engine-2061865

80
[6] Incremental Model (Software Engineering) - javatpoint. (n.d.).

Www.Javatpoint.Com. Retrieved September 9, 2021, from

https://www.javatpoint.com/software-engineering-incremental-model

[7] What is Unified Modeling Language (UML)? (n.d.). What Is Unified Modeling

Language (UML). Retrieved September 9, 2021, from https://www.visual-

paradigm.com/guide/uml-unified-modeling-language/what-is-uml/

[8] What is Activity Diagram? (n.d.). Visual-Paradigm. Retrieved September 9, 2021,

from https://www.visual-paradigm.com/guide/uml-unified-modeling-

language/what-is-activity-diagram/

[9] Sequence Diagrams - What is a Sequence Diagram? (n.d.). Smart draw Retrieved

September 9, 2021, from https://www.smartdraw.com/sequence-diagram/

[10] UML - Class Diagram. (n.d.). Tutorials point. Retrieved September 9, 2021,

from https://www.tutorialspoint.com/uml/uml_class_diagram.htm

81
[11] What is Component Diagram? (n.d.). Visual-Paradigm. Retrieved September 9,

2021, from https://www.visual-paradigm.com/guide/uml-unified-modeling-

language/what-is-component-diagram/

[12] Sharma, P., & Singh, D. (2015). Comparative Study of Various SDLC Models

on Different Parameters. International Journal of Engineering Research, 4(4),

188–191. https://doi.org/10.17950/ijer/v4s4/405

[13] Hypertext Markup Language – HTML. (n.d.). Investopedia. Retrieved September

9, 2021, from https://www.investopedia.com/terms/h/html.asp

[14] CSS - MDN Web Docs Glossary: Definitions of Web-related terms | MDN.

(2021, September 6). Developer. Mozilla. https://developer.mozilla.org/en-

US/docs/Glossary/CSS

[15] PCMag. (n.d.). Definition of PHP. Retrieved September 9, 2021, from

https://www.pcmag.com/encyclopedia/term/php

[16] Moore, L. (2018, July 31). MySQL. Search Oracle.

https://searchoracle.techtarget.com/definition/MySQL

[17] T. (2021, August 23). What Is the Software Testing Life Cycle? A Complete

Guide. AI-Driven E2E Automation with Code-like Flexibility for Your Most

Resilient Tests. https://www.testim.io/blog/software-testing-life-cycle/

82
[18] Test Case. (n.d.). Tutorials point. Retrieved September 9, 2021, from

https://www.tutorialspoint.com/software_testing_dictionary/test_case.htm

[19] LAS VEGAS SANDS CORP., a Nevada corporation, Plaintiff, v. UKNOWN

REGISTRANTS OF www.wn0000.com, www.wn1111.com,

www.wn2222.com, www.wn3333.com, www.wn4444.com,

www.wn5555.com, www.wn6666.com, www.wn7777.com,

www.wn8888.com, www.wn9999.com, www.112211.com,

www.4456888.com, www.4489888.com, www.001148.com, and

www.2289888.com, Defendants. (2016). Gaming Law Review and Economics,

20(10), 859–868. https://doi.org/10.1089/glre.2016.201011

83