I like the model, and have had to use UML in security architecture where the whole thing hinges on consistency from the top level context to the code. The simpl

I like the model, and have had to use UML in security architecture where the whole thing hinges on consistency from the top level context to the code. The simplicty of this C4 model is a forcing function, where if there is hidden context or components, they have to shake out in the model. I'd suggest resistance to something this simple chould indicate there may be hidden elements (which there are more often than not on large projects). Forcing people to clarify their thinking into something like this decentralizes them by having them commit to statements and ideas instead of just reserving a right to suggest and criticize, and you can get a lot of resistance to that as well. These aren't model problems though, but they're what happens when models meet people. I'll use something like this as a reference for security design as I really like its consistency.