曝光台 注意防骗
网曝天猫店富美金盛家居专营店坑蒙拐骗欺诈消费者
intended function. Consideration should be given to the long-term display degradation as a result of
abrasion and aging.
D2.3 Input Devices
In choosing and designing input devices such as keyboards or cursor-control devices, applicants
should consider the type of entry to be made and flight deck environmental factors, such as
turbulence, that could affect the usability of that input device. Typically, the performance parameters
of cursor control devices should be tailored for the intended application function as well as for the
flight deck environment.
D2.4 General EFB design guidelines
D2.4.1 Messages and the Use of Colours. For any EFB system, EFB messages and reminders
should meet the requirements in CS 23.1322 or 25.1322, as is appropriate for the intended aircraft.
While the regulations refer to lights, the intent should be generalised to extend to the use of colours
on displays and controls. That is, the colour “red” shall be used only to indicate a warning level
condition. “Amber” shall be used to indicate a caution level condition. Any other colour may be used
for items other than warnings or cautions, providing that the colours used, differ sufficiently from the
colours prescribed to avoid possible confusion. EFB messages and reminders should be integrated
with (or compatible with) presentation of other flight deck system alerts. EFB messages, both visual
and auditory, should be inhibited during critical phases of flight. Flashing text or symbols should be
avoided in any EFB application. Messages should be prioritised and the message prioritisation
scheme evaluated and documented. Additionally, during critical phases of flight, required flight
information should be continuously presented without un-commanded overlays, pop-ups, or preemptive
messages, excepting those indicating the failure or degradation of the current EFB
application. However, if there is a regulatory or Technical Standard Order (TSO) requirement that is
in conflict with the recommendation above, those should have precedence.
D2.4.2 System Error Messages. If an application is fully or partially disabled, or is not visible or
accessible to the user, it may be desirable to have a positive indication of its status available to the
2 8 FLIGHT SAFETY FOUNDATION • FLIGHT SAFETY DIGEST • JUNE 2005
A P P E N D I X
JAA Administrative & Guidance Material
Section Four: Operations, Part Three: Temporary Guidance Leaflets (JAR-OPS)
Section 4/Part 3 (JAR-OPS) 36-18 01.10.04
user upon request. Certain non-essential applications such as e-mail connectivity and administrative
reports may require an error message when the user actually attempts to access the function rather
than an immediate status annunciation when a failure occurs. EFB status and fault messages should
be prioritised and the message prioritisation scheme evaluated and documented.
D2.4.3 Data Entry Screening and Error Messages. If user-entered data is not of the correct format
or type needed by the application, the EFB should not accept the data. An error message should be
provided that communicates which entry is suspect and specifies what type of data is expected. The
EFB system should incorporate input error checking that detects input errors at the earliest possible
point during entry, rather than on completion of a possibly lengthy invalid entry.
D2.5 Error and Failure Modes
D2.5.1 Flight Crew Error. The system should be designed to minimise the occurrence and effects
of flight crew error and maximise the identification and resolution of errors. For example, terms for
specific types of data or the format in which latitude/longitude is entered should be the same across
systems. Data entry methods, colour-coding philosophies and symbology should be as consistent as
possible across the various hosted EFB applications. These applications should also be compatible
with other flight deck systems.
D2.5.2 Identifying Failure Modes. The EFB system should be capable of alerting the flight crew of
probable EFB system failures.
D2.6 Responsiveness of Application
The system should provide feedback to the user when user input is accepted. If the system is busy
with internal tasks that preclude immediate processing of user input (e.g., calculations, self-test, or
data refresh), the EFB should display a “system busy” indicator (e.g., clock icon) to inform the user
that the system is occupied and cannot process inputs immediately.
The timeliness of system response to user input should be consistent with an application’s intended
function. The feedback and system response times should be predictable to avoid flight crew
distractions and/or uncertainty.
D2.7 Off-Screen Text and Content
中国航空网 www.aero.cn
航空翻译 www.aviation.cn
本文链接地址：
航空资料31(97)
