#BPMN #DCR Process Methodology

DCR Process Methodology

A major benefit of DCR Processes is the way processes are discovered and defined.

In traditional flow based methods using process notations such as BPMN, you have to identify exactly where the process start and end as well as all the steps and paths in order to complete the process. Collecting such knowledge takes a long time and you cannot digitalize your process before the flow has been defined from start to end.

DCR Processes are faster to work with as you can digitalize the process incrementally, based on just a few pieces of the process known. Once digitalized you can learn from experience what people do and refine the process based on actual experience. The D in DCR Process stands for dynamic, which mean that during the digitalized process the user can even add new activities and rules meeting the need in the actual instance of the process.

When dealing with processes start focusing on who is involved, the roles, and the work they do, the activities. You might be surprised that even in a large group of people there will be little discussion about this. Of course naming convention will be challenged and some activities might be broken down to more details by some, why others refer to it as a group.

Secondly, ask people, individually, to create example flows of how the process could be executed. You as well as the participants will most likely be surprised that there is a huge diversity in how processes are in fact executed. Instead of looking for the classical process standardization and streamlining trying to find the happy path, simply accept the diversity and proceed.

As a final step ask for the rules that governs the process.

If some activity, A, always occur before another activity, B, ask if there is a rule that states that before B can be done, A must have been done. This is a condition type of rule. As an example, you cannot pay the invoice, before the approval has been completed.

If some activity, C, always occur after another activity, D, ask if there is a rule that states that whenever C is done, then D must be done later. This is a response type of rule. As an example, whenever a payment is approved, the payment must be completed.

You might even use DCR Process Discovery to find the rules from the flows.

The flows represent a valuable ressource for many reasons. Flows can be classified as Required or Forbidden, and using DCR compliance engine you can verify that flows are still working as expected when changing the model. Also, the users that created the flows will probably learn that their flows might not always be optimal and might even in some situations be invalid. Given the rules they now know why the flow is invalid.

Download the DCR Cheatsheet (in Danish) for details.

Related Release notes

Release 6.9

  • Welcome to generative AI in wizard
  • Welcome to improved Activity Effects
  • Import DCR graphs from BPMN and Excel

Related Videos

Related Articles

Transforming Dynamic Condition Response Graphs to Safe Petri Nets