Class Diagram - Revision history

imported>WikiSysop at 13:06, 4 January 2013

2013-01-04T13:06:11Z

← Older revision		Revision as of 13:06, 4 January 2013
Line 8:		Line 8:
	[[Category:User documentation]]		[[Category:User documentation]]
	[[Category:UML-B]]		[[Category:UML-B]]

	~~[git://git.code.sf.net/p/rodin-b-sharp/rodincore]~~

imported>WikiSysop at 13:05, 4 January 2013

2013-01-04T13:05:55Z

← Older revision		Revision as of 13:05, 4 January 2013
Line 8:		Line 8:
	[[Category:User documentation]]		[[Category:User documentation]]
	[[Category:UML-B]]		[[Category:UML-B]]

			[git://git.code.sf.net/p/rodin-b-sharp/rodincore]

imported>Mathieu: Robot: Changing Category:User Documentation

2008-09-10T20:27:13Z

Robot: Changing Category:User Documentation

← Older revision		Revision as of 20:27, 10 September 2008
Line 6:		Line 6:
	Classes may contain events that modify their attributes. Event parameters can be added to an event providing local variables to be used in the transition’s guards and actions. These parameters can be used to model inputs and outputs. Class events implicitly utilise a parameter to non-deterministically select the affected instance of the class. This instance is referred to via the reserved word self when referencing the attributes of the class.		Classes may contain events that modify their attributes. Event parameters can be added to an event providing local variables to be used in the transition’s guards and actions. These parameters can be used to model inputs and outputs. Class events implicitly utilise a parameter to non-deterministically select the affected instance of the class. This instance is referred to via the reserved word self when referencing the attributes of the class.

			[[Category:User documentation]]
	[[Category:User ~~Documentation~~]]
	[[Category:UML-B]]		[[Category:UML-B]]

imported>Mathieu: Category:UML-B

2008-07-10T07:02:38Z

Category:UML-B

← Older revision		Revision as of 07:02, 10 July 2008
Line 8:		Line 8:

	[[Category:User Documentation]]		[[Category:User Documentation]]
	[[Category:~~Plugin~~]]		[[Category:UML-B]]

imported>Mathieu: Category:User Documentation Category:Plugin

2008-07-02T17:22:53Z

Category:User Documentation Category:Plugin

← Older revision		Revision as of 17:22, 2 July 2008
Line 5:		Line 5:

	Classes may contain events that modify their attributes. Event parameters can be added to an event providing local variables to be used in the transition’s guards and actions. These parameters can be used to model inputs and outputs. Class events implicitly utilise a parameter to non-deterministically select the affected instance of the class. This instance is referred to via the reserved word self when referencing the attributes of the class.		Classes may contain events that modify their attributes. Event parameters can be added to an event providing local variables to be used in the transition’s guards and actions. These parameters can be used to model inputs and outputs. Class events implicitly utilise a parameter to non-deterministically select the affected instance of the class. This instance is referred to via the reserved word self when referencing the attributes of the class.


			[[Category:User Documentation]]
			[[Category:Plugin]]

imported>Colin at 12:34, 3 April 2008

2008-04-03T12:34:32Z

← Older revision		Revision as of 12:34, 3 April 2008
Line 1:		Line 1:
			Return to [[UML-B]]

	Class diagrams are used to describe the behavioural part of a model. Classes represent subsets (variable or fixed) of the ClassTypes that were introduced in the context. The class’ associations and attributes are similar to those in the context but represent variables instead of constants.		Class diagrams are used to describe the behavioural part of a model. Classes represent subsets (variable or fixed) of the ClassTypes that were introduced in the context. The class’ associations and attributes are similar to those in the context but represent variables instead of constants.
	The correspondence between an association’s multiplicity constraints and the constraints on the resulting Event-B relationship is clear from the drawing tool. The multiplicity properties are described in the properties view using the usual mathematical terminology (functional, total, injective, surjective) with the UML style multiplicity also shown and annotated automatically on the diagram.		The correspondence between an association’s multiplicity constraints and the constraints on the resulting Event-B relationship is clear from the drawing tool. The multiplicity properties are described in the properties view using the usual mathematical terminology (functional, total, injective, surjective) with the UML style multiplicity also shown and annotated automatically on the diagram.

	Classes may contain events that modify their attributes. Event parameters can be added to an event providing local variables to be used in the transition’s guards and actions. These parameters can be used to model inputs and outputs. Class events implicitly utilise a parameter to non-deterministically select the affected instance of the class. This instance is referred to via the reserved word self when referencing the attributes of the class.		Classes may contain events that modify their attributes. Event parameters can be added to an event providing local variables to be used in the transition’s guards and actions. These parameters can be used to model inputs and outputs. Class events implicitly utilise a parameter to non-deterministically select the affected instance of the class. This instance is referred to via the reserved word self when referencing the attributes of the class.

imported>Colin: New page: Class diagrams are used to describe the behavioural part of a model. Classes represent subsets (variable or fixed) of the ClassTypes that were introduced in the context. The class’ assoc...

2008-04-03T12:30:15Z

New page: Class diagrams are used to describe the behavioural part of a model. Classes represent subsets (variable or fixed) of the ClassTypes that were introduced in the context. The class’ assoc...

New page

Class diagrams are used to describe the behavioural part of a model. Classes represent subsets (variable or fixed) of the ClassTypes that were introduced in the context. The class’ associations and attributes are similar to those in the context but represent variables instead of constants.
The correspondence between an association’s multiplicity constraints and the constraints on the resulting Event-B relationship is clear from the drawing tool. The multiplicity properties are described in the properties view using the usual mathematical terminology (functional, total, injective, surjective) with the UML style multiplicity also shown and annotated automatically on the diagram.

Classes may contain events that modify their attributes. Event parameters can be added to an event providing local variables to be used in the transition’s guards and actions. These parameters can be used to model inputs and outputs. Class events implicitly utilise a parameter to non-deterministically select the affected instance of the class. This instance is referred to via the reserved word self when referencing the attributes of the class.