Skip to main content
Software Engineering

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

2
  • Looking at your response and those of others, I conclude that the implementation itself doesn't matter much, for two reasons. First, the diagram doesn't focus on implementation per se, but on the OCP. Second, how models are implemented outside the boundaries doesn't really matter, as the core is protected by interfaces and dependency inversion. Uncle Bob has an approach different from what I'm used to, likely due to years of experience and different contexts. Perhaps this is why I’ve become so attached to simple details like the "naming" of boxes. Thank you. Commented Dec 4, 2024 at 22:17
  • @Tozine OCP and DIP are considerations but what this diagram tells you more than anything else is what knows about what. That's the big lesson any UML class diagram teaches. Commented Dec 4, 2024 at 22:23