The C4 model is to visualize software architecture using: Context, Containers, Components, and Code.
The C4 model was created as a way to help software development teams describe and communicate software architecture, both during up-front design sessions and when retrospectively documenting an existing codebase. It's a way to create maps of your code, at various levels of detail, in the same way you would use something like Google Maps to zoom in and out of an area you are interested in.
CaseTalk has a primary focus on information models and generates artifacts, amongst which are the UML Class Diagrams. UML Class Diagrams are the lowest grain in the C4 architecture. So, when CaseTalk starts supporting the C4 architecture by being able to model all of the above it would result in a so-called C4i solution.
Here you see a diagram created in CaseTalk using example models from typical C4 websites.
Not depicted is the links to other models, diagrams or even Object/Fact Types which can be annotated on these CaseTalk Concepts and -Containers. Also the lines in between the concepts and containers are stored in the repository of CaseTalk and therefor persisted. If a diagram element is added, CaseTalk will remember the relations and draw lines where available.
In other words, a wonderful addition to CaseTalk and the C4 approach.
