Multiple versions of one architecture model

[mathias-muench]

Hi,

I would like to model two versions of the "same" architecture in structurizr (baseline - target). Between the versions not only elements are added, but also properties of existing elements and relationships are changed. For example, the authentication method as a relationship technology may change from "basic auth" to "OIDC". Most parts of the model do not change between versions, just having two workspaces would lead to a lot of duplication.

I have played around with version tags and filtered views, but having the same relationship twice with two different version tags leads to all sorts of unexpected results.

What is the best way to have two versions of a model with only a few elements and/or relationships changed?

Kind regards, Mathias

[simonbrowndotje]

Perhaps the workspace extension feature?

[mathias-muench]

Yes, perhaps. It is on my list to try. Upfront I see some questions and (minor) drawbacks.

• Can I have only one set of documentation and decisions in two different extended workspaces?
• How to use workspace extension with structurizr lite? It always searches workspace.dsl. Different directories for every version? How to refer to the "base" workspace file then? Subdirecories and refer to ../base_workspace.dsl?
• Compared with filtered views, we loose that nice feature of "consistent placement between two views".

[simonbrowndotje]

Can I have only one set of documentation and decisions in two different extended workspaces?

It depends where you define the documentation/decisions ... the parent or the child workspaces.

How to use workspace extension with structurizr lite? It always searches workspace.dsl. Different directories for every version? How to refer to the "base" workspace file then? Subdirecories and refer to ../base_workspace.dsl?

See https://structurizr.com/share/76352/documentation#usage

Compared with filtered views, we loose that nice feature of "consistent placement between two views".

Correct. You could write some code to copy the layout information between workspaces though.

[mathias-muench]

Documentation beyond "Getting Started" does not count. :-) I am not completely sure about the interference of sub directory and "!docs", but I will try myself. Thank you for the pointer.

[mathias-muench]

For my use case the "STRUCTURIZR_WORKSPACE_FILENAME" feature already does the trick so I assume this to be a solution. Having two workspaces for comparing and discussing two versions of the same system right now feels a little bit heavyweight, but I will just try it and see how it works.

Thanks again!