Specifications

\
MIL-STD- 1472E
5.15.4.5.12
Destmctive commands. If a command entry may have disruptive consequences,
the user shalI be required to review and confirm a dkplayed interpretation of the command before it is
executed.
5.15.4.6 Question and answer.
5.15.4.6.1 ~. Question-and-answer dialogues may be used for routine data entry tasks where
data items are known and their ordering can be constrained, where users will have little or no training,
and where the computer is expected to have medium respme speed.
5.15.4.6.2 Qu@.t
“ensdist)laved scmarateiy. Each question should be displayed separately in
question-and-answer dialogues; users should not be tequired to answer several questions at once.
5.15 .4.6.3 Recapitulating
prior answers. When a series of computer-posed questions are
intemelated, answers to previous questions should be displayed when those will provide context to
help a user answer the current question.
5.15.4.6.4 Source document capability.
When questions prompt entry of data fimma source
document the question sequence shall match the data sequence in the source document.
5.15.4.7 @e ry laruwaue.
5.15 .4.7.1 ~. Query language dialogue should be used for tasks emphasizing unpredictable
information retrieval (as in many analysis and planning tasks), with moderately trained users.
5.15.4.7.2 Natural ormnizationofdata Query Ian
T
should reflect a data structure or
organization perceived by users to be natural. For example, i a user supposes that all data about a
pmc~ topic arc@ in one PI=, then the cpexy laguage should permit such data to be retrieved
by a single query, even though various data maybe stortxi in
dif%rentcanputer files.
5.15.4.7.3 Cohelentrumwuon
“ ofdataOmamAon A single representation of the data
organization for use in query formulation should be established, i.e., the user should not necessady
ned to know if diffexent queries will acws dMfercntdatabases over different routes.
5.15 .4.7.4 Task-oriented wording. The wording of a query should simply specify what data
are requested; a user should not have to tell the computer how to fmd the data.
5.15 .4.7.5 Lotic to link ctueties. The query hmguage should be designed to include logic
elements that permit users to link (e.g., “ancL””or”) sequentia.i queries as a single entry.
5.15.4.7.6 ~
“ lue-scale retrieval. If a uery will result in a hrge-scaie data mrievrd,
the user shall be required to confirm the transaction or
&
e Ikt.her action to narrow the quay before
prtxessing.
5.15,4.8 GraRhicinteraction.
5.15 .4.8.1 Use. Graphic interaction as a dta!ogue may be mnsidemd for use by casual utwr~LO
provide graphic ai~m a supplement to other types of interactive control.
5.15.4.8.2 lconic m
enus. When system users have different linguistic backgrounds, graphw
menus may be used winch dtipby W* h ~ Uaccoalrol options. Where the system is
intended for use by foreign military personnel, icon design shall be consistent with applicable cultural
tinderhruc vw%tbks MensuJc cumprchcnsion and (u avoid potential offense
I79
.... ... ..... . . ...,