Developers frequently communicate about their job using sequence diagrams. Each step in a sequence diagram might be related to a task defined in a kanban tool such as Trello. Looking at the diagram, it is hard to tell which task is related to which step. We can make this connection more visible by defining both the tasks and the diagram in the same tool - Notion, in this example - and rendering the sequence diagram with a script that uses Notion's API for fetching the defined diagram and tasks. The result is displayed here.
Developers frequently communicate about their job using sequence diagrams.
Sequence diagrams make it possible for many teams to agree on a design specification and implement it in parallel.
Suppose that a sequence diagram is represented as a notion table. Then, the sequence diagram can be linked with tasks.
In this way, when someone creates a task, it will have a column that links it to a step in the sequence diagram.
Assumption: we can generate the diagram based on this table (by using Notion's API, for example) whenever the table is updated.
First, we define a table containing all the tasks. Ignore the Sequence diagram step column for now.
Then, we define a table that represents the sequence diagram. Each diagram step is listed in order.
This table represents the following diagram:
The crux of the problems is how to link the diagram to the tasks. This is possible because is connected to through the Task column. This column is a relation. You can think of it as a
join operation in SQL.
In this way, adding a Task to a sequence diagram step is quite simple: just click on Task and all tasks will be listed. Then, you can choose one or more tasks. Alternatively, in the table, you can link a task on the Sequence diagram step column. Note that you can't reproduce this behavior on this page because it's read-only.