In BPMN, should data objects appear at the source, destination or both? -
Pending: I sign a receipt for a pizza in Pizzeria and receive a copy of it. I take that receipt home and log in it strictly. Whether the data object represents the receipt, most properly appears at the point at which I sign (make an object) or at the point where I log in it with a smooth (ending with object) . Here's how it will work ...
In much more complex documents, is it appropriate to have a duplicate instance of receipt in each floating? What would be the most proper signaling?
Use the data object shown in your diagram correct .
Displaying the data object is optional in BPMN, it means you can decide to show important aspects, but not all the data involved is required to be displayed: just because you are not certain aspect It does not mean that it is not there, except that you can show just like the point of change (similarities / updates / delete) (point to the data object and A colleague showing) as well as the only point of the consumer (Reading) (a data object showing Pointing to a company).
In more complex diagrams, I recommend showing only the most important data aspects, because this is an important problem for overall readability. Unpublicized readers mixed the sequence flow and data associations, which in fact have a very different meaning. As a trend, I would recommend showing only one side of both mentioned (either creation / change or consumption) and they will imitate objects in favor of readability, but only if in many places They are really important for. In my mind, this is rarely the case.
Comments
Post a Comment