Semantic Annotation for Process Models: - Department of Computer ...

180 APPENDIX B. EEML 2005
B.1.2
Decision Point
A decision point models a (normally manual) decision performed as part of the overall
process. The behavior of the decision point is largely defined by Logical Relation specified
in a decision point, which describes how to handle multiple flows in or out from
the decision point.
A default icon for the decision point is a diamond. And the logical relations can be
specified within a diamond. Figure B.2 presents three types of decision points – OR,
AND and XOR.
Figure B.2: EEML Decision Points
Figure B.3: EEML Milestone
B.1.3
Milestone
The Milestone concept is used to denote a decision point that is regarded to be of
specific importance in the process it is a part of.
Examples: When ready to issue a contract, When ready to start a project.
The behavior of Milestone is largely defined by the property Logical Relation, which
has similar semantics as described on decision-point above. The default icon for a
Milestone is in Figure B.3.
B.1.4
Resource role
The term "role" designates some part played by some resource. A role should always
be specified within a context. Typical examples of a role context are i) the organization
as a whole, ii) organizational units within an organization iii) a task within
the extended enterprise. Roles can be modeled in the context of Task, or externally,
meaning the given (implicit) organizational context of the model. In addition, roles
may be connected to flows, which is particularly relevant for the Roles of the objecttype.
Connecting object roles to flows is a convenient way to model document flow, for
instance.
Roles may be considered as placeholders for resources, and are introduced to make
it possible to talk about the use of resources without being concrete. In principal the