D32 UML-B - Revision history

imported>Tommy: /* Planning */

2011-01-27T11:05:05Z

Planning

← Older revision		Revision as of 11:05, 27 January 2011
Line 72:		Line 72:
	* Improve facilities for navigating between state-machines and visualising multiple state-machines.		* Improve facilities for navigating between state-machines and visualising multiple state-machines.

	The new iUML-B tools will continue to be developed and ~~release~~ including,		The new iUML-B tools will continue to be developed and released including,
	* Enhancement of the Project Diagram Plugin for Event-B to make it extensible and/or to automatically cater for future component types,		* Enhancement of the Project Diagram Plugin for Event-B to make it extensible and/or to automatically cater for future component types,
	* Release of the State-machine diagram plug-in as an integrated part of Event-B modelling,		* Release of the State-machine diagram plug-in as an integrated part of Event-B modelling,

imported>Tommy: /* Enhancement and Maintenance of Existing UML-B */

2011-01-27T11:02:06Z

Enhancement and Maintenance of Existing UML-B

← Older revision		Revision as of 11:02, 27 January 2011
Line 45:		Line 45:

	== Enhancement and Maintenance of Existing UML-B ==		== Enhancement and Maintenance of Existing UML-B ==
	: As UML-B is already a relatively mature product attracting strong interest from various institutions, the main goal is currently to improve usability and stability of the tool rather than develop major new features. Consequently development has concentrated primarily on improving the basic tooling and user interface. However, ~~when~~ users are limited by the modelling language ~~this~~ can be ~~seen~~ as a usability issue ~~and may result in the addition of~~ new features to the language.		: As UML-B is already a relatively mature product attracting strong interest from various institutions, the main goal is currently to improve usability and stability of the tool rather than develop major new features. Consequently development has concentrated primarily on improving the basic tooling and user interface. However, if users are limited by the modelling language, which can be interpreted as an usability issue, new features to the language may be added.

	== UML-B State-machine Animation ==		== UML-B State-machine Animation ==

imported>Tommy: /* Enhancement and Maintenance of Existing UML-B */

2011-01-27T10:57:43Z

Enhancement and Maintenance of Existing UML-B

← Older revision		Revision as of 10:57, 27 January 2011
Line 45:		Line 45:

	== Enhancement and Maintenance of Existing UML-B ==		== Enhancement and Maintenance of Existing UML-B ==
	: As UML-B is already a relatively mature product attracting strong interest from various institutions, the main goal currently is to improve usability and stability of the tool rather than develop major new features. Consequently development has concentrated primarily on improving the basic tooling and user interface. However, when users are limited by the modelling language this can be seen as a usability issue and may result in the addition of new features to the language.		: As UML-B is already a relatively mature product attracting strong interest from various institutions, the main goal is currently to improve usability and stability of the tool rather than develop major new features. Consequently development has concentrated primarily on improving the basic tooling and user interface. However, when users are limited by the modelling language this can be seen as a usability issue and may result in the addition of new features to the language.

	== UML-B State-machine Animation ==		== UML-B State-machine Animation ==

imported>Tommy: /* iUML-B - Integrated UML-B */

2011-01-27T10:57:03Z

iUML-B - Integrated UML-B

← Older revision		Revision as of 10:57, 27 January 2011
Line 40:		Line 40:

	== iUML-B - Integrated UML-B ==		== iUML-B - Integrated UML-B ==
	:The motivations for an alternative version of UML-B that is tightly integrated with Event-B was recognised at the beginning of the Deploy project. The aim of UML-B was to provide an easier modelling environment for users that were familiar with UML-like modelling but not with textual mathematical notations. Experienced Event-B users would also benefit from the visualisations provided by UML-B but they do not wish to be distanced from the generated Event-B and would prefer to be able to create parts of their models in the Event-B notation alongside the diagrammatic parts.		:The motivations for an alternative version of UML-B, that is tightly integrated with Event-B, was recognised at the beginning of the Deploy project. The aim of UML-B was to provide an easier modelling environment for users that were familiar with UML-like modelling but not with textual mathematical notations. Experienced Event-B users would also benefit from the visualisations provided by UML-B but they do not wish to be distanced from the generated Event-B and would prefer to be able to create parts of their models in the Event-B notation alongside the diagrammatic parts.

	= Choices / Decisions =		= Choices / Decisions =

imported>Tommy: /* Enhancement and Maintenance of Existing UML-B */

2011-01-27T10:51:53Z

Enhancement and Maintenance of Existing UML-B

← Older revision		Revision as of 10:51, 27 January 2011
Line 34:		Line 34:

	== Enhancement and Maintenance of Existing UML-B ==		== Enhancement and Maintenance of Existing UML-B ==
	:The aim is to continually improve the usability of UML-B in the light of experience. Although the motivation for a more integrated version of UML-B that would be attractive to experienced Event-B users has been recognised for some time, the original aim of UML-B was to make formal modelling more accessible to new users. This aim remains valid and therefore the current non-integrated UML-B should be developed and enhanced wherever possible. Therefore, some issues concerning its usability have been identified and rectified. Some of these required enhancements to the modelling language. In particular, several case studies have highlighted the need for transitions that may be taken from any sub-state or a range of sub-states.		:The aim is to continually improve the usability of UML-B in the light of experience. Although the motivation for a more integrated version of UML-B that would be attractive to experienced Event-B users has been recognised for some time, the original aim of UML-B was to make formal modelling more accessible to new users. This aim remains valid and therefore the current non-integrated UML-B should be developed and enhanced wherever possible. Therefore, some issues concerning its usability have been identified and rectified. Some of these issues required enhancements to the modelling language. In particular, several case studies have highlighted the need for transitions that may be taken from any sub-state or a range of sub-states.

	== UML-B State-machine Animation Plug-in==		== UML-B State-machine Animation Plug-in==

imported>Tommy: /* Enhancement and Maintenance of Existing UML-B */

2011-01-27T10:46:27Z

Enhancement and Maintenance of Existing UML-B

← Older revision		Revision as of 10:46, 27 January 2011
Line 16:		Line 16:
	:# Enhancements to improve usability		:# Enhancements to improve usability
	:#* Report to user if translation didn't proceed due to model validator - previously, it was not clear when the model had failed validation and the translation had not been executed.		:#* Report to user if translation didn't proceed due to model validator - previously, it was not clear when the model had failed validation and the translation had not been executed.
	:#* Improve refresh of diagrams - in some situations the diagram graphics did not update error marking and ~~properties~~ changes unless some other event caused a refresh.		:#* Improve refresh of diagrams - in some situations the diagram graphics did not update error marking and property changes unless some other event caused a refresh.
	:#* Improvements and additions to model validations - some model validations were inconsistent or incomplete.		:#* Improvements and additions to model validations - some model validations were inconsistent or incomplete.
	:#* Preference for line routing style for each diagram type - allows the user to choose whether to use rectilinear or oblique line routing for each diagram type.		:#* Preference for line routing style for each diagram type - allows the user to choose whether to use rectilinear or oblique line routing for each diagram type.

imported>Colin: /* Planning */

2011-01-27T09:55:07Z

Planning

← Older revision		Revision as of 09:55, 27 January 2011
Line 64:		Line 64:

	= Planning =		= Planning =
	~~During the coming year, special efforts will be made on the following topics,~~		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,
	* 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 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,		* Support for re-attaching links (e.g. transitions) to different source/target elements,
Line 77:		Line 71:
	* Integration of Context Diagram model elements on Class diagrams,		* Integration of Context Diagram model elements on Class diagrams,
	* Improve facilities for navigating between state-machines and visualising multiple state-machines.		* Improve facilities for navigating between state-machines and visualising multiple state-machines.

			The new iUML-B tools will continue to be developed and release including,
			* Enhancement of the Project Diagram Plugin for Event-B to make it extensible and/or to automatically cater for future component types,
			* Release of the State-machine diagram plug-in as an integrated part of Event-B modelling,
			* Development of a new plug-in to support event refinement diagrams.

	== References ==		== References ==

imported>Colin: /* Choices / Decisions */

2011-01-27T09:45:55Z

Choices / Decisions

← Older revision		Revision as of 09:45, 27 January 2011
Line 43:		Line 43:

	= Choices / Decisions =		= Choices / Decisions =

			== Enhancement and Maintenance of Existing UML-B ==
			: As UML-B is already a relatively mature product attracting strong interest from various institutions, the main goal currently is to improve usability and stability of the tool rather than develop major new features. Consequently development has concentrated primarily on improving the basic tooling and user interface. However, when users are limited by the modelling language this can be seen as a usability issue and may result in the addition of new features to the language.

	== UML-B State-machine Animation ==		== UML-B State-machine Animation ==

imported>Colin: /* Motivations */

2011-01-27T09:36:24Z

Motivations

← Older revision		Revision as of 09:36, 27 January 2011
Line 34:		Line 34:

	== Enhancement and Maintenance of Existing UML-B ==		== Enhancement and Maintenance of Existing UML-B ==
	The aim is to continually improve the usability of UML-B in the light of experience. Although the motivation for a more integrated version of UML-B that would be attractive to experienced Event-B users has been recognised for some time, the original aim of UML-B was to make formal modelling more accessible to new users. This aim remains valid and therefore the current non-integrated UML-B should be developed and enhanced wherever possible. Therefore, some issues concerning its usability have been identified and rectified. Some of these required enhancements to the modelling language. In particular, several case studies have highlighted the need for transitions that may be taken from any sub-state or a range of sub-states.		:The aim is to continually improve the usability of UML-B in the light of experience. Although the motivation for a more integrated version of UML-B that would be attractive to experienced Event-B users has been recognised for some time, the original aim of UML-B was to make formal modelling more accessible to new users. This aim remains valid and therefore the current non-integrated UML-B should be developed and enhanced wherever possible. Therefore, some issues concerning its usability have been identified and rectified. Some of these required enhancements to the modelling language. In particular, several case studies have highlighted the need for transitions that may be taken from any sub-state or a range of sub-states.

	== UML-B State-machine Animation Plug-in==		== UML-B State-machine Animation Plug-in==
	The motivation for the State-machine Animation plug-in was to extend UML-B with animation capabilities similar to those that the 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 State-machine Animation plug-in uses the ProB tool to animate the translated Event-B models and provides an animation interface based on the UML-B State-machine models.		:The motivation for the State-machine Animation plug-in was to extend UML-B with animation capabilities similar to those that the 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 State-machine Animation plug-in uses the ProB tool to animate the translated Event-B models and provides an animation interface based on the UML-B State-machine models.

	== iUML-B - Integrated UML-B ==		== iUML-B - Integrated UML-B ==
	The motivations for an alternative version of UML-B that is tightly integrated with Event-B was recognised at the beginning of the Deploy project. The aim of UML-B was to provide an easier modelling environment for users that were familiar with UML-like modelling but not with textual mathematical notations. Experienced Event-B users would also benefit from the visualisations provided by UML-B but they do not wish to be distanced from the generated Event-B and would prefer to be able to create parts of their models in the Event-B notation alongside the diagrammatic parts.		:The motivations for an alternative version of UML-B that is tightly integrated with Event-B was recognised at the beginning of the Deploy project. The aim of UML-B was to provide an easier modelling environment for users that were familiar with UML-like modelling but not with textual mathematical notations. Experienced Event-B users would also benefit from the visualisations provided by UML-B but they do not wish to be distanced from the generated Event-B and would prefer to be able to create parts of their models in the Event-B notation alongside the diagrammatic parts.

	= Choices / Decisions =		= Choices / Decisions =

imported>Colin: /* Choices / Decisions */

2011-01-27T09:35:47Z

Choices / Decisions

← Older revision		Revision as of 09:35, 27 January 2011
Line 43:		Line 43:

	= Choices / Decisions =		= Choices / Decisions =

			== UML-B State-machine Animation ==
			: 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.

	== iUML-B - Integrated UML-B ==		== iUML-B - Integrated UML-B ==
	: A precursor stage to developing iUML-B 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. A plug-in for State-Machine diagram models as an extension to the Event-B EMF models is currently being developed and is nearing release.		: A precursor stage to developing iUML-B 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. A plug-in for State-Machine diagram models as an extension to the Event-B EMF models is currently being developed and is nearing release.

	~~== 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 =		= Available Documentation =