Connection rules are useful
to understand how Flow Object, Swimlane, and Artifact may be connected to each
other, and what condition is required to connect them together. As an example, message
flow cannot connect objects in the same Lane but only objects in two different
Lanes; similarly sequence flow cannot connect an object in two different Lanes but
only objects in the same Lane.
At this point we can observe that with four different types of objects (and relative
subtypes) and following simple connecting rules, business users are able to design
the process in all its complexity, but implementation details are needed.
BPMN defines another detail level: each BPMN elements has its own properties.
Suppose, for example, that the designer defines a start event of type ???message.??? In
the implementation phase IT experts need to know what message is required and
what technology is used to send/receive the message. Start event has among its
property the attribute message that allows us to supply the message to send/receive
and the attribute implementation to define the technology used to receive the message
(Web services or other technology).
Pages:
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210