Hot Air Balloon Booking System Design

This assignment delves into the design of an information system for booking hot air balloon rides. It outlines use cases, activity diagrams, sequence diagrams, state machine diagrams, and a user acceptance test plan to demonstrate the system's functionality. The focus is on capturing passenger information, managing bookings, scheduling flights, and maintaining records of maintenance activities.

Running head: ICT284 SYSTEMS ANALYSIS AND DESIGN
ICT284 Systems Analysis and Design
Name of the Student
Name of the University
Author’s Note

1
ICT284 SYSTEMS ANALYSIS AND DESIGN
Table of Contents
1. Stakeholders...........................................................................................................................2
2. Requirement Analysis............................................................................................................3
2.1. Functional requirements..................................................................................................3
2.2. Non-functional requirements..........................................................................................3
3. Use case..................................................................................................................................4
3.1. List of use cases from user goal technique......................................................................4
3.2. List of use cases from event decomposition technique...................................................5
4. Domain model class diagram.................................................................................................6
5. CRUD matrix.........................................................................................................................6
6. Fully-developed use case description.....................................................................................7
7. Activity diagram.....................................................................................................................9
8. System Sequence Diagram (SSD)........................................................................................10
9. State Machine Diagram (SMD)...........................................................................................10
10. User acceptance test plan...................................................................................................10
Bibliography.............................................................................................................................13

2
ICT284 SYSTEMS ANALYSIS AND DESIGN
1. Stakeholders
The stakeholders finds their interest in the development of the project for increasing the
efficiency of the ticket booking system for Light As Air Ballooning.
The list if stakeholders identified for the development of the information system are listed
below:
Stakeholder#1: Passenger – They finds the interest to book their ticket searching for
the availability of the seats and the fares. The development of the information system would
help them to book ticket from remote location and eliminate the needs to book ticket by
standing in queue.
Stakeholder#2:Mr TEO – Finds interest in development of the ticket booking system
such that the manual effort of the staffs can be reduced and the errors in the current business
process can be eliminated.
Stakeholder#3: Maintenance Staffs – The schedule of maintenance can be loaded into
the database and updated periodically that helps the maintenance staffs to work according to
the schedule and increase the safety of the light as air ballooning system.
Stakeholder#4: Pilot – The pilots can see their flight time and duration from the
information system and keep track on their attendance using the information system. The
certificate of the pilot can be shared for checking the qualification of the pilot and adding
safety in the flight.
Stakeholder#5: Manufacturer – The records of the balloons and the technical
equipment can be recorded into the database and used by the manufactured for finding the
spare parts and providing service to the customers.

3
ICT284 SYSTEMS ANALYSIS AND DESIGN
2. Requirement Analysis
2.1. Functional requirements
Registration /Login – The passenger needs to register for using the online booking
system and book a flight.
Search – the passenger and the staff can use the search function for finding the flight
information and the other information such as certification, maintenance etc. from the
information system.
Logout – The user needs to log out from the information system after completion of
their activity.
Status – the status of the booking of the flight can be get from the information system
after successfully registering into the information system. The available flight and the number
of seats occupied can be seen from the information system on the data selected by the
customer.
Book ticket – The passenger needs to book ticket for getting for experiencing the
flight session.
Cancel ticket – the ticket can be cancelled prior 4 weeks of booking and thus the
booking data is checked for cancelling the ticket without any extra charges.
Tracking – The flights can be tracked with the help of the information system and it
should be updated with the latest information.
2.2. Non-functional requirements
Security – The information of the balloons, staffs and the customers should be
secured from illegal access such that it cannot be misused for illegal purpose.

4
ICT284 SYSTEMS ANALYSIS AND DESIGN
Storage – Remote servers should be secured and cloud storage should be used for
storing the data and the information.
Availability – The data should be stored redundantly such that the availability of the
data is increased and the efficiency of the information system is improved.
Reliability – Redundant link should be used for the management of the information
and make it available to all the users. The servers should be configured such that there are no
errors in configuration and the information’s are available to the user all the time.
3. Use case
3.1. List of use cases from user goal technique
Participating actors Use case name Brief use case description
Passengers Register The passengers or users are
responsible for booking
ticket and enjoy the flight.
Airline Agency Review Order The Airline agency is
responsible for the
management of the business
information and improve the
efficiency of the current
business process.
Staffs Maintain flight The staffs are responsible
for the management of the
airline information and
proceed with the
maintenance of the balloons

5
ICT284 SYSTEMS ANALYSIS AND DESIGN
for increasing the security of
the flight trip.
3.2. List of use cases from event decomposition technique
Event Event Type Trigger Use case
name
Brief use case
description
Payment External An analysis is
made on all the
business needs of
the organization
for the
identification of
the use cases and
it finds the
external entities
that are associated
with the
development of
the information
system.
Make
payment
For the
development
of the
information
system the
external entity
is the payment
processing
system and it
should be
integrated
with the
information
system for
getting the
payment from
the passenger.

6
ICT284 SYSTEMS ANALYSIS AND DESIGN
4. Domain model class diagram
5. CRUD matrix
Entity
Function
Book Ticket
Make Booking C
Booking Confirmation RU
Accept Cancellation D
Issue Tickets RU
Where,
C = Create
R = Read
U = Update

7
ICT284 SYSTEMS ANALYSIS AND DESIGN
D = Delete
6. Fully-developed use case description
Use Case Name: Book Ticket
Scenario: Book a flight
Triggering Event: The user should be registered and seats
should be available in the balloon basket.
Brief Description: The main goals of the passenger is to book a
flight using the information system. For
booking the flight the user needs to register
into the information system or the already
registered user can login into the system for
searching the available flight. The airline
agency have the goal to record all the details
of the business for the management of the
information. The staffs have the goal to use
the information system for checking the
details and the schedule of the flight and
increase their work efficiency for providing
better service to the passengers.
Actors: The main actors found for the development
of the information system are the passenger
and LAA organization
Stakeholders: The stakeholders identified for the
development of the information system are

8
ICT284 SYSTEMS ANALYSIS AND DESIGN
the pilots, staffs and mechanics
Preconditions: The passenger needs to register with a
unique username and password for booking
ticket for their flight and seats must be
available.
Post conditions: After the booking the passenger needs to
complete the payment for the booking. The
passenger can also cancel the ticket prior 4
months from the booking journey date.
Flow of Activities Actor System
Passenger The passenger needs
to connect with the
information system
for searching for the
available seats and
book ticket.
Exception Conditions: Smart phone and laptop is needed for
booking the ticket and it should also
connected to the internet for connecting to
the light as air ballooning server

9
ICT284 SYSTEMS ANALYSIS AND DESIGN
7. Activity diagram

10
ICT284 SYSTEMS ANALYSIS AND DESIGN
8. System Sequence Diagram (SSD)
9. State Machine Diagram (SMD)
10. User acceptance test plan
ID Reference
Use case
Description Test
Condition
Expected
outcome
Comments

11
ICT284 SYSTEMS ANALYSIS AND DESIGN
01 100 Maintain
passenger
information
Add user,
update,
delete
account
New user
can be
added after
the
completion
of the
registration
with the
selected
fields.
02 200 Maintain
Booking
records
Create
schedule
and update
booking
status
The
database
should be
updated for
the
management
of the
booking and
enabling
transactions.
03 300 Maintain
maintenanc
Create
notification,
The
database