Semantic Annotation for Process Models: - Department of Computer ...
Semantic Annotation for Process Models: - Department of Computer ... Semantic Annotation for Process Models: - Department of Computer ...
174 APPENDIX A. BPMN Figure A.1: BPMN Events A.2.2 Activities An Activity is a generic term for work that company performs. An activity can be atomic or non-atomic (compound). The types of activities that a part of a Process Model are: Process, Sub-Process, and Task. Tasks and Sub-Processes are either unbounded or a contained within a Pool. In Metis, notations of Tasks and Sub-Processes look same – round rectangles. Besides for those Activities, Input and Output can be attached. The notations of Activities are listed in Figure A.2. Figure A.2: BPMN Activities – Sub-Process, Task A.2.3 Gateways A Gateway is used to control the divergence and convergence of multiple Sequence Flow. Thus, it will determine branching, forking, merging, and joining of paths. Gateways are represented with diamonds and they can be specified with Gateway Control Types which are icons within the diamond shape (Figure A.3). A.3 Connecting Objects A.3.1 Sequence flow A Sequence Flow is used to show the order that activities will be performed in a Process. A Sequence Flow can be further elaborated as Normal Flow and Exception Flow. A Normal Sequence Flow is usually notated by a line with an arrow connecting activities or gateways. Exception Flow occurs outside the Normal Flow of the Process and is based upon an Intermediate Event that occurs during the performance of the Process. Figure A.4 provides the graphical notation of a Normal Sequence Flow and an Exception Flow.
A.3. CONNECTING OBJECTS 175 Figure A.3: BPMN Gateways Figure A.4: BPMN Sequence Flows A.3.2 Message flow A Message Flow is used to show the flow of messages between two participants that are prepared to send and receive them. In BPMN, two separate Pools in the Diagram will represent the two participants (e.g., business entities or business roles). The notation for a Message Flow is illustrated in Figure A.5. Figure A.5: BPMN Message Flow A.3.3 Association An Association is used to associate information with Flow Objects. Text and graphical non-Flow Objects can be associated with the Flow Objects. A dash line with an arrow is used to associate between Data Objects and Activities. A dash line without arrows is to link between Data Objects to a Sequence Flow or a Message Flow (Figure A.6).
- Page 144 and 145: 124 CHAPTER 7. EXEMPLAR STUDIES AND
- Page 146 and 147: 126 CHAPTER 7. EXEMPLAR STUDIES AND
- Page 149 and 150: Chapter 8 Quality Evaluation of the
- Page 151 and 152: 8.2. SETTING FOR THE QUALITY EVALUA
- Page 153 and 154: 8.2. SETTING FOR THE QUALITY EVALUA
- Page 155 and 156: 8.3. QUALITY ANALYSIS 135 to those
- Page 157 and 158: 8.3. QUALITY ANALYSIS 137 annotatio
- Page 159 and 160: 8.3. QUALITY ANALYSIS 139 • G1 -
- Page 161 and 162: 8.5. SUMMARY 141 3. Semantic annota
- Page 163 and 164: Chapter 9 Validation of Applicabili
- Page 165 and 166: 9.1. VALIDATION DESIGN 145 - RE3.3
- Page 167 and 168: 9.2. SWRL FORMULATION 147 Table 9.1
- Page 169 and 170: 9.2. SWRL FORMULATION 149 RE3.2 RE3
- Page 171 and 172: 9.3. APPLICABILITY VALIDATION IN AN
- Page 173 and 174: 9.3. APPLICABILITY VALIDATION IN AN
- Page 175 and 176: 9.3. APPLICABILITY VALIDATION IN AN
- Page 177 and 178: 9.3. APPLICABILITY VALIDATION IN AN
- Page 179 and 180: 9.4. DISCUSSION ON RESULTS OF THE V
- Page 181 and 182: 9.4. DISCUSSION ON RESULTS OF THE V
- Page 183: Part IV Synopsis 163
- Page 186 and 187: 166 CHAPTER 10. CONCLUSIONS AND FUT
- Page 188 and 189: 168 CHAPTER 10. CONCLUSIONS AND FUT
- Page 190 and 191: 170 CHAPTER 10. CONCLUSIONS AND FUT
- Page 193: Appendix A BPMN This chapter presen
- Page 197 and 198: A.6. BPMN META-MODEL TREE IN METIS
- Page 199 and 200: Appendix B EEML 2005 The language v
- Page 201 and 202: B.2. RECOURSES MODELING DOMAIN 181
- Page 203 and 204: Appendix C SCOR SCOR — Supply Cha
- Page 205 and 206: C.2. LEVEL 2 TOOLKIT 185 Level 1 Me
- Page 207 and 208: C.3. LEVEL 3 PROCESS ELEMENTS 187 F
- Page 209 and 210: Appendix D Algorithm for Semi-Autom
- Page 211 and 212: 191 Algorithm 1 Goal Annotation Alg
- Page 213 and 214: Algorithm 4 Goal Annotation Algorit
- Page 215 and 216: 195 Algorithm 6 Goal Annotation Alg
- Page 217 and 218: Appendix E GUI of Pro-SEAT The prop
- Page 219 and 220: 199 Figure E.3: Mapping meta-model
- Page 221 and 222: 201 Figure E.5: Goal annotation UI
- Page 223 and 224: Appendix F Analysis of the Annotati
- Page 225 and 226: F.2. INTEGRATION APPLICATION BASED
- Page 227 and 228: F.2. INTEGRATION APPLICATION BASED
- Page 229 and 230: Appendix G Schema of PSAM and SWRL
- Page 231 and 232: G.1. PSAM IN OWL 211
- Page 233 and 234: G.2. RULE DEFINITIONS IN SWRL 213
- Page 235 and 236: G.2. RULE DEFINITIONS IN SWRL 215
- Page 237 and 238: Appendix H Annotation Results in Ex
- Page 239 and 240: H.2. ANNOTATION OF PM B1 219 xmlns:
- Page 241 and 242: H.3. ANNOTATION OF PM B2 221 Av
- Page 243 and 244: Bibliography [1] ALTOVA. What is th
174 APPENDIX A. BPMN<br />
Figure A.1: BPMN Events<br />
A.2.2<br />
Activities<br />
An Activity is a generic term <strong>for</strong> work that company per<strong>for</strong>ms. An activity can be<br />
atomic or non-atomic (compound). The types <strong>of</strong> activities that a part <strong>of</strong> a <strong>Process</strong><br />
Model are: <strong>Process</strong>, Sub-<strong>Process</strong>, and Task. Tasks and Sub-<strong>Process</strong>es are either unbounded<br />
or a contained within a Pool. In Metis, notations <strong>of</strong> Tasks and Sub-<strong>Process</strong>es<br />
look same – round rectangles. Besides <strong>for</strong> those Activities, Input and Output can be<br />
attached. The notations <strong>of</strong> Activities are listed in Figure A.2.<br />
Figure A.2: BPMN Activities – Sub-<strong>Process</strong>, Task<br />
A.2.3<br />
Gateways<br />
A Gateway is used to control the divergence and convergence <strong>of</strong> multiple Sequence Flow.<br />
Thus, it will determine branching, <strong>for</strong>king, merging, and joining <strong>of</strong> paths. Gateways<br />
are represented with diamonds and they can be specified with Gateway Control Types<br />
which are icons within the diamond shape (Figure A.3).<br />
A.3 Connecting Objects<br />
A.3.1<br />
Sequence flow<br />
A Sequence Flow is used to show the order that activities will be per<strong>for</strong>med in a<br />
<strong>Process</strong>. A Sequence Flow can be further elaborated as Normal Flow and Exception<br />
Flow. A Normal Sequence Flow is usually notated by a line with an arrow connecting<br />
activities or gateways. Exception Flow occurs outside the Normal Flow <strong>of</strong> the <strong>Process</strong><br />
and is based upon an Intermediate Event that occurs during the per<strong>for</strong>mance <strong>of</strong> the<br />
<strong>Process</strong>. Figure A.4 provides the graphical notation <strong>of</strong> a Normal Sequence Flow and<br />
an Exception Flow.
Change language