ICT284 System Analysis and Design

This document provides information about the stakeholders, requirements, use cases, domain model class diagram, CRUD matrix, and user acceptance test plan for the ICT284 System Analysis and Design course. It also includes references for further reading.

ICT284 System Analysis and
Design
April 4
2019
Student ID:
Student Name:
Module Tutor:

Report
Contents
Report..........................................................................................................................................................2
Stakeholders................................................................................................................................................3
Requirements...............................................................................................................................................4
Functional Requirements.........................................................................................................................4
Non-Functional Requirements.................................................................................................................4
Use Cases....................................................................................................................................................5
By User Goal Technique.........................................................................................................................5
By Event Decomposition Technique.......................................................................................................5
Domain Model Class Diagram....................................................................................................................7
CRUD Matrix..............................................................................................................................................8
Use Case Description for the ‘Reserve a Book’ Use Case...........................................................................9
Activity Diagram for the ‘Inspect Balloon’ Use Case...............................................................................10
System Sequence Diagram for the ‘Inspect Balloon’ Use Case.................................................................11
State Machine Diagram for the ‘Balloon’ Object......................................................................................12
User Acceptance Test Plan........................................................................................................................12
References.................................................................................................................................................13

Stakeholders
There are three main stakeholders in the new Light-As-Air Ballooning System like below-
- Customer
- Pilot
- Staff
- Service Engineer
- Manufacturer
Customer
The customer is the main stakeholder in the new Light-As-Air Ballooning System. The customer
books the flight sessions online or directly at office. The new Light-As-Air Ballooning System
will be very beneficial for the customers because they can book online via system and the system
will also send the notifications regarding booking schedule etc. The condition of customers will
be stored into the system like injuries, pregnancy, weight etc.
Pilot
The pilot is the main stakeholder in the new Light-As-Air Ballooning System. The pilot flies the
flights along with the staff. The pilot is the main person who handles the flight.
Staff Member
The staff member is the main stakeholder in the new Light-As-Air Ballooning System. The staff
member works as the co pilot. The complete information about staff members, their certifications
etc. will be stored into the system.
Service Engineer
The service engineer is the main stakeholder in the new Light-As-Air Ballooning System. The
mechanical check of all equipments gets done by service engineer.
Manufacturer
The manufacturer is the main stakeholder in the new Light-As-Air Ballooning System. The
control system gets serviced by the manufacturer.

Requirements
There are so many requirements of the new Light-As-Air Ballooning System that are categorized
into functional and non functional.
Functional Requirements
These are the functional requirements of the new Light-As-Air Ballooning System-
1. Allow flight session booking. It will be of two types- Flight and Deluxe experience.
2. Check staff member certifications like pilot certificate, first aid certificate etc.
3. Send flight schedule reminders to the clients.
4. Maintain client details like weight, any injury etc.
5. Maintain flight session like schedule, pilot, co-pilot etc.
6. Maintain cancellation charges for the flight sessions of clients.
7. Send alerts to staff members for certifications in case of any issue like expiry date etc.
8. Maintain the usage hours of each balloon and basket.
9. Mechanical check of all equipments on regular basis.
10. Control system service at regular interval by manufacturer.
11. Generate status report of equipment like hour usage, in use or not, schedule of next
service etc.
Non-Functional Requirements
These are the non-functional requirements of the new Light-As-Air Ballooning System-
1. Maintain all equipments physically and check cleanliness etc.
2. Maintain system functionality from all aspects.
3. Validate equipment’s functionality.
4. Secure system data and functionality.
5. Validate database used in the system.

Use Cases
By User Goal Technique
These are the use cases that are categorized by the user goal technique-
Actors Use Case Use Case Description
Customer Book a flight The customer will book the
flight sessions.
System Ensure the certificate The system will ensure all
certificates of staff members.
Staff Member Collect customer conditions The staff member will collect
all customer conditions like
weight, injuries etc.
Staff Member Generate status report The system will give option to
staff members to generate
status report to staff members.
By Event Decomposition Technique
These are the use cases that are categorized by the user goal technique-
Event Event Type Trigger Use Case Use Case
Description
Cancel Flight State Cancel the
booking of
customer
Cancel Flight
Session
This use case
cancels the
customer’s
bookings. It may
be customer’s
reason or may be
from the
company’s side.
Balloon
Inspection
State Inspect balloons
before assigning
to flight
Inspect Balloon This use case
inspects the
balloons before
assigning to
flights. The
inspection will
be physical or
cleaning etc.
Send reminder
for flight
Temporal Send notification
to customers
Reminder of
Flight Schedule
This use case
sends

schedule notifications to
customers before
24 hours to
remind about
their bookings.
Check control
system of
equipments
State Check all
equipments
before assigning
to flights
Mechanical
check of
equipments
This use case
checks all
equipments by
manufacturer
before every
flight session.
Check all
equipments
physically and
check
cleanliness.
State Check all
equipments
before assigning
to flights
Technical check
of equipments
This use case
checks all
equipments by
service engineer
before every
flight session.
Calculate used
hours of all
equipments
State Calculate usage
hours of all
equipments and
calculate again
after 50 hours
after servicing.
Calculate usage
hours
This use case
calculate total
usage hours of all
equipments.

Domain Model Class Diagram
(Scott W. Ambler 2014)
(Microsoft 2015)

CRUD Matrix
Use
Cases
Cli
ent
Staf
f
Me
mbe
r
Equi
pmen
t
Bas
ket
Ball
oon
Equipment
Inspection
Equipme
ntService
Flight
Sessio
n
FlightSessionC
ustomerDetail
Book
a
flight
- - - - - - - CRUD CRUD
Cance
l
Flight
Sessi
on
- - - - - - - CRUD CRUD
Remi
nder
of
Flight
Sched
ule
R - - - - - - RU RU
Ensur
e the
certifi
cate
- R - - - - - - -
Colle
ct
custo
mer
condit
ions
R - - - - - - CRU CRU
Inspe
ct
Ballo
on
- - - CR
UD
CR
UD
CRUD - - -
Techn
ical
check
of
equip
ments
- - - CR
UD
CR
UD
CRUD - - -
Mech
anical
check
of
- - - CR
UD
CR
UD
- CRUD - -

equip
ments
Calcu
late
usage
hours
- - CRU CR
U
CR
U
- - - -
Gener
ate
status
report
R R R R R R R R R
(Ziff Davis, LLC 2015)
Use Case Description for the ‘Reserve a Book’ Use Case
Use Case Name: Book a flight
Scenario: Book a flight
Triggering Event: Insert client detail and booking session detail.
Brief Description: The customer will book the flight online via new system
or will book directly at the air-space. The information
about customer will be stored into the database and the
flight session for that customer will also be stored into the
database.
Actors: Client
Stakeholders: Client, Pilot, Co-Pilot
Pre Conditions: Flight is not available on required date and time
Post Conditions: The booking is confirmed. The system will send
reminders to customer before scheduling date.
Flow of Activities Actor System
1. The customer
searches the flight
on specific date.
6. The customer will
select a flight from
the given flights
and will book the
flight.
2. The system will show all
available flights.
4. The system will send
notifications regarding
flight sessions.
Exception Conditions

Activity Diagram for the ‘Inspect Balloon’ Use Case

(Sparx System Pty Ltd. 2015)
System Sequence Diagram for the ‘Inspect Balloon’ Use Case
(Sourcemaking.com n.d.)
(Microsoft Corporation 2015)

State Machine Diagram for the ‘Balloon’ Object
User Acceptance Test Plan
Use case Test Condition Expected Outcomes
Book a flight Add Customer Detail, Search
Equipment Availability
Booking Confirmed, Not
Available on Required Date
and Time
Cancel Flight Session Is Flight Available Return Valid Amount, Cancel
Booking Session
Reminder of Flight Schedule Regular Check Flight
Scheduling
Send Reminder to Customers
Before Flight Schedule
Ensure the certificate Check all Certificates of Staff
Members like medical
certificate, pilot certificate
etc.
Send notification, Allow
booking
Collect customer conditions Collect customer detail like
weight, injury etc.
Store Customer Detail, Ask
for Detail in case of
insufficient Data
Inspect Balloon Check Balloon’s Physical
Condition, cleanliness etc.
Allow for Booking, Send for
Repairing/Replacement
Technical check of
equipments
Check Equipment’s Physical
Condition, , cleanliness etc.
Allow for Booking, Send for
Repairing/Replacement
Mechanical check of
equipments
Check control system, service
of equipments etc.
Allow for Booking, Send for
Repairing/Replacement

Calculate usage hours Check equipments Calculate hour usage of
Equipments
Generate status report Check all equipments,
customers, flight details etc.
Generate different status
report
References
Microsoft Corporation (2015). Create a UML Sequence Diagram. Retrieved from:
http://office.microsoft.com/en-in/visio-help/create-a-uml-sequence-diagram-
HP001208871.aspx
Scott W. Ambler (2014). UML2 Class Diagrams: An Agile Introduction. Retrieved from:
http://www.agilemodeling.com/artifacts/classDiagram.htm
Sparx System Pty Ltd. (2015). UML2 Activity Diagram: An Agile Introduction, Retrieved from:
http://www.sparxsystems.com/resources/uml2_tutorial/uml2_activitydiagram.html
Microsoft (2015). UML Class Diagrams: Reference, Retrieved from:
http://msdn.microsoft.com/en-us/library/dd409437.aspx
Sourcemaking.com (n.d.). Sequence Diagrams. Retrieved from:
http://sourcemaking.com/uml/modeling-business-systems/external-view/sequence-
diagrams
Ziff Davis, LLC (2015). Building CRUD Diagrams. Retrieved from:
http://it.toolbox.com/blogs/enterprise-solutions/building-crud-diagrams-15327