I got a question of a fellow-blogger, Peter Rajsky, about how to model EDA. He posted about it on his own blog, but he is a bit disappointed that no discussion arose. Perhaps his posting didn't reach the right specialists or nobody gets the clue.
To be honest, I did not spent any effort on this subject either. I promote the event-driven approach, I draw pictures from a conceptual point of view. But I did not (yet) dive into the details of hard core modeling techniques. Which I think I should do, eventually. Not because it's the enterprise architect's task (which I think it isn't), but to learn, to gain deeper insights in the solution design details and to be able to share my deeper insights here on my blog.
Peter puts the following requirements for a modeling technique (extension of UML):
- To be able to define event taxonomy - using class diagrams would be sufficient
- Explicit modeling of outbound interface - interface, which produces events (instead of providing operations)
- To use this outbound interface in sequence and activity diagrams (in the similar way as inbound interface) to be able to model event reactions
- With regard to event taxonomy, the concept of the Canonical Data Model could be in charge.
- With regard to modeling outbound interfaces and event reactions, the concept of a declarative process modeling approach could be in charge.
And Peter, thanks for initiating the awareness.