Running Head: SYSTEM ANALYSIS & DESIGN

SYSTEM ANALYSIS & DESIGN

SYSTEM ANALYSIS & DESIGN
1

Table of Contents
Answer 1: Stakeholders...................................................................................................................2

Investors of LAABS.....................................................................................................................2

Employees of LAABS.................................................................................................................2

Mr. Teo (Main) owner of LAABS...............................................................................................2

Customers of LAABS..................................................................................................................2

Answer 2a: Main functional requirements......................................................................................2

Answer 2b: Main functional requirements......................................................................................3

Answer 3a: User Goal Technique....................................................................................................4

Answer 3b: Event decomposition technique...................................................................................5

Answer 4: Domain model class diagram.......................................................................................13

Answer 5: CRUD matrix...............................................................................................................13

Answer 6: Fully developed utilization of case description............................................................19

Answer 7: Activity diagram to inspect balloon scenario...............................................................21

Answer 8: System sequence diagram............................................................................................23

Answer 9: State machine diagram.................................................................................................24

Answer 10: User acceptance test plan...........................................................................................24

References......................................................................................................................................26
SYSTEM ANALYSIS & DESIGN
2

Answer 1: Stakeholders

Investors of LAABS
With IS, every customers will easily find it very easy to book necessary sessions and
recommending others to work similarly and improve the level of profit for every investor.

Employees of LAABS
With IS, employees have the less chance in forgetting to full needs for doing the work.
They are timely sent the reminders for easily complete the all necessities.

Mr. Teo (Main) owner of LAABS

With bookings as well as its needs subsequently all managed through IS as owner Mr.
Teo is enough free for dedicate the time to expand solely organization thus bringing in effective
services for every customer as well as profits for the organization.

Customers of LAABS
Every customer will have the easy time as prefer to do future sessions of flight as every
information has been saved already through IS, along with gaining reminders timely to complete
the booking.

Answer 2a: Main functional requirements

 System will create, update, and case flight session data at automatic level
 System will create and update the customer data at automatic level
 System will create and update balloon as well as basket maintenance information at
automatic level
 System will create and update the pilot and information of employees within the regards
to certification to the relevant works (Chung, & do Prado Leite, 2009)
 System will easily trigger the reminders of text to be send out easily consumers
reminding them about their booking
 System will regularly produce as hoc status reports of basket as well as balloon
SYSTEM ANALYSIS & DESIGN
3

 System will easily store main notes done through the employees on technological check
of equipment after every flight
 System will store notes that completed through the employees on inspection of basket as
well as balloon before every flight
 System will notify the employee before the expiry of certification that are within the
requirement of passing particular needs to be available for relevant responsibilities
 System will regularly update about the contracts availability

Answer 2b: Main functional requirements

1. Usability needs

System will present the context-sensitive support if cursor is held over the filed for more
than one second.

This system will also present the key available feature on the menu (level of visibility)

2. Reliability needs

System will send out the message in text a day before the scheduled job regarding 99% of
time

3. Performance needs

System will update automatically schedule in 2 minutes of order which being updated

System will update every status about the balloons as well as basket in time period of 1
second

4. Security needs

System will easily grant level of access to account of users only if log in was effective
and successful (Chung, et al., 2012)

5. Constrains of design

System is supported on many different mobiles as well as desktops operating software

SYSTEM ANALYSIS & DESIGN
4

6. Implementation needs

System is enough capable to be translated into almost five languages. These are English,
French, German, Chinese, Malay that just a click of an option.

Answer 3a: User Goal Technique

Customers Case for utilization Description about the utilize
case
Consumers Make account of customer It uses the case which enables
customers for make the online
account as well as enable the
employees to create the
account regarding consumers
at the office
Employees Make account of employee It mainly utilizes the case
which helps employees to
easily register them within the
organization
Pilot Make account of pilot It mainly uses the case which
helps the pilot to easily
register them within the
organization
Basket Make account of basket It enables the information of
Basket’s to be regularly
inserted into system
Balloon Make account of balloon It enables the information of
Balloons to be mainly inserted
into the system
Service engineer Make account of service It uses case which enables the
engineer service engineers to easily
register them within the
organization
SYSTEM ANALYSIS & DESIGN
5

Employee Look for account of employee It uses the case which helps to
view the detail of employees
Customers, Employees, Look for account of customer It uses the case which helps to
Account view the details of customers
Customer, Employees, Flight, Look for details of flight It uses the case which enable
Pilot to book details of flight which
need to be reviewed
Pilot Look for account of pilot It uses the case which enable
to view the details of pilot
Balloon, Employee, Pilot, Look for status of balloon It uses the case which help to
Service Engineer view the details of basket
Basket, Employee, Pilot, Look for status of basket It uses the case which help to
Service Engineer view the details of balloon
Customer, Employee Update consumer status It enables the customers and
employees to update details of
customers
Service Engineer Look for account of service It uses the case which enable
engineer the customers and employees
to update the details of
customers

Answer 3b: Event decomposition technique

Serial Number Event Kind of Event Utilization of Brief explanation
Case
1 Customer selects External level Book a flight It uses the case
to complete the event which helps
booking of flight customers for
make the online
booking as well
as employees to
make the booking
within the office
2 7 days before Temporal Send texts for Send the
flight booked reminder important
SYSTEM ANALYSIS & DESIGN
6

reminder
regarding flight
texts to
consumers at the
specified period
of time before
time of flight
3 1 day before Temporal Send texts for Send text for
flight booked reminder reminder of flight
to customers at
the main specified
time before time
of flight
4 After two months Temporal Send text of It utilizes the case
of last medical warning which will send
the text of
warning to trained
employees which
they have to pass
the test of
medical in next
month of they
will mainly
considered as not
fit regarding duty
5 After completion External Update the It enables the
of employee first employee employees to
assistant training regarding the easily input to
status of first key system as
assistant training they are enough
qualified for
provide the first
SYSTEM ANALYSIS & DESIGN
7

assistance
6 After completed External Update the status It enables the
Commercial of staff pilot employees to
Balloon Pilots license input to system
license which as they
have the license
of pilots
7 After medical External Update the It enables the
test has been employees employees to
passed regarding status easily input to
of medical system as they are
fit medically
8 4 weeks before Temporal Update the status It utilize the case
data of booking of refund which will change
the refund status
from possibility
with no payment
for possible with
entire payment,
when the present
date mainly
reaches the 4
weeks before date
of booking
9 After employees External Safety check in It enables the
completes the relation to pre- employees to
inspection about flight input that they
the basket as have easily
well as balloon completed the
before flight check of safety
before flight
10 After employees External Technological It enables the
SYSTEM ANALYSIS & DESIGN
8

completes the check in relation employees to

technological to post flight easily provide the
check after the input as they have
flight easily completed
the technological
cross-check after
the flight
11 After services External Begin of day It enables the
engineer with mechanical services engineer
completes the check to provide the
mechanical input that already
checks at the has carried out
beginning of day mechanical level
checks about the
equipment as the
start of day
12 After completion External Mechanical It enables service
of service check after the engineer to input
engineers end of day that already has
completes the carried out checks
mechanical level at mechanical
check at the day level about the
end equipment at day
end
13 After services of State Update of It enables the
flight is booking in system to easily
completed relation to post update that
flight booking of flight
has been
completed easily.
This is no longer
within the section
SYSTEM ANALYSIS & DESIGN
9

of booking
14 After completion State Basket usage It enables the
of flight update in relation system to easily
to post flight update how long
basket has been
within the use as
well as add to the
whole usage of
basket easily
15 After the State Usage update It enables the
completion of within the system to easily
flight relation of post update how long
flight balloon balloon has been
within the
utilization as well
as add it to the
whole usage of
balloon
16 After utilization State Record balloon Call mainly
of 50 hours start regarding manufacturer as
servicing well as change
balloon state from
available to
within the
maintenance
17 After utilization State Record balloon Call manufacture
of 3 months beginning as well as change
regarding the sate regarding
servicing balloon that
remain available
regarding under
maintenance if 50
SYSTEM ANALYSIS & DESIGN
10

hours has not

been extended
18 After use of 50 State Record the Change basket
hours basket beginning state which
regarding remain available
servicing under the
maintenance
19 After the State Record the Change basket
utilization of 3 balloon stage which
months beginning remain available
regarding regarding under
servicing maintenance if 50
hours has not
been mainly
reached
20 After completion External Record the Change balloon
of servicing balloon that state from within
ready regarding the maintenance
utilization to available
21 After completion External Record basket Change the basket
of servicing that remain state from
available for available for
utilization undermaintenance
22 When requested External Product the ad It utilizes the case
for produce hoc report of which will lead to
report of an ad balloon prompt the
hoc status system for
produce the report
within the relation
to status of
balloon whenever
needed and
SYSTEM ANALYSIS & DESIGN
11

requested
23 When requested External Create the report It utilizes the case
for produce the within the which will lead to
an ad hoc status relation of ad hoc prompt the
report balloon system for create
the balloon status
report as per the
request
24 Dec 31 which Temporal event Checks in It utilize the case
present end of relation to which will
year produce the prompt the
basket system for
mechanical as produce the
well as report of basket annual
services level report that
is to be mainly
send at annual
level of
manufactures
25 December 31 Temporal event Produce the It use the case
which present balloon which will mainly
end of year mechanical level prompt system for
checks as well as produce the
report of services annual report of
balloon that is to
be mainly send to
annual tunnel
manufacturers
26 When needed External Produce the System mainly
through the report of produce the report
owner for customer usage in relation to
produce the usage of
SYSTEM ANALYSIS & DESIGN
12

report in relation customers

to customer regarding the
usage owner so that user
can easily see
what are mainly
famous time of
year as well as
kinds of flights
and main plan
regarding
expansion
27 Three months Sate event Remove It utilize the case
after the past employees which will lead to
medical remove the
employees from
active list that
remain available
as member is not
fit regarding duty
as well as will set
the reminder
within the form of
text to member
for pass the level
of medical as
soon as possible
SYSTEM ANALYSIS & DESIGN
13

Answer 4: Domain model class diagram

Answer 5: CRUD matrix

Utilization Customer Employee Pilot Flight Basket Balloon Service
of case engineer
Make C
account of
customers
Make C
account of
employee
Make C
account of
pilot
Book a C
flight
SYSTEM ANALYSIS & DESIGN
14

Make the C
account of
basket
Make the C
account of
balloon
Make the C
account of
service
engineer
Look R R R
regarding
account of
customers
Loo R
regarding
account of
employee
Look R
regarding
account of
pilot
Look R R R R
regarding
details of
flight
Look R R R R
regarding
status of
basket
Look R
regarding
status of
SYSTEM ANALYSIS & DESIGN
15

Balloon
Look R R R R
regarding
the
account of
services
engineer
Update UD
status of
customer
Update UD
status
about the
employee
first
assistance
Update the UD
status of
employee
pilot
license
Update the UD
status of
medical
employees
Update the UD
status of
refund
Safety U U U
check in
relation of
pre-flight
Technical U U U
SYSTEM ANALYSIS & DESIGN
16

check in
relation to
post flight
Beginning U U U
of the data
with
mechanica
l check
Finish of U U U
the day
with
mechanica
l check
Send text U U
of
reminder
Send text U U
of warning
Update U U
within the
relation of
post flight
booking
Update U
about the
usage of
post flight
basket
Update U
about the
usage of
post flight
balloon
SYSTEM ANALYSIS & DESIGN
17

Record U
basket
beginning
regarding
servicing
Record the U
balloon
beginning
regarding
servicing
Record the U
level of
balloon
ready
regarding
utilization
Produce ad R
hoc report
within the
relation of
ad hoc
balloon
Produce R
the report
within the
relation of
ad hoc
basket
Produce R
the report
within the
relation of
SYSTEM ANALYSIS & DESIGN
18

mechanica
l check
balloon
Produce R
the report
within the
relation of
mechanica
l check
basket
Produce R
the report
within the
relation of
customer
usage
Remove UD
employee

Answer 6: Fully developed utilization of case description

Utilization of case name: Book a flight
Key scenario User selects to complete the booking of flight
Event of triggering User go at online level or office of LAA
Singapore city to complete a booking
Brief explanation Online consumer or employee at office of LAA
completes the booking within the system
through writing the flight booking data, type of
flight selected and number of individual going
regarding flight
Key actors Marketing and accounting
Pre-conditions Subsystem of booking should remain available
Account of customer should be generated,
saved, and remain valid
SYSTEM ANALYSIS & DESIGN
19

Customer should meet the all health needs to

be on every flight
Baskets as well as balloon should be ready
regarding utilization (Kobayashi, et al., 2016)
Activities flow Main actor System
1. Customer or 1.1 System makes the
employees on the new booking
customer behalf 1.2 System mainly
presents the desire for prompts regarding
generate the booking type of flight
as well as enters the
date and time of flight
2. Customers or 2.1 System makes the
employee enters the sort of flight within
kind of flight they the booking
prefer to take 2.2 System mainly
prompts regarding
number of individuals
going within the flight
3. Customer or 3.1 System mainly
employee mainly enters the number of
enters the number of individuals into
individuals that booking
attending flight 3.2 System mainly
prompts regarding
every information of
customers entering to
flight
4. Customer or 4.1 System enters
employee enter the every detail about the
information of every individual into
individuals through booking
SYSTEM ANALYSIS & DESIGN
20

researching regarding 4.2 System regular

individual’s account validates that every
within the system customers is valid
regarding the flight
4.3 System mainly
prompts regarding the
credit/debit card
5. Customer records 5.1 System regularly
and enters the record enters the all details of
of credit/debit card individual into
booking
5.2 At effective level
system validate the all
consumers are right
and valid regarding
flight
5.3 System regularly
prompts regarding
credit/debit card
Exceptional conditions 1.1 Account of customers is not valid and
completed
4.1 Account of customers is not valid and
completed
5.1 Information of Credit/debit card is not valid
SYSTEM ANALYSIS & DESIGN
21

Answer 7: Activity diagram to inspect balloon scenario

SYSTEM ANALYSIS & DESIGN
22
SYSTEM ANALYSIS & DESIGN
23

Answer 8: System sequence diagram

SYSTEM ANALYSIS & DESIGN
24

Answer 9: State machine diagram

SYSTEM ANALYSIS & DESIGN
25

Answer 10: User acceptance test plan

SYSTEM ANALYSIS & DESIGN
26
SYSTEM ANALYSIS & DESIGN
27

References
Chung, L., & do Prado Leite, J. C. S. (2009). On non-functional requirements in software
engineering. In Conceptual modeling: Foundations and applications (pp. 363-379).
Springer, Berlin, Heidelberg.

Chung, L., Nixon, B. A., Yu, E., & Mylopoulos, J. (2012). Non-functional requirements in
software engineering (Vol. 5). Springer Science & Business Media.

Kobayashi, N., Morisaki, S., Atsumi, N., & Yamamoto, S. (2016). Quantitative Non Functional
Requirements evaluation using softgoal weight. J. Internet Serv. Inf. Secur., 6(1), 37-46.