The great variety of CASE tools available on the market implies a need for data interchange. One approach to satisfying this need is the export and import of models. For this to be vendor independent requires standardized common interchange formats, either in the form of meta-models or a common transfer format. CASE tools use some type of explicit or implicit design transformations to transform different types of models, for example conceptual to logical. The transformations are important for interchange since a set of models which are consistent in one tool may be inconsistent in another tool that does not support the same set of transformations. Subsequent modification in the latter tool may lead to irresolvable inconsistencies. In this paper we define a common, model independent notation for design transformations to facilitate interchange between tools so that the meaning of different transformations can remain consistent between different CASE tools. The proposal is made in the form of a conservative extension to OCL. A run-time interpreter for the extension has been built.
[1]
Ramez Elmasri,et al.
Fundamentals of Database Systems
,
1989
.
[2]
Jean-Luc Hainaut,et al.
Specification Preservation in Schema Transformations - Application to Semantics and Statistics
,
1996,
Data Knowl. Eng..
[3]
Mohamed E. Fayad.
Review of SanFrancisco component framework: An introduction by Paul Monday, James Carey, and Mary Dangler Addison-Wesley Longman, Inc., Reading, MA, 2000
,
2000
.
[4]
Louise Scott,et al.
Issues in software engineering tool construction
,
2000,
Inf. Softw. Technol..
[5]
C. J. Date.
An introduction to database systems (7. ed.)
,
1999
.
[6]
Anneke Kleppe,et al.
Extending OCL to include Actions
,
2000,
UML.
[7]
Alexandra Poulovassilis,et al.
A Uniform Approach to Inter-model Transformations
,
1999,
CAiSE.
[8]
Jos Warmer,et al.
The object constraint language
,
1998
.
[9]
S. Brinkkemper,et al.
Integrating diagrams in CASE tools through modelling transparency
,
1993,
Inf. Softw. Technol..