曝光臺 注意防騙 網曝天貓店富美金盛家居專營店坑蒙拐騙欺詐消費者

all related systems. Each of these Task-Blocks will call for
procedures, but also for all relevant information useful for
the user to be able to accomplish them.
All the links that are defined during the initial Task-
Block tree construction are Action Links. A scenario is a
particular path through the Task-Block tree that makes it
possible to accomplish part of the house task. The
complete SOP tree should build a solid, useful and well
known structure to enable the first step of DU database
construction.
Initial Construction of Documentation
Once a Task-Block is defined, the technical writer will
write all information which appears necessary in the
situation described through the TD history. This process
should take place in an iterative way with end users. The
documentation will be written for the six predefined
domains.
To assure a good coherence of the documentation, the
technical writer should write the domain related DUs in a
linear order. The relative position of the DUs inside a
particular domain should be kept in memory to enable a
coherent reconstruction of Task-Block related domains
even if some DUs are missing (due to Context Descriptors
choices). Similarly to the DU/sub-DU construction, the
domain is an ordered succession of DU-Links, which
points to all DUs defined during documentation construction.
Such a construction could lead to much redundant
information between two neighbor Task-Blocks. A tool
facility for the technical writer should allow him/her to
pick up DUs already created for neighbor Task-Blocks,
and he/she would then modify, add or complete, in an
iterative manner, Task-Blocks documentation.
64 HCI-Aero 2002
Figure 2: Initial Task-Block tree example
All DUs created in this manner get their attributes from
the TD history used to define them. It is a cumulative
process, if a DU is used under several Task-Blocks, then it
will be attributed all TDs of the multiple Task-Blocks’ TD
history. This process will enable technical writers to
implicitly connect the context of use to the documentation
during the data construction.
In parallel, the technical writers will define for each DU
relevant Context Descriptors (for example an ATA
chapter) for information retrieval purposes.
Augmented Task-Block Tree
Once created, the initial Task-Block tree should summarize
all the planned tactics that the aircrew could encounter
during the flight. Running through a particular scenario of
one of these tactics can be schematized in a linear form
considering the one way time line property. All the present
links that connect all flight tasks are Action Links. If a non
standard situation occurs, a scenario has to remain possible
(under conditions). The purpose of Reaction Links is to
define all possible non standard situations that can arise.
For instance, if a failure occurs, this fault can be considered
as a furniture TD, and remains true during the rest
of the flight. If information is demanded, then the choice of
documentation has to take into account this restriction.
Parallel scenarios can be built which will again be the base
and structure for further documentation construction
(abnormal procedures, supplementary techniques,…).
Many events can occur at any time during a flight. Two
parallel scenarios are characterized by adding the same
furniture TD to it. Links that connect two parallel scenarios
are in-line Reaction Links (or “weak links” using the
Interaction Block terminology). An in-line Reaction Link
is a link between two Task-Blocks with adding furniture
TD(s) in the TD history.
It can happen that during the flight, an event pushes a
change in the tactics. In that case, adding a furniture TD
will force a change of room TD. Those links are called outof-
line Reaction Links (or “strong links” using the
Interaction Block terminology). An out-of-line Reaction
Link is a link between two Task-Blocks with adding
furniture TD(s) and change of room TD(s) in the TD
history.
All relevant furniture TD in a TD history will have to be
taken into account to build a complete Task-Block tree
(figure 3).
HCI-Aero 2002 65
Figure 3: in-line R. Link and out-of-line R. Link
Augmented cCnstruction of Documentation
The process of documentation construction out of each
Task-Block remains the same as explained for the initial
documentation construction.
However, some documentation will be necessary which
is not directly related to the Task-Blocks, but related to the
Reaction Links defined. For instance, some specific
　
中國航空網 www.k6050.com
航空翻譯 www.aviation.cn
本文鏈接地址：航空資料11(84)