Business architects, enterprise architects, and business departments often model business processes without considering the architectural layers they are positioned in. Many modeling tools further support this approach. For example, it is possible to use Event Process Chains (EPC), the very prominent modeling language right below value chains, down to use cases, and here, detailing out toward last-minute details of user interactions. When we attempt to automate processes, there is an important architectural barrier depicted earlier as page flows. Other feasible terms are UI flows, sequence of forms, steps in user stories, or use cases.

The demarcation line can be drawn at the notion of human tasks entered in process models. When a user logs in to a role that is recognized by the process engine since it is configured as a lane in the model, the automatic process enters a task for the user or his role. This task is presented as an item...