Difference between revisions of "D23 UML-B"
imported>Colin (New page: === Overview === This first paragraph shall identify the involved partners and give an overview of the contribution. In particular, it shall provide answers to the following questions: * W...) |
imported>Colin |
||
| Line 1: | Line 1: | ||
=== Overview === | === Overview === | ||
| − | This | + | This part of the deliverable describes improvements to the UML-B plug-in feature, which is the responsibility of University of Southampton. |
| − | + | ||
| − | + | A new plug-in feature has been developed to provide Animation of UML-B State-machine diagrams. This feature was developed by University of Southampton. | |
| − | + | ||
| − | + | The longer term development of UML-B relies on an EMF representation of Event-B. The development of a new EMF Event-B plugin-in feature is also described in this section. This feature was initially developed by University of Southampton, Heinrich Heine Universistat, Duesseldorf and University of Newcastle. It is now mostly maintained and developed by University of Southampton | |
| − | + | ||
=== Motivations === | === Motivations === | ||
Revision as of 16:52, 25 November 2009
Overview
This part of the deliverable describes improvements to the UML-B plug-in feature, which is the responsibility of University of Southampton.
A new plug-in feature has been developed to provide Animation of UML-B State-machine diagrams. This feature was developed by University of Southampton.
The longer term development of UML-B relies on an EMF representation of Event-B. The development of a new EMF Event-B plugin-in feature is also described in this section. This feature was initially developed by University of Southampton, Heinrich Heine Universistat, Duesseldorf and University of Newcastle. It is now mostly maintained and developed by University of Southampton
Motivations
This paragraph shall express the motivation for each tool extension and improvement. More precisely, it shall first indicate the state before the work, the encountered difficulties, and shall highlight the requirements (eg. those of industrial partners). Then, it shall summarize how these requirements are addressed and what are the main benefits.
Choices / Decisions
This paragraph shall summarize the decisions (eg. design decisions) and justify them. Thus, it may present the studied solutions, through their main advantages and inconvenients, to legitimate the final choices.
Available Documentation
This paragraph shall give pointers to the available wiki pages or related publications. This documentation may contain:
- Requirements.
- Pre-studies (states of the art, proposals, discussions).
- Technical details (specifications).
- Teaching materials (tutorials).
- User's guides.
A distinction shall be made on the one hand between these different categories, and on the other hand between documentation written for developers and documentation written for end-users.
Planning
This paragraph shall give a timeline and current status (as of 29 Jan 2010).
