Model transformation: Difference between revisions

Content deleted Content added
Citation bot (talk | contribs)
m Alter: template type, journal. Add: isbn, series, journal, citeseerx, pages, issue, volume. Removed parameters. Formatted dashes. | You can use this bot yourself. Report bugs here. | User-activated.
 
(9 intermediate revisions by 6 users not shown)
Line 1:
{{Data transformation}}
A '''model transformation''', in [[model-driven engineering]], is an automated way of modifying and creating models. An example use of model transformation is ensuring that a family of [[Computer model|model]]s is consistent, in a precise sense which the software engineer can define. The aim of using a model transformation is to save effort and reduce errors by automating the building and modification of models where possible.
 
A '''model transformation''', in [[model-driven engineering]], is an automated way of modifying and creating models[[platform-specific model]] from platform-independent ones. An example use of model transformation is ensuring that a family of [[Computer model|model]]s is consistent, in a precise sense which the software engineer can define. The aim of using a model transformation is to save effort and reduce errors by automating the building and modification of models where possible.
 
== Overview ==
Line 17 ⟶ 19:
=== Endogenous versus exogenous ===
 
Endogenous transformations are transformations between models expressed in the same language. Exogenous transformations are transformations between models expressed using different languages.<ref>Tom Mens, Pieter Van Gorp: A Taxonomy of Model Transformation. Electr. Notes Theor. Comput. Sci. 152: 125-142 (2006)</ref> For example, in a process conforming to the [[Object Management Group|OMG]] [[Model Driven Architecture]], a [[platform-independent model]] might be transformed into a [[platform-specific model]] by an exogenous model transformation.
 
=== Unidirectional versus bidirectional ===
Line 69 ⟶ 71:
| doi=10.1007/978-3-540-88643-3_10
| last=Stevens
| journalfirst=Perdita | title=Generative and Transformational Techniques in Software Engineering II
| first=Perdita
| titlechapter=OnA the UseLandscape of Higher-OrderBidirectional Model Transformations
| title=A landscape of bidirectional model transformations
|author-link=Perdita Stevens
| journal=Generative and Transformational Techniques in Software Engineering II
| volume=5235
| pages=408–424
Line 77 ⟶ 79:
| year=2008| series=Lecture Notes in Computer Science
| isbn=978-3-540-88642-6
| chapter-url=https://www.research.ed.ac.uk/en/publications/f1706efc-3370-472c-b506-bd65680a04b6
}}
</ref>
 
Line 84 ⟶ 87:
| doi=10.1007/s10270-008-0109-9
| last=Stevens
| first=Perdita |author-link=Perdita Stevens
| title=Bidirectional model transformations in QVT: semantic issues and open questions
| year=2010
| journal=Software and Systems Modeling| volume=9
| pages=7–20
| s2cid=371579
}}
| url=https://www.pure.ed.ac.uk/ws/files/12628301/bidirectional.pdf
}}
</ref>
 
Line 97 ⟶ 102:
| last=Tisi
| first=Massimo
| title=Model Driven Architecture - Foundations and Applications
| title=On the Use of Higher-Order Model Transformations
| chapter=On the Use of Higher-Order Model Transformations
| publisher=[[Springer Publishing|Springer]]
| year=2009
Line 128 ⟶ 134:
| journal=Science of Computer Programming| volume=85
| pages=41–99
| doi-access=free
}}
</ref>