Изменения
Перейти к навигации
Перейти к поиску
Строка 10:
Строка 10: − + − + − + Строка 25:
Строка 25: − + − ** Branch/Merge : Branch and merge correspond to making decision of which path to choose among several control flows. A branch may have one incoming control flow and two or more outgoing control flows. When the condition is fulfilled, a branch activates exactly only one of the outgoing control flows and deactivates the others. The counterpart of a branch is a merge. A merge may have two or more incoming flows and one outgoing control flow. A merge synchronizes an activated and the deactivated alternatives. The control will then be passed to the next element after the merge. A branch in the EPC is represented by an opening XOR, whereas a merge is represented as a closing XOR connectors. − <!-- Actually, the branch diagram at the right must show a second operand inputting to the XOR block as XOR is a binary operation. Perhaps it may help to think an operand named «condition» entering the XOR block. Or should it be an XOR block at all? --> − ** Fork/Join : Fork and join correspond to activating all paths in the control flow concurrently. A fork may have one incoming control flow and two or more outgoing control flows. When the condition is fulfilled, a fork activates all of the outgoing control flows in parallel. A join may have two or more incoming control flows and one outgoing control flow. A join synchronizes all activated incoming control flows. In the EPC diagram how the concurrency achieved is not a matter. In reality the concurrency can be achieved by true parallelism or by virtual concurrency achieved by interleaving. A fork in the EPC is represented by an opening 'AND', whereas a join is represented as a closing 'AND' connectors. − ** OR : An 'OR' relationship corresponds to activating one or more paths among control flows. An opening 'OR' connector may have one incoming control flow and two or more outgoing control flows. When the condition is fulfilled, an opening 'OR' connector activates one or more control flows and deactivates the rest of them. The counterpart of this is the closing 'OR' connector. When at least one of the incoming control flows is activated, the closing 'OR' connector will pass the control to the next element after it.
→Элементы событийных цепочек процессов
[[Файл:Elements of an Event-driven Process Chain.svg|350px|right]]
[[Файл:Elements of an Event-driven Process Chain.svg|350px|right]]
; Событие : События являются пассивными элементами в EPC. Событием является состояние, которое встречается перед или после функции. Примеры событий: «требование зафиксировано», «материал на складе», и т. д. В EPC график событий представлена в виде шестиугольника. EPC диаграммы должны как начаться с события, так и заканчиваются событием.
; Событие : События являются пассивными элементами в EPC. Событием является состояние, которое встречается перед или после функции, т.е. фиксирует состояние определенных параметров на определенный момент времени. Примеры событий: «договор подписан», «требование зафиксировано», «материал на складе», и т. д. В EPC график событий представлена в виде шестиугольника. EPC диаграммы должны как начаться с события, так и заканчиваются событием.
; Функция : Функции являются активными элементами в EPC. They model the tasks or activities within the company. Functions describe transformations from an initial state to a resulting state. In case different resulting states can occur, the selection of the respective resulting state can be modeled explicitly as a decision function using logical connectors. Functions can be refined into another EPC. In this case it is called hierarchical function. Examples of functions are «capture requirement», «check material on stock», etc. In the EPC graph a function is represented as rounded rectangle.
; Функция : Функции являются активными элементами в EPC. Работа – определенное действие, выполняемое в течение некоторого промежутка времени. Каждая работа может быть декомпозирована.
; Организационная единица : Organization units determine which person or organization within the structure of an enterprise is responsible for a specific function. Examples are «sales department», «sales manager», «procurement manager», etc. It is represented as an ellipse with a vertical line.
; Организационная единица : Должность в организации (например, старший мастер) или подразделение организации (например, отдел закупок).
; Информация, материал, или объект ресурса : In the EPC, the information, material, or resource objects portray objects in the real world, for example business objects, entities, etc., which can be input data serving as the basis for a function, or output data produced by a function. Examples are «material», «order», etc. In the EPC graph such an object is represented as rectangle.
; Информация, материал, или объект ресурса : In the EPC, the information, material, or resource objects portray objects in the real world, for example business objects, entities, etc., which can be input data serving as the basis for a function, or output data produced by a function. Examples are «material», «order», etc. In the EPC graph such an object is represented as rectangle.
|}
|}
;Логические взаимосвязи
;Логические взаимосвязи
* Есть три типа логических взаимосвязей, определенных в EPC:
* Есть три типа логических взаимосвязей, определенных в EPC: And, Or, Xor.
; Поток управления : A control flow connects events with functions, process paths, or logical connectors creating chronological sequence and logical interdependencies between them. A control flow is represented as a dashed arrow.
; Поток управления : A control flow connects events with functions, process paths, or logical connectors creating chronological sequence and logical interdependencies between them. A control flow is represented as a dashed arrow.