The key question - is a thing that executes 100000 times per hour a business process? It’s a matter of definition of course, one may get very different answers from a system integrator and a business analyst. The latter would probably say that business is essentially a human thing. Therefore there are good reasons to treat straight-through processes and long-lasting business processes differently and to use different tools tools in particular just like you said.

As for the article, it was just a fun and pure theoretical challenge, not a solution for realmtask indeed.

Of course it’s no more than excercise that leaves plenty of room for improvements/variants/refinements.

Totally agree with your last point.

Kind regards
Anatoly

Like the approach, but if I was the cruiser’s commander I would like guidance and control algorithms working when the shot misses the target providing feedback target tracking pool.

This kind of process presentation, and this particular one, provides very clear idea how a process is structured. It was considered that there is few human interaction. But but if there were more, would be possible to draw real time collaboration on a crisis situation? I remembered some utilities processes when there is a supply disruption started by system alarm, or by epidemic phone calls from the customer and these ones are quite difficult to do because there are only a sequence of big steps it can be mapped.

Nowadays I see BPMN more suited to present the big picture rather that going deeply to the tasks detail.

Yes, some exception handling is missing.

Concerning “target lifecycle” - I considered it at the beginning (as the specs insisted) but later I preferred to handle targets ONLY by “CENTER-tracking” process (actually by only ONE instance) for better encapsulation (and elimination of doubles). As the result, a separate target-lifecycle process was not necessary as we can obtain all events.

Thanks and a Happy New Year.
AS

Sorry I can’t see the requirement d) implemented in your diagram.

Another difference is the absence of target lifecycle in your diagram: one can’t directly analyze e.g. the average time targets have been tracked.

Thanks,
AS