The Event Coordination Notation: Execution Engine and Programming Framework
Publication: Research - peer-review › Article in proceedings – Annual report year: 2012
Standard
The Event Coordination Notation: Execution Engine and Programming Framework. / Kindler, Ekkart.
In: BM-FA '12 Proceedings of the Fourth Workshop on Behaviour Modelling - Foundations and Applications . Association for Computing Machinery, 2012. p. 8.Publication: Research - peer-review › Article in proceedings – Annual report year: 2012
Harvard
APA
CBE
MLA
Vancouver
Author
Bibtex
}
RIS
TY - GEN
T1 - The Event Coordination Notation: Execution Engine and Programming Framework
A1 - Kindler,Ekkart
AU - Kindler,Ekkart
PB - Association for Computing Machinery
PY - 2012
Y1 - 2012
N2 - ECNO (Event Coordination Notation) is a notation for modelling the behaviour of a software system on top of some object-oriented data model. ECNO has two main objectives: On the one hand, ECNO should allow modelling the behaviour of a system on the domain level; on the other hand, it should be possible to completely generate code from ECNO and the underlying object-oriented domain models. Today, there are several approaches that would allow to do this. But, most of them would require that the data models and the behaviour models are using the same technology and the code is generated together. By contrast, ECNO can be used for modelling the behaviour on top of any object-oriented model - or even on top of manually written object-oriented code. This way, it is easy to integrate ECNO models with other technologies, to use ECNO on top of code generated by other technologies or with code that was written manually. In this paper, we rephrase the main concepts of ECNO. The focus of this paper, however, is on the architecture of the ECNO execution engine and its programming framework. We will show how this framework allows us to integrate ECNO with object-oriented models, how it works without any explicit control, and how it easily integrates with traditional programming.
AB - ECNO (Event Coordination Notation) is a notation for modelling the behaviour of a software system on top of some object-oriented data model. ECNO has two main objectives: On the one hand, ECNO should allow modelling the behaviour of a system on the domain level; on the other hand, it should be possible to completely generate code from ECNO and the underlying object-oriented domain models. Today, there are several approaches that would allow to do this. But, most of them would require that the data models and the behaviour models are using the same technology and the code is generated together. By contrast, ECNO can be used for modelling the behaviour on top of any object-oriented model - or even on top of manually written object-oriented code. This way, it is easy to integrate ECNO models with other technologies, to use ECNO on top of code generated by other technologies or with code that was written manually. In this paper, we rephrase the main concepts of ECNO. The focus of this paper, however, is on the architecture of the ECNO execution engine and its programming framework. We will show how this framework allows us to integrate ECNO with object-oriented models, how it works without any explicit control, and how it easily integrates with traditional programming.
KW - Computer applications
KW - Models
U2 - 10.1145/2325276.2325279
DO - 10.1145/2325276.2325279
SN - 978-1-4503-1187-8
BT - BM-FA '12 Proceedings of the Fourth Workshop on Behaviour Modelling - Foundations and Applications
T2 - BM-FA '12 Proceedings of the Fourth Workshop on Behaviour Modelling - Foundations and Applications
SP - 8
ER -