System Analysis and Design for Light-As-Air Ballooning System

This document provides a system analysis and design for Light-As-Air Ballooning System (LAABS) including stakeholder list, functional and non-functional requirements, use case techniques, class diagram, CRUD matrix, activity diagram, sequence diagram, state machine diagram, and user acceptance test plan.

Running head: SYSTEM ANALYSIS AND DESIGN
System Analysis and Design
Name of Student-
Name of University-
Author’s Note-

1SYSTEM ANALYSIS AND DESIGN
1. Stakeholders List
Stakeholders Name Brief Description
1. Clients or the customers The client interest in this project is to get the
flight ride and enjoy the ride. They are
interested in this system as they can entertain
themselves.
2. Owner of LAA, Teo Hong The owner wants to make profit out of this
project. They need to get profit from the
project.
3. Senior pilot As they are hired, they are responsible for
customer safety and getting salary from the
company.
4. Staff member or Co-pilot Same as senior pilot. They are responsible for
the safety of the customer.
5. Service engineer Checks the balloon condition.
6. Manufacturers Finds damages and repairs the damages. As
they are external stakeholders, they want to
make profit out of the work they do.
7. Database Administrator Manages data in the system.
8. Third party payment administrator Manages the payment and get paid for
maintaining them.
9. Government This system might get advantageous for the

2SYSTEM ANALYSIS AND DESIGN
government as they might attract customers.
Table 1: Stakeholder List
2. a) Functional Requirements
1. The Light-As-Air Ballooning System (LAABS) will makes online registration for the
customers.
2. LAABS system will store the details of all the staffs in the database.
3. LAABS system will store the details of available balloon baskets (small and large) in
the inventory.
4. LAABS system will store the detail of bookings along with the customers’ names.
5. LAABS system will handle the payment system done by third party.
6. LAABS system will store the mechanical storage of the balloons.
b) Non-Functional Requirements
1. The LAABS system will alarm to the customers before one month of booking and the
date before the booking.
2. LAABS system will also inform the customer for the cancellation of the flight.
3. LAABS system will keep a notice on the manufacturing materials of the company that
includes basket and the guy-ropes.
4. LAABS system sends the report to the owner of the company containing the
mechanical checks and all the service included in the system.

3SYSTEM ANALYSIS AND DESIGN
5. Safety of the customers are also maintained by the LAABS system.
6. Two types of experience are offered by the LAABS system.
7. The LAABS system will be secured and all the data will be stored privately in the
database.
8. The customers will able to do online registration with the LAABS system
9. The system will be available for 24x7 days.
3. a) User Goal Technique
Use Case name Brief description
1. Customer Login
The customer needs to login in the system so that they can view
the seat availability of the balloons.
2. Entering the personal
data of the customer
The customer enters the personal details such as the name, address
and phone number of the customer along with the height, weight
and any medical injuries that they will have to provide for booking
the flight.
3. Choosing the balloons
The customer needs to select their balloons as per their
requirement. There are small balloons and large balloons having
seat capacity of 10 and 20 respectively. The customer needs to
choose from them.
4. Make the payment
The customer needs to make the payment as per their selection of
seat in the company.
5. Staff experience The staffs needs to upload their details in the database of the

4SYSTEM ANALYSIS AND DESIGN
details
LAABS system. They are allotted with work as per their medical
experience and their working experience.
6. Inspection of the
balloon
The senior engineer of the system inspects the working process of
the balloon and inspects the cleanliness of the balloon. All the
processes that are involved in the take-off of the flight and while
landing.
7. Checking the damage
If the senior engineer inspects any problem in the system, they
refer the system to the manufacturer as they need to be repair the
damages that are caused to them.
8. Repairing the need
The damages that are found by the manufacturer are to be repaired
for running the business smoothly.
Table 2: Use Case Technique

5SYSTEM ANALYSIS AND DESIGN
Figure 1: Use case Diagram
(Source: Created by Author)
b) Event Decomposition Technique

6SYSTEM ANALYSIS AND DESIGN
Event Type of event Use case Brief Description Actors
Customer login
the system
External Login
The customer logins
the system so that they
can get a become a
member of the system
Customer
Staffs enters their
personal details
Internal
Enter personal
details
The staffs needs to
enter the details of the
own in the system of
LAABS so that their
work can be assigned.
Staffs
Repairs Damage External Damage repairing
The senior engineer
needs to inspect the
balloons and if there is
damage, they have to
repair them.
Manufacturer
Table 3: Event Decomposition Technique
4. Class Diagram

7SYSTEM ANALYSIS AND DESIGN
5. CRUD Matrix
Entity
Process
Customer Staffs Manufacturer Owner Third party
Customer
details
C, U, D R NA R, D NA
Staff Details R C, U, D NA R, D NA
Flight Details R R, U C, U, R, D C, R, U, D NA
Maintain
inventory
NA R, U U C, R, U, D NA
Takes C NA NA NA C, R, U, D

8SYSTEM ANALYSIS AND DESIGN
Payment
Table 4: CRUD Matrix
6. Use Case Description for Book a Flight
Use Case Name Choose a flight
Scenario The customer after login choose the balloon
and then books them accordingly.
Triggering Event The customer needs to login in the system to
book.
Brief Description After the customer login in the system, the
customer searcher for a flight according to
their requirement. They books the flight as
per their choice and makes payment
accordingly.
Actors Customer
Stakeholders Owner, client, and database engineer
Pre-conditions The client needs to login the system
Post-conditions The client needs to make the payment
Actor System
The customer login
the system
The system allows
the customer to login
if the password and
username is correct.

9SYSTEM ANALYSIS AND DESIGN
Exception Condition The customer needs to provide correct user id
and password for booking seat in the flight.
Table 5: Use case Description
7. Activity Diagram for Inspect Balloon
8. Sequence Diagram for Inspect Balloon

10SYSTEM ANALYSIS AND DESIGN
9. State machine diagram
10. User Acceptance Test Plan of a customer
Use Case Name Test Condition Expected Outcomes
Customer login The customer logins the
system by providing the
username and the password.
If the user name and the
password is incorrect, the
login will fail.
If the user name and the
password is correct the

11SYSTEM ANALYSIS AND DESIGN
customer can login the
system.
Customer Checks the seat of
the balloons
The customer checks for the
empty seats available for the
flight and books the seat.
If the customer does not get
any seat, then their booking
gets cancelled.
Table 6: User Acceptance Test Plan

12SYSTEM ANALYSIS AND DESIGN
Bibliography
Dennis, A., & Wixom, B. H. (2018). Systems analysis and design. Wiley.
Gonen, T. (2015). Electrical power transmission system engineering: analysis and design. CRC
press.
Pedrycz, W. (2016). Granular computing: analysis and design of intelligent systems. CRC press.
Rogers, T. R., & Cattell, R. G. G. (1988). Entity-Relationship Database User Interface. IEEE
Data Eng. Bull., 11(2), 44-53.
Satzinger, J. W., Jackson, R. B., & Burd, S. D. (2011). Systems analysis and design in a
changing world. Cengage learning.