Hi,
Managing variations has come up a few times in the forum. From a quick search of previous topics…
In the first instance I would look at this: Multiple Physical Architectures
With respect to variant modelling and a 150% model (similar but not exactly what you are after) I suggest you look at this topic: variant management
I think you have an extra challenging situation as you are looking to model not only current alternatives (LA/PA) for a fixed set of black-box needs analysis (SA) but also an evolving needs analysis (SA). You will have to think carefully about what you want to model now vs in the future.
For modelling your current set of alternatives…
Within a single model this will always be clunky if you start creating multiple versions of functions,behaviors, components. Possible but not recommended. Guidance available in the various books suggests:
- Using multiple models and a version control management system (e.g. GIT)
- Using RECs/RPL to reduce the modelling overhead. This way you can model your various architectural options once then you only have to do the integration modelling/thinking. You dont have to model your embedded PLC each time, just model it once then place it in the model you want to explore the use of.
With respect to documenting choices, the decision of which architecture to go with will not only be based upon the system architecture model but also various analysis and trade studies which all go into the decision making mix. You can reference this back against a given Capella model version controlled in your ADR as well as your wider analysis.
Hope this helps.