How to use the power of the Decision Requirements Graph when using preconditions in business proces modeling [editor]

There is a trend among business process modeling, where modeling with preconditions is taking precedence over modeling flow.
When the business requirements grow, classic BPM flowcharts become less and less readable, until they finally burst with complexity.
Maintenance on such complex flowcharts will become difficult and eventually maybe even impossible.

Using independent ad hoc tasks that have preconditions that state when such a task may be executed and when it must be executed,
will result in far better readable and maintainable business models, a quicker time to market and happier customers.

Using ad hoc tasks and preconditions requires a shift in business process modeling. In stead of thinking about a task and possible
next tasks, the business process modeler needs to figure out when a task is applicable and necessary.