Monitored Event
by
Benedikt Liegener
—
last modified
Apr 26, 2012 14:42
—
filed under:
KnowledgeModel
Definitions
Term: Monitored event |
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) |
The service infrastructure should allow for
propagating dependencies and effects of monitored events and
information across various functional layers and aspects in order to
enable the diagnosability of application behaviors.
[PO-JRA-1.2.1] |
||||
Generic (domain independent) |
A Monitored Event delivers the relevant information about the application evolution and changes in the environment. [PO-JRA-1.2.1] | Event: 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] |
Competencies
-
UniDue: Quality Assurance; http://www.sse.uni-due.de/wms/en/?go=111; Klaus Pohl, Andreas Metzger
- POLIMI: Adaptive Web Services; http://home.dei.polimi.it/pernici/ws-research.html; Barbara Pernici, Maria Grazia Fugini, Danilo Ardagna, Pierluigi Plebani, Cinzia Cappiello, Marco Comuzzi
- POLIMI: Monitoring; http://deepse.dei.polimi.it/; Luciano Baresi
- INRIA: Monitoring Design Principle and Monitoring Framework;http://www.irisa.fr/paris/; Thomas Ledoux, Françoise André, Olivier Barais, Jean-Louis Pazat
Scenarios
References
- [PO-JRA-1.2.1] Deliverable PO-JRA-1.2.1 State of the Art Report, Gap Analysis of Knowledge on Principles, Techniques and Methodologies for Monitoring and Adaptation of SBAs.
- [Wikipedia] http://en.wikipedia.org/wiki/Event_(computing)