You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 10, 2024. It is now read-only.
workspace {
model {
a = softwareSystem "A"
b = softwareSystem "B"
c = softwareSystem "C"
}
views {
dynamic * {
a -> b "Sends customer data to"
b -> c "Sends customer data to"
autoLayout
}
}
}
The communication diagram and sequence diagram generated using PlantUML exporters looks like this:
Even though sequence number is relevant for the communication diagram to understand the order of messages, it’s not the case for a sequence diagram, where the order is already implicit to the diagram. I can see WebSequenceDiagrams exporter is not including order number as part of the message description.
It would be great if messages in sequence diagrams don't include the sequence number.
Thanks.
The text was updated successfully, but these errors were encountered:
Given this example:
The communication diagram and sequence diagram generated using PlantUML exporters looks like this:
Even though sequence number is relevant for the communication diagram to understand the order of messages, it’s not the case for a sequence diagram, where the order is already implicit to the diagram. I can see WebSequenceDiagrams exporter is not including order number as part of the message description.
It would be great if messages in sequence diagrams don't include the sequence number.
Thanks.
The text was updated successfully, but these errors were encountered: