Runtime Event
by
Asli Zengin
—
last modified
Apr 26, 2012 11:40
—
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) |
A monitoring event is an action that is usually initiated outside the scope of a business process 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] | |||
| Service Composition and
Coordination (KM-SC) |
|||||
| Service Infrastructure (KM-SI) |
|||||
| Generic (domain independent) |
Runtime events are events describing the current state of the execution platform (memory levels, CPU load, network bandwidth, etc.), which are produced by the application and are monitored during application run-time in order to trigger the right adaptation actions to ensure the expected running of the overall system. [Morin et al, 2009] | ||||
Competencies
- N/A
References
- [Wikipedia] Event: http://en.wikipedia.org/wiki/Event_(computing)
- [Morin et al, 2009] Brice Morin, Thomas Ledoux, Mahmoud Ben Hassine, Franck Chauvel, Olivier Barais, and Jean-Marc Jezequel. Unifying Runtime Adaptation and Design Evolution. Proceeding of IEEE International Conference on Computer and Information Technology, 2009.
