A domain specific aspect language for run-time inspection

Authors:
Wouter De Borger;Bert Lagaisse;Wouter Joosen
Affiliations:
KU Leuven, Leuven, Belgium;KU Leuven, Leuven, Belgium;KU Leuven, Leuven, Belgium
Venue:
Proceedings of the seventh workshop on Domain-Specific Aspect Languages
Year:
2012

Citing 6
Cited 0

Feature-based survey of model transformation approaches

IBM Systems Journal - Model-driven software development
Diagnosing Distributed Systems with Self-propelled Instrumentation

Middleware '08 Proceedings of the ACM/IFIP/USENIX 9th International Middleware Conference
The art of the meta-aspect protocol

Proceedings of the 8th ACM international conference on Aspect-oriented software development
A generic and reflective debugging architecture to support runtime visibility and traceability of aspects

Proceedings of the 8th ACM international conference on Aspect-oriented software development
FAIDECS: fair decentralized event correlation

Middleware'11 Proceedings of the 12th ACM/IFIP/USENIX international conference on Middleware
A generic solution for agile run-time inspection middleware

Middleware'11 Proceedings of the 12th ACM/IFIP/USENIX international conference on Middleware

Quantified Score

Hi-index	0.00

Visualization

Abstract

When inspecting a running system, be it for debugging or monitoring purposes, developers are often faced with an abstraction gap: the run-time structure is not represented in terms of high-level programming abstractions, but in terms of low-level run-time constructs. To present developers with an understandable view on the system, a transformation can be performed to restore the programming abstractions. In the current state of the art, two types of transformations exist: state-based transformations (model transformation) and event-based transformation (complex event processing). These two types of transformations can bridge the same abstraction gap, but deliver a different quality of service. There are domain specific languages for these two kinds of transformations, but they can not be composed into a single overarching transformation automatically. While such unified transformations can deliver a superior quality of service, there is no language to express them. Therefor we are currently working on a unified model, that considers both types of transformation as aspects contributing to a unified transformation. This papers sketches our approach to unifying these two types of declarative languages.