曝光台 注意防骗
网曝天猫店富美金盛家居专营店坑蒙拐骗欺诈消费者
philosophy and define some tool concepts for its
application. The task structure methodology for
documentation construction uses these concepts. Next, the
development of a demonstrator is described. Finally the
improvement of documentation by using the task structure
methodology is discussed.
Electronic Documentation
For a paper-based document, the properties of documentation
are its organization in chapters, and its linear coherence
with physical page attribution and format. With
electronic documentation, these properties will no longer
exist, and new properties have to be defined. The concept
of Documentary Unit (DU) is at the heart of segmentation
of electronic documentation into defined entities for
revision purpose (Payeur, 2001). A DU will have a small
size, in terms of text, usually a paragraph, and can contain
descriptions, schematics, animations, performance data etc.
Each of these entities may be hierarchically organized into
levels of sub-DUs.
For flight operational needs, the relevant information
will be split into six user-oriented domains:
Procedures (meant as commented procedures);
Description;
Limitations;
62 HCI-Aero 2002
From: HCI-02 Proceedings. Copyright © 2002, AAAI (www.aaai.org). All rights reserved.
Performances;
Supplementary techniques;
Dispatch requirements (i.e. MEL and CDL).
From a database structure point of view, we cannot
consider splitting the whole database into the six domains.
DUs like warnings, notes or sounds can be floating sub-
DUs between domains. Domain definition is an interface
concept describing the documentation and enabling the
user to structure his or her navigation.
For retrieval purposes, descriptors will be assigned to
each self-sufficient DU. A DU descriptor is meant to
qualify the content of a DU. DU descriptor attribution is a
process which will have to take place in parallel with DU
construction. Descriptors can be split into families, such
as:
Domain Descriptors;
Context Descriptors;
Task Descriptors;
Revision Descriptors.
These families are needed for EFCOM use, but more
families can be defined if necessary.
Contextual Documentation
There are two principal ways of describing a context. The
system approach or the task approach. The system
approach is an engineering approach, and groups the
information into topics. The task approach is a usercentered
approach describing a particular situation. These
two approaches are complementary. A system can include
information considering several tasks, and to accomplish a
task, several systems can be needed. For instance, a
context description in operation could be: “Limitation
(Domain Descriptor) of the landing gear (Context
Descriptor) in taxi (Task Descriptor)”. This property is a
great advantage for information retrieval. A smaller set can
be chosen with an overlapping system of information
description than with a mutual inclusive system. It is true
as long as the documentation description is exhaustive.
Users who want to answer questions like: what do I have
to do if?; what are the limitations?; how does the system
work?; will build the Manual Context by entering one or
several keywords. From this list of keywords, all relevant
DUs will be activated. A thesaurus will help compare
descriptors to keywords.
Beside information retrieval, one of the most attractive
possibilities of electronic material is interaction between
systems. An issue of context-driven concept is to let the
aircraft data help provide the context. For instance, if a
failure occurs, the documentation used in operation should
not display information in discordance with this particular
context. This help is called context-sensitive help (Boy,
1998). A one way link from the aircraft systems to the
EFCOM should permit, when wished, to dynamically
overlay the actual state of the aircraft to the available
documentation.
Task Structure Philosophy
Why a Task-based Structure?
Because one of the top requirements is to be pilot-oriented,
let’s get into a pilot’s skin. The main property of aircrew
work is to be guided by the time line. Along this time line,
the past cannot be changed, and will condition the
immediate future. If the aircrew does not take into account
(and accepts) this property, then they will not be able to
accomplish their work under time pressure.
Operational documentation can be seen like a cane. A
cane helps its user to accomplish a task (going from A to
B). But the cane is useless if its use does not match the
中国航空网 www.aero.cn
航空翻译 www.aviation.cn
本文链接地址：
航空资料11(82)
