Naming Conventions

Giving names to entities in models and diagrams is one of the difficult things. Using a consistent naming scheme in your team or throughout the organization is even harder or maybe sometimes impossible.

In order to prevent duplicate items, sometimes with a slight difference or a mistake because of ambiguity, it is wise to create a naming convention.

Dragon1 promotes the following naming convention:

• If you want to name an entity class in your model or diagram, use one term: like Process or Service
• If you want to name an entity type, use a single dot prefix: Business.Process
• If you want to name an entity instance, use a double dot prefix: Amsterdam Sales.Business.Process
• If you give the process or processes a name agree on the number of parts of which it consists and how you use verbs, nouns and adjectives. Dragon1 promotes this setting: