Specifications

MIL-STI)-1472E
d. use an accentuating technique different and easily distinguished from the method used to
highiight or code emergency or critical messages,
e. be unique and meaningful to distinguish them from data, error messages, or other
alphanumerics,
f. be displayed in upper case only, while text maybe displayed in upper and lower case, and
g. reflect the question or decision posed to the user, when presenting a list of user options.
5.15.3.1.11 Scrolling. hems continued on the next page (scrolled) should be numbered relative
to the last item on the previous page,
5.15.3.1.12 Pagenumbering. Each page of a multiple page display shall be labeled to identify
[he currently displayed page and the total number of pages, e.g., Page 2 of 5.
5.15.3.1.13 Frame identification. Every display frame shall have a unique identification to
provide a reference for use in requesting the display of that !iame. The frame identification should be
an alphanumeric code or an abbreviation which is prominently displayed in a consistent location. It
should be short (3-7 characters) and/or meaningful enough to be learned and remembemd easily.
5.15.3.2 Display content.
5.15 .3.2.1 Standardization. The content of displays within a system shall be presented in a
consistent, standardized manner.
5.15 .3.2.2 Information density. Information density should be minimized in displays used for
critical task sequences. At bat one character space shall be left blank above and below critical
information; at least two character spaces shall left blank to the left and right of critical information (see
5.15.3.1.5 and 5.15.3.3.1).
5.15 .3.2.2.1 Crowded displays. When a display
contains tcmmuch data for presentation in a
single frame, the data shall be partitioned into separately displayable pages.
5.15.3 .2.2.2 Related data on same Page. When partitioning displays into multiple pages,
functionally related
data items shall be displayed together on one page.
5.15.3 .2.2.3 Page labeling. In a multipage display, each page shall be labeled to show its
relation to the others,
5.15.3.2.3 Abbreviations and
acronmns. Information shail be disphtycd in phdn concise text
wherever possible. Where abbreviations and acronyms are required, they shall conform to existing
standards, if available (e.g., MIL-STD-783). New acronyms, if required, shall be developed using
logical rules of abbreviation. Abbreviations should be distinctive to avoid confhion. Words should
have on!y one consistent abbrwiation. No punctuation should be used in abbreviations. Definitions
of all abbreviations, mnemonics and codes should be provided at the user’s request
5.] 5.3.2.4 Data en~ and display consistency. Data display word choice, format, and style
ANJJCJbe consistent with the requirements for data entry and control.
5.15 .3.2.5 Context for displayed data, The
user should not have to re]y on memo~ to interpret
!x’~t LI:IU, each
d~!:idispJa} shou]d prt,n’idc net’dt’[i~’lmlex(,int’]udingttc.iipitt]];~!ing prl(v d;!!:! fuvl!
prmr dI@ftvs m necessw.