Differences

This shows you the differences between two versions of the page.

--- research:modelling [2006/11/09 14:17] – created stijnm
+++ research:modelling [2006/11/09 19:50] (current) – stijnm
@@ Line 3: / Line 3: @@
 [[http://prog.vub.ac.be/~evpaessc/|Ellen Van Paesschen]]
 [[http://prog.vub.ac.be/~smostinc/|Stijn Mostinckx]]
+[[http://www2.lifl.fr/~dhondt/|Maja D'Hondt]]
 ===== Context =====
@@ Line 8: / Line 9: @@
 needs to be developed.
-The development of such co-operative software typically focusses on either the computation level or the domain level. The former is concerned with developing computation models and programming languages that take the inherent characteristics of mobile networks into account. The latter is concerned with high-level concerns on how the software allows its user to interact with (the devices in) their environment.
+The development of such co-operative software typically focusses on either the computational level or the domain level. The former is concerned with developing computation models and programming languages that take the inherent characteristics of mobile networks into account. The latter is concerned with high-level concerns on how the software allows its user to interact with (the devices in) their environment.
-We observe that there is a gap between the two aforementioned levels. On one hand, the computational level strives for the development of programming idioms to deal with the inherent and very stringent hardware phenomena of mobile networks. On the other hand, the domain level is concerned with addressing the expected behaviour of the system, e.g. how and when a system responds to changes in the context, when information can be made public etc. Nevertheless, both levels have to co-exist: the computing level needs to be steered by the constraints and rules which exist at the domain level, whereas the domain needs to adapt to the particulars of the ever-changing mobile network that is monitored and managed at the computing level.
+We observe that there is a gap between the two aforementioned levels. On one hand, the computational level strives for the development of programming idioms to deal with the inherent and very stringent hardware phenomena of mobile networks. On the other hand, the domain level is concerned with addressing the expected behaviour of the system, e.g. how and when a system responds to changes in the context, when information can be made public etc. Nevertheless, both levels have to co-exist: the computational level needs to be steered by the constraints and rules which exist at the domain level, whereas the domain needs to adapt to the particulars of the ever-changing mobile network that is monitored and managed at the computational level.
 ===== Co-Existence of Models and Programs =====
@@ Line 22: / Line 23: @@
 ===== Ambient-Oriented Programming =====
-Software development for ambient intelligence requires a paradigmatic shift at the computation level. Networks of mobile devices are inherently dynamic and unreliable. Programming software for such a setting in a conventional (synchronous, thread-based) model would forego the very nature of the problem one is addressing. Indeed, when programming for ambient intelligence one can no longer abstract from an inherently event-based reality.
+Software development for ambient intelligence requires a paradigmatic shift at the computational level. Networks of mobile devices are inherently dynamic and unreliable. Programming software for such a setting in a conventional (synchronous, thread-based) model would forego the very nature of the problem one is addressing. Indeed, when programming for ambient intelligence one can no longer abstract from an inherently event-based reality.
 In previous work, we have proposed the ambient-oriented programming paradigm which reconciles traditional programming techniques with the inherently event-based nature of the underlying networks. The work encompasses various communication strategies [3] as well as abstractions for service discovery in a mobile environment [4].
@@ Line 28: / Line 29: @@
 ===== Ambient-Oriented Modelling =====
-Our goal is to bridge the gap between the computation level and the domain level in AmI. We intend to transfer our previous work on the co-existence of models and programs to the field of AmI. We propose to represent knowledge of the AmI domain in models and synchronise them with a dedicated ambient-oriented programming language which expresses the computation level. The models can represent concepts but also behaviour of the domain, such as interaction protocols and policy rules. Moreover, the models have a live link with the computation level, such that certain adaptations, driven from the domain, can be made via the models and propagated to the computation level. The other way around, models being synchronised when the computation level changes, is also supported for relevant aspects of the computation level. Since the notions at the computation level are different from the domain concepts, there will not always be a trivial one-to-one mapping from the one to the other. Furthermore, since the targets are mobile devices, the implementation of the models and their link with the computation level has to be efficient both in terms of space and time.
+Our goal is to bridge the gap between the computational level and the domain level in AmI. We intend to transfer our previous work on the co-existence of models and programs to the field of AmI. We propose to represent knowledge of the AmI domain in models and synchronise them with a dedicated ambient-oriented programming language which expresses the computational level. The models can represent concepts but also behaviour of the domain, such as interaction protocols and policy rules. Moreover, the models have a live link with the computational level, such that certain adaptations, driven from the domain, can be made via the models and propagated to the computation level. The other way around, models being synchronised when the computational level changes, is also supported for relevant aspects of the computational level. Since the notions at the computational level are different from the domain concepts, there will not always be a trivial one-to-one mapping from the one to the other. Furthermore, since the targets are mobile devices, the implementation of the models and their link with the computation level has to be efficient both in terms of space and time.
 ===== References =====
   - **SelfSync: A Dynamic Round-Trip Engineering Environment** Ellen Van Paesschen, Wolfgang De Meuter, Maja D'Hondt //In "Proceedings of the ACM/IEEE 8th International Conference on Model-Driven Engineering Languages and Systems (MoDELS'05 - formerly UML conference series), October, Montego Bay, Jamaica", 2005//
-  - **Mapping High-level Business Rules to and through Aspects** Maria Agustina Cibrán, Maja D'Hondt, Viviane Jonckers //Journal L’Objet, vol. 12, no. 2-3 (April-September 2006), Hèrmes.//
+  - **A Slice of MDE with AOP: Transforming High-Level Business Rules to Aspects** María Agustina Cibrán and Maja D’Hondt //In "Proceedings of the ACM/IEEE 9th International Conference on Model-Driven Engineering Languages and Systems (MoDELS'06 - formerly UML conference series), October, Genoa, Italy" 2006.//
   - **Ambient-Oriented Programming in AmbientTalk** Jessie Dedecker, Tom Van Cutsem, Stijn Mostinckx, Theo D'Hondt, Wolfgang De Meuter //In "Proceedings of the 20th European Conference on Object-Oriented Programming (ECOOP), Dave Thomas (Ed.), Lecture Notes in Computer Science Vol. 4067, pp. 230-254, Springer-Verlag", 2006//
   - **Ambient References: Addressing Objects in Mobile Networks** Tom Van Cutsem, Jessie Dedecker, Stijn Mostinckx, Elisa Gonzalez Boix, Theo D'Hondt, Wolfgang De Meuter //In "Proceedings of the Dynamic Language Symposium - OOPSLA '06: Companion of the 21st annual ACM SIGPLAN Conference on Object-Oriented Programming, Systems, Languages and Applications. Portland, U.S.A.", 2006//