Formal Specification of Domain-Specific ECA Policy Models

Romeikat, Raphael; Bauer, Bernhard

doi:10.1109/tase.2011.29

Cited by 1 publication

(1 citation statement)

References 10 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Models are specified using CML, which contain representations of concepts relevant in the user-centric communication domain [65]. we utilize the Event Condition Action (ECA) policy model [49], where events are control script commands being realized or events from the underlying layer being responded to, conditions are state information retrievable directly from the middleware or through an external monitor, and actions are accompanying actions that must be performed when realizing the initially requested command or the action association with the event being responded to.…”

Section: And Cvmmentioning

confidence: 99%

A Middleware to Support Services Delivery in a Domain-Specific Virtual Machine

Morris¹

View full text Add to dashboard Cite

The increasing use of model-driven software development has renewed emphasis on using domain-specific models during application development. More specifically, there has been emphasis on using domain-specific modeling languages (DSMLs) to capture user-specified requirements when creating applications. The current approach to realizing these applications is to translate DSML models into source code using several model-to-model and model-to-code transformations. This approach is still dependent on the underlying source code representation and only raises the level of abstraction during development. Experience has shown that developers will many times be required to manually modify the generated source code, which can be error-prone and time consuming.An alternative to the aforementioned approach involves using an interpreted domain-specific modeling language (i-DSML) whose models can be directly executed using a Domain Specific Virtual Machine (DSVM). Direct execution of i-DSML models require a semantically rich platform that reduces the gap between the application models and the underlying services required to realize the application. One layer in this platform is the domain-specific middleware that is responsible for the management and delivery of services in the specific domain.In this dissertation, we investigated the problem of designing the domain-specific middleware of the DSVM to facilitate the bifurcation of the semantics of the dovi main and the model of execution (MoE) while supporting runtime adaptation and validation. We approached our investigation by seeking solutions to the following sub-problems: (1) How can the domain-specific knowledge (DSK) semantics be separated from the MoE for a given domain? (2) How do we define a generic model of execution (GMoE) of the middleware so that it is adaptable and realizes DSK operations to support delivery of services? (3) How do we validate the realization of DSK operations at runtime?Our research into the domain-specific middleware was done using an i-DSML for the user-centric communication domain, Communication Modeling Language (CML), and for microgrid energy management domain, Microgrid Modeling Language (MGridML). We have successfully developed a methodology to separate the DSK and GMoE of the middleware of a DSVM that supports specialization for a given domain, and is able to perform adaptation and validation at runtime.

show abstract

Section: And Cvmmentioning

confidence: 99%

A Middleware to Support Services Delivery in a Domain-Specific Virtual Machine

Morris¹

View full text Add to dashboard Cite

show abstract

Formal Specification of Domain-Specific ECA Policy Models

Cited by 1 publication

References 10 publications

A Middleware to Support Services Delivery in a Domain-Specific Virtual Machine

A Middleware to Support Services Delivery in a Domain-Specific Virtual Machine

Contact Info

Product

Resources

About