No standard diagramming / modelling approach for Solution Architectures
No clear way to re-use model elements between solutions, team members
No consistent collaboration approach
Approaches based on drawing vs. modelling further compounds these problems
Difficult to trace from Capabilities down to implementing systems and technologies
Proposal
Leverage a standard modelling notation such as UML for solution architecture capture
A proper modelling tool will permit re-use of elements, enforce notational rules, establish context vs. diagramming tools which essentially just create pictures
Leverage a framework such as C4 to assist in exposing right-sized / right-audience diagrams
To provide audience-pertinent levels of detail while still preserving the details
Establish a set of modelling standards to establish mappings to corresponding CSDM-defined CMDB elements so that traceability from Capabilities can be established
Complications
Practical issues around engagement with ITSM teams and service, for example SA's are involved with Release Management, but DevOps personnel interact with Change and Config Management, which is more pertinent to how the CSDM / CMDB will be interacted with, metadata provided, etc.
In reality this may not be feasible to tie-in with SA modelling tools at all, but will be instead require more of a DevOps focus