Actions

Difference between revisions of "Resource"

From EPC Standard

 
Line 16: Line 16:
 
== Semantic ==
 
== Semantic ==
 
In EPC there is no common understanding which resources can be annotated to [[Function|functions]]. Examples are [[Organizational unit|organizational units]], application systems or documents, where each resource has a specific [[Resource relation|resource relation]] to a [[Function|function]]. An [[Organizational unit|organizational unit]] for example can have the relation type “is responsible for”, which it not allowed for an [[Data object|data object]] like document. [1]
 
In EPC there is no common understanding which resources can be annotated to [[Function|functions]]. Examples are [[Organizational unit|organizational units]], application systems or documents, where each resource has a specific [[Resource relation|resource relation]] to a [[Function|function]]. An [[Organizational unit|organizational unit]] for example can have the relation type “is responsible for”, which it not allowed for an [[Data object|data object]] like document. [1]
 
== XML Representation ==
 
  
 
== References ==
 
== References ==

Latest revision as of 09:20, 11 September 2018


Resource
Graphical Notation
Resource
IsSubClassOf
Successors
Predecessors
HasIncomingControlFlow 0
HasOutgoingControlFlow 0
HasResource 0
HasAttribute 0
Edit the Properties


Brief Information

This is an autogenerated section!

You are not able to edit this information by hand, but by edit the Form (and therefore the properties) of this page. Please refer to the Edit the properties link at the bottom of the info box.
   The cardinalities are 0 (incoming) and 0 (outgoing) respectively .  


Short description

A resource is part of the EPC meta model. Resources are used to provide additional information for EPC functions and thereby the process model. Resources may be represented by organizational units, data objects or information systems. They are attached to functions and represent further necessary details, like which organizational unit is responsible for the execution of the associated task, which information systems are involved, what input is needed to perform it and what output is generated by it.

Syntax

There is no common understanding which resources can be annotated to functions. [1] A consensus in the literature seems to be the classification in organizational unit, data object and information object. [1], [2], [3], [4] There can be any number of resources associated to process elements. All possible relationship types between resources and process elements are represented by the class resource relation. [1], [2], [5]

Semantic

In EPC there is no common understanding which resources can be annotated to functions. Examples are organizational units, application systems or documents, where each resource has a specific resource relation to a function. An organizational unit for example can have the relation type “is responsible for”, which it not allowed for an data object like document. [1]

References


  • [1] ^ 1 2 3 4 C. Seel and D. Vanderhaeghen, “Meta-Model based Extensions of the EPC for Interorganisational Process Modelling,” EPK 2005. 4. Work. der Gesellschaft für Inform. e.V. und Treffen ihres Arbeitkreises "Geschäftsprozessmanagement mit Ereignisgesteuerten Prozessketten, pp. 117–136, 2005.
  • [2] ^ 1 2 B. Korherr and B. List, “A UML 2 Profile for Event Driven Process Chains *,” vol. 205, pp. 161–172, 2006.
  • [3] ^ R. S. Mans, “Generic and specific eEPCs for product and customer groups,” no. February, 2006.
  • [4] ^ G. Decker and W. Tscheschner, “Migration von EPK zu BPMN,” EPK 2009. 8. Work. der Gesellschaft für Inform. e.V. und Treffen ihres Arbeitkreises "Geschäftsprozessmanagement mit Ereignisgesteuerten Prozessketten (WI-EPK). Gesellschaft für Inform., pp. 91–109, 2009.
  • [5] ^ O. Thomas, Fuzzy Process Engineering. 2009.