The purpose of naming standards is mainly to enforce consistency and its immunity to remain compatible with the environment. Naming standards should be decided for each and every resource in the application including the database name, form, view, agent, and other design elements.
In additional to the name, make use of alias names wherever possible. This allows you to change or translate the name without breaking the reference to the original name in the application design.
If your development team already uses a more elaborate naming standard where aliases for different design elements have different prefixes, you can stay with that naming standard. The important thing is to have a consistent standard and to apply it from the very start of the development cycle.
The following are the general guidelines about naming:
- Consistent naming conventions across design module.
- Name should identify an item or its purpose.
- Use of prefix to group the like items.
- Use of cascading names to provide a hierarchy representation to group elements (that is, use “\” backslash).
- User interface elements should be descriptive and accelerator key character should be identified.
- Long names should be avoided.
- Special characters usage to be avoided, for example, “$”, “#”, and “@”.
- Special keywords should be avoided.
Parent topic: 4.0 Coding techniques