Method & Style Validation
111701
|
Message
|
Action
|
|
A Timer Start Event should be labeled to indicate the process schedule. |
Label the Timer Start Event. |
|
Wrong: |
Right: |
|
 |
 |
111702
|
Message
|
Action
|
|
A Signal start event should be labeled to indicate the Signal name. |
Label Signal start event. |
|
Wrong: |
Right: |
|
 |
 |
111703
|
Message
|
Action
|
|
A Conditional start event should be labeled to indicate the condition. |
Label Conditional start event. |
|
Wrong: |
Right: |
|
 |
 |
111704
|
Message
|
Action
|
|
A Message start event should be labeled “Receive {message name}”. The trigger has to be specified (message or multiple). |
Label start event(s) and specify trigger. |
|
Wrong: |
Right: |
|
 |
 |
113701
|
Message
|
Action
|
|
A Boundary event should be labeled. |
Label Boundary event. |
|
Wrong: |
Right: |
|
 |
 |
113702
|
Message
|
Action
|
|
A Throwing Intermediate event should be labeled. |
Label Throwing Intermediate event. |
|
Wrong: |
Right: |
|
 |
 |
113703
|
Message
|
Action
|
|
A Catching Intermediate event should be labeled. |
Label Catching Intermediate event. |
|
Wrong: |
Right: |
|
 |
 |
120701
|
Message
|
Action
|
|
Activities should be labeled. |
Label the Activity. |
|
Wrong: |
Right: |
|
 |
 |
123601
|
Message
|
Action
|
|
A Call Activity SHOULD call a Global Element. |
Label the Activity. |
|
Wrong: |
Right: |
|
IMAGE |
IMAGE |
161701
|
Message
|
Action
|
|
A conditional Sequence Flow should be labeled. |
Label conditional Sequence Flow. |
|
Wrong: |
Right: |
|
IMAGE |
IMAGE |
161702
|
Message
|
Action
|
|
An unconditional Sequence Flow should not be labeled. |
Do not label unconditional Sequence Flow. |
|
Wrong: |
Right: |
|
IMAGE |
IMAGE |
162701
|
Message
|
Action
|
|
A message flow should be labeled with the name of the message. |
Label message flow. |
|
Wrong: |
Right: |
|
 |
 |
190701
|
Message
|
Action
|
|
A Message should be labeled. |
Label the Message. |
|
Wrong: |
Right: |
|
 |
 |
211701
|
Message
|
Action
|
|
A Message Start Event should have an incoming Message Flow. |
Add an incoming Message Flow. |
|
Wrong: |
Right: |
|
 |
 |
213701
|
Message
|
Action
|
|
A Catching message event should have an incoming Message flow. |
Add incoming Message flow. |
|
Wrong: |
Right: |
|
 |
 |
213702
|
Message
|
Action
|
|
A Throwing Message event should have an outgoing Message flow. |
Add outgoing Message flow. |
|
Wrong: |
Right: |
|
 |
 |
222701
|
Message
|
Action
|
|
A Send Task should have an outgoing Message Flow. |
Add an outoing Message Flow. |
|
Wrong: |
Right: |
|
 |
 |
222702
|
Message
|
Action
|
|
A Receive task should have an incoming message flow. |
Add an incoming Message Flow. |
|
Wrong: |
Right: |
|
 |
 |
230701
|
Message
|
Action
|
|
An Exclusive gateway should have at most one unlabeled gate. |
Label the gates. |
|
Wrong: |
Right: |
|
 |
 |
230702
|
Message
|
Action
|
|
An Exclusive or Inclusive gateway with an unlabeled gate should be labeled. |
Label the gates. |
|
Wrong: |
Right: |
|
 |
 |
231604
|
Message
|
Action
|
|
A Sequence Flow can only connect to an Activity, a Gateway or an Event. |
TEXT |
|
Wrong: |
Right: |
|
IMAGE |
IMAGE |
231701
|
Message
|
Action
|
|
TEXT Prüfen (engl. Übersetzung)
If an exclusive gateway is labeled with a question, there are exactly two gates, labeled with ‘yes’ and ‘no’.Falls ein exklusives Gateway mit einer Frage beschriftet ist, dann sollte es genau zwei (2) Gates haben, die mit ‘ja’ und ‘nein’ beschriftet sind. |
Label the gates with ‘yes’ and ‘no’. |
|
Wrong: |
Right: |
|
IMAGE |
IMAGE |
311701
|
Message
|
Action
|
|
A start event in a top-level process should be labeled. If a top-level process contains more than one start event, all should be labeled to identify the alternative start conditions. |
Label every single start event. |
|
Wrong: |
Right: |
|
 |
 |
312701
|
Message
|
Action
|
|
Two end events in a process level should not have the same name. |
If they mean the same end state, combine them; otherwise give them different names. |
|
Wrong: |
|
|
 |
|
Right: |
|
|
 OR: |
312702
|
Message
|
Action
|
|
If there is more than one End Event in a process level, all should be labeled with the name of the end state. |
Label all End Events. |
|
Wrong: |
Right: |
|
 |
 |
313701
|
Message
|
Action
|
|
An Error Boundary event on an sub-process should be labeled to match the throwing Error event. |
Label the Error Boundary event to match the throwing Error event. |
|
Wrong: |
|
|
 |
|
Right: |
|
|
 |
313702
|
Message
|
Action
|
|
An Escalation Boundary event on a sub-process should be labeled to match the throwing Escalation event. |
Label the Escalation Boundary event to match the throwing escalation event. |
|
Wrong: |
|
|
 |
|
Right: |
|
|
 |
320701
|
Message
|
Action
|
|
Two activities in the same process should not have the same name. |
Use global activity to reuse a single activity in a process. |
|
Wrong: |
|
|
 |
|
Right: |
|
|
 |
321701
|
Message
|
Action
|
|
The label of a child-level page should match the name of the subprocess. |
Rename the child-level page. |
|
Wrong: |
|
|
 |
|
Right: |
|
|
 |
321702
|
Message
|
Action
|
|
Only one start event should be used in a subprocess. |
Remove additional start events. |
|
Wrong: |
Right: |
|
 |
 |
321703
|
Message
|
Action
|
|
If a sub-process is followed by a yes/no gateway, at least one end event of the sub-process should be labeled to match the gateway label. |
Label one end event of the sub-process according to gateway label. |
|
Wrong: |
|
|
 |
|
Right: |
|
|
 |
321704
|
Message
|
Action
|
|
A child level diagram should not be enclosed in an expanded sub-process shape. |
|
|
Wrong: |
|
 |
|
Right: |
|
|
 |
321705
|
Message
|
Action
|
|
If a subprocess is followed by a gateway labeled as a question, it must have more than one end event. |
Add additional end events. |
|
Wrong: |
Right: |
|
 |
 |
321706
|
Message
|
Action
|
|
The child-level expansion should not be enclosed in a pool if the top-level process is not enclosed in a pool. |
Remove the enclosing pool on the child-level page. |
321707
|
Message
|
Detail
|
Action
|
|
The process pool on the child-level page should have the same name as the corresponding pool on the top-level page, i.e. they must be identical. |
If the ‘Auto-make identical pools’ is turned on in the options, pools with the same name will automatically be identified to be the same. Alternatively, use the ‘reuse’ function in the context menu. |
Use the ‘reuse’ function to make the two pools identical. |
321708
|
Message
|
Action
|
|
Structure error: All flow elements on a child-level page must belong to the parent-level subprocess. |
Remove any flow elements that do not belong to the subprocess. |
321709
|
Message
|
Action
|
|
Structure error: If a pool is used in the child-level, all flow elements on the child-level page must be drawn within the pool boundaries. |
Move all flow elements inside the pool boundary. |
362701
|
Message
|
Action
|
|
A Message flow from a collapsed sub-process should be replicated in the child level diagram. |
Replicate Message flow in the child level diagram. |
|
Parent level: |
|
|
 |
|
Child level: |
|
|
 |
362702
|
Message
|
Action
|
|
A Message flow to a collapsed sub-process should be replicated in the child level diagram. |
Replicate Message flow in the child level diagram. |
|
Wrong: |
|
|
 |
|
Right: |
|
|
 |
362703
|
Message
|
Action
|
|
An incoming message flow in child level diagram should be replicated in the parent level. |
Replicate the message flow in the parent level. |
|
Wrong: |
|
|
 |
|
Right: |
|
|
 |
362704
|
Message
|
Action
|
|
An outgoing message flow in child level diagram should be replicated in the parent level. |
Replicate the message flow in the parent level. |
|
Wrong: |
|
|
 |
|
Right: |
|
|
 |
