These modeling conventions go beyond meresyntax rules: A syntactically correct process model might still be hard to read due to layout issues. It may even be impossible to understand due to ambiguous semantics.
The Signavio Process Editor defines two sets of modeling conventions by default:
To ensure conventions are used effectively, they should be clearly defined and a compliance check should be automatically executed.
You can check your model adheres to these guidelines via the toolbar of the Process Editor. Signavio analyzes theof the process model automatically and displays errors, warnings and/or hints if applicable:
Diagrams are automatically checked against the ‘Signavio Best Practices’ when saving.
To illustrate the benefits of modeling conventions, let’s take a look at some of the layout rules:
Hint: The corrected diagram could look like this:
The rule usage of a restricted diagram size ensures modelers stick to a manageable diagram. Diagrams exceeding the size limit should be refactored using sub-processes or process links.
The Signavio Ultimate Edition allows you to
When creating a custom modeling convention, we recommend that you copy one of the default subsets (Signavio Best Practices or Method & Style) and adapt it according to your needs.
An example of a rule you may like to modify is the Definition of required mandatory attributes, as it will vary depending on your specific BPM scenario. Before defining this ruleset, it makes sense to configure your custom attributes and to then adjust the attribute configuration of your Collaboration Portal.
Examples of other rules you might want to configure are Usage of a definedsubset and Definition of required dictionary links.
For further information on modeling best practices and conventions, we recommend you to read Bruce Silver’s BPMN Method & Style and to visit our.