IcePanel app container and C4 model

• IcePanel is a modelling and diagramming tool for communicating system architectures.
• It adopts an abstraction-first approach.
• Changes sync automatically through all diagrams in the model.

C4 Model

• The C4 model allows users to drill down into different levels of detail.
• It helps explain how things work to both technical and non-technical audiences.
• The audiences include developers, architects, product and business stakeholders.

Step 1: Create a Context View

• Focus on the big-picture view of the system architecture.
• The view should show how the customer's problems are solved.
• The view should remain primarily at the business level.
• This view is useful for anyone needing a high-level overview of how systems work.
• Example audiences are business, product and non-technical peers, also new technical teammates.

Step 2: Add an App Container

• This is the App level.
• It shows the runnable units in each System that execute or store code.
• The audience is mainly technical people, such as architects and developers.
• Some product people (such as product owners, product managers, or business analysts) will gain value here for planning purposes.

Step 3: Add Existing Objects from the Level Above

• Objects from higher levels, such as other systems and people, can be added.
• Add Actors and Systems from the level above.
• Connections created at a higher level will show as higher connections.
• Multiple diagrams can be created to show different views of the model.
• Examples can include customer-specific views, focusing on one object, and current vs. future design.

Step 4: Add Technology Choices

• Start adding tech choices, such as AWS, GCP or Azure services, languages, libraries or frameworks.
• Search for the tech choice and add it.
• These choices come with preassigned documentation and a simple description.
• The tech choices can be used later to highlight tech choices.
• It allows people to learn the technical choice landscape.
• Users can also filter the model.

Step 5: Describe Each Object and Diagram

• Each object and diagram has a description, adding details to understand how things work.
• The descriptions are linked to your model, and follow that object wherever it is.
• The minimum to add is a brief displayed description for each object to help teammates.
• The detailed description field supports Markdown.
• Existing documents and formatting can be imported manually or through our.

Step 6: Create a Flow

• Flows show how your system works in multiple scenarios or user journeys on the same view.
• Flows can be created in the diagram Flows tab.
• Use the Back and Next buttons to step through your flow when complete.

Step 7: Add Tags

• Tags show multiple perspectives of your diagrams without duplicating them.
• Tag groups show different information, such as deployment information, the risk, or the cost of your model.
• Add tags that apply to the tag group you want to show in the Tags bar.
• Hover over the tags to highlight them.
• You can also pin them or select the hide/focus options.
• Tags help target specific areas of focus for each audience; also, change the design focus with little effort.

Step 8: Collaborate and Share

• Invite teammates as viewers (unlimited and free on all IcePanel plans).
• Interactive read-only share links of your designs can be created.
• Copy and paste the link to anyone you want to show your designs.
• Wherever you are when you create a share link will be where your audience lands when opening the URL, including position, selected object, Flow, Tags etc.

Step 9: Create a Version

• Versions of landscapes can be created to track changes and visualize how your architecture has evolved.
• Name your version and add notes.