Layout and display standards promote the creation of consistent maps. The following considerations should be kept in mind when designing map layout and design standards.
Associate Areas with Particular Uses
Each specific area of a map should be devoted to a particular use. For example, the top five lines of the screen could be reserved for product and title information and the bottom five for map and control key information.
Display like Fields in the Same Location
Similar fields should be displayed in the same location and with consistent display attributes on all maps. A given site usually uses the same or similar fields on several maps. For example, message fields and titles are included on most maps, and should be presented consistently.
Limit the Number of Fields on a Screen
The amount of data transmitted down a line is affected by the number of fields on a map. This can affect line contention and should be considered when designing a map. Do not do borders or one-byte literal fields.
Handle Operations and Prompts Consistently
Frequently used operations or prompts should be handled consistently. For example, yes and no responses should be requested in the same way on every map.
Handle Default Values Consistently
Consistent methods should be developed for indicating default values. For example, an asterisk (*) or a special display color might be used to identify the default value for a list of options. A default entry for a data field might be specified by a literal field adjacent to the data field.
Standardize Map Templates
A standard map template should be used for each type of map. For example, many applications prompt the operator to select an item from a menu. A template for this type of screen is different than a template for a screen that requests words and numbers from a user. The following considerations apply to the design of a template:
|
Copyright © 2013 CA.
All rights reserved.
|
|