Documentation to explain how to use CALM to 'evolve' system architecture

[rocketstack-matt]

Feature Request

Description of Problem:

CALM provides a tool set to enable enterprise and solution architects to communicate the constrains (controls) a system should implement in certain scenarios and also to enable architects to incrementally build out the detailed view of a systems architecture.

We need documentation clearly explaining how to use the tools in this scenario.

Potential Scenarios:

Create a tutorial demonstrating how different types of architect at different stages of design and review would use CALM to facilitate those conversations and capture the details.

• As a solution architect how can I start with a black box architecture (single node system)?
• As an enterprise architect how can I attach various control requirements I need the solution architect to fulfil at the single node level?
• As a solution architect how can I provide control configurations for how the requirements will be fulfilled?
• As a solution architect how can I explode the single node to start to providing greater detail of how the system will be implemented?
• As a solution architect how can I move control requirements / configurations from higher to lower levels?
• As an engineer how can I evidence that I have fulfilled the control requirement in line with the configuration?