ICT103 System Analysis and Design: World Tours Online Booking System
VerifiedAdded on  2023/03/31
|18
|1773
|382
Case Study
AI Summary
This document presents a comprehensive analysis and design of an online tour booking system for "World Tours," a company providing online tour booking and payment facilities. The analysis includes use cases such as login, payment, tour scheme updates, and reservation, detailing actors, preconditions, triggers, and postconditions. A use case diagram illustrates the interactions between customers, staff, and the system administrator. The activity diagram outlines dynamic operations like customer login, tour booking, and employee management. Sequence diagrams depict the order of activities between the customer, system interface, and database, as well as the administrator's role in managing staff and tour schemes. A domain model class diagram identifies classes like customer, staff, tour, and payment, showcasing their attributes and operations. State machine diagrams detail the login and booking processes. User interface storyboards visualize the customer, guide, and admin interfaces. The conclusion summarizes the benefits of the online system and recommends user training. This case study provides a thorough overview of the system's functionality and design, offering valuable insights into online tour management.

Running head: Online Tour Booking 1
Online Tour Booking
Student Name
Student Number
Professor’s Name
Institution
Location of Institution
Date
Online Tour Booking
Student Name
Student Number
Professor’s Name
Institution
Location of Institution
Date
Paraphrase This Document
Need a fresh take? Get an instant paraphrase of this document with our AI Paraphraser

Online Tour Booking 2
Table of Contents
List of Figures..................................................................................................................................3
1 Introduction...................................................................................................................................4
1.1 Assumptions made............................................................................................................4
2 Use Cases......................................................................................................................................5
2.1 Login use case........................................................................................................................5
2.2 Payment Use Case.................................................................................................................5
2.3 Update tour scheme Use Case...............................................................................................6
2.4 Reservation use case..............................................................................................................6
3 Use Case Diagram........................................................................................................................7
4 Activity Diagram..........................................................................................................................9
5 Sequence Diagram......................................................................................................................10
5.1 Sequence Diagram one........................................................................................................10
5.2 Sequence diagram two.........................................................................................................11
6 Domain Model Class Diagram...................................................................................................12
7 State Machine Diagram..............................................................................................................13
7.1 Login....................................................................................................................................13
7.2 Booking................................................................................................................................13
8 User Interface Story Board.........................................................................................................14
8.1 Customer Storyboard...........................................................................................................14
8.2 Guide Storyboard.................................................................................................................15
8.3 Admin Storyboard...............................................................................................................16
9 Conclusion..................................................................................................................................17
9.1 Summary..............................................................................................................................17
9.2 Recommendation.................................................................................................................17
References......................................................................................................................................18
Table of Contents
List of Figures..................................................................................................................................3
1 Introduction...................................................................................................................................4
1.1 Assumptions made............................................................................................................4
2 Use Cases......................................................................................................................................5
2.1 Login use case........................................................................................................................5
2.2 Payment Use Case.................................................................................................................5
2.3 Update tour scheme Use Case...............................................................................................6
2.4 Reservation use case..............................................................................................................6
3 Use Case Diagram........................................................................................................................7
4 Activity Diagram..........................................................................................................................9
5 Sequence Diagram......................................................................................................................10
5.1 Sequence Diagram one........................................................................................................10
5.2 Sequence diagram two.........................................................................................................11
6 Domain Model Class Diagram...................................................................................................12
7 State Machine Diagram..............................................................................................................13
7.1 Login....................................................................................................................................13
7.2 Booking................................................................................................................................13
8 User Interface Story Board.........................................................................................................14
8.1 Customer Storyboard...........................................................................................................14
8.2 Guide Storyboard.................................................................................................................15
8.3 Admin Storyboard...............................................................................................................16
9 Conclusion..................................................................................................................................17
9.1 Summary..............................................................................................................................17
9.2 Recommendation.................................................................................................................17
References......................................................................................................................................18

Online Tour Booking 3
List of Figures
Figure 1: World tour company use case diagram............................................................................8
Figure 2: Activity Diagram..............................................................................................................9
Figure 3: Customer Sequence diagram..........................................................................................10
Figure 4: System administrator sequence diagram........................................................................11
Figure 5: Class diagram for World tour company online system..................................................12
Figure 6: Login State machine Diagram........................................................................................13
Figure 7: Booking State machine Diagram...................................................................................13
Figure 8: Customer Storyboard.....................................................................................................14
Figure 9: Guide Storyboard...........................................................................................................15
Figure 10: Admin Storyboard........................................................................................................16
List of Figures
Figure 1: World tour company use case diagram............................................................................8
Figure 2: Activity Diagram..............................................................................................................9
Figure 3: Customer Sequence diagram..........................................................................................10
Figure 4: System administrator sequence diagram........................................................................11
Figure 5: Class diagram for World tour company online system..................................................12
Figure 6: Login State machine Diagram........................................................................................13
Figure 7: Booking State machine Diagram...................................................................................13
Figure 8: Customer Storyboard.....................................................................................................14
Figure 9: Guide Storyboard...........................................................................................................15
Figure 10: Admin Storyboard........................................................................................................16
⊘ This is a preview!⊘
Do you want full access?
Subscribe today to unlock all pages.

Trusted by 1+ million students worldwide

Online Tour Booking 4
1 Introduction
In any touring company, there are a lot of activities like different customers requesting for
services at the same time. Every customer needs best services to be offered. This cone not be
done manually since the task will take a lot of time and may bring in confusion in an
organization. World Tours operates online to make the process of booking tours easy for
customers. Customers can book for their tours with ease because the services are available
always. This company provides customers with unique IDs and password to enhance data
security. June, Wiley & Cousins (2015). Every organization should try to employ such as the
system to solve the problem of services delay and cut down on cost.
1.1 Assumptions made.
a) There are hostels in the company where customers are accommodated during their tour
are the staffs are in charge of this hostels.
b) The charges for touring are included in the tour’s information.
c) The system allows multiple users at the same time because many users can book at the
same time.
d) One customer can book many tours at the same time.
1 Introduction
In any touring company, there are a lot of activities like different customers requesting for
services at the same time. Every customer needs best services to be offered. This cone not be
done manually since the task will take a lot of time and may bring in confusion in an
organization. World Tours operates online to make the process of booking tours easy for
customers. Customers can book for their tours with ease because the services are available
always. This company provides customers with unique IDs and password to enhance data
security. June, Wiley & Cousins (2015). Every organization should try to employ such as the
system to solve the problem of services delay and cut down on cost.
1.1 Assumptions made.
a) There are hostels in the company where customers are accommodated during their tour
are the staffs are in charge of this hostels.
b) The charges for touring are included in the tour’s information.
c) The system allows multiple users at the same time because many users can book at the
same time.
d) One customer can book many tours at the same time.
Paraphrase This Document
Need a fresh take? Get an instant paraphrase of this document with our AI Paraphraser

Online Tour Booking 5
2 Use Cases
These are activities that take place in World Tour Company to facilitate booking and payment of
the tour by the customers. These activities are carried out by different people (actors).
2.1 Login use case
Name Login use case
Actor Customer
Precondition The customer must be existing in the system
Summary A user provides the ID and the password for
signing into the system before any
transaction.
Triggers Staff
Postcondition Check details and tours
After the system has generated unique user IDs and passwords, the customer is required to
provide those IDs and passwords to access his tour information. This helps the system to be sure
that the person checking the information is the owner.
2.2 Payment Use Case
Name Make payment use case
Actor Customer
Precondition Must have selected a tour to book
Summary Involves the payment of the booking.
2 Use Cases
These are activities that take place in World Tour Company to facilitate booking and payment of
the tour by the customers. These activities are carried out by different people (actors).
2.1 Login use case
Name Login use case
Actor Customer
Precondition The customer must be existing in the system
Summary A user provides the ID and the password for
signing into the system before any
transaction.
Triggers Staff
Postcondition Check details and tours
After the system has generated unique user IDs and passwords, the customer is required to
provide those IDs and passwords to access his tour information. This helps the system to be sure
that the person checking the information is the owner.
2.2 Payment Use Case
Name Make payment use case
Actor Customer
Precondition Must have selected a tour to book
Summary Involves the payment of the booking.

Online Tour Booking 6
Triggers The system
Postconditions Request for reservation
Once the customer has checked the variety of tours and gets interested in one, he or she requests
for reservation and makes payment for the system to reserve that until he attends to it or decides
to cancel it.
2.3 Update tour scheme Use Case
Name Update tour scheme
Actor System Administrator
Precondition Need to make changes to the system
Summary The system administrator updates all the tours
both the schedule and the new
Triggers New staff, new tour.
Postcondition Notify the staff
The World tours system administrator is the main controller of the system. He can add, remove
or change tour scheme and can also update the system.
2.4 Reservation use case
Name Reservation use case
Actor Customer
Precondition Payment must have been made
Summary This use case involves a series of events
Triggers The system
Postconditions Request for reservation
Once the customer has checked the variety of tours and gets interested in one, he or she requests
for reservation and makes payment for the system to reserve that until he attends to it or decides
to cancel it.
2.3 Update tour scheme Use Case
Name Update tour scheme
Actor System Administrator
Precondition Need to make changes to the system
Summary The system administrator updates all the tours
both the schedule and the new
Triggers New staff, new tour.
Postcondition Notify the staff
The World tours system administrator is the main controller of the system. He can add, remove
or change tour scheme and can also update the system.
2.4 Reservation use case
Name Reservation use case
Actor Customer
Precondition Payment must have been made
Summary This use case involves a series of events
⊘ This is a preview!⊘
Do you want full access?
Subscribe today to unlock all pages.

Trusted by 1+ million students worldwide

Online Tour Booking 7
where the customer checks the tours available
and proceed to book.
Triggers Interest in a tour
Postconditions Tour reserved and status updated
Figure 4: Reservation use case
The tour is reserved for a customer once payment is made. The only person who can change the
reservation is the customer. That is when he or she decides to withdraw the booking. Otherwise,
the tour is reserved until its date.
3 Use Case Diagram
A use case diagram shows the parties that ensure the success of an organization (Actors) and the
activities performed by actors (use case). Without actors, the organization cannot function. Arora
& Bhatia (2018).
where the customer checks the tours available
and proceed to book.
Triggers Interest in a tour
Postconditions Tour reserved and status updated
Figure 4: Reservation use case
The tour is reserved for a customer once payment is made. The only person who can change the
reservation is the customer. That is when he or she decides to withdraw the booking. Otherwise,
the tour is reserved until its date.
3 Use Case Diagram
A use case diagram shows the parties that ensure the success of an organization (Actors) and the
activities performed by actors (use case). Without actors, the organization cannot function. Arora
& Bhatia (2018).
Paraphrase This Document
Need a fresh take? Get an instant paraphrase of this document with our AI Paraphraser

Online Tour Booking 8
Figure 1: World tour company use case diagram
Use case diagram for World tour company has three main users; customer, staff and system
administrator. The system administrator is the controller of the system whereby he updates tour
schemes. The staff has fewer duties because the users operate the system on their own. The
major duty of staff is to offer a tour guide to the customers. The main system used is the
customer since the main purpose of the system is to manage tours. The customer's books and
make payment online.
Figure 1: World tour company use case diagram
Use case diagram for World tour company has three main users; customer, staff and system
administrator. The system administrator is the controller of the system whereby he updates tour
schemes. The staff has fewer duties because the users operate the system on their own. The
major duty of staff is to offer a tour guide to the customers. The main system used is the
customer since the main purpose of the system is to manage tours. The customer's books and
make payment online.

Online Tour Booking 9
4 Activity Diagram
This UML diagram entails the dynamic operations in the system. Felderer, M., & Herrmann, A.
(2018).
Figure 2: Activity Diagram
So of the dynamic behaviors in the world tour, the online system is customer login, The system
must check if the customer is existing in the system or not. The customer can book a tour and
unbook it by canceling. The system administrator can add and delete employees.
4 Activity Diagram
This UML diagram entails the dynamic operations in the system. Felderer, M., & Herrmann, A.
(2018).
Figure 2: Activity Diagram
So of the dynamic behaviors in the world tour, the online system is customer login, The system
must check if the customer is existing in the system or not. The customer can book a tour and
unbook it by canceling. The system administrator can add and delete employees.
⊘ This is a preview!⊘
Do you want full access?
Subscribe today to unlock all pages.

Trusted by 1+ million students worldwide

Online Tour Booking 10
5 Sequence Diagram
This type of UML diagram shows the order in which activities take place within the system. Xia,
Lv & Liu (2017).
5.1 Sequence Diagram one
Figure 3: Customer Sequence diagram.
5 Sequence Diagram
This type of UML diagram shows the order in which activities take place within the system. Xia,
Lv & Liu (2017).
5.1 Sequence Diagram one
Figure 3: Customer Sequence diagram.
Paraphrase This Document
Need a fresh take? Get an instant paraphrase of this document with our AI Paraphraser

Online Tour Booking 11
The operations in this system are majorly between the customer, system interface and the
database. Whatever the user requests like the tour information, is provided by the system from
the database. All the changes made by the user are updated to the system in the database. The
activities run from the user to the database through the system and back to the user until the tour
is made.
5.2 Sequence diagram two
Figure 4: System administrator sequence diagram
An administrator is the controller of this system. The company's staff cannot add themselves to
the system. After being employed is the work of the admin to enter their details into the system
and remove them once they are no longer staff members. The admin also changes the touring
scheme in the organization in case there is a need to.
The operations in this system are majorly between the customer, system interface and the
database. Whatever the user requests like the tour information, is provided by the system from
the database. All the changes made by the user are updated to the system in the database. The
activities run from the user to the database through the system and back to the user until the tour
is made.
5.2 Sequence diagram two
Figure 4: System administrator sequence diagram
An administrator is the controller of this system. The company's staff cannot add themselves to
the system. After being employed is the work of the admin to enter their details into the system
and remove them once they are no longer staff members. The admin also changes the touring
scheme in the organization in case there is a need to.

Online Tour Booking 12
6 Domain Model Class Diagram
A class diagram classes in a system. Classes are objects that make up a system. It also shows the
attributes and operations of a given class. Abdulkareem, Ali, Admodisastro& Sultan (2017).
Figure 5: Class diagram for World tour company online system.
The classes in this system include; customer, staff, system administrator, tour, payment, and
reservation. There is a relationship between the customer and all other classes. The staff offers
tour guide to customers, system administrator adds or removes staff and customer performs all
the activities related to tour such as requesting for reservation and making payment online.
6 Domain Model Class Diagram
A class diagram classes in a system. Classes are objects that make up a system. It also shows the
attributes and operations of a given class. Abdulkareem, Ali, Admodisastro& Sultan (2017).
Figure 5: Class diagram for World tour company online system.
The classes in this system include; customer, staff, system administrator, tour, payment, and
reservation. There is a relationship between the customer and all other classes. The staff offers
tour guide to customers, system administrator adds or removes staff and customer performs all
the activities related to tour such as requesting for reservation and making payment online.
⊘ This is a preview!⊘
Do you want full access?
Subscribe today to unlock all pages.

Trusted by 1+ million students worldwide
1 out of 18
Related Documents

Your All-in-One AI-Powered Toolkit for Academic Success.
 +13062052269
info@desklib.com
Available 24*7 on WhatsApp / Email
Unlock your academic potential
Copyright © 2020–2025 A2Z Services. All Rights Reserved. Developed and managed by ZUCOL.