I could get the example code to work but the code for sequence diagram didn’t work for me so I used the online version of plantUML directly.

I initially had trouble getting it to work but managed to work re-installing GraphViz. It’s powered by the the plantUML tool which has a extensive support for a sequence diagram (yes!). I came across another R-package for UML diagrams called plantuml. It turns out thought that the nomnoml doesn’t support sequence diagrams and it doesn’t look like it will support it any time either. It seems like you always have to a message when actor/object is interacting. Sequence diagrams are supported by mermaid but there seems to be no distinguishment between an actor and an object. Under the hood, DiagrammeR it’s powered by Graphviz and mermaid. When you go to the website (which has an impressively interface) it has the tagline “Sometimes You Want To Create Nice Diagrams: WHY NOT DO THAT WITH R?”. The most comprehensive R-package to draw a diagram is DiagrammeR. Being somewhat of an anti click-and-point statistical software, I should have perhaps pursued the programmatic route earlier. This was a point when I realise I really need to programmatically create the diagram. Let’s use this in the edibble documentation… Wait the interaction between the statisitican and Design doesn’t fit the narrative well, I need to modify the diagram again! This is perhaps I’ve chosen a font available only in my system (“Fira Code”). One thing to keep in mind is that the font for the PDF version is not rendered correctly. There were some UML stencils and I thought it was going well (result in Figure Aligning the objects as a sequence diagram, even with OmniGraffle’s precise object placement, was a bit difficult but it got the job done in the end. I always find drawing complicated diagrams to be tricky via programming so I initially drew the diagram using OmniGraffle. lifeline) seemed like a good fit to use for illustrating the concept of edibble. The interaction of actors with the system depicted as objects with passage of time depicted as a vertical dotted line (a.k.a. It’s a language that describes standards for all sorts of diagrams, not just the sequence diagram, e.g. communication diagram, interaction overview diagram and so on. UML was developed in the field of software engineering to provide a standard way to visualise the design of a system. One of the standards for drawing this is using the Unified Modelling Language (UML) managed by the Object Management Group (OMG). A sequence diagram, as described in wikipedia, shows objects interactions arranged in time sequence.

Tool to draw sequence diagram