Page History

...

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 understandable maintainable and maintainable flexible business models, a quicker time to market and happier customers with regards to maintenance.

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

...

The first downside has to do with the fact that preconditions might become complex and therefore not understandable. This is arguably true, since complexity of the business will not magically disappear when using preconditions in stead instead of flow. However, the complexity of preconditions is maintainable even at a very large scale, the complexity of flow will - at one point or another - grow beyond repair. Flows become more complex when the scale increases, with more arrows, duplicated activities and decisions used for the sake of control. When using tasks with preconditions, the number of tasks grows with an increasing scale, not the complexity of the tasks.

...