Naming Conventions › Naming Database Information Entities › Sample Glossary of Naming Tokens

Sample Glossary of Naming Tokens

The following sample illustrates sample entries from one type of glossary. The following example shows one way in which a glossary can be defined; each design team must determine the naming conventions that best suit its needs. Note that the word WORD in this example is a user-defined entity defined to the dictionary, as follows:

ADD CLASS NAME IS WORD
CLASS TYPE IS ENTITY.
ADD WORD ABEND           ABBREVIATED NEVER
ADD WORD ABSOLUTE        ABBREVIATED NEVER
ADD WORD ACCEPT          ABBREVIATED NEVER
ADD WORD ACCOUNT         ABBREVIATED SOMETIMES ABBR ACCT
ADD WORD ACCRUAL         ABBREVIATED NEVER
ADD WORD ACCUMULATE      ABBREVIATED SOMETIMES ABBR ACCUM
ADD WORD ACKNOWLEDGE     ABBREVIATED SOMETIMES ABBR ACK
ADD WORD ADMINISTRATION  ABBREVIATED ALWAYS ABBR ADMIN
ADD WORD ADDRESS         ABBREVIATED ALWAYS ABBR ADDR
     .
     .
     .
     .
     .
     .
ADD WORD YIELD           ABBREVIATED SOMETIMES ABBR YLD
ADD WORD YTD             ACRONYM 'YEAR TO DATE'
ADD WORD YY              ABBREVIATED NEVER
ADD WORD ZERO            ABBREVIATED NEVER
ADD WORD ZONE            ABBREVIATED NEVER

The sample entries from this glossary show one way in which naming conventions can be implemented within an installation. In this glossary, the application designers have determined that certain words are always to be abbreviated and others are never to be abbreviated; the majority of words are to be spelled out completely whenever possible. When stored on the dictionary, the glossary is readily available as a reference guide for programmers and developers.