21.01.2014 Views

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

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

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

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

B.2. RECOURSES MODELING DOMAIN 181<br />

role types as such do not imply anything in terms <strong>of</strong> being active or passive. A role can<br />

be filled by any type <strong>of</strong> Resource. The default icon <strong>for</strong> Role is a circle (Figure B.4).<br />

Figure B.4: EEML Resource role<br />

B.2 Recourses Modeling Domain<br />

Resources are things that play specific roles during the process execution or in the<br />

organization in general. The resource roles may vary greatly, - some resources are<br />

typically viewed as enablers, whereas others comprise the result (or part there<strong>of</strong>) <strong>of</strong> the<br />

process.<br />

EEML distinguishes between 6 types <strong>of</strong> resources, namely Person, Organization,<br />

S<strong>of</strong>tware Tool, Manual Tool, Material Object, and In<strong>for</strong>mation Object.<br />

The typical way <strong>of</strong> connecting resources to processes is to assign them to resource<br />

roles included in the process, or attaching them to flows between tasks e.g. document<br />

flow.<br />

The notations <strong>of</strong> those resources are illustrated in Figure B.5.<br />

Figure B.5: EEML Resources<br />

B.3 EEML modeling relationships<br />

Besides the above object types, EEML defines a set <strong>of</strong> relationships to link those object<br />

types. The relationships are: flows into (between two Decision Points), has part<br />

(between a Task and its components, or between a Resource and its component Resources),<br />

has input port (between a Task and its Input Port), has output port (between<br />

a Task and its Output Port), has resource role (between a Task and its components <strong>of</strong><br />

type Role), collaborates with (collaborations between two Tasks), is filled by (between<br />

Roles and its assignment <strong>of</strong> Resources), is candidate <strong>for</strong> (the possible filling <strong>of</strong> a Role

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!