Editing Business process modeling (section)

=== Modelling techniques ===
There are various standards for notations; the most common are:
* Business Process Model and Notation (BPMN), proposed in 2002 by Stephen A. White, published by the Business Process Management Initiative – merged in June 2005 with [[Object Management Group]]
* [[Event-driven process chain]] (EPC), proposed in 1992 by a working group under the leadership of August-Wilhelm Scheer
* ''Value-added chain diagram'' ([[:de:Wertschöpfungskettendiagramm|VAD]]), for visualizing processes mainly at a high level of abstraction
* [[Petri net]], developed by [[Carl Adam Petri]] in 1962
* Follow-up plans (e.g. in the specific form of a [[Flowchart]]), proposed in 1997 by Fischermanns and Liebelt
* [[HIPO model]], developed by IBM around 1970 as a design aid and documentation technology for software (in a non-technical, but business-oriented form)
* [[Lifecycle Modeling Language]] (LML), originally designed by the LML steering committee and published in 2013
* [[Subject-oriented business process management]] (S-BPM)
* [[Cognition enhanced Natural language Information Analysis Method]] (CogNIAM)
* SIPOC diagram, invented in the 1980s as part of the [[Total Quality Management]] movement and then adopted by [[Lean Management]] and Six Sigma practitioners
* [[Unified Modelling Language]] (UML), proposed in 1996 by [[Grady Booch]], [[Ivar Jacobson]], and [[James Rumbaugh]], continuously revised under the aegis of the OMG (provides extensions for business process)
* ICAM DEFinition ([[IDEF0]]), developed for the US Air Force in the early 1980s
* [[Formalized Administrative Notation (FAN)]], created by Pablo Iacub and Leonardo Mayo in the 1990s
* [[Harbarian process modeling]] (HPM)
* [[BPEL|Business Process Execution Language]] (BPEL), an XML-based language developed in 2002 by [[Organization for the Advancement of Structured Information Standards|OASIS]] for the description and automation of business processes
* Turtle diagram (also turtle method, turtle model, 8W method), a simple, clear and easy-to-understand graphical representation of facts about the process

Furthermore:
* ''Communication structure analysis'', proposed in 1989 by Prof. [[:de:Hermann Krallmann|''Hermann Krallmann'']] at the Systems Analysis Department of the TU Berlin.
* ''Extended Business Modelling Language'' (xBML)<ref>Cedric G. Tyler and Stephen R. Baker: ''Business Genetics: Understanding 21st Century Corporations using xBML'', John Wiley & Sons Ltd, 2007, ISBN 978-0-470-06654-6</ref> (seems to be outdated, as the founding company is no longer online<ref>{{Cite web |url=http://www.xbmlinnovations.com/Home.aspx |title=Business Process Improvement |access-date=2024-02-19 |archive-date=2014-01-09 |archive-url=https://web.archive.org/web/20140109032735/http://www.xbmlinnovations.com/Home.aspx |url-status=bot: unknown}} accessed February 19, 2024.</ref>)
* Notation from ''OMEGA'' (object-oriented method for business process modeling and analysis, '''O'''bjektorientierte '''Me'''thode zur '''G'''eschäftsprozessmodellierung und -'''a'''nalyse in German), presented by Uta Fahrwinkel in 1995<ref>{{Webarchive |url=http://prof-mayr.de/bpe.html |text=Prof. Dr.-Ing. R. Mayr: ''OMEGA+ Beschreibungsmethode'' |wayback=20131022212248}}, auf prof-mayr.de, retrieved 5 February 2024; PDF "VL4030_OMEGA+-Beschreibungsmethode.pdf" nicht mehr verfügbar</ref>
* ''Semantic object model'' ([[:de:Semantisches Objektmodell|SOM]]), proposed in 1990 by ''Otto K. Ferstl and Elmar J. Sinz''
* [[:de:PICTURE-Methode|PICTURE-Methode]] for the documentation and modeling of business processes in public administration
* [[Data-flow diagram]], a way of representing a flow of data through a process or a system
* [[Swimlane]] technique, mainly known through [[BPMN]] but also SIPOC, the ''Process chain diagram'' ([[:de:Vorgangskettendiagramm|PCD]]) and other methods use this technique
* [[:de:ProMet|ProMet]], a method set for business engineering
* [[State diagram]], used to describe the behavior of systems

In addition, representation types from [[software architecture]] can also be used:
* [[Flowchart]], standardized in DIN 66001 from September 1966 and last revised in December 1983 or standardized in [[ISO 5807]] from 1985
* [[Nassi-Shneiderman diagram]] or structure diagram, proposed in 1972/73 by [[Isaac Nassi]] and [[Ben Shneiderman]], standardized in DIN 66261.

==== Business Process Model and Notation (BPMN) ====
{{Excerpt|Business Process Model and Notation}}

==== Event-driven process chain (EPC) ====
{{Excerpt|Event-driven process chain}}

==== Petri net ====
{{Excerpt|Petri net}}

==== Flowchart ====
{{Excerpt|Flowchart}}

==== Hierarchical input process output model (HIPO) ====
{{Excerpt|HIPO model}}

==== Lifecycle Modeling Language (LML) ====
{{Excerpt|Lifecycle Modeling Language}}

==== Subject-oriented business process management ====
{{Excerpt|Subject-oriented business process management}}

==== Cognition enhanced Natural language Information Analysis Method ====
{{Excerpt|Cognition enhanced Natural language Information Analysis Method}}

==== SIPOC (suppliers, inputs, process, outputs and customers) ====
{{Excerpt|SIPOC}}

==== Unified Modelling Language (UML) ====
{{Excerpt|Unified Modelling Language}}

==== Integration Definition (IDEF) ====
{{Excerpt|IDEF}}

==== Formalized Administrative Notation (FAN) ====
{{Excerpt|Formalized Administrative Notation}}

==== Harbarian process modeling (HPM) ====
{{Excerpt|Harbarian process modeling}}

==== Business Process Execution Language (BPEL) ====
{{Excerpt|Business Process Execution Language}}