D32 UML-B

From Event-B
Revision as of 20:20, 15 December 2010 by imported>Colin (→‎Planning)
Jump to navigationJump to search

Overview

The main progress on UML-B has been to implement new features, improve usability and fix bugs. As in the previous years of DEPLOY, these bugs and features are reported either by mail or through dedicated SourceForge trackers.

The list below gives an overwiew of the noteworthy features added in UML-B during the past year:

  • Additional features added to state machines to support transitions emanating from multiple states
It is often the case that a transition may occur from several (possibly all) states within a state-machine. Such models were impossible to represent in UML-B. Two pseudo-states were added to represent this. Firstly an 'ANY' pseudo-state can be used as a transition source to represent that the transition can occur from ANY state of the state-machine. Secondly a disjunctive pseudo-state can be used to combine several transitions from different source states into a single transition.
  • Support (Conceptual) Singleton classes - no instances generated:
Occasionally a conceptual grouping of associated modelling elements is desired without generating the lifting mechanisms of a class.
  • enable super-type arrows to target ExtendedClassTypes and RefinedClasses
  • provide convergence property on state transitions
  • report to user if translation didn't proceed due to model validator
  • improve refresh of diagrams for error marking and for properties changes
  • improvements and additions to model validations
  • correct and improve missing default labelling in diagrams
  • corrections and improvements to automatic diagram deletion.
  • Requires Rodin 2.0 (Eclipse 3.6 and JVM 1.6)
  • Improved management of diagram files when model changes
  • Add preference for line routing style (default rectilinear) for each diagram type
  • Add missing comment fields in properties view


UML-B State-machine Animation Plug-in is a new feature developed by University of Southampton as a response to a request from industrial partners to support the animation of UML-B state-machine diagrams. The essence of request was to provide a means of visualising the animation and model-checking process of Event-B machines modelled in UML-B tool, in particular state-machines, thus to simplify this process. The tool integrates the capabilities of ProB animation and UML-B tool's notation.

Motivations

Enhancements to state diagram drawing. Several case studies were involving state machine diagrams which were problematic because particular transitions could be enabled from any sub-state. there was no way to represent these cases in UML-B.

The motivation for the Animation Plug-in was to extend already beneficial graphical notation of UML-B with animation capabilities similar to those that ProB tool provides for Event-B models. With the aid of such a plug-in animation and model checking would be possible on UML-B diagrams instead of translated and less obvious Event-B code. The resulting plug-in uses ProB tool to run the standard animation on translated models and animates UML-B state-machines at the same time.

Choices / Decisions

  • Integrated UML-B
It was planned to develop a new version (iUML-B) of UML-B which is more integrated with Event-B. A precursor stage to this was to develop an EMF representation of Event-B. This was completed last year and is now used successfully by several plug-ins. A Records plug-in was developed in response to user requests. The Records plug-in was implemented as an extension to the Event-B EMF framework. This was seen as a 'practice run' before attempting a similar extension to support UML-B. However, the Records plug-in took longer than expected and this has delayed work on iUML-B. Some progress on iUML-B has recently been made with the release of a project level diagram tool for Event-B and some progress on representing State-Machine diagram models as an extension to the Event-B EMF models.
  • State-machine Animation Plug-in
The initial design decision was to extend the UML-B metamodel with the animation components. Due to difficulties with UML-B diagram extensibility an alternative option was determined - to create a separate model, derived from UML-B state-machine subset, with incorporated animation support. This design was successfully implemented together with ProB and Rodin UI extensions into Animation plug-in, which supports such UML-B concepts as classes and different state-machine translation kinds, as well as Event-B refinement.

Available Documentation

The following pages give useful information about UML-B:

  • Lectures[1].
  • Tutorials[2].
  • Worked Examples[3].

UML-B State-machine Animation Plug-in:

  • General information[4]
  • Tutorial[5]

Planning

During the coming year, special efforts will be made on the following topics,

  • Development of the Project Diagram Plugin for Event-B to make it extensible and/or to automatically cater for future component types.
The current version of the Project Diagram Plugin only supports Machines and Contexts and their relationships. Already, several plug-ins are contributing new kinds of components such as theories, tasking machines and compositions. The Project Diagram plug-in will be enhanced to provide an extension mechanism that allow other plug-ins to extend the project diagram to show new kinds of components and their relationship.
  • Development of a State-machine diagram plug-in as an integrated part of Event-B modelling
The State-machine diagram plug-in will provide a diagrammatic modelling environment based on state-machines alongside the usual Event-B modelling format. The two views will contribute to the same model simultaneously.

In parallel with these new plug-ins, the current version of UML-B will continue to be enhanced. This may include some new modelling features such as better support for synchronisation of state-machines and support for more UML modelling details. However, usability of the current features is seen as the main objective. This will include,

  • Support for copy, cut and paste of diagram elements so that they can be moved and/or replicated more easily,
  • Support for re-attaching links (e.g. transitions) to different source/target elements,
  • Facilities for refactoring/renaming elements,
  • Support for the event extension mechanism of Event-B,
  • Integration of Context Diagram model elements on Class diagrams,
  • Improve facilities for navigating between state-machines and visualising multiple state-machines.

References