Best practice grouping your development work

This document defines the naming convention to use while performing standard or specific developments to avoid naming conflicts.

The purpose of this document is to provide best practice guidelines when developing in Version 7 native mode.

The following rules are considered ‘best practice’ for grouping your development work:

Use meaningful names

You should create meaningful names (codes). Avoid using abbreviations and generic words. All codes must be created in English. For example, 'MYPROCESSCODE' instead of 'MYPROCCD'.

Data dictionary item names

Be consistent. Use the same code throughout the development process. Use a common two or three letter prefix to group data dictionary items for a module or project development. Use the same prefix for the module or project as well. This will make it easier to find all data tables, classes, representations, and processes. For example, the Library Management project uses the prefix ‘XLM’ throughout the development process (where X=Add on; LM= Library Management), the Change Control Management prefix is ‘CCM’.

Grouping development work best practice summary

• You must use the naming convention rules.
• You must use meaningful codes.
• Codes must be created in English.
• Use a common prefix.