Scribd
Upload
91 views

Samples of The 162 Data-Display Guidelines From Smith and Mosier

An effective display design should clearly define its purpose and support the perception and processing of relevant information. Effective design principles include simplicity, proportion, organization, and visual structure. Guidelines for data display recommend ensuring needed data is available, labeling elements closely but separately, and allowing users to modify display functions. Empirical results show structured displays from superior to narrative are better, and consistency across screens improves performance. Sequence of displays should be consistent within a system while allowing navigation backwards.

Uploaded by

alax
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
91 views

Samples of The 162 Data-Display Guidelines From Smith and Mosier

An effective display design should clearly define its purpose and support the perception and processing of relevant information. Effective design principles include simplicity, proportion, organization, and visual structure. Guidelines for data display recommend ensuring needed data is available, labeling elements closely but separately, and allowing users to modify display functions. Empirical results show structured displays from superior to narrative are better, and consistency across screens improves performance. Sequence of displays should be consistent within a system while allowing navigation backwards.

Uploaded by

alax
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 2

An effective display design should be able to support the perception of relevant system variables

and to facilitate further processing of that information and should be able to clearly define its
purpose.
Mullet and Sano's categories of design principles include elegance and simplicity, scale, contrast,
and proportion, organization and visual structure, module and program, image and
representation, style.

Samples of the 162 data-display guidelines from Smith and Mosier


 Ensure that any data user needs are available for display.
 Display data to users in directly usable form.
 Maintain a constant format for any particular type of data.
 Use short, simple sentences.
 Use affirmative statements.
 Adopt a logical principle by which to order lists.
 Ensure that labels are sufficiently close but separated by at least one space.
 Left-justify label of alphabetic data.
 Label each page in multipage displays.
 Begin every display with a title or header.
 For size coding, make larger symbols be at least 1.5 times the height of the next-smaller
symbol.
 Consider color coding for applications to distinguish between data.
 Blink coding if used must be rated from 2 to 5 Hz, with a minimum duty cycle of 50%.
 For a large table that exceeds the capacity of one display frame, ensure that user can see
column headings and row labels in all displayed sections of the table.
 Provide a means for users to make necessary changes to display functions.

Field layout
 Blank spaces and separate lines can distinguish fields.
 Names are in chronological order, alignment of dates familiar dates separators.
 Labels are helpful for all.
 Differentiate labels from fata with case, boldfacing etc.
 IF boxes are available they can be used to enhance display.
 Specify the date format for international audiences.

Empirical Results
 Structured from superior to narrative form.
 Performance improves with using appropriate indentation, underlining, improving data
labels, clustering related information and using fewer denser displays.
 Screen content should only contain task relevant information.
 Consistent location, structure, and terminology across displays important.

Sequence of display
Should be similar throughout the system for similar tasks along with exceptions. Within a
sequence, user should be able to sense where they are and how far they have to go. It should be
possible to go backwards for corrections and modifications.

You might also like