Issues in supporting event-based architectural styles
ISAW '98 Proceedings of the third international workshop on Software architecture
The JEDI Event-Based Infrastructure and Its Application to the Development of the OPSS WFMS
IEEE Transactions on Software Engineering
Java.rmi: The Remote Method Invocation Guide
Java.rmi: The Remote Method Invocation Guide
SOAP: Cross Platform Web Service Development Using XML
SOAP: Cross Platform Web Service Development Using XML
Taxonomy of Distributed Event-Based Programming Systems
ICDCSW '02 Proceedings of the 22nd International Conference on Distributed Computing Systems
Integration of third-party applications and web clients by means of an enterprise layer
Annals of cases on information technology
Events as atomic contracts for component integration
Data & Knowledge Engineering - Special issue: Contract-driven coordination and collaboration in the internet context
Integrating COTS Software into Systems through Instrumentation and Reasoning
Automated Software Engineering
On the Definition of Service Granularity and Its Architectural Impact
CAiSE '08 Proceedings of the 20th international conference on Advanced Information Systems Engineering
Data & Knowledge Engineering
| Hi-index | 0.00 |
Integrating and coordinating COTS software requires appropriate analysis and architectural design. Most integration architectures use message-oriented middleware for the interaction between COTS applications. However, the abstraction level of these one-to-one message exchanges is too low to aptly design the integration architecture's coordination aspects. The authors' approach, called BECO (business event-based coordination), improves organizational fit and flexibility by introducing an additional abstraction layer in the interaction stack. Business events are introduced as higher-level, many-to-many coordination units, which enforce consistent processing in multiple applications. Underneath, existing one-to-one communication technologies can be reused for event notification. Furthermore, business processes can be designed and enacted concisely as sequences of business events. The result is a consistent, flexible integration approach that can be layered entirely on top of existing technologies.