Editing Business process modeling (section)

==== Functions (''Tasks'') ====
[[File:Actions-of-an-elementary-process.png|thumb|Tasks of an elementary process, task sequence determined by three different approaches]]
;Delimitation

The term ''functions'' is often used synonymously for a delimited ''corporate function''/action (activita) area, which is assigned to a ''corporate function owner'', and the atomic [[Task (project management)|activity (task)]] at the level of the ''elementary processes''. In order to avoid the double meaning of the term ''function'', the term ''task'' can be used for the atomic activities at the level of the ''elementary processes'' in accordance with the naming in BPMN. Modern tools also offer the automatic conversion of a ''task'' into a ''process'', so that it is possible to create a further level of process decomposition at any time, in which a ''task'' must then be upgraded to an ''elementary process''.

;Utilization

The graphical elements used at the level of elementary processes then describe the (temporal-logical) sequence with the help of functions (''tasks''). The sequence of the functions (''tasks'') within the ''elementary processes'' is determined by their logical linking with each other (by [[Logical connective|logical operators]] or [[Business Process Model and Notation#Gateway|Gateways]]), provided it is not already specified by input/output relationships or Milestones. It is common to use additional graphical elements to illustrate interfaces, states (events), conditions (rules), milestones, etc. in order to better clarify the process. Depending on the modeling tool used, very different graphical representation ([[model]]s) are used.

[[File:FAD-with-input-output-resources-and-regulations.png|thumb|Sample of a '''F'''unction '''A'''llocation '''D'''iagram (FAD) for outsourcing master data to a separate view in order to keep the readability of the process model]]
Furthermore, the functions (''tasks'') can be supplemented with graphical elements to describe inputs, outputs, systems, roles, etc. with the aim of improving the accuracy of the description and/or increasing the number of details. However, these additions quickly make the ''model'' confusing. To resolve the contradiction between accuracy of description and clarity, there are two main solutions: Outsourcing the additional graphical elements for describing inputs, outputs, systems, roles, etc. to a [[Function Allocation Diagram]] (FAD) or selectively showing/hiding these elements depending on the question/application.

The ''function allocation diagram'' shown in the image illustrates the addition of graphical elements for the description of inputs, outputs, systems, roles, etc. to functions (''tasks'') very well.