Difference between pages "UML-B Tutorial" and "Rodin Platform 3.6 Release Notes"

From Event-B
(Difference between pages)
Jump to navigationJump to search
imported>Colin
 
 
Line 1: Line 1:
Guide to Rodin and UML-B
+
{{TOCright}}
  
This document will guide you through Rodin and UML-B using a simple example. The tutorial assumes you have downloaded and installed the Rodin platform and then installed the UML-B and Pro-B plug-in extension features. See http://www.event-b.org/platform.html and  http://www.event-b.org/plugins.html.
+
== What's New in Rodin 3.6? ==
  
 +
Rodin 3.6 brings several bug fixes. It also upgrades the underlying Eclipse to 2020-12, which can be run by Java 11 Runtimes.
  
Getting Started
+
Please note that we only provide 64-bit binary versions of the Rodin platform.
  
1. Start Rodin by clicking on rodin.exe
+
=== Changes for plug-in developers ===
  
2. The workspace launcher will appear - Select or create a workspace on your machine
+
Rodin 3.6 is built on top of Eclipse 4.18 (2020-12), which requires Java 11.
3. Close the welcome message
 
4. Open the UML-B perspective
 
        a. Click on: Window → Open Perspective → Other…
 
        b. Select UML-B and click OK
 
        You are now in the UML-B Perspective
 
5. Open a new UMLB project
 
        a. File → New → Project
 
        b. Select UML-B Project → Next
 
[[Image:UMLBSelectNewProjectType.jpg]]
 
        c. Enter a name for your project and click Finish
 
        d. The UML-B new project wizard, automatically creates and opens a package diagram ready for you to start modelling. You can see that you are in the UMLB perspective, when the UMLB button is clicked.
 
 
Creating the Sleepy model
 
Sleepy Specification
 
A person can go to bed and sleep. After at least one hour, an alarm can be sounded which is waking the person. The person should then get up. A person has a maximum number of hours of sleep after which the person will get up without the alarm being sounded.
 
Package Diagram
 
  
+
There is no API change within Rodin Core.
In the package diagram you have to create a machine and a context for the dynamic and static parts of your model.
 
• Create a machine: click on “machine” in the palette and click in the package diagram space, then name your machine. (You can enter the name on the text field of the diagram element. Alternatively, and more generally, you can edit any element properties in the Properties tab).
 
• Create a context: click on “context” in the palette and click in the package diagram space, then name your context
 
You have to ensure that your machine can see the context.
 
• Click on “Sees” in the palette and create a link from your machine to the context
 
Save your package diagram.
 
• Click save
 
WARNING: Make sure you always save an edited diagram before moving to another diagram in the same UML-B project. There is currently a problem with multiple diagram editors: unsaved changes in the first editor will be lost if you save edits to a second diagram.
 
  
Context Diagram
+
== Installing ==
  
+
=== Downloading ===
Opening a context diagram
 
• Highlight  the context diagram box in your package diagram
 
• In the properties tab click on “open context diagram…”
 
For the sleepy model we need three states: awake, asleep and waking. These are elements of the enumerated set WAKE_STATE. To create this set,
 
• Click on “class type” in the palette and click into the context diagram space
 
• In the properties tab, type a name “WAKE_STATE” for your class type → press enter (DO NOT enter the name of the class type in the diagram, use the properties tab to enter all data)
 
• In the properties tab, click “add new type” in order to add elements to the enumerated set
 
 
• Type “{awake, asleep, waking}” into the Name field of the type expression dialog → OK
 
• In the properties tab, select the type {awake, asleep, waking} from the “instances” drop-down menu
 
For the sleepy model you also have to declare a constant which holds the maximum number of hours a person may sleep.
 
• Select “constant” from the palette and click into the context diagram space
 
 
• In the properties tab, type a name “maxHours” for your constant and give it a type “N”
 
• Save your context diagram
 
Class Diagram
 
The class diagram is used for the dynamic part of your system.
 
• Open your package diagram (either select the tab, or find it in the navigator)
 
 
• Highlight your machine in the package diagram
 
• In the properties tab, click “open class diagram…”
 
Your model only requires one class in the class diagram. This class, person, will require two variables, “hoursOfSleep”, which tracks the amount of hours a person has slept, and “wakeState”, which records the current state of that person.
 
The model also needs several events to manipulate the state. These are
 
“goToBed” (to set the wakeState of a person to asleep),
 
“addMoreSleep” (to add another hour of sleep to the person’s hoursOfSleep count),
 
“soundAlarm” (to wake up a person and set the wakeState of that person to waking) and
 
“getUp” (to set the person’s wakeState to awake).
 
• Select “class” in the palette and click into the class diagram space
 
• In the properties tab, enter a name for your class “person”
 
 
• Move your mouse over the class in the class diagram, and select “add attribute” from the menu that pops up. (You could also use the tool palette).
 
 
• In the properties tab, enter the name “hoursOfSleep”, the type “N” and the initial value “0” of your attribute.
 
 
• Add another attribute to the class, and name it “wakeState”, type “Class Type WAKE_STATE” (this will use the enumerated set you created in the context diagram) and initial value “awake” .
 
 
Now we have to add a constructor to the class, which will initialise the instances of the class.
 
• Add an event to the class “person”
 
 
• In the properties tab, enter a name for the person “CreatePerson” and select “constructor” in the “kind” drop-down menu
 
 
The next event that will be added to the model is “goToBed”
 
• Add another event to the class person
 
• Enter the name “goToBed” in the properties tab
 
• Select “guards” in the properties tab and “add guard…”
 
• In the guard field enter “wakeState(self) = awake” (we only want to put persons into bed that are awake) → OK.
 
[Note that you could also enter “self,.wakeState = awake” (the character pair ,. is converted to a special dot symbol). This gives a more object oriented style for guards and actions].
 
  
+
[http://sourceforge.net/projects/rodin-b-sharp/files/Core_Rodin_Platform/3.6/ Download Rodin 3.6 now !]
• Select “actions” in the properties tab and “add action…”
 
• In the action field enter “wakeState(self) := asleep”  → OK
 
• Add another action and enter: “hoursOfSleep(self) := 0”
 
• Save your class diagram
 
The event “addMoreSleep” can add another hour of sleep to the person’s sleep count. The person may, however, not sleep more than the maximum hours of sleep allowed.
 
• Add another event to class person
 
• In the properties tab, enter the name “addMoreSleep” → press enter
 
• Add two guards: “wakeState(self) = asleep” and “hoursOfSleep(self) < maxHours”
 
• Add one action: “hoursOfSleep(self) := hoursOfSleep(self) + 1”
 
The event “soundAlarm” is used to wake up a person who has slept for at least one hour, and has not slept the maximum amount of hours.
 
• Add another event to class person
 
• Enter name: “soundAlarm”
 
• Add guards: “wakeState(self) = asleep”, “hoursOfSleep(self) > 0” and “hoursOfSleep(self) < maxHours”
 
• Add action: “wakeState(self) := waking”
 
One last event is needed in the system, “getUp”, which will set the person’s wakeState to awake. It should be enabled when the person was woken by the alarm, i.e. is in waking state or if the maximum hours of sleep have been reached.
 
• Add another event to class person
 
• Enter name: “getup”
 
• Enter the following information:
 
Guard1: (wakeState(self) = waking) or (wakeState(self) = asleep & hoursOfSleep(self) ≥ maxHours)
 
Action1: wakeState(self) := awake
 
Action2: hoursOfSleep(self) :=0
 
• Save your model
 
  
[An alternative way to model this same specification using statemachines is given below.
+
=== Upgrading from a previous version of Rodin 3.x ===
 
  
Viewing the generated eventB
+
If you run Rodin 3.1, 3.2, 3.3, 3.4 or 3.5, then you can upgrade your Rodin Platform by clicking Help > Check for Updates, then select Rodin 3.6 in the popup window and accept the licence terms. Note that the upgrading process can take quite a long time.
To view the generated eventB context and machine, open the xxx.eventB folder (where xxx stands for the name of your project). You will see a fairly long list of files. (You could switch to the Event-B perspective, which will filter the files in the Navigator to show the ones you can open). In order to view your context, double click on xxx.buc; for the machine click on xxx.bum.
 
You will see several tabs at the bottom, select “Pretty Print” to view the generated eventB.  
 
[NOTE: If you want to experiment with the Event-B tools, you can edit the Event-B model in this view. However, any changes you make will not be fed back to the UML-B source models, so if you alter the UML-B model your Event-B edits will be overwritten and lost.]
 
 
 
  
   
+
Take care that Rodin 3.6 brings a new version of Eclipse. This means that once you have opened a workspace with Rodin 3.6, you will not be able to open it with a prior version of Rodin anymore.  Please consider copying your workspace for Rodin 3.6 to avoid any disaster.
Creating the Sleepy Model using Statemachines
+
 
Statemachines provide an alternative way to model behaviour. This section shows how a statemachine could be used to replace some of the data, state variables and events of the previous model. If you use a different UML-B project name you can compare the generated Event-B from the two models.
+
If you run Rodin 3.0 or prior, you cannot upgrade to 3.6. You need to download the platform from SourceForge and reinstall your external plugins.
Context Diagram
+
 
The context of this model does not contain the enumerated set WAKE_STATE, because those states are generated by UML-B automatically from the statemachine.
+
== Requirements - Compatibility ==
The context consists of only one constant maxHours.
+
 
• In the context diagram, create one constant (name: maxHours; type: N)
+
=== Supported operating systems ===
+
 
Class Diagram
+
Rodin will work on the following operating systems
The class diagram consists of one class “person”, which has one attribute “hoursOfSleep” to track the amount of hours a person has slept.
+
* macOS 64-bit
• In the class diagram, create a class (name: person)
+
* Linux 64-bit
• Add an attribute to the class (name: hoursOfSleep; type: N; initial value: 0)
+
* Windows 64-bit
This time, the events will be created using a statemachine.
+
 
• Add a statemachine to class “person” and name it
+
=== Java Runtime requirement ===
• Click “Open StateDiagram…”
+
 
+
You need to have a 64-bit Java JRE (version 11 or later) installed on your computer. The Rodin application will not work with a previous version or with a 32-bit JRE.
• From the palette select state and create a state (name: awakeState)
+
 
• Do the same for the other two states: asleepState, wakingState
+
=== macOS specific requirements ===
• Create an initial state
+
 
The state transitions can now be used to relate the different states. They will be translated as events in  eventB.
+
The Rodin application is not notarized.  This means that when you download it from SourceForge, macOS will quarantine the application and tell you that it is broken.  Just run the command <code>xattr -rc Rodin.app</code> in a Terminal to remove the quarantine tag.
• Create transitions to match the diagram  below
+
 
+
=== Linux specific requirements ===
• Add the following detail to the different transitions and then animate your model in ProB
+
 
 +
Package <code>libc6-amd64:i386</code> must be installed, in particular in order to run external prover binaries depending on the distribution, you could instead need these packages: <code>lib32z1</code>, <code>lib32ncurses5</code>, <code>lib32bz2-1.0</code>.
 +
 
 +
=== Windows specific requirements ===
 +
Atelier B provers may work more slowly; it can cause ML to not automatically discharge some sequents that it discharges on windows 32-bit, due to its timeout. A workaround is to download a custom profile: [http://sourceforge.net/projects/rodin-b-sharp/files/DefaultAuto_ML800 DefaultAuto_ML800], then Window > Preferences > Event-B > Sequent Prover > Auto/Post Tactic > Profiles (tab) > Import..., point to the downloaded file, 'Select All' profiles (there are 2), OK. Then in 'Auto/Post Tactic' tab, select 'Default Auto Tactic Profile (ML 800)' profile for auto-tactics. It is the same as the 'Default Auto Tactic Profile', except ML has a longer timeout (800 ms). You can of course change this timeout by editing the 'ML (800)' profile.
 +
 
 +
We have not noticed this problem for Linux 64-bit, nor for other platforms; however if you do, the same workaround applies.
 +
 
 +
=== Math fonts ===
 +
 
 +
To enhance your proving experience, the eclipse font settings (size, aspect...) are available from the preferences (General > Appearance > Colors and Fonts > Rodin). These settings allow you to modify the properties set on the Event-B Keyboard Text Font which is used in many views of the Proving UI. However, to enjoy these functionalities, you need to install the Brave Sans Mono font on your system. You can download this font from the link [http://sourceforge.net/projects/rodin-b-sharp/files/Font_%20Brave%20Sans%20Mono/0.12/ here].
 +
 
 +
== Disclaimer ==
 +
 
 +
Since Rodin is continuously maintained, several unsoundness bugs which have been encountered were investigated and fixed. However, despite the total commitment of our teams to ensure the soundness of the platform, some unexpected and unknown soundness issues could remain. We would be grateful if you would report these issues to the [mailto:rodin-b-sharp-devel@lists.sourceforge.net development mailing list].
 +
 
 +
== About ==
 +
 
 +
Rodin Platform with git commit: <code>77c3449</code><br/>
 +
User Release date : 2021/05/17.
 +
 
 +
[[Category:Rodin Platform Release Notes]]

Latest revision as of 14:09, 25 May 2021

What's New in Rodin 3.6?

Rodin 3.6 brings several bug fixes. It also upgrades the underlying Eclipse to 2020-12, which can be run by Java 11 Runtimes.

Please note that we only provide 64-bit binary versions of the Rodin platform.

Changes for plug-in developers

Rodin 3.6 is built on top of Eclipse 4.18 (2020-12), which requires Java 11.

There is no API change within Rodin Core.

Installing

Downloading

Download Rodin 3.6 now !

Upgrading from a previous version of Rodin 3.x

If you run Rodin 3.1, 3.2, 3.3, 3.4 or 3.5, then you can upgrade your Rodin Platform by clicking Help > Check for Updates, then select Rodin 3.6 in the popup window and accept the licence terms. Note that the upgrading process can take quite a long time.

Take care that Rodin 3.6 brings a new version of Eclipse. This means that once you have opened a workspace with Rodin 3.6, you will not be able to open it with a prior version of Rodin anymore. Please consider copying your workspace for Rodin 3.6 to avoid any disaster.

If you run Rodin 3.0 or prior, you cannot upgrade to 3.6. You need to download the platform from SourceForge and reinstall your external plugins.

Requirements - Compatibility

Supported operating systems

Rodin will work on the following operating systems

  • macOS 64-bit
  • Linux 64-bit
  • Windows 64-bit

Java Runtime requirement

You need to have a 64-bit Java JRE (version 11 or later) installed on your computer. The Rodin application will not work with a previous version or with a 32-bit JRE.

macOS specific requirements

The Rodin application is not notarized. This means that when you download it from SourceForge, macOS will quarantine the application and tell you that it is broken. Just run the command xattr -rc Rodin.app in a Terminal to remove the quarantine tag.

Linux specific requirements

Package libc6-amd64:i386 must be installed, in particular in order to run external prover binaries depending on the distribution, you could instead need these packages: lib32z1, lib32ncurses5, lib32bz2-1.0.

Windows specific requirements

Atelier B provers may work more slowly; it can cause ML to not automatically discharge some sequents that it discharges on windows 32-bit, due to its timeout. A workaround is to download a custom profile: DefaultAuto_ML800, then Window > Preferences > Event-B > Sequent Prover > Auto/Post Tactic > Profiles (tab) > Import..., point to the downloaded file, 'Select All' profiles (there are 2), OK. Then in 'Auto/Post Tactic' tab, select 'Default Auto Tactic Profile (ML 800)' profile for auto-tactics. It is the same as the 'Default Auto Tactic Profile', except ML has a longer timeout (800 ms). You can of course change this timeout by editing the 'ML (800)' profile.

We have not noticed this problem for Linux 64-bit, nor for other platforms; however if you do, the same workaround applies.

Math fonts

To enhance your proving experience, the eclipse font settings (size, aspect...) are available from the preferences (General > Appearance > Colors and Fonts > Rodin). These settings allow you to modify the properties set on the Event-B Keyboard Text Font which is used in many views of the Proving UI. However, to enjoy these functionalities, you need to install the Brave Sans Mono font on your system. You can download this font from the link here.

Disclaimer

Since Rodin is continuously maintained, several unsoundness bugs which have been encountered were investigated and fixed. However, despite the total commitment of our teams to ensure the soundness of the platform, some unexpected and unknown soundness issues could remain. We would be grateful if you would report these issues to the development mailing list.

About

Rodin Platform with git commit: 77c3449
User Release date : 2021/05/17.