Anti Patterns

This is a complete list of the Anti-Patterns recognized by the Consistency Checker. Elements that are part of an Anti-Pattern are highlighted in orange color .

There are Anti-Patterns for the following categories:

All Diagram Types

These are the categories where Anti-Patterns are recognized:

Name Clashes

The naming of shapes should be unique.

Note: This does not apply to Petri Nets!

Block Diagram:

Name Clash Block Diagram

E/R Diagram:

Name Clash ER Diagram

Petri Net Specific

These are the categories where Anti-Patterns are recognized:

Case vs. Concurrency

A case or conflict is shown by a place with multiple outgoing or ingoing edges. To visually emphasize the conflict, these edges should touch in one same point of a place.

As opposed to that, concurrency is depicted by a transition with multiple outgoing(=fork) or ingoing(=join) edges to different places. The edges should touch the transition at different points to visually emphasize the concurrency.

Therefore the examples below represent possible errors because the visual hints for case(=conflict) and concurrency are interchanged. The examples actually show concurrency and not conflict.

Case Differentiation vs. Concurrency: Fork or Case Differentiation vs. Concurrency: Join

Capacity and Arc Weight

The arc weight of an edge should not be higher than the capacity of the place it is connected to because the connected transition becomes a dead one.

Capacity and Arc Weight