Event-Based Software Architectures
- 287 Downloads
Implementation architectures of today are based on the modularisation of software into objects, components, web services, (intelligent) agents, ... with communication and coordination between components being based on peer-to-peer communication (a client-component requests a service from a server-component). Because this binary and uni-directional form of communication implies substantial restrictions on software maintainability, this paper proposes the development of a new N-ary and multi-directional communication paradigm based on the notion of “event": components will interact by jointly participating in events. This new communication paradigm uses event broadcasting as a coordination mechanism between software components. It can be implemented by means of generic binary interaction frameworks applicable across diverse platforms (distributed, web-based and centralised systems) and implementation paradigms (synchronous and asynchronous communication). In addition, events can be enriched with intelligent features so as to be able to act autonomously and to be capable of undertaking some rescue actions when one of the composing actions fails.
KeywordsRemote Service Business Rule Enterprise Information System Output Service Input Service
Unable to display preview. Download preview PDF.
- 1.Cheesman, J., Daniels, J.: UML Components, A simple process for specifying componentbased software, p. 208. Addison Wesley, Reading (2000)Google Scholar
- 2.Fensel, D., Bussler, C.: The Web Service Modeling Framework WSMF. Electronic Commerce Research and Applications 1(2) (2002)Google Scholar
- 3.D’Iverno, M., Luck, M.: Understanding Agent Systems, p. 191. Springer, Heidelberg (2001)Google Scholar
- 4.Jackson, M.A., Cameron, J.R.: Systems Development. Prentice Hall, Englewood Cliffs (1983)Google Scholar
- 5.Nilsson, A.G., Tolis, C., Nellborn, C. (eds.): Perspectives on Domain modeling: understanding and Changing Organisations. Springer, Heidelberg (1999)Google Scholar
- 6.Cook, S., Daniels, J.: Designing object systems: object-oriented modeling with Syntropy. Prentice Hall, Englewood Cliffs (1994)Google Scholar
- 8.McKim, J., Mitchell, R.: Design by Contract: By example, p. 256. Addison-Wesley, Reading (2001)Google Scholar
- 10.Snoeck, M., Dedene, G., Verhelst, M., Depuydt, A.M.: Object-oriented Enterprise Modeling with MERODE. Leuven University Press, Leuven (1999)Google Scholar
- 12.Wilfried, L., Monique, S., Cindy, M.: Integration of Third-Party Applications and Web-Clients by Means of an Enterprise Layer. Accepted for Volume V of the Annals of Cases on Information Technology (2002)Google Scholar
- 13.Wilfried, L., Monique, S., Cindy, M.: An Enterprise Layer based Approach to Application Service integration. Accepted for Business Process Management Journal – Special Issue on ASPGoogle Scholar
- 15.Lemahieu, W., Snoeck, M., Michiels, C., Goethals, F., Dedene, G., Vandenbulcke, J.: A model-driven, layered architecture for web service development submitted to IEEE Computer. Special issue on Web Services Computing (2003)Google Scholar