This repository has been archived by the owner on Jan 10, 2024. It is now read-only.
Replies: 1 comment
-
For a use case specific diagram, I'd recommend using a dynamic diagram, which allows you to override the relationship description. Links:
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I'm trying out structurizr and my goal is to be able to generate use-case specific diagrams from the common model.
I'd like to take the structurizr model and create a use-case specific diagram, where I would also change the relationship text, to better describe the use-case.
For example, the model could describe
customerService -> customerDB "manage customer data"
, however when describing the the "Change Email" use-case, I'd like to clearly state that we're changing the email in the DB:Model-level descriptions are generic and enable browsing through the whole system and getting a high-level understanding. However when working on technical design documents, specificity in the description is needed and I couldn't find a way to achieve that. I know that
dynamic
views can override the description, however it forces an ordering on the operations and that's not what I'm looking for.Any ideas if what I'm looking for can be achieved in structurizr?
Beta Was this translation helpful? Give feedback.
All reactions