ACE3 Scenario Descriptions
-
Upload
techgeekvn -
Category
Documents
-
view
217 -
download
0
Transcript of ACE3 Scenario Descriptions
-
7/26/2019 ACE3 Scenario Descriptions
1/23
ACE3 ConferenceScenario descriptions for the vCabin
EnvironmentPrepared by BCA Mobile and Web Solutions
31 July !1"
-
7/26/2019 ACE3 Scenario Descriptions
2/23
ContentsSystem re#uirements$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$"
All applications$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ "
Mobile cabin panel$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ "
Scenario descriptions$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ "
CAB%& PA&E' ()* WEA*AB'ES$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ "
+ie, ne, seat fault noti-cation$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$"
+ie, ba..a.e/loadin. noti-cation$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ 0
+ie, safety e#uipment noti-cation$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$
+ie, service call noti-cation$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$
2ismiss service call noti-cation$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$
Chan.e li.htin. settin.s$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$
Chan.e accent li.htin. settin.s$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$4
Chan.e cabin pro5ection settin.s$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ 4
M)B%'E CAB%& PA&E'$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$6
Chec7 ba..a.e/loadin. pro.ress$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$6
Con-rm seat occupied$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$1!
+ie, passen.er preferences$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ 1!
+ie, safety e#uipment status$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$11Chan.e li.htin. settin.s$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ 1
Chan.e accent li.htin. settin.s$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ 13
Chan.e cabin pro5ection settin.s$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ 13
Con-rm ,ater #uantity$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ 1"
+ie, cabin faults$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$1"
+ie, active service calls$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$10
2ismiss active service calls$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$1
CAB%& C)MM8&%CA9)*$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ 1Spea7 ,ith cabin cre,member$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$1
A%*C*A(9 :EA'9: MA&A;EME&9$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$1
+ie, seat fault data$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ 1
+ie, seat pro.nostic data$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ 14
+ie, co
-
7/26/2019 ACE3 Scenario Descriptions
3/23
A:M M)B%'E APP'%CA9%)&$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$16
+ie, seat fault data$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ 16
A&A'=9%C 2AS:B)A*2$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ 16
Evaluate lumbar e>tension usa.e$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$16
+ie, mean time bet,een unit replacement$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$!
WA9E* MA&A;EME&9 S=S9EM$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$1
Calculate ,ater #uantity$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ 1
-
7/26/2019 ACE3 Scenario Descriptions
4/23
System re#uirementsAll applications2emonstration reset
A user may reset the scenario so that all chan.es made durin. the previous section
are undone$
Mobile cabin panelModify passen.er manifest
(or the purpose of the demonstration? the environment operator may modify the
passen.er manifest to re@ect the current audience$ 9his demonstrates the
applications ability to inte.rate ,ith and receive updates from an airlines bac7
oce system$
&avi.ate cabin tools
9he @i.ht attendant must complete a number of operations prior to? durin.? and
after a @i.ht se.ment$ 9o facilitate this? applications ,ill consist of related features
bet,een ,hich a @i.ht attendant can easily navi.ate$
(eatures ,ill have a common loo7 and feel and ,ill share common components?
,hen feasible$
Scenario descriptionsCAB%& PA&E' ()* WEA*AB'ES)peratin. system Android
2evice type Android Wear? ;oo.le ;lass? and &e>us Dnoti-cations only
+ie, ne, seat fault noti-cationPrimary actor
(li.ht attendant
2escription
% ,ant to be noti-ed of a ne, seat fault$
9he vCabin scenario calls for a @i.ht attendant to vie, a seat fault noti-cation$
Pre/conditions
9he user has connected the application to the airplane net,or7$
Post/conditions
9he user can act to miti.ate or other,ise address a ne, fault$
-
7/26/2019 ACE3 Scenario Descriptions
5/23
2etails
9he pop/up noti-cation displays the follo,in. information
F (ault description
F (ault priority
F 'ocation De$.$? seat number
9he application ,ill present the pop/up noti-cation over any other open application
on the users mobile device? so that the user must address it before returnin. to
their previous screen$ 9he @i.ht attendant addresses the pop/up noti-cation by
dismissin. it or by optin. to vie, in application$ )ptin. to vie, the application ta7es
the user to the G+ie, cabin faultsH use case$
+ie, ba..a.e/loadin. noti-cationPrimary actor
(li.ht attendant
2escription
% ,ant to 7no, ,hen a hi.h priority item is loaded onto the airplane$
9he vCabin scenario calls for the @i.ht attendant to receive a noti-cation that a
passen.ers pet car.o is on the airplane$
Pre/conditions
9he user has connected the application to the airplane net,or7$
9he passen.er has chec7ed his or her lu..a.e and the airline has attached a
trac7in. technolo.y to the lu..a.e De$.$? *(%2 or &(C/enabled ba..a.e ta.$
Post/conditions9he user understands ,hether a particular hi.h priority item is on board$
2etails
9he application ,ill only send noti-cations for items that the operator has mar7ed
as hi.h priority in some ,ay$ 9he pop/up noti-cation displays the follo,in.
information
F Passen.er name
F Seat number
F %tem description
9he application ,ill present the pop/up noti-cation over any other open application
on the users mobile device? so that the user must address it before returnin. to
their previous screen$ 9he @i.ht attendant addresses the pop/up noti-cation by
dismissin. it or by optin. to vie, in application$ )ptin. to vie, the application ta7es
the user to the GChec7 ba..a.e/loadin. pro.ressH use case de-ned in the ne>t
section$
-
7/26/2019 ACE3 Scenario Descriptions
6/23
+ie, safety e#uipment noti-cationPrimary actor
(li.ht attendant
2escription
% ,ant to be noti-ed ,hen a safety e#uipment item is missin. or removed$
9he vCabin scenario calls for the @i.ht attendant to receive a noti-cation that a
passen.er life vest is missin. on a ,earable device$
Pre/conditions
9he user has connected the application to the airplane net,or7$
Post/conditions
9he user can act to address the missin. or removed safety e#uipment$
2etails
At a minimum? the application ,ill trac7 the follo,in. e#uipment
Passen.er life vest
I&umber of economy seats in the demonstration environment ,ill be e#uipped ,ith
life vests$ 9he application ,ill sho, that every seat in the ')PA has a life vest$ 9he
application only re#uires the capability to sho, ,hich life vests are missin. for
those seats actually e#uipped ,ith life vests$
9he application ,ill present the pop/up noti-cation over any other open application
on the users mobile device? so that the user must address it before returnin. to
their previous screen$ 9he @i.ht attendant addresses the pop/up noti-cation by
dismissin. it or by optin. to vie, in application$ )ptin. to vie, the application ta7es
the user to the G+ie, safety e#uipment statusH use case$
+ie, service call noti-cationPrimary actor
(li.ht attendant
2escription
% ,ant to 7no, ,hen a passen.er has activated his or her attendant call li.ht$
9he vCabin scenario calls for a passen.er to activated his attendant call li.ht in
order to in#uire about the status of his pet that the airline is loadin. into the car.o
hold$ 9he @i.ht attendant receives the noti-cation and dismisses it after
investi.atin. the customer issue$
Pre/conditions
9he user has connected the application to the airplane net,or7$
Post/conditions
9he user can act to address a passen.er issue$
-
7/26/2019 ACE3 Scenario Descriptions
7/23
2etails
9he application ,ill display the seat number associated ,ith the active service call$
9he application ,ill allo, the user to s,itch bet,een or vie, at once multiple
service call noti-cations$
2ismiss service call noti-cationPrimary actor
(li.ht attendant
2escription
% ,ant to turn o< any active service calls$
9he vCabin scenario calls for a passen.er to activated his attendant call li.ht in
order to in#uire about the status of his pet that the airline is loadin. into the car.o
hold$ 9he @i.ht attendant receives the noti-cation and dismisses it after
investi.atin. the customer issue$
Pre/conditions9he user has received a service call noti-cation$
Post/conditions
9he passen.er service call is no lon.er active$
2etails
2ismissin. the service call on the application? the airplane system ,ill dismiss the
actual call li.ht$
Chan.e li.htin. settin.s
Primary actor(li.ht attendant
2escription
% ,ant to chan.e the li.htin. settin.s for the airplane$
9he vCabin scenario calls for the @i.ht attendant to chan.e the li.htin. in the cabin
from a ,earable device$ 9he @i.ht attendant selects from a number of scenes and
the cabin li.htin. Din all parts of the cabin updates to re@ect the chan.e$
Pre/conditions
9he user has connected the application to the airplane net,or7$
Post/conditions9he li.htin. settin.s re@ect the users chan.es$
2etails
9he li.htin. system has numerous built/in settin.s for the passen.er seatin. area?
for,ard entry area? and aft entry area$ 9he @i.ht attendant can manipulate the
settin.s for all three Kones$ 9he passen.er seatin. area has the follo,in. scenes
Scene 1
-
7/26/2019 ACE3 Scenario Descriptions
8/23
Scene
Scene 3
9he application ,ill allo, the user to chan.e li.htin. settin.s usin. voice
commands$
Chan.e accent li.htin. settin.sPrimary actor
(li.ht attendant
2escription
% ,ant to chan.e accent li.htin. settin.s for the airplane$
9he vCabin scenario calls for the @i.ht attendant to chan.e accent li.htin. in the
economy class section of the cabin from a ,earable device$ 9he @i.ht attendant
selects from a number of scenes and the accent li.htin. updates in the economy
Kone to re@ect the chan.e$
Pre/conditions
9he user has connected the application to the airplane net,or7$
Post/conditions
9he li.htin. settin.s re@ect the users chan.es$
2etails
9he accent li.htin. system has numerous built/in settin.s for the passen.er seatin.
area? for,ard entry area? and aft entry area$ 9he @i.ht attendant can manipulate
the settin.s for all three Kones$ 9he passen.er seatin. area has the follo,in.
scenes
Scene 1
Scene
Scene 3
9he application ,ill allo, the user to chan.e accent li.htin. settin.s usin. voice
commands$
Chan.e cabin pro5ection settin.sPrimary actor
(li.ht attendant
2escription
% ,ant to chan.e cabin pro5ection settin.s$
9he vCabin scenario calls for the @i.ht attendant to chan.e the scene that the cabin
pro5ector is displayin. in the demonstration$
-
7/26/2019 ACE3 Scenario Descriptions
9/23
Pre/conditions
9he user has connected the application to the airplane net,or7$
Post/conditions
9he user has chan.ed the cabin pro5ection scene$
2etails9he cabin pro5ector has the follo,in. scenes
Scene 1
Scene
Scene 3
M)B%'E CAB%& PA&E')peratin. system Android
2evice type H mobile tablet
Chec7 ba..a.e/loadin. pro.ressPrimary actor
(li.ht attendant
2escription
% ,ant to 7no, ,hich ba.s are on the airplane$
9he vCabin scenario calls for a user to vie, ba..a.e/loadin. pro.ress for the
notional @i.ht$
Pre/conditions9he user has connected the application to the airplane net,or7$
9he passen.er has chec7ed his or her lu..a.e and the airline has attached a
trac7in. technolo.y to the lu..a.e De$.$? *(%2 or &(C/enabled ba..a.e ta.$
Post/conditions
9he user understands ,hether a particular item is on board$
2etails
9he application ,ill summariKe the ba..a.e loadin. status so that the user has a
comprehensive vie, of the state of the ba..a.e loadin. process$
9he application ,ill display a full vie, of the ba..a.e/loadin. pro.ress by displayin.the number of chec7ed ba.s by passen.er and ,hich of those are on board$ 9he
application ,ill identify the number of ba.s loaded in relation to the number of ba.s
chec7ed De$.$? "0 of 4! ba.s loaded$ 9he application ,ill also provide a separate
count for hi.h priority items$
When displayin. the full vie, ba..a.e/loadin. process? the application ,ill hi.hli.ht
in some ,ay those passen.ers ,ith hi.h/value chec7ed items$
-
7/26/2019 ACE3 Scenario Descriptions
10/23
9he application ,ill display the follo,in. information on each passen.er for a .iven
@i.ht
Passen.er name
2oes the passen.er have a chec7ed ba.L
2oes the passen.er have a hi.h priority itemL
Seat number
%tem description
Ba..a.e trac7in. number
Con-rm seat occupiedPrimary actor
(li.ht attendant
2escription
% ,ant to 7no, ,hether a passen.er has occupied a .iven seat$
9he vCabin scenario calls for the @i.ht attendant to vie, a cabin ')PA to determine
,hich seats are occupied$
Pre/conditions
9he user has connected the application to the airplane net,or7$
Post/conditions
9he user understands the pro.ress of passen.er boardin.$
2etails9he user can refresh seat status to retrieve the latest seat occupancy status by any
one of the follo,in. means openin. the application for the -rst time? reopenin. a
previously opened application runnin. in the bac7.round? usin. an application
feature Dsuch as button or Gpull do,n to refreshH feature to refresh status
9he application ,ill sho, the user ,hich seats are assi.ned a passen.er accordin.
to the passen.er manifest$
9he application ,ill sho, ,hether a passen.er has occupied an assi.ned seat$
9he application ,ill sho, ,hether a passen.er has occupied an unassi.ned seat$
9he application ,ill summariKe the seat occupancy information so that the user hasa comprehensive vie, of the state of the boardin. process$ (or e>ample? the
application may tell the user that a .iven @i.ht has 1!! con-rmed passen.ers and
that 4! of those passen.ers are sittin. in their assi.ned seat$
-
7/26/2019 ACE3 Scenario Descriptions
11/23
+ie, passen.er preferencesPrimary actor
(li.ht attendant
2escription
% ,ant to vie, food and drin7 service preferences for a .iven passen.er$
9he vCabin scenario calls for a passen.er to re#uest a cup of co
-
7/26/2019 ACE3 Scenario Descriptions
12/23
Pre/conditions
9he user has connected the application to the airplane net,or7$
Post/conditions
9he @i.ht attendant understands the status of the airplanes safety e#uipment$
2etails
At a minimum? the application ,ill trac7 the follo,in. e#uipment
F Passen.er life vests
I&umber of economy seats in the demonstration environment ,ill be e#uipped ,ith
life vests$ 9he application ,ill sho, that every seat in the ')PA has a life vest$ 9he
application only re#uires the capability to sho, ,hich life vests are missin. for
those seats actually e#uipped ,ith life vests$
9he application ,ill present the pop/up noti-cation over any other open application
on the users mobile device? so that the user must address it before returnin. to
their previous screen$ 9he @i.ht attendant addresses the pop/up noti-cation by
dismissin. it or by optin. to vie, in application$ )ptin. to vie, the application ta7es
the user to the G+ie, safety e#uipment statusH use case$
Chan.e li.htin. settin.sPrimary actor
(li.ht attendant
2escription
% ,ant to chan.e the li.htin. settin.s for the airplane$
9he vCabin scenario calls for the @i.ht attendant to chan.e the li.htin. in the cabin
from a ,earable device$ 9he @i.ht attendant selects from a number of scenes and
the cabin li.htin. Din all parts of the cabin updates to re@ect the chan.e$
Pre/conditions
9he user has connected the application to the airplane net,or7$
Post/conditions
9he li.htin. settin.s re@ect the users chan.es$
2etails9he li.htin. system has numerous built/in settin.s for the passen.er seatin. area?
for,ard entry area? and aft entry area$ 9he @i.ht attendant can manipulate the
settin.s for all three Kones$ 9he passen.er seatin. area has the follo,in. scenes
Scene 1
Scene
-
7/26/2019 ACE3 Scenario Descriptions
13/23
Scene 3
Chan.e accent li.htin. settin.sPrimary actor
(li.ht attendant
2escription
% ,ant to chan.e accent li.htin. settin.s for the airplane$
9he vCabin scenario calls for the @i.ht attendant to chan.e accent li.htin. in the
economy class section of the cabin from a ,earable device$ 9he @i.ht attendant
selects from a number of scenes and the accent li.htin. updates in the economy
Kone to re@ect the chan.e$
Pre/conditions
9he user has connected the application to the airplane net,or7$
Post/conditions
9he li.htin. settin.s re@ect the users chan.es$
2etails
9he accent li.htin. system has numerous built/in settin.s for the passen.er seatin.
area? for,ard entry area? and aft entry area$ 9he @i.ht attendant can manipulate
the settin.s for all three Kones$ 9he passen.er seatin. area has the follo,in.
scenes
Scene 1
Scene
Scene 3
Chan.e cabin pro5ection settin.sPrimary actor
(li.ht attendant
2escription
% ,ant to chan.e a cabin pro5ection scene$
9he vCabin scenario calls for the @i.ht attendant to chan.e the scene that the cabin
pro5ector is displayin. in the demonstration$
Pre/conditions9he user has connected the application to the airplane net,or7$
Post/conditions
9he cabin pro5ection system has updated to re@ect the users chan.es$
2etails
9he cabin pro5ector has the follo,in. scenes
-
7/26/2019 ACE3 Scenario Descriptions
14/23
Scene 1
Scene
Scene 3
Con-rm ,ater #uantityPrimary actor
(li.ht attendant
2escription
% ,ant to con-rm that the amount of ,ater loaded on my airplane matches the
amount that operations plannin. recommended be loaded on my airplane$
9he vCabin scenario calls for the @i.ht attendant to con-rm that there is enou.h
,ater on board the airplane$ 9he application ,ill display the parameters that the o
-
7/26/2019 ACE3 Scenario Descriptions
15/23
+ie, cabin faultsPrimary actor
(li.ht attendant
2escription
% ,ant to see all open cabin faults applicable to my airplane from the follo,in.systems
F ;alleys
F Seats
F 'avatories
9he vCabin scenario calls for the @i.ht attendant to vie, the seat fault that he or
she received via noti-cation ,ithin the list of active faults for the cabin$
Pre/conditions
9he user has connected the application to the airplane net,or7$
Post/conditions
9he user has sucient information to address a fault$
2etails
9he application displays the follo,in. information on each fault
F 'ocation
F Passen.er name? if applicable
F (ault code
F (ault description
F 9ime
+ie, active service callsPrimary actor
(li.ht attendant
2escription
% ,ant to vie, all active service calls$
9he vCabin scenario calls for a passen.er to activated his attendant call li.ht in
order to in#uire about the status of his pet that the airline is loadin. into the car.ohold$ 9he @i.ht attendant receives the noti-cation and dismisses it after
investi.atin. the customer issue$
Pre/conditions
9he user has connected the application to the airplane net,or7$
Post/conditions
9he user can act to address a passen.er issue$
-
7/26/2019 ACE3 Scenario Descriptions
16/23
2etails
9he application ,ill display the seat number associated ,ith the active service call$
9he application ,ill allo, the user to s,itch bet,een multiple service call
noti-cations$
2ismiss active service callsPrimary actor
(li.ht attendant
2escription
% ,ant to dismiss active service calls$
9he vCabin scenario calls for a passen.er to activated his attendant call li.ht in
order to in#uire about the status of his pet that the airline is loadin. into the car.o
hold$ 9he @i.ht attendant receives the noti-cation and dismisses it after
investi.atin. the customer issue$
Pre/conditions9he user has received a service call noti-cation$
Post/conditions
9he passen.er service call is no lon.er active$
2etails
9B2$
CAB%& C)MM8&%CA9)*)peratin. system Android
2evice type Android Wear and ;oo.le ;lass
Spea7 ,ith cabin cre,memberPrimary actor
(li.ht attendant
2escription
% ,ant to spea7 to my cabin cre,mates via mobile device$
9he vCabin scenario calls for a passen.er ,ho arrives late to the @i.ht$ :e has a
carry/on ba. but cannot -nd a place to put it$ :e enlists the help of the @i.ht
attendant ,ho calls another @i.ht attendant to chec7 about availability else,here inthe cabin$
Pre/conditions
9he user has connected the application to the airplane net,or7$
Post/conditions
(li.ht attendant has completed a conversation ,ith another @i.ht attendant$
-
7/26/2019 ACE3 Scenario Descriptions
17/23
2etails
9he @i.ht attendant may access this application via mobile device$ 9his ,ill involve
cooperation bet,een up to three di
-
7/26/2019 ACE3 Scenario Descriptions
18/23
2etails
9his application displays the process for receivin. and mana.in. a fault$ %t should
sho, the path from a planner receivin. a ne, fault or pro.nostic to closin. the
issue$
+ie, seat pro.nostic dataPrimary actorMaintenance planner
2escription
% ,ant to vie, pro.nostic and parametric data reported by an airplaneOs business
and -rst class seats$
9he vCabin scenario calls for a user to vie, pro.nostic data related to a seat unit
usin. the A:M bro,ser/based application to determine ,hether it is li7ely to fail$
Pre/conditions
9he system has received the re#uired data from a .iven airplane$Post/conditions
9he user has information needed to schedule maintenance if necessary$
2etails
&one$
+ie, co
-
7/26/2019 ACE3 Scenario Descriptions
19/23
F By departure and arrival time
F By ma5or model
F By minor model
F By @i.ht len.th
F By destination type
F By departuredestination country
F By departuredestination airport
F By component manufacturer
F By component installation date
F By airplane delivery date
A:M M)B%'E APP'%CA9%)&)peratin. system Android
2evice type H mobile tablet
+ie, seat fault dataPrimary actor
Mechanic
2escription
% ,ant to vie, seat fault data reported by an airplaneOs business or -rst class seats$
9his vCabin scenario calls for a user to vie, the seats fault data on the A:M &otify
application$
Pre/conditions
9he system has received the re#uired data from a .iven airplane$
Post/conditions
9he user has information needed to schedule maintenance if necessary$
2etails
&one$
A&A'=9%C 2AS:B)A*2)peratin. system Bro,ser/based ,eb application
2evice type Any
-
7/26/2019 ACE3 Scenario Descriptions
20/23
Evaluate lumbar e>tension usa.ePrimary actor
)perations analyst
2escription
% ,ant to see the fre#uency ,ith ,hich passen.ers use a particular feature on a -rstor business/class seat$
Pre/conditions
9he system has received the re#uired data from a .iven airplane$
9he system has received enou.h data from the operators @eet to evaluate feature
usa.e$
Post/conditions
9he user has enou.h information to identify data usa.e trends$
2etails
9he vCabin scenario calls for a user to determine ,hether or ho, fre#uentlypassen.ers use the lumbar e>tension feature$ 9he user ,ill evaluate usa.e for a
sin.le @i.ht and over a ran.e of @i.hts$
9he user may vie, -lter data the follo,in. ,ays
F By aircraft type Dnarro, vs$ ,ide body
F By departure and arrival time
F By ma5or model
F By minor model
F By @i.ht len.th
F By destination type
F By departuredestination country
F By departuredestination airport
F By component manufacturer
F By component installation date
F By airplane delivery date
F By cabin Kone
F By seat position Daislecenter,indo,
F By passen.er type
-
7/26/2019 ACE3 Scenario Descriptions
21/23
+ie, mean time bet,een unit replacementPrimary actor
)perations analyst
2escription
% ,ant to see avera.e life cycle for a .iven cabin component$
9he vCabin scenario calls for a user to loo7 at the avera.e life cycle for a
co
-
7/26/2019 ACE3 Scenario Descriptions
22/23
Calculate ,ater #uantityPrimary actor
)perations planner
2escription
% ,ant to calculate a recommended ,ater #uantity for a .iven @i.ht based on ,aterusa.e data collected from previous @i.hts$ 9he user ,ill chan.e the destination to
sho, ho, the calculation chan.es for a lon.ershorter @i.ht$
9he vCabin scenario calls for a user to submit certain @i.ht parameters to a system
that returns a recommended volume of ,ater to be loaded onto the airplane$
Pre/conditions
9he system has received ,ater usa.e data from previous @i.hts$ 9he operations
planner possesses the re#uired details for the system to calculate a recommended
,ater #uantity$
Post/conditions9he system presents ,ater #uantity values that state recommended ,ater #uantity
after -ll and amount of ,ater to load onto the airplane to meet that #uantity$
2etails
9he user ,ill locate a .iven @i.ht by selectin. from a list of @i.ht numbers provided
by the application$ When the user selects a @i.ht? the system calculates a
recommended ,ater #uantity$ 9his calculation considers the follo,in. parameters
from previous @i.hts to provide a recommendation based on the current @i.hts
parameters
&umber of passen.ers
Airplane con-.uration information
2eparture and arrival cities
2eparture and arrival time
9he user ,ill edit the follo,in. parameters to receive an accurate calculation
&umber of passen.ers
2eparture and arrival cities
2eparture and arrival time
9he system ,ill return a recommended ,ater #uantity and ,ill display the follo,in.
values used to calculate the ,ater #uantity
&umber of passen.ers
(li.ht distance
2eparture and arrival cities
-
7/26/2019 ACE3 Scenario Descriptions
23/23
2eparture and arrival time
9he results of the calculation ,ill include a reserve amount of ,ater to account for
usa.e variance and une>pected circumstances that increase ,ater consumption
beyond the typical amount for a @i.ht ,ith those parameters$
+alue of the recommended ,ater #uantity after -ll ,ill be in .allons or liters and inpercenta.e of tan7 capacity$ 9he amount of ,ater to be loaded ,ill be in .allons or
liters$ (or e>ample? the system recommends that the a.ent add 1! .allons to a "!/
.allon tan7 that contains ! .allons of ,ater$ 9he system ,ill state the follo,in.
Add 1! .allons? post/-ll #uantity of "! .allons D0Q full$ 9he format of the
recommendation ,ill be determined durin. desi.n$