Modeling Event Publish/Subscribe behaivor

[andrewd]

When I create a static diagram of a component or interface, I can specify the interface functions as public operations.  This is fine for a polling environment, but I also want a way to show when a component generates an event that other code can subscribe to.

For example if component A generates event E1, I would like to show that component B subscribes to that event and the callback function in component B that would get called.  Maybe specifying callback functions is too close to implementation, and there is another way to describe this a the architecture/design level.

I currently heavily use the public operations in the sequence diagrams, so I would also want to show the event/callback in the sequence diagram as well.
Any thoughts on best practice for this?

[qwerty]

I don't see the problem. If you offer a Subscribe method on the one side you will have some Callback on the other side. First message from subscriber to Subscribe. Later you'll get Callbacks. Both can be visible members of your interface on the respective side.

q.