Basic Event
by
Asli Zengin
—
last modified
Apr 26, 2012 14:08
—
filed under:
KnowledgeModel
Definitions
Term: term |
Domain: Cross-cutting issues | ||||
---|---|---|---|---|---|
Engineering and Design (KM-ED) |
Adaptation and Monitoring (KM-AM) |
Quality Definition, Negotiation and
Assurance (KM-QA) |
Generic (domain independent) |
||
D o m a i n : L a y e r s |
Business Process Management (KM-BPM) |
||||
Service Composition and
Coordination (KM-SC) |
|||||
Service Infrastructure (KM-SI) |
|||||
Generic (domain independent) |
Basic events are the data that we collect at runtime, and are used to evolve a monitor's state. A basic event is defined by a declaration, a location, and a property. The declaration defines the event's name, its type, and its parameters, i.e., the run-time data needed to execute the basic event's property. The location consists of an XPATH expression that selects a unique BPEL activity in the process definition. Finally, the property is given in an extended version of the Web Service Constraint Language. A property can produce one of three possible types: boolean, numeric, or tick. [Baresi et al. 2009] | In computing an event is an action that is usually initiated outside the scope of a program and that is handled by a piece of code inside the program. Typically events are handled synchronous with the program flow, that is, the program has one or more dedicated places where events are handled. [Wikipedia] |
Scenarios
- Original Equipment Automotive Supply Chain (Case Study Solution)
References
- [Baresi et al. 2009] Luciano Baresi, Sam Guinea, Michele Trainotti, and Marco Pistore. "Dynamo + Astro: An Integrated Approach for BPEL Monitoring." in Proc. ICWS, 2009, pp. 230-237.
- [Wikipedia] http://en.wikipedia.org/wiki/Event_(computing)