曝光台 注意防骗
网曝天猫店富美金盛家居专营店坑蒙拐骗欺诈消费者
aircraft designer. We calI this the operational phase.
2. A dialogue between the documentation and the users,
created by the documentation author. We call this the
referential phase.
In the operational dialogue, the acts are generally (but not
exclusively) domain acts among agents in the flightdeck. The
term agent is used in sense that elements of the aircraft
(especially its interfaces) and all members of the crew have
defined roles, responsibilities and capabilities. Thus the
dialogues designed for the operational phase may also be
among the users. As a typical example, an airline’s FCOM for
the Airbus A320 specifies a procedure for Flight Plan
Completion in which key elements are carried out solely by
the crew rather than through an action in the interface to the
aircraft; in this case, the crew compares (a) flight-plan
information from the interface with (b) clearance information
received from air-&& control.
In the referential dialogue, the acts are generally (but not
exclusively) meta acts from the documentation to the users.
The design of the understanding dialogue for the FCOM is an
especially difficult task because the set of intended users of the
manual is not homogeneous. Foreseeable users include not
only flightcrew but trainers, future designers and engineers,
future authors, and regulators (i.e., for certification). Each of
these users has a distinct background, set of goals and way of
using the documentation.
3. APPLICATION
Having introduced the AFP model generally, we now turn to
application of the model to a specific instance of
documentation, demonstrating that relevant features of the
documentation can be mapped onto the model’s key concepts.
3.1. Example
Figure 1 presents an excerpt of the procedure for navigating an
Airbus A340 into a holding pattern during the descent phase of
a flight. This procedure is part of the FCOM chapter of
proceduresf or the Flight Management System (FMS). The
interface to the FMS is called the Multipurpose Control and
Display Unit (MCDU). To interpret Figure 1 it is important to
understand that the flightcrew read information, enter data, snd
push buttons to perform commands on the MCDU; some of
these actions can modify the current flight plan.
244
(HOLDING PATTERN I
Refer to “HOW TO USE” for details.
PROCEDURE
El
F-PLN key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DEPRESS
. LATERAL revision page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1
SELECT
l HOLD prompt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
l HOLDING data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CHECK / MODIFY
l TMPY F-PLN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CHECK / INSERT
Figure I. Excerpt of FMGS Procedure for Holding Pattern
Applying the AFP model to the initial actions of the holding- (7) choose-display&J,S , lateral-revision(fix0))
pattern procedure and its documentation, it is important to note
first that the procedure itself consists mainly of domain acts
carrying out a prescriptive function in the operational phase. In
particular, the actions presented in the procedure can be
abstracted into acts as follows:
Depressing the “F-PLN” key causes the flight-plan page
to appear on the MCDU. Among other things, this page
presents tbe list of navigation “fixes” that compose the flight
plan. This action can be viewed as a set of combined
operational-phasea cts:
(1) comrnand(U, S, offer-choice(S. U, fixes@)))
(2) choose-display(U, S, flight-plan)
where U is the user, S is the system, and Fs a list of fixes. Act
1 is a domain act and Act 2 is a meta act. Together, they lead
to the domain and meta responses:
(3) offer-choice(S, U, fixes(E))
(4) present-display(S, U, flight-plan).
Moreover, the documentation of the action can be seen as a
referential-phase act that can be linked to Acts 1 and 2:
(5) inform(S, U, proc-action@epress-F-PLN key))
in the context of the holding pattern procedure.
Selecting the lateral revision page is performed
中国航空网 www.aero.cn
航空翻译 www.aviation.cn
本文链接地址：
航空资料3(49)
