[ghetto-software] emergency functions
- From: Nathan E Moore <nmoore4@xxxxxxxxxxx>
- To: ghetto-software@xxxxxxxxxxxxx
- Date: Wed, 14 Apr 2004 20:38:06 -0400 (EDT)
Hey, I don't have access to the lab, so I had to write these in txt
format. I don't know if its just a matter of cutting and pasting these
into a template, so sorry if this is a pain in the ass. The pdf I saw
looks really nice.
I will be available tomorrow for the duration to help finish this up,
12-5
Will post my data dictionary stuff before lecture tomorrow.
Nathan
clear_gate:
description: communicates the need for a gate to be cleared in the
event of an emergency to the ground and airspace management staffs, prevents
other sub systems from allocating gates to other flights
inputs: gate ID gate_DB preserves
open gate_DB modifies
in use gate_DB preserves
1) The emergency manager selects view current gate status from the menu.
2) The current gates both in use and open are displayed.
3) The emergency manager modifies all gates currently open to in use.
4) The emergency manager is prompted to confirm the modification, and
once confirmed the open gates are changed to in use status.
outputs: modified open gate_DB,screen modifies
in use screen preserves
requirements: gate_DB
pre-conditions: gate_DB should exist
post-condidtions: the current gates that are open are modified to
in use
side effects: notifies ground control and airspace managers of
changes to gate status
response to abnormal behavior: if all gates are open, then their
status is changed to in use,
if all gates are in use, then ground
control is notified to contact each plan and halt their motion.
stability: stable
necessity: mandatory
clear_runway:
description: communicates the need for a runway to be cleared in the
event of an emergency to the ground and airspace management staffs, prevents
other sub systems from allocating runways to other flights
inputs: runway ID runway_DB preserves
open runway_DB modifies
in use runway_DB preserves
1) The emergency manager selects view current runway status from the
menu.
2) The current runways both in use and open are displayed.
3) The emergency manager modifies all runways currently open to in use.
4) The emergency manager is prompted to confirm the modification, and
once confirmed the open runways are changed to in use status.
outputs: modified open runway_DB,screen modifies
in use screen preserves
requirements: runway_DB
pre-conditions: runway_DB should exist
post-condidtions: the current runways that are open are modified
to in use
side effects: notifies ground control and airspace managers of
changes to runway status
response to abnormal behavior: if all runways are open, then their
status is changed to in use,
if all runways are in use, then ground
control is notified to contact each plan and halt their motion.
stability: stable
necessity: mandatory
clear_taxiway:
description: communicates the need for a taxiway to be cleared in
the event of an emergency to the ground and airspace management staffs,
prevents other sub systems from allocating taxiways to other flights
inputs: taxiway ID taxiway_DB
preserves
open taxiway_DB modifies
in use taxiway_DB preserves
1) The emergency manager selects view current taxiway status from the
menu.
2) The current taxiways both in use and open are displayed.
3) The emergency manager modifies all taxiways currently open to in use.
4) The emergency manager is prompted to confirm the modification, and
once confirmed the open taxiways are changed to in use status.
outputs: modified open taxiway_DB,screen modifies
in use screen preserves
requirements: taxiway_DB
pre-conditions: taxiway_DB should exist
post-condidtions: the current taxiways that are open are modified
to in use
side effects: notifies ground control and airspace managers of
changes to taxiway status
response to abnormal behavior: if all taxiways are open, then their
status is changed to in use,
if all taxiways are in use, then ground
control is notified to contact each plan and halt their motion.
stability: stable
necessity: mandatory
Emergency Functions:
hold_all_flights
decription: represents to the system that all flights have been
grounded; prevents other sub-systems from allocating airport resources needed
in an emergency
inputs:
Record_ID schedule_DB preserves
Flight_ID schedule_DB preserves
ETD schedule_DB Modifies
Detination schedule_DB preserves
processing:
1) The emergency manager selects view current shedule from the
Menu.
2) The current flights schedule for take off are selected by
the Record_ID, Flight_ID, and ETD.
3) The flights scheduled for take-off are selected ETD is
modified to HOLD.
4) The emergency manager is prompted to confirm the
modification, and once confirmed the flights are put on hold.
outputs:
modified ETD schedule_DB, screen modifies
requirements: schedule_DB
Pre-conditions: schedule_DB should exist
Post-conditions: the current flights on schedule are modified to
reflect the HOLD ETD, holding the flights
Side effects: invokes the clear_runway, clear_taxiway, and clear_gate
functions sequentially
Response to Abnormal Behavior: If their are know flights sheduled for
take-off, than display message <Their are no flights scheduled for take off,
please contact ground control manager for confirmation.
Stability: Stable
Necessity: Mandatory
Other related posts:
