Lesson 152 - Modeling Distributed Workflows

[@code4it]

Great lesson! This kind of model is useful both as documentation for future reference and as a way to wrap your head around the different moving parts. I feel that, somehow, it fits perfectly with ADRs

[@kamalbakarim3385]

Wow another great lesson for Mark thanks so much for your efforts

[@markrichards5014]

Thanks Kamal!

[@tharnendil]

Nice and clean method 👍

[@alexsharma]

We can also mention numbers for easy reference in modelling diagram which will help stakeholders to understand it better.

[@markrichards5014]

Good point! Yes, numbering would be useful, particularly for complex workflows having lots of callbacks

[@pouyanpiano]

Mark, How would you contrast this with a classic sequence diagram?

[@markrichards5014]

I'm SO glad you asked that question! The business automation model is at a much higher level than a sequence diagram. Typically sequence diagrams indicate the methods being called between classes, whereas the business automation model shows workflow steps between services or systems.

[@ren.oooooo]

I tried playing around with PlantUML but unfortunately I couldnt get it to work. Which tool do you recommend to draw these diagrams?

[@markrichards5014]

I really like ExcaliDraw for draft architectures (excalidraw.com), and use Omnigraffle, visio, C4 Model, or Archimate as well for more formal diagrams.

[@sant4398]

Another interesting video! Why the "route order to trader" process has no continuation to other processes? Am I missing something? Thanks.

[@markrichards5014]

Hi SanT, I tried to simplify the flow for illustration purposes, but you are correct - normally the router service would send the trade to what is known as a "trader blotter" - a reserved area for trades assigned to a trader. I shortened that step and instead incorporated it into the user interface.

[@sant4398]

@@markrichards5014 Thank you for the elaboration.

[@fuzzy0001]

is it the same as BPMN Specification or different

[@agilebot1]

Looks like there is a mistake in the workflow model. The arrow to the "route order to trader" should be from "pre-trade compliance".

[@markrichards5014]

Not a mistake, but I'm glad you pointed that out; you see, here, the route order to trader is initiated from the trader user interface, NOT pre-trade compliance. This is an important distinction because it means the SERVICE itself is not responsible for routing to the trader, and therefore not coupled to the trade router service.

[@kurtrichards159]

Promo sm