D23 General Platform Maintenance - Revision history

imported>Laurent: /* Planning */

2010-01-27T11:30:32Z

Planning

← Older revision		Revision as of 11:30, 27 January 2010
Line 94:		Line 94:

	* Documentation.		* Documentation.
	: The purpose is to continuously increase ~~the~~ available documentation on the Wiki. It may ~~contains~~ requirements, pre-studies (states of the art, proposals, discussions), technical details (specifications), teaching materials (tutorials), user's guides, etc. The intended audience may be ~~the~~ developers or ~~the~~ end-users.		: The purpose is to continuously increase and improve available documentation on the Wiki. It may contain requirements, pre-studies (states of the art, proposals, discussions), technical details (specifications), teaching materials (tutorials), user's guides, etc. The intended audience may be developers or end-users.

	[[Category:D23 Deliverable]]		[[Category:D23 Deliverable]]

imported>Laurent: /* Motivations */

2010-01-27T11:26:19Z

Motivations

← Older revision		Revision as of 11:26, 27 January 2010
Line 57:		Line 57:
	\|}		\|}

	The priorities are discussed during the WP9 meetings (a management conference call ~~is planned every two weeks~~, ~~and the~~ WP9 meetings ~~are organised~~ during ~~the~~ DEPLOY workshops).		The priorities are discussed during the WP9 meetings (bi-weekly management conference call, WP9 face-to-face meetings during DEPLOY workshops).

	= Choices / Decisions =		= Choices / Decisions =

imported>Laurent: /* Motivations */

2010-01-27T11:24:31Z

Motivations

← Older revision		Revision as of 11:24, 27 January 2010
Line 23:		Line 23:
	The main evolutions of the Rodin platform are driven by the description of work for the DEPLOY project and the requirements expressed by industrial WP1 to WP4 partners or by advanced users during the lifecycle of the project.		The main evolutions of the Rodin platform are driven by the description of work for the DEPLOY project and the requirements expressed by industrial WP1 to WP4 partners or by advanced users during the lifecycle of the project.

	Beyond that, any user registered on SourceForge may record any encountered bug on the Rodin platform or request a new feature, using the dedicated [http://wiki.event-b.org/index.php/D23_General_Platform_Maintenance#Available_Documentation trackers]. Depending on the category, the bug / feature is assigned to the WP9 partner who is in charge of ~~its treatment~~:		Beyond that, any user registered on SourceForge may record any encountered bug on the Rodin platform or request a new feature, using the dedicated [http://wiki.event-b.org/index.php/D23_General_Platform_Maintenance#Available_Documentation trackers]. Depending on the category, the bug / feature is assigned to the WP9 partner who is in charge of processing it:
	{{SimpleHeader}}		{{SimpleHeader}}
	\|-		\|-

imported>Laurent: /* Motivations */

2010-01-27T11:24:00Z

Motivations

← Older revision		Revision as of 11:24, 27 January 2010
Line 21:		Line 21:

	= Motivations =		= Motivations =
	The main evolutions of the Rodin platform are driven by the description of work for the DEPLOY project and the requirements expressed by industrial WP1 to ~~WP5~~ partners or by ~~consultants~~ during the lifecycle of the project.		The main evolutions of the Rodin platform are driven by the description of work for the DEPLOY project and the requirements expressed by industrial WP1 to WP4 partners or by advanced users during the lifecycle of the project.

	Beyond that, any user registered on SourceForge may record any encountered bug on the Rodin platform or request a new feature, using the dedicated [http://wiki.event-b.org/index.php/D23_General_Platform_Maintenance#Available_Documentation trackers]. Depending on the category, the bug / feature is assigned to the WP9 partner who is in charge of its treatment:		Beyond that, any user registered on SourceForge may record any encountered bug on the Rodin platform or request a new feature, using the dedicated [http://wiki.event-b.org/index.php/D23_General_Platform_Maintenance#Available_Documentation trackers]. Depending on the category, the bug / feature is assigned to the WP9 partner who is in charge of its treatment:

imported>Pascal: /* Planning */

2010-01-26T17:58:56Z

Planning

← Older revision		Revision as of 17:58, 26 January 2010
Line 84:		Line 84:
	The [http://wiki.event-b.org/index.php/D23_General_Platform_Maintenance#Available_Documentation Rodin Platform Releases] wiki page lists in particular the upcoming releases and give the scheduled release dates.		The [http://wiki.event-b.org/index.php/D23_General_Platform_Maintenance#Available_Documentation Rodin Platform Releases] wiki page lists in particular the upcoming releases and give the scheduled release dates.

	Special efforts will be made on the following topics, which are ~~highlighted~~ by all industrial ~~partners~~:		Special efforts will be made on the following topics, which are requested by all users in an industrial context:
	* Mathematical Extensions.		* Mathematical Extensions.
	: Currently, the operators and basic predicates of the Event-B mathematical language supported by the Rodin platform are fixed. The purpose is to extend the platform to support user-defined data types and associated operators, including inductive data types. Users will then be able to define operators of polymorphic type as well as parameterised predicate definitions.		: Currently, the operators and basic predicates of the Event-B mathematical language supported by the Rodin platform are fixed. The purpose is to extend the platform to support user-defined data types and associated operators, including inductive data types. Users will then be able to define operators of polymorphic type as well as parameterised predicate definitions.

imported>Pascal: /* Planning */

2010-01-26T17:56:31Z

Planning

← Older revision		Revision as of 17:56, 26 January 2010
Line 90:		Line 90:
	* Team-based Development.		* Team-based Development.
	: The purpose is to perform simultaneous developments.		: The purpose is to perform simultaneous developments.
	: The [http://wiki.event-b.org/index.php/D23_Decomposition Decomposition plug-in] gives an answer to this requirement by allowing to cut a model in sub-models which may be handled independently. In the same manner, the [http://wiki.event-b.org/index.php/EMF_Compare_Editor_installation EMF Compare Editor] enables the comparison of machines and contexts: it is a first step to be able to use the Rodin platform in a team environment by putting a code repository (e.g. Subversion) underneath it.		: The [http://wiki.event-b.org/index.php/D23_Decomposition Decomposition plug-in] gives an answer to this requirement by allowing to cut a model in sub-models which may be handled independently. In the same manner, the [http://wiki.event-b.org/index.php/EMF_Compare_Editor_installation EMF Compare Editor] enables the comparison of machines and contexts: it is a first step to be able to use the Rodin platform in a team environment by putting a code repository (e.g., Subversion) underneath it.
	: In order to understand the problem properly, some usage scenarios for [http://wiki.event-b.org/index.php/Scenarios_for_Team-based_Development team-based development] and for [http://wiki.event-b.org/index.php/Scenarios_for_Merging_Proofs merging proofs] have already been written. Moreover, a page has been initiated to remember the main requirements (see [http://wiki.event-b.org/index.php/Teamwork_Requirements Teamwork Requirements]). These pages provide a basis for brainstorming and further developments on the topic.		: In order to understand the problem properly, some usage scenarios for [http://wiki.event-b.org/index.php/Scenarios_for_Team-based_Development team-based development] and for [http://wiki.event-b.org/index.php/Scenarios_for_Merging_Proofs merging proofs] have already been written. Moreover, a page has been initiated to remember the main requirements (see [http://wiki.event-b.org/index.php/Teamwork_Requirements Teamwork Requirements]). These pages provide a basis for brainstorming and further developments on the topic.

imported>Pascal: /* Planning */

2010-01-26T17:56:11Z

Planning

← Older revision		Revision as of 17:56, 26 January 2010
Line 84:		Line 84:
	The [http://wiki.event-b.org/index.php/D23_General_Platform_Maintenance#Available_Documentation Rodin Platform Releases] wiki page lists in particular the upcoming releases and give the scheduled release dates.		The [http://wiki.event-b.org/index.php/D23_General_Platform_Maintenance#Available_Documentation Rodin Platform Releases] wiki page lists in particular the upcoming releases and give the scheduled release dates.

	Special efforts will be made on the following topics:		Special efforts will be made on the following topics, which are highlighted by all industrial partners:
	* Mathematical Extensions.		* Mathematical Extensions.
	: Currently, the operators and basic predicates of the Event-B mathematical language supported by the Rodin platform are fixed. The purpose is to extend the platform to support user-defined data types and associated operators, including inductive data types. Users will then be able to define operators of polymorphic type as well as parameterised predicate definitions.		: Currently, the operators and basic predicates of the Event-B mathematical language supported by the Rodin platform are fixed. The purpose is to extend the platform to support user-defined data types and associated operators, including inductive data types. Users will then be able to define operators of polymorphic type as well as parameterised predicate definitions.
Line 90:		Line 90:
	* Team-based Development.		* Team-based Development.
	: The purpose is to perform simultaneous developments.		: The purpose is to perform simultaneous developments.
	: ~~In order to understand the problem properly, some usage scenarios (see~~ [http://wiki.event-b.org/index.php/~~Scenarios_for_Team~~-~~based_Development Scenarios for Team-based Development~~]~~) for team~~-~~based Development have already been written~~, ~~and a page has also been started to express merging proofs scenarios (see~~ [http://wiki.event-b.org/index.php/~~Scenarios_for_Merging_Proofs Scenarios for Merging Proofs~~]).		: The [http://wiki.event-b.org/index.php/D23_Decomposition Decomposition plug-in] gives an answer to this requirement by allowing to cut a model in sub-models which may be handled independently. In the same manner, the [http://wiki.event-b.org/index.php/EMF_Compare_Editor_installation EMF Compare Editor] enables the comparison of machines and contexts: it is a first step to be able to use the Rodin platform in a team environment by putting a code repository (e.g. Subversion) underneath it.
	~~: A prototype plug-in is available, which~~ enables the ~~use~~ of ~~the EMF compare editor for~~ machines and contexts~~. The DEPLOY partners will try out this plug-in and gather requirements for~~ the ~~teamwork plug-~~in.		: In order to understand the problem properly, some usage scenarios for [http://wiki.event-b.org/index.php/Scenarios_for_Team-based_Development team-based development] and for [http://wiki.event-b.org/index.php/Scenarios_for_Merging_Proofs merging proofs] have already been written. Moreover, a page has been initiated to remember the main requirements (see [http://wiki.event-b.org/index.php/Teamwork_Requirements Teamwork Requirements]). These pages provide a basis for brainstorming and further developments on the topic.
	: ~~See~~ [http://wiki.event-b.org/index.php/~~EMF_Compare_Editor_Investigation EMF Compare Editor Investigation~~] ~~(Implementation issues).~~
	~~: See~~ [http://wiki.event-b.org/index.php/~~EMF_Compare_Editor_installation EMF Compare Editor installation~~] ~~(How~~ to ~~install~~ the ~~EMF Compare editor).~~
	~~: See~~ [http://wiki.event-b.org/index.php/Teamwork_Requirements Teamwork Requirements] ~~(Feedback page / Requirements~~).

	* Documentation.		* Documentation.

imported>Pascal: /* Added paragraph on mathematical extensions. */

2010-01-26T15:35:59Z

Added paragraph on mathematical extensions.

← Older revision		Revision as of 15:35, 26 January 2010
Line 85:		Line 85:

	Special efforts will be made on the following topics:		Special efforts will be made on the following topics:
	* Team-based ~~development~~.		* Mathematical Extensions.
			: Currently, the operators and basic predicates of the Event-B mathematical language supported by the Rodin platform are fixed. The purpose is to extend the platform to support user-defined data types and associated operators, including inductive data types. Users will then be able to define operators of polymorphic type as well as parameterised predicate definitions.

			* Team-based Development.
	: The purpose is to perform simultaneous developments.		: The purpose is to perform simultaneous developments.
	: In order to understand the problem properly, some usage scenarios (see [http://wiki.event-b.org/index.php/Scenarios_for_Team-based_Development Scenarios for Team-based Development]) for team-based Development have already been written, and a page has also been started to express merging proofs scenarios (see [http://wiki.event-b.org/index.php/Scenarios_for_Merging_Proofs Scenarios for Merging Proofs]).		: In order to understand the problem properly, some usage scenarios (see [http://wiki.event-b.org/index.php/Scenarios_for_Team-based_Development Scenarios for Team-based Development]) for team-based Development have already been written, and a page has also been started to express merging proofs scenarios (see [http://wiki.event-b.org/index.php/Scenarios_for_Merging_Proofs Scenarios for Merging Proofs]).

imported>Pascal: /* Planning */

2010-01-08T11:11:22Z

Planning

← Older revision		Revision as of 11:11, 8 January 2010
Line 82:		Line 82:

	= Planning =		= Planning =
	The [[#~~Available%20Documentation \|~~ Rodin Platform Releases]] wiki page lists in particular the upcoming releases and give the scheduled release dates.		The [http://wiki.event-b.org/index.php/D23_General_Platform_Maintenance#Available_Documentation Rodin Platform Releases] wiki page lists in particular the upcoming releases and give the scheduled release dates.

	Special efforts will be made on the following topics:		Special efforts will be made on the following topics:
	* Team-based development.		* Team-based development.
	: The purpose is to perform simultaneous developments.		: The purpose is to perform simultaneous developments.
	: In order to understand the problem properly, some usage scenarios (see [http://wiki.event-b.org/index.php/Scenarios_for_Team-based_Development ~~http://wiki.event~~-~~b.org/index.php/Scenarios_for_Team-based_Development~~]) for team-based Development have already been written, and a page has also been started to express merging proofs scenarios (see [http://wiki.event-b.org/index.php/Scenarios_for_Merging_Proofs ~~http://wiki.event-b.org/index.php/Scenarios_for_Merging_Proofs~~]).		: In order to understand the problem properly, some usage scenarios (see [http://wiki.event-b.org/index.php/Scenarios_for_Team-based_Development Scenarios for Team-based Development]) for team-based Development have already been written, and a page has also been started to express merging proofs scenarios (see [http://wiki.event-b.org/index.php/Scenarios_for_Merging_Proofs Scenarios for Merging Proofs]).
	: A prototype plug-in is available, which enables the use of the EMF compare editor for machines and contexts. The DEPLOY partners will try out this plug-in and gather requirements for the teamwork plug-in.		: A prototype plug-in is available, which enables the use of the EMF compare editor for machines and contexts. The DEPLOY partners will try out this plug-in and gather requirements for the teamwork plug-in.
	: See [http://wiki.event-b.org/index.php/EMF_Compare_Editor_Investigation ~~http://wiki.event-b.org/index.php/EMF_Compare_Editor_Investigation~~] (Implementation issues).		: See [http://wiki.event-b.org/index.php/EMF_Compare_Editor_Investigation EMF Compare Editor Investigation] (Implementation issues).
	: See [http://wiki.event-b.org/index.php/EMF_Compare_Editor_installation ~~http://wiki.event-b.org/index.php/EMF_Compare_Editor_installation~~] (How to install the EMF Compare editor).		: See [http://wiki.event-b.org/index.php/EMF_Compare_Editor_installation EMF Compare Editor installation] (How to install the EMF Compare editor).
	: See [http://wiki.event-b.org/index.php/Teamwork_Requirements ~~http://wiki.event-b.org/index.php/Teamwork_Requirements~~] (Feedback page / Requirements).		: See [http://wiki.event-b.org/index.php/Teamwork_Requirements Teamwork Requirements] (Feedback page / Requirements).

	* Documentation.		* Documentation.

imported>Pascal: /* Available Documentation */

2010-01-08T11:09:41Z

Available Documentation

← Older revision		Revision as of 11:09, 8 January 2010
Line 75:		Line 75:
	* Release notes.		* Release notes.
	: See [http://wiki.event-b.org/index.php/Rodin_Platform_Releases Rodin Platform Releases].		: See [http://wiki.event-b.org/index.php/Rodin_Platform_Releases Rodin Platform Releases].
	: More details are provided in the notes distributed with each release (eg. [~~http://sourceforge.net/project/shownotes.php?release_id=693928~~ http://sourceforge.net/project/shownotes.php?release_id=693928]).		: More details are provided in the notes distributed with each release (eg. [http://sourceforge.net/project/shownotes.php?release_id=693928]).
	* Bugs.		* Bugs.
	: See [http://sourceforge.net/tracker/?atid=651669&group_id=108850 ~~http://sourceforge.net/tracker/?group_id=108850&atid=651669~~].		: See [http://sourceforge.net/tracker/?atid=651669&group_id=108850].
	* Feature requests.		* Feature requests.
	: See [~~http://sourceforge.net/tracker/?group_id=108850&atid=651672~~ http://sourceforge.net/tracker/?group_id=108850&atid=651672].		: See [http://sourceforge.net/tracker/?group_id=108850&atid=651672].

	= Planning =		= Planning =