OODE - Revision history

Suhridk: /* Statechart: Represent state automata */

2011-10-30T12:00:39Z

Statechart: Represent state automata

2011-10-30T11:35:51Z

Statechart: Represent state automata

2011-10-30T11:34:10Z

Communication Diagrams

2011-10-30T11:33:12Z

Objects

2011-10-25T19:39:50Z

Object Diagram

2011-10-25T19:39:19Z

Communication Diagrams

2011-10-25T19:38:54Z

Objects

2011-10-25T19:37:24Z

Communication Diagrams

2011-10-25T19:34:09Z

Objects

2011-10-25T19:15:08Z

Objects

← Older revision		Revision as of 12:00, 30 October 2011
Line 181:		Line 181:
	* '''Important in system function modeling''' - focusing on control flow in objects.		* '''Important in system function modeling''' - focusing on control flow in objects.
	* The fork - join concept is important. Fork can be used to represent concurrent activities.		* The fork - join concept is important. Fork can be used to represent concurrent activities.
		+
		+	=== Component and Deployment Diagrams ===
		+
		+	* Component Diagram:
		+	* A component is a set of classes, interfaces or collaborations
		+	* A component diagram represents the organization and dependencies between the components.
		+	* [TODO] Give a good example.
		+
		+	* Deployment Diagram:
		+	* Deployment diagrams show the static deployment view of an architecture. They are linked to component diagrams.
		+	* [TODO] Give a good example.
		+
		+
		+	=== Use Case Models ===
		+
		+	* See REQE's Use Case Models Page.

← Older revision		Revision as of 11:35, 30 October 2011
Line 180:		Line 180:
	* Activity Diagram: Special kind of statechart - describing series of activities within systems.		* Activity Diagram: Special kind of statechart - describing series of activities within systems.
	* '''Important in system function modeling''' - focusing on control flow in objects.		* '''Important in system function modeling''' - focusing on control flow in objects.
		+	* The fork - join concept is important. Fork can be used to represent concurrent activities.

@@ Line 161: / Line 161: @@
 * Sequence and Collaboration diagrams are interchangeable - they can be transformed into one another.
-* Sequence Diagram: focus on the chronological ordering of messages.
+==== Sequence Diagram ====
-** It is a temporal vision of an interaction : It is for a '''''particular''''' interaction or a scenario.
+* focus on the chronological ordering of messages.
-* Collaboration Diagram: focus on the structural organization of the elements sending the messages.
+* It is a temporal vision of an interaction : It is for a '''''particular''''' interaction or a scenario.
 * Represents a collaboration between roles. Focuses on the structure, not that much on the time.
 * Time ordering can be shown by numbering notations.
-* Statechart: Represent state automata.
+==== Statechart: Represent state automata ====
 * Activity Diagram: Special kind of statechart - describing series of activities within systems.
 * '''Important in system function modeling''' - focusing on control flow in objects.

← Older revision		Revision as of 11:33, 30 October 2011
Line 171:		Line 171:
	* Represents a collaboration between roles. Focuses on the structure, not that much on the time.		* Represents a collaboration between roles. Focuses on the structure, not that much on the time.
	* Time ordering can be shown by numbering notations.		* Time ordering can be shown by numbering notations.
		+
		+	* Statechart: Represent state automata.
		+
		+	* Activity Diagram: Special kind of statechart - describing series of activities within systems.
		+	* '''Important in system function modeling''' - focusing on control flow in objects.

@@ Line 154: / Line 154: @@
 * Represents the structure of objects at run time, since object behaviour is dynamic, this is effectively a snapshot.
 * Also represent the links between the objects.
-* The links are instances of the associations between the object's classes.
+* The links are '''instances of the class associations.'''
 * An object diagram '''is an instance''' of a class diagram.

@@ Line 159: / Line 159: @@
 === Communication Diagrams ===
-* Sequence and Collaboration diagrams are interchangeable.
+* Sequence and Collaboration diagrams are interchangeable - they can be transformed into one another.
 * Sequence Diagram: focus on the chronological ordering of messages.

@@ Line 150: / Line 150: @@
 * Three diagram types of object:
-* Object Diagram: Represents the structure of objects at run time, since object behaviour is dynamic, this is effectively a snapshot.
+=== Object Diagram ===
 === Communication Diagrams ===

@@ Line 151: / Line 151: @@
 * Object Diagram: Represents the structure of objects at run time, since object behaviour is dynamic, this is effectively a snapshot.
-* Communication Diagrams:
-** Sequence Diagram: focus on the chronological ordering of messages.
+=== Communication Diagrams ===
 ** Collaboration Diagram: focus on the structural organization of the elements sending the messages.