We are practicing to return to the inheritance or implementation relationship with UML as much as possible. It's impossible to know which units are moving and which are capable of ground or air attacks <<>> is the interface, and the normal class abstract is the abstract class. Please reply to the awkward parts.
java uml
UML is a communication tool. It's not something that's essential to express exactly what.
The questions aren't low because I've been thinking about them in the past.
As you design the system, you draw various diagrams. One of them is just a class diagram. That is to paint a static image.
In conclusion, you just have to express what you need to communicate. The sample of the questioner is a little bit too much. Specifically, the dotted line, I don't think we need to express all of the dependencies.
Dependencies can also be inferred through sequence diagrams, so it may be better (to understand) to express only the essentials and write down the message.
© 2024 OneMinuteCode. All rights reserved.