D45 General Platform Maintenance - Revision history

imported>Tommy: /* Motivations */

2012-04-23T10:12:02Z

Motivations

@@ Line 21: / Line 21: @@
 == Motivations ==
 The tasks to resolve the issues faced by the DEPLOY industrial partners have been listed and have been assigned to groups according to their priority. A high priority means a high need in the outcome of a given task. Group 1 has the highest priority, group 2 has an intermediate priority, and group 3 has the lowest priority. Group 4 concerns topics that could not be resourced during the lifetime of DEPLOY.
 [[Image:Table_Priorities_Tasks.png]]

imported>Tommy: /* Motivations */

2012-04-23T10:11:39Z

Motivations

← Older revision		Revision as of 10:11, 23 April 2012
Line 66:		Line 66:
	\|Code Generation \|\| Southampton \|\|Integrity of Code Generation		\|Code Generation \|\| Southampton \|\|Integrity of Code Generation
	\|}		\|}

			[[Image:Table_Priorities_Tasks.png]]

	The platform maintenance, as it can be deduced from the above tables, mainly concerned stability and performance improvement. These topics will be discussed and detailed in a separate chapter about scalability improvements.<br>		The platform maintenance, as it can be deduced from the above tables, mainly concerned stability and performance improvement. These topics will be discussed and detailed in a separate chapter about scalability improvements.<br>

imported>Tommy at 09:58, 23 April 2012

2012-04-23T09:58:51Z

Show changes

imported>Tommy: Reverted edits by Tommy (Talk); changed back to last version by Alexili

2012-04-23T09:57:07Z

Reverted edits by Tommy (Talk); changed back to last version by Alexili

Show changes

imported>Tommy at 09:56, 23 April 2012

2012-04-23T09:56:36Z

Show changes

imported>Tommy: /* Motivations */

2012-04-23T09:03:58Z

Motivations

← Older revision		Revision as of 09:03, 23 April 2012
Line 33:		Line 33:
	\|ProB Disprover (incl. counter examples to DLF POs) \|\| Düsseldorf \|\| Plug-in incompatibilities \|\| Newcastle		\|ProB Disprover (incl. counter examples to DLF POs) \|\| Düsseldorf \|\| Plug-in incompatibilities \|\| Newcastle
	\|-		\|-
	\|Stability (crash, corruption, etc.) \|\| SYSTEREL \|\|Model-based testing \|\| Pitesti/Düsseldorf		\|Stability (crash, corruption, etc.) \|\| SYSTEREL \|\| Model-based testing \|\| Pitesti/Düsseldorf
	\|-		\|-
	\|Editors \|\| SYSTEREL/Düsseldorf \|\| ProR \|\| Düsseldorf		\|Editors \|\| SYSTEREL/Düsseldorf \|\| ProR \|\| Düsseldorf
Line 42:		Line 42:
	! scope=col \| Group 3 \|\| Responsible \|\| Group 4		! scope=col \| Group 3 \|\| Responsible \|\| Group 4
	\|-		\|-
	\|Scalability <br /> - Generic instantiation <br /> - UML-B maintenance <br /> \|\| . ETH Zürich/Southampton <br /> Southampton \|\|Prover Integrity		\|Scalability <br /> - Generic instantiation <br /> - UML-B maintenance <br /> \|\| . <br> ETH Zürich/Southampton <br /> Southampton \|\|Prover Integrity
	\|-		\|-
	\|Code Generation \|\| Southampton \|\|Integrity of Code Generation		\|Code Generation \|\| Southampton \|\|Integrity of Code Generation

imported>Tommy: /* Motivations */

2012-04-23T09:03:14Z

Motivations

← Older revision		Revision as of 09:03, 23 April 2012
Line 40:		Line 40:
	{{SimpleHeader}}		{{SimpleHeader}}
	\|-		\|-
	! scope=col \| Group 3 \|\| Responsible		! scope=col \| Group 3 \|\| Responsible \|\| Group 4
	\|-		\|-
	\|Scalability <br /> - Generic instantiation <br /> - UML-B maintenance <br /> \|\| . ETH Zürich/Southampton <br /> Southampton		\|Scalability <br /> - Generic instantiation <br /> - UML-B maintenance <br /> \|\| . ETH Zürich/Southampton <br /> Southampton \|\|Prover Integrity
	\|-		\|-
	\|Code Generation \|\| Southampton		\|Code Generation \|\| Southampton \|\|Integrity of Code Generation
	\|}
	~~{{SimpleHeader}}~~
	\|-
	~~! scope=col \| Group 4~~
	\|-
	~~\|Prover Integrity~~
	\|-
	\|Integrity of Code Generation
	\|}		\|}

imported>Tommy: /* Available Documentation */

2012-04-23T08:28:30Z

Available Documentation

← Older revision		Revision as of 08:28, 23 April 2012
Line 294:		Line 294:

	== Available Documentation ==		== Available Documentation ==
	* BMotion Studio Documentation for end users and plugin developers <ref>http://www.stups.uni-duesseldorf.de/BMotionStudio</ref>		* BMotion Studio Documentation for end users and plugin developers.<ref>http://www.stups.uni-duesseldorf.de/BMotionStudio</ref>
	* Context sensitive help is in work		* Context sensitive help is under work.

	== Status ==		== Status ==

imported>Tommy: /* Choices / Decisions */

2012-04-23T08:25:59Z

Choices / Decisions

← Older revision		Revision as of 08:25, 23 April 2012
Line 69:		Line 69:

	== Choices / Decisions ==		== Choices / Decisions ==
	* '''Revisited task priority'''		'''Revisited task priority'''<br>
	This year, the process of giving priority to maintenance tasks was revisited according to the refocus mentioned above. The aim was to address all the major scalability issues before the end of DEPLOY. Thus, the requests coming from DEPLOY partners were given high priorities, and they were also prioritized against the already planned tasks coming from both DEPLOY partners and the Description of Work.		This year, the process of giving priority to maintenance tasks was revisited according to the refocus mentioned above. The aim was to address all the major scalability issues before the end of DEPLOY. Thus, the requests coming from DEPLOY partners were given high priorities, and they were also prioritized against the already planned tasks coming from both DEPLOY partners and the Description of Work.
	* '''Keep 32-bit versions of the Rodin platform on Linux and Windows systems'''		'''Keep 32-bit versions of the Rodin platform on Linux and Windows systems'''<br>
	It was asked by end users to make both 32-bit and 64-bit versions of the Rodin platform available for Linux and Windows platforms. Only a 64-bit version of Rodin is available on Mac platforms as 32-bit Mac (early 2006) platforms are no longer maintained. The request to offer 64-bit was motivated by the possibility to increase for them the available Java heap size for some memory greedy platforms (these before Rodin 2.3). After having ensured to get all physical platforms to test the different versions, and despite the drawbacks of assembling and maintaining more platforms (5 platforms instead of 3), Rodin 2.4 has started a new era where Rodin platforms are available on Linux and Windows 64-bit as well as 32-bit.		It was asked by end users to make both 32-bit and 64-bit versions of the Rodin platform available for Linux and Windows platforms. Only a 64-bit version of Rodin is available on Mac platforms as 32-bit Mac (early 2006) platforms are no longer maintained. The request to offer 64-bit was motivated by the possibility to increase for them the available Java heap size for some memory greedy platforms (these before Rodin 2.3). After having ensured to get all physical platforms to test the different versions, and despite the drawbacks of assembling and maintaining more platforms (5 platforms instead of 3), Rodin 2.4 has started a new era where Rodin platforms are available on Linux and Windows 64-bit as well as 32-bit.

imported>Tommy: /* Choices / Decisions */

2012-04-23T08:24:49Z

Choices / Decisions

← Older revision		Revision as of 08:24, 23 April 2012
Line 69:		Line 69:

	== Choices / Decisions ==		== Choices / Decisions ==
	* Revisited task priority		* '''Revisited task priority'''
	This year, the process of giving priority to maintenance tasks was revisited according to the refocus mentioned above. The aim was to address all the major scalability issues before the end of DEPLOY. Thus, the requests coming from DEPLOY partners were given high priorities, and they were also prioritized against the already planned tasks coming from both DEPLOY partners and the Description of Work.		This year, the process of giving priority to maintenance tasks was revisited according to the refocus mentioned above. The aim was to address all the major scalability issues before the end of DEPLOY. Thus, the requests coming from DEPLOY partners were given high priorities, and they were also prioritized against the already planned tasks coming from both DEPLOY partners and the Description of Work.
	* Keep 32-bit versions of the Rodin platform on Linux and Windows systems		* '''Keep 32-bit versions of the Rodin platform on Linux and Windows systems'''
	It was asked by end users to make both 32-bit and 64-bit versions of the Rodin platform available for Linux and Windows platforms. Only a 64-bit version of Rodin is available on Mac platforms as 32-bit Mac (early 2006) platforms are no longer maintained. The request to offer 64-bit was motivated by the possibility to increase for them the available Java heap size for some memory greedy platforms (these before Rodin 2.3). After having ensured to get all physical platforms to test the different versions, and despite the drawbacks of assembling and maintaining more platforms (5 platforms instead of 3), Rodin 2.4 has started a new era where Rodin platforms are available on Linux and Windows 64-bit as well as 32-bit.		It was asked by end users to make both 32-bit and 64-bit versions of the Rodin platform available for Linux and Windows platforms. Only a 64-bit version of Rodin is available on Mac platforms as 32-bit Mac (early 2006) platforms are no longer maintained. The request to offer 64-bit was motivated by the possibility to increase for them the available Java heap size for some memory greedy platforms (these before Rodin 2.3). After having ensured to get all physical platforms to test the different versions, and despite the drawbacks of assembling and maintaining more platforms (5 platforms instead of 3), Rodin 2.4 has started a new era where Rodin platforms are available on Linux and Windows 64-bit as well as 32-bit.