Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - Jacob Vos

Pages: 1 2 3 [4]
Uml Process / Re: BPMN Common Processes
« on: May 02, 2014, 04:33:19 pm »
Hi Chris,

Did you finally solve your problem? Can you share your solution?

When I did an investigation, I noticed that following the BPMN specs is hard to do with Sparx EA. For example to use a shared task in a process of company A, BPMN says to have a Call Activity in that process that refers to that shared task. In Sparx EA: set the 'calledActivityRef' tag at the Call Activity to refer to the shared task. However, then in Sparx EA the layout of the Call Activity symbol doesn't change.

- Jacob

Uml Process / Re: Alternate End Events
« on: May 07, 2014, 05:25:24 pm »
Hi Chris,

Find my advice on how to model your situation in BPMN below, first some starting points (alas I cannot add a picture, that would have been easier):

1. There is a (global) process 'Transmit', called from the processes 'Add', 'Delete' and 'Update'.

2. The process 'Transmit' comprises the activities 'Generate', 'Send' and 'End'.

3. At the activities 'Generate' and 'Send' an exception can occur that aborts that activitiy concerned and by that also the 'Transmit' process.

4. At the processes 'Add', 'Delete' and 'Update', when the called 'Transmit' process is aborted, another path is followed than when that process was ended normally.

I modelled in Sparx EA in the following way the error throw-catch mechanism:

A. In the process 'Transmit', at the activity 'Generate' a boundary Error intermediate event with an outgoing sequence flow to a throwing error end event called 'Aborted - generate error'.

B. The same for the 'Send' activity, but named 'Aborted - send error'.

C. In the process 'Add' (and the same should be done for the processes 'Delete' and 'Update') I added two error intermediate boundary events to the call activity 'Transmit' (which calls the process 'Transmit'). One is named 'Aborted - generate error' and the other 'Aborted - send error'. Those are the catching events for the throwing events on the called process level.

D. Each of those catching events has an outgoing sequence flow, namely to an activity 'Act on Generate error' and 'Act on Send error' respectively.

Hope this helps.

- Jacob

Uml Process / Re: Activity Parameters
« on: May 02, 2014, 04:59:18 pm »
Hi Chris,

I try to understand what you want to model in order to help you. However the first two sentences of your first post raised questions:

1. BPMN has the concept of a Call Activity which can call a Global Task or a (global) Process. In Sparx EA you can set at an activity the BPMN tag 'isACalledActivity' to 'true', by which you define it as a Global Task. What do you mean with 'Callable Activity'? I would say: a Global Task, because a reusable process isn't an activity.

2. You say you create an activity as a Callable Activity "with a Composite Diagram". Do you mean that you have defined a 'Call Activity' that calls a global Process?

3. Parameters: BPMN has boundary events. Those are different from end events. End events may not be displayed on a boundary.

- Jacob

Pages: 1 2 3 [4]