Take UML class diagram as an example, there may be a domain diagram that presents all the entity classes and, another diagram that presents the associations and dependencies between a specific controller class and its related entity classes. In fact, this is extremely common when modeling with class diagram and business process diagram. You need to borrow shapes from a diagram to make them appear in other diagrams (i.e. When you are dealing with a complex project, you may need to draw multiple diagrams to represent different contexts.
Each of them represents a distinct design idea and there is no overlapping between diagrams. The diagrams are simple and self-explanatory. When your project is simple, you are able to express all of the design ideas with just a few diagrams.
0 kommentar(er)
