Page History

...

In this phase, there is one mandatory () task, RequestProduct. A precondition will determine whether the task may be performed or not, but the phase Apply will not never end unless the task is performed.

Preconditions

All other tasks can be performed in the a phase as well, but the order in which they may or must be performed is not set in stone, neither is the applicability of these tasks. Preconditions tell us when the tasks may be performed and (as mentioned here) a . A Decision Requirements Graph will tell what can be used to vusualize the precondition is, as shown below for the task RequestRegistration.

...

Of course there are some concerns regarding this approach. The main concern regards insight. In a previous article (How to use Decision Requirements Graphs to visualize ad-hoc tasks in business process modeling), we discussed how Decision Requirements Graphs help visualize ad-hoc tasks. This article was written as a response to often heard comments on ad-hoc task modeling regarding insight and overview when modeling business processes with ad-hoc tasks rather than (work)flow oriented tasks. Using the strategy described in this article, combined with the design as outlined here, will result in dynamic processes which are not only really flexible, but also maintainable.