Class: interface realization / lollipop
See original GitHub issueThere doesn’t seem to be a way to define this currently: https://www.uml-diagrams.org/realization.html
PlantUML calls it lollipop: https://plantuml.com/class-diagram and supports it like this:
bar ()- foo
bar ()-- foo
foo -() bar
Issue Analytics
- State:
- Created 4 years ago
- Comments:6 (4 by maintainers)
Top Results From Across the Web
BallAndSocket - Martin Fowler
The origins of this was the 'lollipop' notation that was popularized by Microsoft to show a class implementing multiple interfaces.
Read more >Using lollipops/sockets in UML, why and when? - Stack Overflow
I have any number of class's that Implements an interface. (all with a realization arrow to that interface). that means exactly the same....
Read more >Adding a dependency to a lollipop or cup on a diagram
To add a realization interface dependency to a cup: 1. On the Class Diagram or Structure Diagram toolbar, click the Provided Interface button....
Read more >Section 9.6. Unified Modeling Language - People
UML uses a "lollipop" to denote an interface, which can be appended to classes and subsystems, among other things. UML also allows a...
Read more >Show Realized Interfaces of Class | Enterprise Architect User ...
The Bank Class realizes (or provides) the Internet Banking Interface. ... Therefore you can represent the realized interface as the 'lollipop' node, ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I think that resolves part of it. The other part was being able to do something like the following:
I have update the code according to the changes of the code base Please refer to the PR #3311 The redundant classbox for this simple interface is not handled yet.