science

UML-RSDS

UML-RSDS is a science topic covered in the lgStudy science library. This page brings together a partial reference excerpt, illustrations, worked examples, real-world applications and a short study plan, so you can understand UML-RSDS rather than just read about it. In short: 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.

Key takeaways

UML-RSDS belongs to science; place it in that map before memorising details.
Learn the definition first, then one example that makes the definition concrete.
Connect UML-RSDS to a quantity you can measure, compute or draw — that is where exam questions come from.
Reproduce the core statement of UML-RSDS from memory before moving on to harder problems.

Reference excerpt

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. 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 and to many different kinds of transformation problems, for example

Language characteristics 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. Either a graphical or textual notation can be used for UML-RSDS specifications. For example, a simple class specification could be written as:

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:

Verification procedures have been defined for this style of transformation specification. 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 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. 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 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: It is notable as one transformation language which supports the property of additivity, 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. In particular, the UML-RSDS solution came 3rd in the TTC 2014 "Movie Database" case contest. 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

External links UML-RSDS book review: https://modeling-languages.com/uml-rsds-agile-model-based-development-uml/ Computerphile video: https://www.youtube.com/watch?v=Xz06zYlQrck EPSRC project: https://gow.epsrc.ukri.org/NGBOViewGrant.aspx?GrantRef=GR/R81701/01

Worked examples

Example 1 — a first encounter with UML-RSDS

Start with the simplest possible case. Write down what UML-RSDS claims or describes in one sentence, then invent the smallest concrete situation in which that sentence is true. In science, the smallest case is usually a single object, a single equation or a single measurement. Check that every symbol or term in your sentence has a meaning in that case.

Example 2 — changing one variable

Take the situation from Example 1 and change exactly one quantity: double it, halve it, or set it to zero. Predict what should happen to UML-RSDS before you calculate. Comparing your prediction with the result is the fastest way to find out whether you understand the idea or only the words.

Example 3 — an exam-style question

Typical questions about UML-RSDS ask you to (a) state it precisely, (b) apply it to given data, and (c) explain a limitation. Practise writing all three answers in under five minutes; the third part is what separates a full-mark answer from an average one.

Applications of UML-RSDS

In research: UML-RSDS appears in science research whenever the underlying quantities have to be modelled precisely. Papers usually cite it as a starting assumption and then explore where it breaks down.
In technology and industry: Engineering practice reuses UML-RSDS in design rules, simulations and safety margins. Knowing the idea lets you read a specification sheet and understand why the numbers look the way they do.
In the classroom: UML-RSDS is common in secondary-school and first-year university syllabi. It links to neighbouring topics Unified Modeling Language, so understanding it makes those chapters shorter.
In everyday life: Look for UML-RSDS outside the textbook — in sport, cooking, traffic, electronics or the sky above you. An example you found yourself is remembered far longer than one you were given.

Ask Teacher Smith questions about this articleOpens your AI tutor with a question about “UML-RSDS” →

Affiliate

Preply — study more efficiently by working with a personal tutor. 50% off.

How to study UML-RSDS in 20 minutes

Read the reference excerpt below once, without taking notes.
Close the page and write down what UML-RSDS means in your own words.
Compare your version with the excerpt and mark what you missed.
Work through the three examples above with pen and paper.
Explain UML-RSDS out loud to somebody else — or to Teacher Smith in the lgStudy chat.

Frequently asked questions

What is UML-RSDS in simple terms?

Why does UML-RSDS matter?

Because it connects several science ideas at once: it gives you a definition you can apply, a quantity you can calculate, and a way to check whether a result is plausible.

How should I study UML-RSDS?

Read the excerpt, restate it from memory, then work through the examples and applications listed on this page. The five-step study plan above takes about twenty minutes.

What does this page cover?

It gives you a compact reference excerpt plus original lgStudy explanations, examples, applications and study material on UML-RSDS.