Why use Conventions?
It is advisable for a site to develop naming conventions for map-related entity occurrences. While mnemonic names work well at sites that have a few basic applications, mnemonic names become difficult to use as the number and complexity of applications increase.
Adhering to naming conventions makes it easier to construct names, easier to reconstruct names if one is forgotten, and easier for different users to determine the purpose of a map or map component. Naming conventions facilitate the construction of alternative map tables when alternative maps are required.
Sample Naming Conventions
The following naming conventions illustrate a sample system for giving names to map-related entities. PANEL and TABLE occurrence names can be from 1 through 32 characters in length. Names of MAP occurrences can be from 1 through 8 characters in length. The sample naming convention specifies 8-character names since it is intended for MAP occurrences as well as for PANEL and TABLE occurrences.
Notes:
Position |
Meaning |
Value |
Description |
---|---|---|---|
1 |
Source of entity |
C |
CA entity |
2-3 |
Application |
EX FS SY |
Example application Financial system application System application |
4 |
Type of entity |
L M C E |
Panel occurrence Map occurrence Table occurrence (code table) Table occurrence (edit table) |
5 |
Special information |
E F G S |
English-language application French-language application German-language application Spanish-language application |
6-8 |
Identification of entity |
xxx |
|
Sample Names
The following sample names demonstrate the naming conventions described in the previous table:
It is often useful to integrate map-naming conventions for map-related entities with conventions used for dialogs and programs.
Copyright © 2013 CA.
All rights reserved.
|
|