
They are known to be functions and events. The so called “logical relationships” between elements in the control flow in the event-driven process chain are known to be described by the “logical connectors”. The material, resource objects and information in the event-driven process chain portray objects in the real world, such as business entities, objects and other, inputting data serving it as the basis for a function or outputting it produced by a function. “Organization units” are meant to be determining which exactly organization within one particular structure of some enterprise is the one responsible for some specific function, represented in a way of an ellipse with a single vertical line. The process owner is known to be responsible for a function, being a part of some organization unit usually represented in a way of a square with a single vertical line.

At the same time, “functions are known to be the “active” elements in an event-driven process chain, being used for modelling the activities or tasks within one company, describing the transformations simply from an initial state to a resulting one. They also can be used for clarifying which of them a process results in or for stating a function. They are used for describing under what circumstances a function (or a process) works. They can be events, which are simply are passive elements in the described before “event-driven process chains”.

There are a few elements which are used in the usual “event-driven process chain diagram”. Thus, in this case they are known to be called as “UML activity diagrams”. At the same time, the non-trivial structures involve parallelism having the so called “ill-defined execution semantics”. There are no restrictions appearing for existing on the possible structure of EPCs. The mentioned “event-driven process chain method” was the one developed within the framework of “Architecture of Integrated Information Systems” (or simply “ARIS”), as it was mentioned before, and the statement that event-driven process chains are ordered graphs was also one of those found in other so called “directed graphs”. Nowadays different businesses use the made event-driven process chain diagrams for laying out their business process workflows, used by many companies for many different business processes, such as analyzing, redesigning the business processes themselves as well as for modelling. The method of the “event-driven process chain” was developed by August-Wilhelm Scheer in 1990s within the framework of so called “Architecture of Integrated Information Systems”. It is a process chain used in a “workflow management” and in other fields of the business activity.

They can be very useful in the process of the business process improvement as well as for controlling the work share with instances of the autonomous workflows. They can be also used in order to configure a so called “enterprise resource planning” implementation. The Best Tool for Business Process Modeling Event Driven Process Chain (EPC)Īn event-driven process chain is well known as well as a commonly used type of flowchart, especially within the business process modelling science.
