Use case name: Coordinate Response
Reuse category: Kernel
Summary: Police Station Coordinator and Fire Station Coordinator coordinate the police and fire vehicle
response to a single vehicle crash crisis
Actors: Police Station Coordinator(PSC)(Primary), Fire Station Coordinator(FSC)(Primary), and
Timer(Secondary)
Dependency: Include Negotiate Routes abstract use case, Include Dispatch and Track Vehicles abstract
use case
Preconditions: The PSC and the FSC are aware of the crisis and have defined the crisis details within
their separate databases, but have not established contact with each other to coordinate the response
to the crisis.
Description:
1. The PSC or FSC selects the crisis coordination initiation option.
2. System displays “Crash Crisis Coordination” and prompts for the names of the PSC and the FSC
on their respective screens.
3. The PSC and the FSC enter their names
4. System displays the coordinators’ names and roles and prompts for the crisis details
5. The PSC and the FSC select the display crisis details option
6. System displays the police station active crisis details and the fire station active crisis details. A
periodic timer is started that refreshes the display of the crisis details and the related vehicle
and timeout data every second.
7. Include Negotiate Routes use case
8. Include Dispatch and Track Vehicle use case
9. The PSC or the FSC selects the crisis closure option
10. System displays “Proposal to Close Crisis(Crisis identifier)”
11. The responding coordinator enters agreement with closure request
12. System displays “Crisis is closed”, updates the status field in the Crisis details record in both
databases to Closed, and exits crash crisis coordination mode.
Alternatives:
At step 8, the PSC or the FSC selects a reroute option for one of their deployed vehicles which has not
reached the crash site by its ETA due to heavy traffic on its planned route
Negotiate Routes 6.a: PCS requests a list of possible routes from the delayed vehicle’s current location
to the crash site
Negotiate Routes 6.b: System displays on the PSC’s screen an alternative route to the crash site and sets
a route negotiation timer.
Negotiate Routes 7.a: The PSC selects the proposed route for the delayed vehicle
Negotiate Routes 8.a: System displays the proposed route for the blocked vehicle and prompts the FSC
for an agreement or disagreement.
Negotiate Routes 9a: FSC agrees to the revised route
Continue with Negotiate Routes step 10
At step 8, the PSC and the FSC become aware that the crisis is more severe than expected
8a: PSC selects the deploy additional vehicles options
Negotiate Routes 1.a: System sets a timer for a fixed time period for negotiations on vehicle routes and
prompts for the number of additional police vehicles to be deployed.
Negotiate Routes 2.a: PSC enters a number equal to or greater than zero
Negotiate Routes 3.a: System displays the number of additional police vehicles and creates a
deployment record for each vehicle with the vehicle ID and ETA being blank and location set to Station.
System then prompts for the number of additional fire trucks
Negotiate Routes 4.a: FSC enters a number equal to or greater than zero
Negotiate Routes 5.a: System displays the number of additional fire trucks and creates a deployment
record for each vehicle with the vehicle ID and ETA being blank and location set to Station.
Continue with Negotiate Routes step 6
At any step when communications have been restored after a period of unavailable communications
and the crisis has been resolved
N.a1: Continue with step 9
Step 1 has not yet been completed and communications have been restored after a period of
unavailable communications
N.a2: Continue with step 1
Communications have been lost at some step after route agreement had been reached but
communications have been restored before all vehicles have completed their objectives.
N.a3: System displays the current values for the fire station and police station crisis details
Continue with Route and Dispatch Vehicles step 1
Variation Points:
Name: Shared Identifier
Type of functionality: Optional
Line numbers: 1
Description of functionality: If an active crisis already exists when a new crisis coordination is
initiated,
Step 1a: The System displays the message “Additional Crisis Event Coordination” and displays the
crisis details from both stations
Step 1b: The initiating coordinator enters a global identifier for each crisis record where no global
identifier exists.
Step 1c: The System updates the identifier field in each crisis detail record as well as the Crisis ID field
in routing , deployed vehicle and timeout records linked to the crisis detail record.
Step 1d: Continue at step 7
Name: Multiple Crisis Display
Type of functionality: Optional
Line numbers: 6
Description of functionality: If multiple active crises are being coordinated, the System displays
current information related to each crisis
Name: Designated Crisis Closure
Type of functionality: Optional
Line numbers: 9
Description of functionality: If multiple active crises are being coordinated
9.a: The System Prompts the proposing coordinator for the Crisis Identifier of the Crisis to be closed
9.b: The proposing coordinator enters the Crisis Identifier”
9.c: Continue with step 10
Name: Change of Primary Crisis Coordinator
Type of Functionality: Optional
Line Numbers: 7, 8
Description of Functionality: If multiple PSCs or FSCs exist the system shall allow the active primary
coordinator to transfer responsibility to another coordinator. The coordinator indicates that they
wish to delegate authority, the system prompts the current coordinator for the coordinator that will
take over responsibilities and the crisis ID should multiple crises exist. The system then saves the
changes and notifies the replacement as well as the PSC/FSC counterpart for the crisis that a switch
has been made.
Postcondition: The crisis has been closed
Outstanding questions: