曝光台 注意防骗
网曝天猫店富美金盛家居专营店坑蒙拐骗欺诈消费者
way the user accomplishes the task (walking). In the same
way, if operational documentation cannot be related to the
user’s cognitive structure, then its utility in an operational
environment will be minimal. The goal of the task-based
structure is to articulate the relation between documentation
and operation. To reach this goal, it is necessary to
build the DU database in such a way that each DU is related
to its context of use.
Technical writers cannot fully anticipate all the contexts
of use of a piece of information. This is the reason why an
iterative process has to take place with end users to build
up a useful DU database. A task-based structure, in the
form of an exhaustive task tree, would be the backbone of
database construction, and would guarantee a coherent task
description of the documentation. Such a structure is the
interface between documentation from technical writers
and operations by end users.
Task-Block Concept
In an operational environment, a task can be seen as a set
of actions that has to be performed in a certain context. In
an aeronautical operational environment, this concept is
implicitly present, based on experience knowledge and
feedback. The smallest operational element of this concept
is clearly defined, and known as procedures. A task can be
represented as a Task-Block (or Interaction Block (Boy,
1998)), taking into account its context history through
Task Descriptors (TD), and leading to a set of actions.
Actions can be explicit like procedures, but is a more
general concept meant to define, describe and qualify the
necessary knowledge, skills and attitude needed to face a
situation. The Task-Block concept is a way to explicitate
the context of use of each related documentation.
Task-Block properties are:
Linear browse: Task-Blocks are linked. Each link is a one
way link and comes from (leads to) another Task-Block;
and Mutual Inclusion: a context of Task-Block can be a
Task-Block itself.
Task-Block organization. Following the property of
mutual inclusion, we will build the Task-Block
organization taking the example of a house.
- A Task-Block is characterized by the TD history
- A TD history must have one house TD (first layer)
HCI-Aero 2002 63
- A TD history may have one (or more) room TD (second
layer). Room TD can be mutual inclusive.
- A TD history may have one or more pieces of furniture
TD (third layer)
Figure 1: Task-Block & TD history organization
Task-Block links. The links between Task-Blocks will
principally reflect the one way time line property of flight.
Links can be of three different kinds: normal links,
abnormal links or emergency links. Links between Task-
Blocks are one way links. Two Task-Blocks are called
neighbors if a link connects them.
Two families of links are possible:
- Action Links: which are characterized by a change (add
or replacement) of room TD;
- Reaction Links: which are characterized by an addition
of furniture TD.
Construction of Documentation
Because task definition calls for documentation
(procedures, system explanation,…), but also
documentation demands further task definitions (possible
failures, supplementary techniques,…), construction of
documentation has to be an iterative process to ensure a
complete structure.
Initial Task-Block Tree
Let’s get back into a pilot’s skin. your job is to accomplish
a flight from Toulouse to Chicago with an A380. This
context can be seen as the first layer of TD. Implication of
the destination is beyond the scope of the present FCOM,
but aircraft type and version have to be considered. It will
be our house TD. You already know you will have to
proceed through different phases like preparation, departure,
cruise and arrival. These flight phases have been
analyzed and described for standardization purposes
(Travers, 2000). They can be seen as the second layer of
TD for your job. These flight phases are linearly defined,
and each one of them is independent. They can be
considered as room TD. For each of these phases, experience
has brought Standard Operation Procedures (SOP),
which are aircraft dependent, and enable you to operate
safely under normal conditions. These SOP definitions
would be the first apparent structure of the documentation
construction (figure 2).
Principally, the initial Task-Block tree can be
characterized by the first two layers of TD. This initial
Task-Block tree construction is a mutual inclusive segmentation
of the considered house task, and should define
中国航空网 www.aero.cn
航空翻译 www.aviation.cn
本文链接地址：
航空资料11(83)
