A major contributor to this article appears to have a close connection with its subject.(February 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]
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.
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).
The unified modeling language (UML) is a general-purpose visual modeling language that is intended to provide a standard way to visualize the design of a system.
The Meta-Object Facility (MOF) is an Object Management Group (OMG) standard for model-driven engineering. Its purpose is to provide a type system for entities in the CORBA architecture and a set of interfaces through which those types can be created and manipulated. MOF may be used for domain-driven software design and object-oriented modelling.
Model Driven Architecture (MDA) is a software design approach for the development of software systems. It provides a set of guidelines for the structuring of specifications, which are expressed as models. Model Driven Architecture is a kind of domain engineering, and supports model-driven engineering of software systems. It was launched by the Object Management Group (OMG) in 2001.
The Object Constraint Language (OCL) is a declarative language describing rules applying to Unified Modeling Language (UML) models developed at IBM and is now part of the UML standard. Initially, OCL was merely a formal specification language extension for UML. OCL may now be used with any Meta-Object Facility (MOF) Object Management Group (OMG) meta-model, including UML. The Object Constraint Language is a precise text language that provides constraint and object query expressions on any MOF model or meta-model that cannot otherwise be expressed by diagrammatic notation. OCL is a key component of the new OMG standard recommendation for transforming models, the Queries/Views/Transformations (QVT) specification.
Meta-process modeling is a type of metamodeling used in software engineering and systems engineering for the analysis and construction of models applicable and useful to some predefined problems.
A metamodel is a model of a model, and metamodeling is the process of generating such metamodels. Thus metamodeling or meta-modeling is the analysis, construction and development of the frames, rules, constraints, models and theories applicable and useful for modeling a predefined class of problems. As its name implies, this concept applies the notions of meta- and modeling in software engineering and systems engineering. Metamodels are of many types and have diverse applications.
Agile modeling (AM) is a methodology for modeling and documenting software systems based on best practices. It is a collection of values and principles that can be applied on an (agile) software development project. This methodology is more flexible than traditional modeling methods, making it a better fit in a fast-changing environment. It is part of the agile software development tool kit.
VIATRA is an open-source model transformation framework based on the Eclipse Modeling Framework (EMF) and hosted by the Eclipse Foundation.
Model-driven engineering (MDE) is a software development methodology that focuses on creating and exploiting domain models, which are conceptual models of all the topics related to a specific problem. Hence, it highlights and aims at abstract representations of the knowledge and activities that govern a particular application domain, rather than the computing concepts.
ATL is a model transformation language and toolkit developed and maintained by OBEO and AtlanMod. It was initiated by the AtlanMod team. In the field of Model-Driven Engineering (MDE), ATL provides ways to produce a set of target models from a set of source models.
QVT (Query/View/Transformation) is a standard set of languages for model transformation defined by the Object Management Group.
A model transformation, in model-driven engineering, is an automated way of modifying and creating platform-specific model from platform-independent ones. An example use of model transformation is ensuring that a family of models 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 language in systems and software engineering is a language intended specifically for model transformation.
Executable UML is both a software development method and a highly abstract software language. It was described for the first time in 2002 in the book "Executable UML: A Foundation for Model-Driven Architecture". The language "combines a subset of the UML graphical notation with executable semantics and timing rules." The Executable UML method is the successor to the Shlaer–Mellor method.
Syntropy is a second-generation object-oriented analysis and software design method developed at Object Designers Limited in the UK during the early 1990s. The goal in developing Syntropy was to provide a set of modelling techniques that would allow precise specification and would keep separate different areas of concern. The approach was to take established techniques, as found in methods such as the Object-modeling technique and Booch method, and reposition and refine them. In recognition that graphical notations were much favoured by the market but lacked rigour, Syntropy adopted ideas from formal specification languages, specifically Z notation, to provide tools for both precise definition of the graphical notations and for the construction of richer models than are possible with pictures alone.
Kevin C. Lano is a British computer scientist.
The Production Rule Representation (PRR) is a proposed standard of the Object Management Group (OMG) to provide a vendor-neutral rule-model representation in UML for production rules as used in forward-chaining rule engines.
The Triune Continuum Paradigm is a paradigm for general system modeling published in 2002. The paradigm allows for building of rigorous conceptual frameworks employed for systems modeling in various application contexts.
Robert Bertrand France was a Jamaica-born American computer scientist.