Classification:
Kingdom of Saudi Arabia
Personal
Ministry of Education
King Khalid University
Applied College
English Title
العنوان بالعربي
: Prepared by
االرقام الجامعية أسماء الطالبات
Supervisor
Classification:
Personal
This document is submitted to King Khalid University to fulfill the
requirements for an applied diploma degree in ……….
2026 - 1447
Classification:
Personal
Committee report
I
Classification:
Personal
Acknowledgement
First and foremost, praise and thanks to God, the Almighty, for His showers of
blessings throughout my project to complete this work successfully.
We would like to express my deep and sincere gratitude to my project supervisor,
(Name) , for giving me the opportunity to do this project and providing invaluable
guidance throughout this project. Her dynamism, vision, sincerity, and motivation
have deeply inspired me. She has taught me the methodology to carry out this project
and to present the work as clearly as possible. It was a great privilege and honor to
work and study under her guidance. We extremely grateful for what he has offered
me.
We extremely grateful to our parents for their love, prayers, caring, and sacrifices to
educate and prepare me for our future. Also, We express my thanks to our sisters and
brothers for their support and valuable prayers.
Finally, we thanks go to all the people who have supported me to complete this
project directly or indirectly.
II
Classification:
Personal
ABSTRACT
III
Classification:
Personal
TABLE OF CONTENTS
IV
Classification:
Personal
TABLE OF FIGURES
V
Classification:
Personal
Tables
VI
Classification:
Personal
Chapter 1
Introduction
VII
Classification:
Personal
1- BACKGROUND
2- PROBLEM DEFINITION
3- IMPORTANCE OF RESEARCH
4- OBJECTIVES
1
Classification:
Personal
5- RESEARCH METHODOLOGY
The construction will be used to create the website following the
waterfall methodology.
Requirement
Design
Development
Testing
Deployment
Maintenance
Figure 1.2: Waterfall Methodology
Requirements:
The Waterfall methodology depends on the belief that all project requirements can
be gathered and understood upfront. The project members does their best to get a
detailed understanding of the project sponsor’s requirements. Written requirements,
we contained in a single document, are used to describe each stage of the project,
including the costs, assumptions, risks, dependencies, success metrics, and timelines
for completion.
Design:
Here, website developers design a technical solution to the problems set out by the
product requirements, including scenarios, layouts, and data models. First, a higher-
level or logical design is created that describes the purpose and scope of the project,
the general traffic flow of each component, and the integration points. Once this is
2
Classification:
Personal
complete, it is transformed into a physical design using specific hardware and
software technologies.
Implementation:
Once the design is complete, technical implementation starts. This might be the
shortest phase of the Waterfall process because painstaking research and design
have already been done. In this phase, programmers code applications based on
project requirements and specifications, with some testing and implementation
taking place as well. If significant changes are required during this stage, this may
mean going back to the design phase.
Verification or testing:
Before a product can be released to customers, testing needs to be done to ensure the
product has no errors and all the requirements have been completed, ensuring a
good user experience with the software. The testing team will turn to the design
documents, personas, and user case scenarios supplied by the product manager to
create their test cases.
Deployment and maintenance:
Once the software has been deployed in the market or released to customers, the
maintenance phase begins. As defects are found and change requests come in from
users, a team will be assigned to take care of updates and release new versions of the
software.
3
Classification:
Personal
6. Timeline
The following table outlines the expected timeline for our project:
PHASE DURATION
Information collection 1 weak
Data analysis 1 week
Design website 2 weeks
Test the website 1 day
Publish the website 1 day
Report writing 1 month
Table 1.1 time line
4
Classification:
Personal
7. LITERATURE REVIEW
5
Classification:
Personal
Chapter 2
Design
6
Classification:
Personal
1. HOW TO DESIGN
2. TOOLS
3. SOFTWARE
4. HARDWARE
Its requirement PC configuration:
PROCESSOR NAME : Intel Core i5 or more.
THE PROCESSOR SPEED is 2.5 GHz.
RAM: 16 GB
REQUIREMENT MEMORY STORAGE have 128 GB.
7
Classification:
Personal
CHAPTER 3
ANALAYSIS
8
Classification:
Personal
3.1. USE CASE DIAGRAM
A UML use case diagram is the primary form of system/software requirements
for a new software program underdeveloped. Use cases specify the expected
behavior (what), and not the exact method of making it happen (how). Use cases
once specified can be denoted both textual and visual representation (i.e. use case
diagram). A key concept of use case modeling is that it helps us design a system
from the end user's perspective. It is an effective technique for communicating
system behavior in the user's terms by specifying all externally visible system
behavior.
A use case diagram is usually simple. It does not show the detail of the use cases:
• It only summarizes some of the relationships between use cases, actors, and
system.
• It does not show the order in which steps are performed to achieve the goals of
each use case.
As said, a use case diagram should be simple and contains only a few shapes. If
yours contain more than 20 use cases, you are probably misusing use case diagram.
The figure below shows the UML diagram for the research.
Figure 3.1: Use Case Diagram for Tourist & Site Manager
3.2. SEQUENCE DIAGRAM
UML Sequence Diagrams are interaction diagrams that detail how operations are
carried out. They capture the interaction between objects in the context of a
collaboration. Sequence Diagrams are time focus and they show the order of the
interaction visually by using the vertical axis of the diagram to represent time what
messages are sent and when.
9
Classification:
Personal
Sequence Diagrams captures:
• the interaction that takes place in a collaboration that either realizes a use case or
an operation (instance diagrams or generic diagrams).
• high-level interactions between user of the system and the system, between the
system and other systems, or between subsystems (sometimes known as system
sequence diagrams).
Purpose of Sequence Diagram:
• Model high-level interaction between active objects in a system. • Model the
interaction between object instances within a collaboration that realizes a use case. •
Model the interaction between objects within a collaboration that realizes an
operation. • Either model generic interactions (showing all possible paths through
the interaction) or specific instances of an interaction (showing just one path
through the interaction).
The figure below shows the Sequence diagram for the research.
Figure 3.2: Sequence Diagram
3.3. CLASS DIAGRAM
In software engineering, 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 classes, their attributes, operations (or methods), and the
relationships among objects.
Purpose of Class Diagrams:
1. Shows static structure of classifiers in a system.
2. Diagram provides a basic notation for other structure diagrams prescribed by
UML.
3. Helpful for developers and other team members too.
4. Business Analysts can use class diagrams to model systems from a business
perspective.
A UML class diagram is made up of:
10
Classification:
Personal
• A set of classes and • A set of relationships between classes.
The figure below shows the Class diagram for the research.
Figure 3.5: Class Diagram
11
Classification:
Personal
CHAPTER4
Result
12
Classification:
Personal
4.1. INTRODUCTION
This chapter presents the website with all its pages
4.2. WEBSITE PAGES OR Software Interfaces
13
Classification:
Personal
Chapter 5
Testing
14
Classification:
Personal
5.1. System Testing:
5.2. Testing Objectives:
5.3. Testing result
Pages Pages Task Pass Not Pass
Does the browse link work? yes
Does the browse link work? yes
Does the browse link work? yes
Does the browse link work? yes
Does the browse link work? yes
Does the browse link work? yes
Does the browse link work? yes
Does the browse link work? yes
Table 5.1 Testing
15
Classification:
Personal
CHAPTER 6
CONCLUSION &
FUTURE WORK
16
Classification:
Personal
6.1. CONCLUSION
17
Classification:
Personal
6.2. FUTURE WORK
18
Classification:
Personal
REFERENCES
19