Naming Conventions
It makes sense to apply the same naming conventions and organization of the Implementation folder to all your Designer projects. This makes reading a model much easier.
Naming Conventions
Agree on one language for names and documentation. This can be your native language or English for international projects.
Suggestion for a naming convention:
Convention | Example | ||
|---|---|---|---|
General | upper or lower camel case |
| |
for signal, exception, send signal action, scheduler, event observer, ports, RFC ports: |
| ||
Classes | upper camel case |
| |
Attributes | lower camel case |
| |
Operations | lower camel case |
| |
Services | Don't use service in the name, except for base services. |
| |
Use a project specific pattern. |
| ||
Aliases | upper camel case |
| |
Model Names | upper camel case |
| |
Libraries | Lib suffix |
| |