Specifications

MlL-STII- 1472E
5.15.4.3.13 Flexible data entry.
When multiple data items areentered as a single transaction,
the
user shall be allowed to re-enter, change, or cancel any item before taking a final ENTER action.
5.15.4.3.14 Infonnativc labels. Descriptive wording shall be employed when labeling data
fields; use of arbitrary codes shall be avoided.
5.15.4.3.15 [e-mail] order. Where no source document or external information is involved,
forms should be designed so that data items are ordered in a logical sequenee for input.
5.15.4.3,16 Form filling for control entry.
Form filling may be used as an aid for composing
complex control entries. For example, for a print request, a displayed form might help a user invoke
the various format controls that are available.
5.15.4.4 Fixed function keys. Fixed function key interactive control may be used for tasks
requiring only a limited number of control inputs or in conjunction with other dialogue types. (See
5.15.2.3)
5.15.4.5 Command kmzuute.
5.15 .4.5.1 Use. Command language interactive control maybe used for tasks involving a wide
range of user inpu=md where user famiharity with the system can take advantage of the flexibility and
speed of the control technique.
5.15 .4.5.2 User viewmint. A command language shall reflect the user’spoint of view such
that the commands are Iogicrdly related to the user’s conception of what is being done.
5.15 .4.5.3 Distinctiveness. Command names shall be distinctive from one another.
5.15 .4.5.4
Punctuation. The co-d language shall contain a minimum of punctuation or
other special characters.
5.15 .4.5.5 Abbreviations. The user shall be permitted to enter the full command name or an
abbreviation for any command of more than 5 characters.
5.15 .4.5.6 Standardization. All commands and their abbreviations, if any,
shall be standardized
(e.g., see
MIL-STD-783).
5.15 .4.5.7 Displaved location. Commands shall be entered and dispiayed in a standard location
on the display.
5.15.4.5.8 Command txom~.
The user shall be able to request prompts, as nbssw. to
determine required parameters or available options for an appropriate next command entry.
5.15.4.5.9 Complexity.
The command hmguage should be programmed in !ayms of q~xi~
such that the basic layer will allow the inexperienced user to control a transaction. As this person’s
skill increases, the command language should allow skipping from basic to more advarwxl layers to
meet the use$s current needs.
f ] f a ‘i 10 { lSeT defi~itinn of macrocornrnands. ●The programming shall not accept a user
designated macro name that is the same
as an existing command name.
5.15.4.5.11 Standard tcchniaues for command editing.
Users shall be allowed [o edit erroneous
~utiuuand cnti}w with the same techniques that are employed to edit data entries since
consislcnf
r[iltln: ~.xhniq(ws WIIIKped learning and redIIce errors
I
1%