In Axon Ivy, we have the possibility to model in different layers, starting from a business point of view and go down to the integration/technical view. We have different concepts on how we can model a readable process that covers business needs as well as technical needs. It's possible to introduce N Layers; in practice, we use three layers to keep it simple. Let us illustrate this with a simple example.
Layer 1 - Business Layer
This layer is primarily used to get the discussion with the business users going. The goal of this layer is to get a basic understanding of the process flow. Any technical issues are not important here. In this layer, we only work with the BPMN Activity Elements from Axon Ivy.
Layer 2- Business Detail Layer or Technical Layer (in case of easy processes)
This layer provides more details about a BPMN activity, e.g. a webform is used here or decisions are taken, etc. For less complex process applications, this layer can also include technical stuff, like DB elements, web service elements, etc. In our example, we illustrate the order activity, where the management does the ordering of requested goods by preparing the order. If the execute order service is not working, the task for management is regenerated again.
Layer 3 - Technical Layer/Integration Layer
In the last layer, we include technical implementation details, like system integrations, data mappings, calculations, execution of backend services. etc.