System design using CIMap
First sample is a design at programming level, but CIMap is originally intended to more rough modeling.
System design using CIMap flow will be as the following.
- Create "System Context"
- Break down "Components"
- Create "Deployment Unit/Node Matrix"
- Create "Physical Node Deployment Diagram"
Refer to sample (sample2.cimap).
Create "System Context"

At first, to clarify the boundary between the subject of analysis/design and the external. Here you define "Users to use it", "External systems connected to it", "Interaction(service/function) between it and the external".
In addition, you shoud get the following information for non-functional requirements,
- User/ExternalSystem
- number, location, interface protocol, service time etc.
- Interaction
- availability (service time/RPO/RTO etc.), transaction volume, data volume to submit/receive etc.
On CIMap editor, you can fill them in "Description" property of each entity (or element).
Break down "Components"

Break components down logically, functionally and sequentially from system context.
Breaking down must be done with keeping the consistency of its peripheral interactions.
In this process, you might have to break the other elements down. On CIMap editor, you can manage the hierarchy of entity with using "Entity Tree" on [Entity] dialog.
Create "Deployment Unit/Node Matrix"

The component of the bottom level can be broken further to physical deployment units(DU).
On CIMap editor, you can get the list of components (csv format) with "Generate Entity List". You can import it to your spreadsheet software.
You can define the other DUs related to IT system management (monitoring/job scheduler/backup agent etc.) with this matrix.
Create "Physical Node Deployment Diagram"

Create a deployment diagram of physical nodes that was derived in the "DU/Node Matrix". In addition, you can describe the redundant configuration.
This figure has been written to divert the CIMap editor.
Through all tasks
Like this way, we believe it is important to proceed with a consistent way from system context to physical configuration. As you move through the analysis, design etc., tend to become "not see the forest for the trees". It is important to be always aware of the hierarchical structure of the components. (Icon of CIMap editor (3 rounded rectangle) represents the hierarchical structure of the component.)