Editing Business process modeling (section)

=== Further structuring of business processes ===
[[File:VAC-production-company4.png|thumb|Example of the decomposition of a business process into sub-processes – supplemented by milestones, business units, data objects and IT-systems]]
The rough structure of the business processes created so far will now be decomposed – by breaking it down into sub-processes that have their own attributes but also contribute to achieving the goal of the business process. This decomposition should be significantly influenced by the ''application'' and ''strategy for the long-term success of business process modeling'' and should be continued as long as the tailoring of the sub-processes defined this way contributes to the implementation of the ''purpose'' and ''strategy''.

A sub-process created in this way uses a [[Scientific modelling|model]] to describe the way in which procedures are carried out in order to achieve the intended operating goals of the company. The model is an abstraction of reality (or a target state) and its concrete form depends on the intended use (application).

A further decomposition of the sub-processes can then take place during [[#Modeling business process|business process modeling]] if necessary. If the business process can be represented as a sequence of phases, separated by [[Milestone (project management)|milestones]], the decomposition into phases is common. Where possible, the transfer of milestones to the next level of decomposition contributes to general understanding.

The result of the further structuring of business processes is usually a hierarchy of sub-processes, represented in value chain diagrams. It is common that not all business processes have the same depth of decomposition. In particular, business processes that are not safety-relevant, cost-intensive or contribute to the operating goal are broken down to a much lesser depth. Similarly, as a preliminary stage of a decomposition of a process planned for (much) later, a common understanding can first be developed using simpler / less complex means than ''value chain diagrams'' – e.g. with a textual description or with a turtle diagram<ref name="FUEERMANN" /> <sup>(Chapter 3.1 Defining process details) ← automatic translation from German</sup> (not to be confused with [[Turtle graphics|turtle graphic]]!).