Keep it simple and use https://c4model.com/. - Source: Hacker News / 8 days ago
Second this. Reference for anyone looking I to it: https://c4model.com/ There is also quite a lot of options for helping create these diagrams. I've found https://structurizr.com/ to be the best of what I've tried so far. - Source: Hacker News / 8 days ago
What you are describing sounds a lot like C4: https://c4model.com/. - Source: Hacker News / 2 months ago
The C4 model [0] provides a mostly sensible structure and techniques for representing pure software systems across different abstraction levels. For systems involving software and hardware, or other complex interfacing (both technology and bureaucracy) this starts to delve into the universe of systems engineering. There's a decent assembly of knowledge on that in the SEBoK [1]. As another commenter has already... - Source: Hacker News / 3 months ago
There a various standards for documenting software architecture, like arc42 or C4. While useful and somewhat well-known (there is certainly a correlation here), here architecture documentation can be further simplified, particularly due to the self-similarity of project and component. Following is a small template, that can also serve as a project's and component's README:. - Source: dev.to / 5 months ago
I would suggest that if your architecture diagrams are a bunch of icons provided by AWS/Azure/GCP with lines pointing at each other... You are doing it wrong. The 'what does this box do for my system' is vastly more important than the 'which in vogue offering from my cloud provider implements it'. I highly suggest folks take a look at the C4 Model: https://c4model.com/. - Source: Hacker News / 7 months ago
We often use abstractions in software engineering to communicate complex architectures and software systems. In this article, we’ll discuss how abstractions are inherently hierarchical and how the C4 model provides a nested structure for defining your software architecture. We’ll then cover how IcePanel allows you to create interactive and zoomable diagrams for your audience to zoom in and out of different levels... - Source: dev.to / 8 months ago
You probably want https://c4model.com/ which explains what a C4 architecture diagram is. (See the first footnote in the article.). - Source: Hacker News / 9 months ago
I looked at the book OP is talking about and it seems to be advocating 'C4' (https://c4model.com/). IMO this is the same kind of block diagrams we end up creating organically. I dunno that I'd call this 'modern' or anything special, it's just what everyone already does. I've done hundreds of these and not once has anyone ever mentioned 'C4' or anything being 'modern'. Shrug. Source: 11 months ago
We recommend using the C4 model as a simple structure to diagram your system and C4 model stickies as an easy way to use the C4 model with a whiteboard. - Source: dev.to / 11 months ago
> What do you think is the whole point of a modeling language? Not building an entire system down to class level which is what it is all too often used for (in my experience exclusively by people who have never and cannot code). It's inefficient, doesn't play well with Software Engineering (diff, version control etc..) and is a relic of the past. Keep the classes in code, project that into a diagram for the few... - Source: Hacker News / 11 months ago
> Class, component, package, activity and state machine diagrams are all useful ways to model the structure and behavior of a system visually They're not bad, but the C4 model is a much better approach to high level modelling (while you can still use class diagrams on the lowest level). https://c4model.com/. - Source: Hacker News / 11 months ago
> Comprehensibility > Comprehensiveness # > The most common failure mode for sequence diagrams is over-complication. (This also is the failure mode for most diagrams, as I wrote in an article on flow charts). Agreed. UML – with the goal of being a graphical language for _complete_ specification of a system (both for code generation as well as to have diagrams generated from code introspection) – has to be... - Source: Hacker News / 11 months ago
In this model, I would expect the tech teams to submit a simple box diagram to begin with if submitting a full fledged component design. I recommend my tech organization to use standard models like the C4Model that makes visualization easy and helps address viewpoints for multiple stakeholders that will be attending the sessions. When conversation proceed to low level considerations, I would want the team to share... Source: 11 months ago
I suggest you to model your building blocks in order to better understand your needs. https://c4model.com/ is a good approach for that, particularly the deployment diagram in your case. Source: 11 months ago
Solutions: a. Creative communication: encouraging team members to repeat tasks or provide feedback in their own words. b. Being aware: understanding that words can be interpreted differently by different people is crucial. c. Using frameworks: implementing communication frameworks, such as the C4 model reported enhanced communication by encouraging clear and concise documentation of ideas and designs. Source: 11 months ago
The C4 model is a popular approach for describing a system or software architecture. There is also PlantUML library for creating the corresponding diagrams, see for example here. Source: 12 months ago
Do you know an article comparing C4 model to other products?
Suggest a link to a post with product alternatives.
This is an informative page about C4 model. You can review and discuss the product here. The primary details have not been verified within the last quarter, and they might be outdated. If you think we are missing something, please use the means on this page to comment or suggest changes. All reviews and comments are highly encouranged and appreciated as they help everyone in the community to make an informed choice. Please always be kind and objective when evaluating a product and sharing your opinion.