Event-Based Software Architectures

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.

[1]  James C. McKim,et al.  Design by Contract, By Example , 2001, TOOLS.

[2]  Timo Steffens,et al.  Understanding Agent Systems , 2004, Künstliche Intell..

[3]  Monique Snoeck,et al.  An Event Based Approach to Web Service Design and Interaction , 2003, APWeb.

[4]  John Daniels,et al.  UML Components: A Simple Process for Specifying Component-Based Software , 2000 .

[5]  Michael Luck,et al.  Understanding Agent Systems , 2001, Springer Series on Agent Technology.

[6]  Dieter Fensel,et al.  The Web Service Modeling Framework WSMF , 2002, Electron. Commer. Res. Appl..

[7]  Monique Snoeck,et al.  Object-Oriented Enterprise Modelling with MERODE , 1999 .

[8]  Bertrand Meyer,et al.  Object-Oriented Software Construction, 2nd Edition , 1997 .

[9]  Geert Poels,et al.  Improving the Reuse Possibilities of the Behavioral Aspects of Object-Oriented Domain Models , 2000, ER.

[10]  Monique Snoeck,et al.  Integration of third-party applications and web clients by means of an enterprise layer , 2003 .

[11]  John F. Sowa,et al.  Extending and Formalizing the Framework for Information Systems Architecture , 1992, IBM Syst. J..

[12]  Monique Snoeck,et al.  Existence Dependency: The Key to Semantic Integrity Between Structural and Behavioral Aspects of Object Types , 1998, IEEE Trans. Software Eng..

[13]  MeyerBertrand,et al.  Design by Contract , 1997 .

[14]  簡聰富,et al.  物件導向軟體之架構(Object-Oriented Software Construction)探討 , 1989 .

[15]  John Daniels,et al.  Designing object systems: object-oriented modelling with Syntropy , 1995 .

[16]  Kunii Kunii,et al.  Conceptual Modeling -ER2001 , 2001 .

[17]  Monique Snoeck,et al.  An enterprise layer-based approach to application service integration , 2003, Bus. Process. Manag. J..

[18]  Veda C. Storey,et al.  Conceptual Modeling — ER 2000 , 2003, Lecture Notes in Computer Science.