Jump to content

UML-RSDS: Difference between revisions

From Wikipedia, the free encyclopedia
Content deleted Content added
Added reliable sources
Citation bot (talk | contribs)
Removed proxy/dead URL that duplicated identifier. Removed parameters. | Use this bot. Report bugs. | Suggested by Corvus florensis | #UCB_webform 945/2500
 
(21 intermediate revisions by 13 users not shown)
Line 1: Line 1:
{{Short description|Model-transformation language (software)}}
{{AFC submission|d|v|u=92.19.74.54|ns=118|decliner=Pbritti|declinets=20230223025036|ts=20230220190528}} <!-- Do not remove this line! -->
{{AFC submission|d|v|u=2.101.89.142|ns=118|decliner=S0091|declinets=20230219210827|reason2=context|small=yes|ts=20230219180147}} <!-- Do not remove this line! -->


{{AFC comment|1=Still significant lack of sourcing. [[User:Pbritti|Pbritti]] ([[User talk:Pbritti|talk]]) 02:50, 23 February 2023 (UTC)}}

{{AFC comment|1=Most of the content is unsourced and the content is quite technical for the average reader. Also keep in mind what the developers/those involved say about the tool is not useful. Only summarize what secondary reliable sources with no connection have written about it. [[User:S0091|S0091]] ([[User talk:S0091|talk]]) 21:08, 19 February 2023 (UTC)}}

{{AFC comment|1=Please move external links to External link section at the end. —[[User:Anomalocaris|Anomalocaris]] ([[User talk:Anomalocaris|talk]]) 20:15, 19 February 2023 (UTC)}}

----

{{Short description|Model-transformation language (software)}}
{{COI|date=February 2023}}
{{COI|date=February 2023}}
{{Draft topics|software|computing|technology}}
{{AfC topic|stem}}

'''UML-RSDS''' is a lightweight [[Model-driven engineering]] (MDE) and [[Model transformation]] tool supporting the [[UML]] 2.5 class diagram notation and OCL 2.4 [[Object Constraint Language]]. It supports code-generation in multiple 3GLs: [[Java (programming language)|Java]], [[C Sharp (programming language)|C#]], [[C++]], [[Python (programming language)|Python]], [[Go (programming language)|Go]], [[Swift (programming language)|Swift]] and [[ANSI C]].


'''UML-RSDS''' is a lightweight [[model-driven engineering]] (MDE) and [[model transformation]] tool supporting the [[Unified Modeling Language|UML]] 2.5 class diagram notation and OCL 2.4 [[Object Constraint Language]]. It supports code-generation in multiple 3GLs: [[Java (programming language)|Java]], [[C Sharp (programming language)|C#]], [[C++]], [[Python (programming language)|Python]], [[Go (programming language)|Go]], [[Swift (programming language)|Swift]] and [[ANSI C]].
The toolset has been defined as an Eclipse project AgileUML under the modeling category.<ref>https://projects.eclipse.org/projects/modeling.agileuml</ref>.


The toolset has been defined as an Eclipse project AgileUML under the modeling category.<ref>{{cite web | url=https://projects.eclipse.org/projects/modeling.agileuml | title=Agile UML | date=5 February 2019 }}</ref>
The toolset repository is hosted on GitHub. A book on UML-RSDS is published by CRC Press<ref>https://www.amazon.co.uk/Agile-Model-Based-Development-Using-UML-RSDS-ebook/dp/B06VWZ7NTP/</ref>.


The toolset originated from EPSRC-funded research at Imperial College and King's College London in the period 1996–2014. It was publicly released in 2010 and defined as an Eclipse project in 2019. It is now supported by AgileMDE Ltd: agilemde.co.uk.
The toolset originated from EPSRC-funded research at Imperial College and King's College London in the period 1996–2014. It was publicly released in 2010 and defined as an Eclipse project in 2019. It is now supported by AgileMDE Ltd: agilemde.co.uk.


One motivation of the tools has been to provide a means for general software practitioners to use MDE in a flexible manner, to support agile development using MDE. The tool has been applied to financial software development<ref>{{Cite conference|url=https://link.springer.com/chapter/10.1007/978-3-030-01042-3_14 |first1=Hessa |last1=Alfraihi |title=The Impact of Integrating Agile Software Development and Model-Driven Development: A Comparative Case Study |date=2018}}</ref> and to many different kinds of transformation problems, for example<ref>{{Cite journal|url=https://www.sciencedirect.com/science/article/pii/S0167642313002803|title=A survey and comparison of transformation tools based on the transformation tool contest|first1=Edgar|last1=Jakumeit|first2=Sebastian|last2=Buchwald|first3=Dennis|last3=Wagelaar|first4=Li|last4=Dan|first5=Ábel|last5=Hegedüs|first6=Markus|last6=Herrmannsdörfer|first7=Tassilo|last7=Horn|first8=Elina|last8=Kalnina|first9=Christian|last9=Krause|first10=Kevin|last10=Lano|first11=Markus|last11=Lepper|first12=Arend|last12=Rensink|first13=Louis|last13=Rose|first14=Sebastian|last14=Wätzoldt|first15=Steffen|last15=Mazanek|date=June 1, 2014|journal=Science of Computer Programming|volume=85|pages=41–99|via=ScienceDirect|doi=10.1016/j.scico.2013.10.009}}</ref><ref>{{Cite journal|url=https://doi.org/10.1007/s10270-012-0245-0|title=Graph and model transformation tools for model migration|first1=Louis M.|last1=Rose|first2=Markus|last2=Herrmannsdoerfer|first3=Steffen|last3=Mazanek|first4=Pieter|last4=Van Gorp|first5=Sebastian|last5=Buchwald|first6=Tassilo|last6=Horn|first7=Elina|last7=Kalnina|first8=Andreas|last8=Koch|first9=Kevin|last9=Lano|first10=Bernhard|last10=Schätz|first11=Manuel|last11=Wimmer|date=February 1, 2014|journal=Software & Systems Modeling|volume=13|issue=1|pages=323–359|via=Springer Link|doi=10.1007/s10270-012-0245-0}}</ref>
One motivation of the tools has been to provide a means for general software practitioners to use MDE in a flexible manner, to support agile development using MDE. The tool has been applied to financial software development<ref>{{Cite conference|chapter-url=https://link.springer.com/chapter/10.1007/978-3-030-01042-3_14 |first1=Hessa |last1=Alfraihi |title=System Analysis and Modeling. Languages, Methods, and Tools for Systems Engineering |chapter=The Impact of Integrating Agile Software Development and Model-Driven Development: A Comparative Case Study |series=Lecture Notes in Computer Science |date=2018|volume=11150 |pages=229–245 |doi=10.1007/978-3-030-01042-3_14 |isbn=978-3-030-01041-6 }}</ref> and to many different kinds of transformation problems, for example<ref>{{Cite journal|title=A survey and comparison of transformation tools based on the transformation tool contest|first1=Edgar|last1=Jakumeit|first2=Sebastian|last2=Buchwald|first3=Dennis|last3=Wagelaar|first4=Li|last4=Dan|first5=Ábel|last5=Hegedüs|first6=Markus|last6=Herrmannsdörfer|first7=Tassilo|last7=Horn|first8=Elina|last8=Kalnina|first9=Christian|last9=Krause|first10=Kevin|last10=Lano|first11=Markus|last11=Lepper|first12=Arend|last12=Rensink|first13=Louis|last13=Rose|first14=Sebastian|last14=Wätzoldt|first15=Steffen|last15=Mazanek|date=June 1, 2014|journal=Science of Computer Programming|volume=85|pages=41–99|doi=10.1016/j.scico.2013.10.009|doi-access=free}}</ref><ref>{{Cite journal|url=https://doi.org/10.1007/s10270-012-0245-0|title=Graph and model transformation tools for model migration|first1=Louis M.|last1=Rose|first2=Markus|last2=Herrmannsdoerfer|first3=Steffen|last3=Mazanek|first4=Pieter|last4=Van Gorp|first5=Sebastian|last5=Buchwald|first6=Tassilo|last6=Horn|first7=Elina|last7=Kalnina|first8=Andreas|last8=Koch|first9=Kevin|last9=Lano|first10=Bernhard|last10=Schätz|first11=Manuel|last11=Wimmer|date=February 1, 2014|journal=Software & Systems Modeling|volume=13|issue=1|pages=323–359|via=Springer Link|doi=10.1007/s10270-012-0245-0|s2cid=254172124 }}</ref>


== Language characteristics ==
== Language characteristics ==
The main specification notations in UML-RSDS are [[Unified Modeling Language|UML]] class diagrams and use cases, together with [[Object Constraint Language]] (OCL)

expressions, used to define invariants and operation pre and post-conditions.<ref>{{cite book | url=https://www.taylorfrancis.com/books/mono/10.1201/9781315368153/agile-model-based-development-using-uml-rsds-kevin-lano | doi=10.1201/9781315368153 | title=Agile Model-Based Development Using UML-RSDS | year=2017 | last1=Lano | first1=Kevin | isbn=9781498752237 }}</ref> Either a graphical or textual notation can be used for UML-RSDS
The main specification notations in UML-RSDS are [[UML]] class diagrams and use cases, together with [[Object Constraint Language]] (OCL)
specifications.
expressions, used to define invariants and operation pre and post-conditions. Either a graphical or textual notation can be used for UML-RSDS
specifications.


For example, a simple class specification could be written as:
For example, a simple class specification could be written as:


<syntaxhighlight >
<syntaxhighlight lang="text">
class Person {
class Person {
attribute age: int;
attribute age: int;
attribute name: String;
attribute name: String;


operation birthday()
operation birthday()
pre: true
pre: true
post: age = age@pre + 1;
post: age = age@pre + 1;
}
}
</syntaxhighlight >
</syntaxhighlight>


Transformations are defined as use cases together with constraints expressing how result data is derived from input data.<ref>{{cite book | chapter-url=https://ieeexplore.ieee.org/document/8101243 | doi=10.1109/MODELS.2017.21 | chapter=On Additivity in Transformation Languages | title=2017 ACM/IEEE 20th International Conference on Model Driven Engineering Languages and Systems (MODELS) | year=2017 | last1=Hidaka | first1=Sochiro | last2=Jouault | first2=Frederic | last3=Tisi | first3=Massimo | pages=23–33 | isbn=978-1-5386-3492-9 | s2cid=9109050 | url=https://hal.archives-ouvertes.fr/hal-01566259/file/models2017-additivity.pdf }}</ref> Thus a declarative specification style similar to the [[QVT]] relations language is supported, but without the need to define additional syntax or language elements - only OCL is used. For example, to copy every person instance to a 'PersonRecord' with a 'data' attribute formed from the name and age, it is sufficient to write:
Transformations are defined as use cases together with
constraints expressing how result data is derived from input data. Thus a declarative specification style similar to the [[QVT]] relations language is supported, but without the need to define additional syntax or language elements - only OCL is used. For example, to copy every person instance to a 'PersonRecord' with a 'data' attribute formed from the name and age, it is sufficient to write:


<syntaxhighlight >
<syntaxhighlight lang="text">
usecase copyPersons {
usecase copyPersons {
Person::
Person::
PersonRecord->exists( r | r.data = name + age )
PersonRecord->exists( r | r.data = name + age )
}
}
</syntaxhighlight >
</syntaxhighlight>


Verification procedures have been defined for this style of transformation specification.<ref>{{cite journal | url=https://www.ingentaconnect.com/content/ben/rascs/2020/00000013/00000002/art00021 | doi=10.2174/2213275912666190129121059 | title=A Comparative Study on Transformation of UML/OCL to Other Specifications | year=2020 | last1=Thangaraj | first1=Jagadeeswaran | last2=Ulaganathan | first2=Senthilkumaran | journal=Recent Advances in Computer Science and Communications | volume=13 | issue=2 | pages=256–264 | s2cid=86744559 }}</ref>
For more general software applications, procedural-style code using statements such as assignment (:=), loops (while, for), conditionals (if then else) and sequencing (;) can be used to define operation and usecase behaviour. These statements correspond to a text version of UML activity models.


For more general software applications, procedural-style code using statements such as assignment ({{mono|1=:=}}), loops ({{mono|while, for}}), conditionals ({{mono|if then else}}) and sequencing ({{char|;}}) can be used to define operation and usecase behaviour. These statements correspond to a text version of UML activity models<ref>{{cite book | url=https://www.taylorfrancis.com/books/mono/10.1201/9781315368153/agile-model-based-development-using-uml-rsds-kevin-lano | doi=10.1201/9781315368153 | title=Agile Model-Based Development Using UML-RSDS | year=2017 | last1=Lano | first1=Kevin | isbn=9781498752237 }}</ref>
The version of OCL used is an extension of OCL version 2.4, with additional data types Map and Function, together with extended sets of operators for strings (such as regular expressions) and collections. One motivation for these extensions was to provide an adequate representation for the semantics of reverse-engineered programs from languages such as [[Java]] or [[COBOL]]. In turn, the representations in UML/OCL can then be translated to other languages such as [[Swift]] or Python.

The version of OCL used is an extension of OCL version 2.4, with additional data types Map and Function, together with extended sets of operators for strings (such as regular expressions) and collections.<ref>{{cite book | chapter-url=https://link.springer.com/chapter/10.1007/978-3-030-89247-0_8 | doi=10.1007/978-3-030-89247-0_8 | chapter=Extending OCL with Map and Function Types | title=Fundamentals of Software Engineering | series=Lecture Notes in Computer Science | year=2021 | last1=Lano | first1=Kevin | last2=Kolahdouz-Rahimi | first2=Shekoufeh | volume=12818 | pages=108–123 | isbn=978-3-030-89246-3 | s2cid=239029860 }}</ref> These can be used to provide a representation for the semantics of reverse-engineered programs from languages such as [[Java (programming language)|Java]] or [[COBOL]]. In turn, the representations in UML/OCL can then be translated to other languages such as [[Swift (programming language)|Swift]] or Python.


== Application and evaluation ==
== Application and evaluation ==


UML-RSDS has been the subject of a number of independent reviews and comparative evaluations by the model-transformation research community, such as the following secondary reliable sources authored by researchers independent of the UML-RSDS development team:<ref>{{Cite journal|url=https://www.sciencedirect.com/science/article/pii/S1571066113000042|title=Verification of Model Transformations: A Survey of the State-of-the-Art|first1=Daniel|last1=Calegari|first2=Nora|last2=Szasz|date=March 5, 2013|journal=Electronic Notes in Theoretical Computer Science|volume=292|pages=5–25|via=ScienceDirect|doi=10.1016/j.entcs.2013.02.002}}</ref><ref>{{Cite journal|url=https://doi.org/10.1007/s10270-018-0665-6|title=Survey and classification of model transformation tools|first1=Nafiseh|last1=Kahani|first2=Mojtaba|last2=Bagherzadeh|first3=James R.|last3=Cordy|first4=Juergen|last4=Dingel|first5=Daniel|last5=Varró|date=August 1, 2019|journal=Software & Systems Modeling|volume=18|issue=4|pages=2361–2397|via=Springer Link|doi=10.1007/s10270-018-0665-6}}</ref><ref>{{Cite journal|url=https://doi.org/10.1007/s10270-013-0358-0|title=A survey of approaches for verifying model transformations|first1=Lukman|last1=Ab. Rahim|first2=Jon|last2=Whittle|date=May 1, 2015|journal=Software & Systems Modeling|volume=14|issue=2|pages=1003–1028|via=Springer Link|doi=10.1007/s10270-013-0358-0}}</ref><ref>{{Cite journal|url=https://www.sciencedirect.com/science/article/pii/S0167642313002803|title=A survey and comparison of transformation tools based on the transformation tool contest|first1=Edgar|last1=Jakumeit|first2=Sebastian|last2=Buchwald|first3=Dennis|last3=Wagelaar|first4=Li|last4=Dan|first5=Ábel|last5=Hegedüs|first6=Markus|last6=Herrmannsdörfer|first7=Tassilo|last7=Horn|first8=Elina|last8=Kalnina|first9=Christian|last9=Krause|first10=Kevin|last10=Lano|first11=Markus|last11=Lepper|first12=Arend|last12=Rensink|first13=Louis|last13=Rose|first14=Sebastian|last14=Wätzoldt|first15=Steffen|last15=Mazanek|date=June 1, 2014|journal=Science of Computer Programming|volume=85|pages=41–99|via=ScienceDirect|doi=10.1016/j.scico.2013.10.009}}</ref><ref>{{Cite journal|url=https://doi.org/10.1007/s10270-012-0245-0|title=Graph and model transformation tools for model migration|first1=Louis M.|last1=Rose|first2=Markus|last2=Herrmannsdoerfer|first3=Steffen|last3=Mazanek|first4=Pieter|last4=Van Gorp|first5=Sebastian|last5=Buchwald|first6=Tassilo|last6=Horn|first7=Elina|last7=Kalnina|first8=Andreas|last8=Koch|first9=Kevin|last9=Lano|first10=Bernhard|last10=Schätz|first11=Manuel|last11=Wimmer|date=February 1, 2014|journal=Software & Systems Modeling|volume=13|issue=1|pages=323–359|via=Springer Link|doi=10.1007/s10270-012-0245-0}}</ref>
UML-RSDS has been the subject of a number of independent reviews and comparative evaluations by the model-transformation research community, such as the following secondary reliable sources authored by researchers independent of the UML-RSDS development team, which highlight the characteristics of UML-RSDS which support transformation verification:<ref>{{Cite journal|title=Verification of Model Transformations: A Survey of the State-of-the-Art|first1=Daniel|last1=Calegari|first2=Nora|last2=Szasz|date=March 5, 2013|journal=Electronic Notes in Theoretical Computer Science|volume=292|pages=5–25|doi=10.1016/j.entcs.2013.02.002|doi-access=free}}</ref><ref>{{Cite journal|url=https://doi.org/10.1007/s10270-018-0665-6|title=Survey and classification of model transformation tools|first1=Nafiseh|last1=Kahani|first2=Mojtaba|last2=Bagherzadeh|first3=James R.|last3=Cordy|first4=Juergen|last4=Dingel|first5=Daniel|last5=Varró|date=August 1, 2019|journal=Software & Systems Modeling|volume=18|issue=4|pages=2361–2397|via=Springer Link|doi=10.1007/s10270-018-0665-6|s2cid=254169720 }}</ref><ref>{{Cite journal|url=https://doi.org/10.1007/s10270-013-0358-0|title=A survey of approaches for verifying model transformations|first1=Lukman|last1=Ab. Rahim|first2=Jon|last2=Whittle|date=May 1, 2015|journal=Software & Systems Modeling|volume=14|issue=2|pages=1003–1028|via=Springer Link|doi=10.1007/s10270-013-0358-0|s2cid=254156898 }}</ref>


It is notable as one transformation language which supports the property of additivity,<ref>S. Hidaka et al., On Additivity in Transformation Languages, MODELS 2017, ACM Press</ref> this means that the semantics of UML-RSDS specifications are compositional.
The UML-RSDS solution to the TTC 2017 bidirectional transformation case was highly rated <ref>https://docs.google.com/spreadsheets/d/1w3VBZJGe9nhwcrHn_RDn5YunR9ZNicJJ0t77WwlzaPc/edit#gid=424564886</ref>


UML-RSDS has been used by several case study solutions in the Transformation Tool Contest (TTC), the leading model transformation venue for transformation evaluation.<ref>{{Cite journal|title=A survey and comparison of transformation tools based on the transformation tool contest|first1=Edgar|last1=Jakumeit|first2=Sebastian|last2=Buchwald|first3=Dennis|last3=Wagelaar|first4=Li|last4=Dan|first5=Ábel|last5=Hegedüs|first6=Markus|last6=Herrmannsdörfer|first7=Tassilo|last7=Horn|first8=Elina|last8=Kalnina|first9=Christian|last9=Krause|first10=Kevin|last10=Lano|first11=Markus|last11=Lepper|first12=Arend|last12=Rensink|first13=Louis|last13=Rose|first14=Sebastian|last14=Wätzoldt|first15=Steffen|last15=Mazanek|date=June 1, 2014|journal=Science of Computer Programming|volume=85|pages=41–99|doi=10.1016/j.scico.2013.10.009|doi-access=free}}</ref><ref>{{Cite journal|url=https://doi.org/10.1007/s10270-012-0245-0|title=Graph and model transformation tools for model migration|first1=Louis M.|last1=Rose|first2=Markus|last2=Herrmannsdoerfer|first3=Steffen|last3=Mazanek|first4=Pieter|last4=Van Gorp|first5=Sebastian|last5=Buchwald|first6=Tassilo|last6=Horn|first7=Elina|last7=Kalnina|first8=Andreas|last8=Koch|first9=Kevin|last9=Lano|first10=Bernhard|last10=Schätz|first11=Manuel|last11=Wimmer|date=February 1, 2014|journal=Software & Systems Modeling|volume=13|issue=1|pages=323–359|via=Springer Link|doi=10.1007/s10270-012-0245-0|s2cid=254172124 }}</ref>{{Excessive citations inline|date=February 2023}}
The UML-RSDS solution came 3rd in the TTC 2014 "Movie Database" case contest<ref>http://www.transformation-tool-contest.eu/2014/solutions_movie.html</ref>
In particular, the UML-RSDS solution came 3rd in the TTC 2014 "Movie Database" case contest.<ref>{{cite web | url=http://www.transformation-tool-contest.eu/2014/solutions_movie.html | title=Transformation Tool Contest (TTC) 2014 }}</ref>


It has been used in education and research by a number of universities, in particular, King's College London (UK), the University of Isfahan (Iran), Texas A and M International University (USA), TU Darmstadt (Germany), Azarbaijan Shahid Madani University (Iran) and University of Waterloo (Canada).
It has been used in education and research by a number of universities, in particular, King's College London (UK), the University of Isfahan (Iran), Texas A and M International University (USA), TU Darmstadt (Germany), Azarbaijan Shahid Madani University (Iran) and University of Waterloo (Canada).


== Functionalities ==
== References ==


The main functionalities of UML-RSDS are:

* Creation and editing of [[UML]] Version 2 class diagrams, supporting classes with attributes, associations, inheritance and operations
* Specification of functionality using OCL 2.4 definitions of operations and use cases
* Type-analysis and quality analysis of specifications
* Code generation in multiple target languages: Java (3 versions), C#, C++, ANSI C, Python, Go, and Swift
* Code generation of Android and IOS apps (using SwiftUI)

Additional features include:

* Reverse-engineering from [[Java]], [[JavaScript]], VB6, COBOL 85 and C code
* Formalisation of textual requirements
* Support for [[QVT]] and other model transformations
* Machine learning of model transformations from examples
* Machine learning of code generators from examples

== References ==
<!-- Inline citations added to your article will automatically display here. See en.wikipedia.org/wiki/WP:REFB for instructions on how to add citations. -->
{{reflist}}
{{reflist}}


Line 96: Line 65:


<!-- categories go here -->
<!-- categories go here -->



[[Category:Unified Modeling Language]]

Latest revision as of 04:24, 25 November 2023

UML-RSDS is a lightweight model-driven engineering (MDE) and model transformation tool supporting the UML 2.5 class diagram notation and OCL 2.4 Object Constraint Language. It supports code-generation in multiple 3GLs: Java, C#, C++, Python, Go, Swift and ANSI C.

The toolset has been defined as an Eclipse project AgileUML under the modeling category.[1]

The toolset originated from EPSRC-funded research at Imperial College and King's College London in the period 1996–2014. It was publicly released in 2010 and defined as an Eclipse project in 2019. It is now supported by AgileMDE Ltd: agilemde.co.uk.

One motivation of the tools has been to provide a means for general software practitioners to use MDE in a flexible manner, to support agile development using MDE. The tool has been applied to financial software development[2] and to many different kinds of transformation problems, for example[3][4]

Language characteristics

[edit]

The main specification notations in UML-RSDS are UML class diagrams and use cases, together with Object Constraint Language (OCL) expressions, used to define invariants and operation pre and post-conditions.[5] Either a graphical or textual notation can be used for UML-RSDS specifications.

For example, a simple class specification could be written as:

class Person {
  attribute age: int;
  attribute name: String;

  operation birthday()
  pre: true
  post: age = age@pre + 1;
}

Transformations are defined as use cases together with constraints expressing how result data is derived from input data.[6] Thus a declarative specification style similar to the QVT relations language is supported, but without the need to define additional syntax or language elements - only OCL is used. For example, to copy every person instance to a 'PersonRecord' with a 'data' attribute formed from the name and age, it is sufficient to write:

usecase copyPersons {
  Person::
    PersonRecord->exists( r | r.data = name + age )
}

Verification procedures have been defined for this style of transformation specification.[7]

For more general software applications, procedural-style code using statements such as assignment (:=), loops (while, for), conditionals (if then else) and sequencing (;) can be used to define operation and usecase behaviour. These statements correspond to a text version of UML activity models[8]

The version of OCL used is an extension of OCL version 2.4, with additional data types Map and Function, together with extended sets of operators for strings (such as regular expressions) and collections.[9] These can be used to provide a representation for the semantics of reverse-engineered programs from languages such as Java or COBOL. In turn, the representations in UML/OCL can then be translated to other languages such as Swift or Python.

Application and evaluation

[edit]

UML-RSDS has been the subject of a number of independent reviews and comparative evaluations by the model-transformation research community, such as the following secondary reliable sources authored by researchers independent of the UML-RSDS development team, which highlight the characteristics of UML-RSDS which support transformation verification:[10][11][12]

It is notable as one transformation language which supports the property of additivity,[13] this means that the semantics of UML-RSDS specifications are compositional.

UML-RSDS has been used by several case study solutions in the Transformation Tool Contest (TTC), the leading model transformation venue for transformation evaluation.[14][15][excessive citations] In particular, the UML-RSDS solution came 3rd in the TTC 2014 "Movie Database" case contest.[16]

It has been used in education and research by a number of universities, in particular, King's College London (UK), the University of Isfahan (Iran), Texas A and M International University (USA), TU Darmstadt (Germany), Azarbaijan Shahid Madani University (Iran) and University of Waterloo (Canada).

References

[edit]
  1. ^ "Agile UML". 5 February 2019.
  2. ^ Alfraihi, Hessa (2018). "The Impact of Integrating Agile Software Development and Model-Driven Development: A Comparative Case Study". System Analysis and Modeling. Languages, Methods, and Tools for Systems Engineering. Lecture Notes in Computer Science. Vol. 11150. pp. 229–245. doi:10.1007/978-3-030-01042-3_14. ISBN 978-3-030-01041-6.
  3. ^ Jakumeit, Edgar; Buchwald, Sebastian; Wagelaar, Dennis; Dan, Li; Hegedüs, Ábel; Herrmannsdörfer, Markus; Horn, Tassilo; Kalnina, Elina; Krause, Christian; Lano, Kevin; Lepper, Markus; Rensink, Arend; Rose, Louis; Wätzoldt, Sebastian; Mazanek, Steffen (June 1, 2014). "A survey and comparison of transformation tools based on the transformation tool contest". Science of Computer Programming. 85: 41–99. doi:10.1016/j.scico.2013.10.009.
  4. ^ Rose, Louis M.; Herrmannsdoerfer, Markus; Mazanek, Steffen; Van Gorp, Pieter; Buchwald, Sebastian; Horn, Tassilo; Kalnina, Elina; Koch, Andreas; Lano, Kevin; Schätz, Bernhard; Wimmer, Manuel (February 1, 2014). "Graph and model transformation tools for model migration". Software & Systems Modeling. 13 (1): 323–359. doi:10.1007/s10270-012-0245-0. S2CID 254172124 – via Springer Link.
  5. ^ Lano, Kevin (2017). Agile Model-Based Development Using UML-RSDS. doi:10.1201/9781315368153. ISBN 9781498752237.
  6. ^ Hidaka, Sochiro; Jouault, Frederic; Tisi, Massimo (2017). "On Additivity in Transformation Languages". 2017 ACM/IEEE 20th International Conference on Model Driven Engineering Languages and Systems (MODELS) (PDF). pp. 23–33. doi:10.1109/MODELS.2017.21. ISBN 978-1-5386-3492-9. S2CID 9109050.
  7. ^ Thangaraj, Jagadeeswaran; Ulaganathan, Senthilkumaran (2020). "A Comparative Study on Transformation of UML/OCL to Other Specifications". Recent Advances in Computer Science and Communications. 13 (2): 256–264. doi:10.2174/2213275912666190129121059. S2CID 86744559.
  8. ^ Lano, Kevin (2017). Agile Model-Based Development Using UML-RSDS. doi:10.1201/9781315368153. ISBN 9781498752237.
  9. ^ Lano, Kevin; Kolahdouz-Rahimi, Shekoufeh (2021). "Extending OCL with Map and Function Types". Fundamentals of Software Engineering. Lecture Notes in Computer Science. Vol. 12818. pp. 108–123. doi:10.1007/978-3-030-89247-0_8. ISBN 978-3-030-89246-3. S2CID 239029860.
  10. ^ Calegari, Daniel; Szasz, Nora (March 5, 2013). "Verification of Model Transformations: A Survey of the State-of-the-Art". Electronic Notes in Theoretical Computer Science. 292: 5–25. doi:10.1016/j.entcs.2013.02.002.
  11. ^ Kahani, Nafiseh; Bagherzadeh, Mojtaba; Cordy, James R.; Dingel, Juergen; Varró, Daniel (August 1, 2019). "Survey and classification of model transformation tools". Software & Systems Modeling. 18 (4): 2361–2397. doi:10.1007/s10270-018-0665-6. S2CID 254169720 – via Springer Link.
  12. ^ Ab. Rahim, Lukman; Whittle, Jon (May 1, 2015). "A survey of approaches for verifying model transformations". Software & Systems Modeling. 14 (2): 1003–1028. doi:10.1007/s10270-013-0358-0. S2CID 254156898 – via Springer Link.
  13. ^ S. Hidaka et al., On Additivity in Transformation Languages, MODELS 2017, ACM Press
  14. ^ Jakumeit, Edgar; Buchwald, Sebastian; Wagelaar, Dennis; Dan, Li; Hegedüs, Ábel; Herrmannsdörfer, Markus; Horn, Tassilo; Kalnina, Elina; Krause, Christian; Lano, Kevin; Lepper, Markus; Rensink, Arend; Rose, Louis; Wätzoldt, Sebastian; Mazanek, Steffen (June 1, 2014). "A survey and comparison of transformation tools based on the transformation tool contest". Science of Computer Programming. 85: 41–99. doi:10.1016/j.scico.2013.10.009.
  15. ^ Rose, Louis M.; Herrmannsdoerfer, Markus; Mazanek, Steffen; Van Gorp, Pieter; Buchwald, Sebastian; Horn, Tassilo; Kalnina, Elina; Koch, Andreas; Lano, Kevin; Schätz, Bernhard; Wimmer, Manuel (February 1, 2014). "Graph and model transformation tools for model migration". Software & Systems Modeling. 13 (1): 323–359. doi:10.1007/s10270-012-0245-0. S2CID 254172124 – via Springer Link.
  16. ^ "Transformation Tool Contest (TTC) 2014".
[edit]