Do generalization arrows in class diagram has to be strictly open or is there a margin of tolerance on style of this arrows?
相关问题
- how to define constructor for Python's new Nam
- Keeping track of variable instances
- Object.create() bug?
- System sequence diagram - Can system request input
- std::vector of objects / pointers / smart pointers
相关文章
- 接口B继承接口A,但是又不添加新的方法。这样有什么意义吗?
- NameError: name 'self' is not defined, eve
- Implementation Strategies for Object Orientation
- Check if the Type of an Object is inherited from a
- When to use Interfaces in PHP
- Are default parameters bad practice in OOP?
- How to return new instance of subclass while initi
- In OOP, what is the best practice in regards to us
Talking about UML designs without an image is like talking about girl without ...... :-) Here is the picture of UML2 connectors in the class diagram:
alt text http://www.forum-omondo.com/documentation_eclipseuml_2008/connectors_uml2.png
Open arrows are used together with a dashed/dotted line to represent dependencies.
I can't think of a standard way to use them with a regular line.
Furthermore, as Martin Fowler clearly indicates in UML Distilled, UML is just a notation. If the people that will read your diagrams are aware that
open arrow = closed arrow
, then feel free to use it. There is no strictness in UML.Each element in UML has to strictly follow the normative notation proposed in the standard. With so many symbols there is a high risk that a notation variant for a symbol coincides with the normative representation of another one