In Axon.ivy we have the possibility to model different layers, starting from a business point of view and go down to the integration/technical view. We have different concepts how we can model a readable process that covers business needs, as well as technical needs. It's also possible to introduce N Layers, but in practice we usually use three layers to keep it simple. Let us illustrate this issue with a simple example.
Layer 1 - Business Layer
This layer is primary used to get in discussion with the business user and 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 an BPMN activity, e.g. a web form is used here or any decision is done, etc. For less complex process applications, this layer can also use technical stuff, like DB elements, web service elements, etc. In our example we illustrate the order activity, where the management do the ordering of requested goods, by prepare the ordering. If the execute order service is not working, the task for the management is regenerated again.
Layer 3 - Technical Layer/Integration Layer
In the last layer we usually use technical stuff, like system integrations, data mappings, calculations, execution of backend services. etc.