This one has me stumped regularly while creating top level class diagrams for documentation. Methods and attributes/fields are easy to model. I usually end up adding a method named EvChanged to indicate a .Net event Changed.
What is the right way to show that a type publishes a specific event?
The receiver finds the addressee (Target) and calls its corresponding method (Target. OnMyEvent()). To emphasize that this call is event-triggered, I introduce a stereotype called "Event". This scheme may look somewhat clumsy, but, to me, it covers the case.
The plus signs indicate the means you must use to interact with the properties and methods of the class. In other words, the Public items of a class define the interface for the class object and how you must interact with it.
Class (i.e. static) methods and fields are indicated by underlining. Constant (i.e. final) fields are indicated via naming convention: constants should be in ALL_CAPS.
Just add an «event» stereotype to a classifier attribute.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With