- dead line for submission : april
17
- held on : monday, june
18
- location: room Mon -1.63/P48B, Eotvos Lorand University, Budapest,
Hungary (Ecoop ws staff will provide a local map for the room arrangements
later)
Associated Url:
http://adaptiveobjectmodel.com/ECOOP2001/
and/or
http://www-poleia.lip6.fr/~revault/research/ecoop01ws
A system with an Adaptive Object-Model (AOM) has an explicit object model that it interprets at run-time. If you change the object model, the system changes its behavior. For example, a lot of workflow systems have an Adaptive Object-Model. Objects have states and respond to events by changing state. The Adaptive Object-Model defines the objects, their states, the events, and the conditions under which an object changes state.
There are various techniques that share common features with AOM's.
Especially, those that try also to capture business rules and build domain
specific languages, namely – Grammar-oriented Object Design (applied in the
three major areas of configurable workflow, tier-to-tier mapping and object
graph traversal) or – Meta-CASE tools and environments approaches, à la
MetaEdit+ or à la MétaGen (applied in various fields of information system
modeling: telecom, finance, medicine, etc.). There are other techniques which
also describe ways to build systems that change behavior at runtime, namely – Reflection
at the language level (mostly applied to programming language design). What is
actually common to those various techniques is that they are leading to, or are
driven by, metamodeling principles and implementation using OO languages.
This workshop will focus on identifying, cataloging and comparing these
techniques one towards another. We will also try to establish the conditions of
use of these techniques, look at where they meet or overlap, and hopefully set
some cross-fertilization ideas of benefit for each technique.
(develop all sections here)