Where object-oriented languages deal with objects as described by classes, model-driven development uses models, as graphs of interconnected objects, described by metamodels. A number of new languages have been and continue to be developed for this model-based paradigm, both for model transformation and for general programming using models. Many of these use single-object approaches to typing, derived from solutions found in object-oriented systems, while others use metamodels as model types, but without a clear notion of polymorphism. Both of these approaches lead to brittle and overly restrictive reuse characteristics. In this paper we propose a simple extension to object-oriented typing to better cater for a model-oriented context, including a simple strategy for typing models as a collection of interconnected objects. Using a simple example we show how this extended approach permits more flexible reuse, while preserving type safety.
%0 Book Section
%1 steel_05_model
%A Steel, Jim
%A J'ez'equel, Jean M.
%D 2005
%J Model Driven Engineering Languages and Systems
%K _hardcopy mde reuse 2005 _folder_2 model_typing
%P 84--96
%R 10.1007/11557432_7
%T Model Typing for Improving Reuse in Model-Driven Engineering
%U http://dx.doi.org/10.1007/11557432_7
%X Where object-oriented languages deal with objects as described by classes, model-driven development uses models, as graphs of interconnected objects, described by metamodels. A number of new languages have been and continue to be developed for this model-based paradigm, both for model transformation and for general programming using models. Many of these use single-object approaches to typing, derived from solutions found in object-oriented systems, while others use metamodels as model types, but without a clear notion of polymorphism. Both of these approaches lead to brittle and overly restrictive reuse characteristics. In this paper we propose a simple extension to object-oriented typing to better cater for a model-oriented context, including a simple strategy for typing models as a collection of interconnected objects. Using a simple example we show how this extended approach permits more flexible reuse, while preserving type safety.
@incollection{steel_05_model,
abstract = {Where object-oriented languages deal with objects as described by classes, model-driven development uses models, as graphs of interconnected objects, described by metamodels. A number of new languages have been and continue to be developed for this model-based paradigm, both for model transformation and for general programming using models. Many of these use single-object approaches to typing, derived from solutions found in object-oriented systems, while others use metamodels as model types, but without a clear notion of polymorphism. Both of these approaches lead to brittle and overly restrictive reuse characteristics. In this paper we propose a simple extension to object-oriented typing to better cater for a model-oriented context, including a simple strategy for typing models as a collection of interconnected objects. Using a simple example we show how this extended approach permits more flexible reuse, while preserving type safety.},
added-at = {2009-02-11T21:04:07.000+0100},
author = {Steel, Jim and J'{e}z'{e}quel, Jean M.},
biburl = {https://www.bibsonomy.org/bibtex/2238b803fc346450f82f0b14eb27af4b5/leonardo},
citeulike-article-id = {1822909},
doi = {10.1007/11557432_7},
interhash = {cd4ffbd623251a93f1d43a5b1fbf3b6d},
intrahash = {238b803fc346450f82f0b14eb27af4b5},
journal = {Model Driven Engineering Languages and Systems},
keywords = {_hardcopy mde reuse 2005 _folder_2 model_typing},
pages = {84--96},
posted-at = {2007-10-26 01:55:12},
priority = {4},
timestamp = {2009-02-11T21:04:07.000+0100},
title = {Model Typing for Improving Reuse in Model-Driven Engineering},
url = {http://dx.doi.org/10.1007/11557432_7},
year = 2005
}