in conjunction with
26th International Conference on Software Engineering
The workshop proceedings are also available on-line here.
In addition to the technical program, the workshop provided a good "social" program
The event-based communication style (also called implicit invocation or publish/subscribe event notification) has been considerably and increasingly deployed over the past years. The number of non-trivial case studies in which this paradigm is applied is significant, and ranges in scope from simple desktop applications to widely distributed and critical systems such as real-time, automotive, traffic control (including air and railway), e-commerce, workflow, and mobile computing. The acceptance of this paradigm is witnessed by its incorporation into standards such as CORBA and JMS, and commercial systems such as TIBCO. In fact, this paradigm is becoming the de-facto communication mechanism for loosely coupled software systems.
Another important application domain for event-based communication is the monitoring and management of systems and networks. In this case, software components and network devices signal faults or other anomalous conditions (directly or through a local watchdog agent) by raising alarms. The alarms are then dispatched to one or more management stations, where management applications or administrators can formulate a diagnosis and take appropriate corrective and/or preventive actions. Within management platforms, event correlation plays a central role. Event correlation is the automated process by which individual events or sequences of events that determine the root causes of a high-level problem are singled out of a stream of low-level events.
The purpose of this research workshop is to bring together people from academia and industry interested in the foundations and development of event-based applications, event-based communication infrastructures, and event correlation techniques.
We believe that a number of issues remain open in the engineering of event-based applications, event-based infrastructures, event correlation techniques, and, notably, in the integration of these areas. Examples of open questions are: How to specify an event-based application? How to verify that such an application satisfies its specification? How to test an event-based application? What are the best practices in developing event-based applications? What requirements are put on middleware by methodologies for constructing event-based applications? What value-added services are needed, and which one can be built on top of a basic publish/subscribe infrastructure? What correlation techniques are most appropriate for which classes of applications? How to scale up event correlation in the presence of intense event traffic and dynamic dependencies among components? What levels of service are needed for event-based applications? Modeling an event-based infrastructure as a communication network, what are the best routing protocols and forwarding algorithms? Which network architectures and protocols can provide the necessary quality of service? How to provide reliable event notification over an unreliable network? How to test a distributed event-based infrastructure for correctness and/or for performance? How to compare two implementations? Is a distributed event-based infrastructure really necessary? What is a "killer application"?
The goal of this workshop is to share and discuss original and innovative ideas in the area of event-based systems. Therefore, we invite authors interested in event-based applications, event-based infrastructures, and event correlation to submit a paper to this workshop. Below is a list of topics of interest grouped by areas. (The list should not be seen as exhaustive.)
Papers do not have to be based on complete and comprehensive works. In fact, we prefer and welcome position papers as well as papers based on preliminary results, provided that they be forward-looking and that they remain well-argued and justified in terms of existing work.
Authors of accepted papers are expected to participate in the workshop.
|Deadline for paper submission||March 8, 2004|
|Decision to paper authors||April 5, 2004|
|Final version of accepted papers due||April 12, 2004|
|DEBS 2004 workshop and on-site registration||May 24-25, 2004|