Management of multiple models in an extensible database design tool

Atzeni, Paolo; Torlone, Riccardo

doi:10.1007/bfb0014144

Cited by 51 publications

(74 citation statements)

References 11 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…The starting point for our work is the MDM proposal [4], whose principles are as follows. A metamodel is a set of constructs that can be used to define models, which are instances of the metamodel.…”

Section: Background Contribution and Related Workmentioning

confidence: 99%

“…The description of models in terms of the (meta-)constructs of a metamodel was proposed by Atzeni and Torlone [4]. But it used a sophisticated graph language, which was hard to implement.…”

Section: Background Contribution and Related Workmentioning

confidence: 99%

“…An early approach to ModelGen was proposed by Atzeni and Torlone [4,5] who developed a tool, called MDM, to manage heterogeneous schemas based on a notion of metamodel. A metamodel is a set of constructs (the metaconstructs) that can be used to define models.…”

Section: Introductionmentioning

confidence: 99%

See 2 more Smart Citations

A Multilevel Dictionary for Model Management

Atzeni

Cappellari

Bernstein

2005

Conceptual Modeling – ER 2005

Self Cite

View full text Add to dashboard Cite

Abstract. We discuss the main features of a multilevel dictionary based on a metamodel approach. The application is an implementation of ModelGen, the model management operator that translates schemas from one model to another, for example from ER to relational or from XSD to object. The dictionary manages schemas and, at a metalevel, a description of the models of interest. It describes all models in terms of a limited set of metaconstructs. It describes all the schemas in a unifying model, called the supermodel, which generalizes all the others. The dictionary is composed of four parts, based on the combination of two features: schema level or model level, and model specific or model generic. We also show how such a dictionary can be the basis for a model independent approach to reporting, that provides a detailed textual and XML description of schemas.

show abstract

Section: Background Contribution and Related Workmentioning

confidence: 99%

“…The description of models in terms of the (meta-)constructs of a metamodel was proposed by Atzeni and Torlone [4]. But it used a sophisticated graph language, which was hard to implement.…”

Section: Background Contribution and Related Workmentioning

confidence: 99%

See 1 more Smart Citation

A Multilevel Dictionary for Model Management

Atzeni

Cappellari

Bernstein

2005

Conceptual Modeling – ER 2005

Self Cite

View full text Add to dashboard Cite

show abstract

“…This has usually been done by adopting some "universal data model," a model that is more general than the various models of interest in a heterogeneous framework. In the literature, such a data model is called universal metamodel [11] or supermodel [3,6]. If the operations of interest also include translations from a data model to another (the modelgen operator), it is important that the individual data models are represented, in such a way that it becomes possible to describe the fact that a schema belongs to a data model.…”

Section: Introductionmentioning

confidence: 99%

MISM: A Platform for Model-Independent Solutions to Model Management Problems

Atzeni

Bellomarini

Bugiotti

et al. 2009

Journal on Data Semantics XIV

Self Cite

View full text Add to dashboard Cite

Abstract. Model management is a metadata-based approach to database problems aimed at supporting the productivity of developers by providing schema manipulation operators. Here we propose MISM (Model Independent Schema Management), a platform for model management offering a set of operators to manipulate schemas, in a manner that is both model-independent (in the sense that operators are generic and apply to schemas of different data models) and model-aware (in the sense that it is possible to say whether a schema is allowed for a data model). This is the first proposal for model management in this direction. We consider the main operators in model management: merge, diff, and modelgen. These operators play a major role in solving various problems related to schema evolution (such as data integration, data exchange or forward engineering), and we show in detail a solution to a major representative of the class, the round-trip engineering problem.

show abstract

“…operations that manipulate models and mappings). There have been earlier approaches to model management [1,12], which did address especially the transformation of models between different metamodels. Model management has become more important recently, as the integration of information systems requires the management of complex models.…”

Section: Model Managementmentioning

confidence: 99%

GeRoMe: A Generic Role Based Metamodel for Model Management

Kensche

Quix

Chatti

et al.

Journal on Data Semantics VIII

View full text Add to dashboard Cite

Abstract. The goal of Model Management is the development of new technologies and mechanisms to support the integration, evolution and matching of models. Such tasks are to be performed by means of a set of model management operators which work on models and their elements, without being restricted to a particular metamodel (e.g. the relational or UML metamodel). We propose that generic model management should employ a generic metamodel (GMM) which serves as an abstraction of the features of particular metamodels while preserving the semantics of its different elements. A naive generalization of the elements of concrete metamodels in generic metaclasses would loose some of the specific features of the metamodels, or yield a prohibitive number of metaclasses in the GMM. To avoid these problems, we propose the Generic Role Based Metamodel GeRoMe in which each model element is decorated with a set of role objects that represent specific properties of the model element. Roles may be added to or removed from elements at any time, which enables a very flexible and dynamic yet accurate definition of models. Roles constitute to operators different views on the same model element. Thus, operators concentrate on features which affect their functionality but may remain agnostic about other features. Consequently, these operators can use polymorphism and have to be implemented only once using GeRoMe, and not for each specific metamodel. We verified our results by implementing GeRoMe and a selection of model management operators using our metadata system ConceptBase.

show abstract

Management of multiple models in an extensible database design tool

Cited by 51 publications

References 11 publications

A Multilevel Dictionary for Model Management

A Multilevel Dictionary for Model Management

MISM: A Platform for Model-Independent Solutions to Model Management Problems

GeRoMe: A Generic Role Based Metamodel for Model Management

Contact Info

Product

Resources

About