UML diagram Comparison Table

Object Oriented Software Engineering View all facts Glossary Help

subject > representation > coding technique > diagram > UML diagram

Next diagram: earned value chart Up: diagram Previous diagram: PERT chart

UML diagram comparison table

Subject have part model have advantage be is a subtopic of show that describe nest inside create after have purpose generate by has part associate with use generate has definition help represent summarize show contain

activity diagram it can represent concurrent activities 5.1 - What is UML? aspects of the architectural model rendezvous several classes A UML diagram showing sequences of activities, typically for multiple threads
the flow of work that an object or component performs
the interaction between different use cases
the partition of activities among the existing classes using swimlanes

class diagram an important tool for requirements analysis and design of object oriented software systems 5.1 - What is UML? a class has no attributes or operations by showing an empty box the data found in a software system OCL statement in a class diagram an infinite number of instance diagrams A UML diagram that primarily indicates classes and the associations between those classes the services offered by components and the main data to be stored symbols for classes, associations, attributes, operations, generalizations

component diagram 5.1 - What is UML? aspects of the architectural model note A UML diagram showing components and their relationships how the various components of systems are arranged logically and physically

deployment diagram 5.1 - What is UML? aspects of the architectural model note A UML diagram showing hardware nodes, how they are interconnected, and what components will exist on them at run time where various instances of components reside at run time nodes which represent computational units such as a computer, a processing card, a sensor or a device

instance diagram similar to collaboration diagram except that it shows links of associations 5.5 - Instance Diagrams aspects of the architectural model class diagram which means that it contains instances and links that are present in the class diagram, and are consistent with that class diagram note A UML diagram that shows objects and the links between them an instance of both classes that are joined by an association in the associated class diagram a generalization

interaction diagram object symbol the dynamic aspects of a software system 5.1 - What is UML? aspects of the architectural model developing a class diagram and a use case model because you need to know the actors and objects involved in an interaction to better understand the sequence of messages note to define the protocol used when two components communicate with each other A sequence diagram or collaboration diagram used to model the dynamic aspects of a software system you to visualize how the system runs the behaviour of systems in terms of how objects interact with each other more or less detail depending on what you wish to communicate

package diagram 9.4 - Software Architecture aspects of the architectural model note A type of UML class diagram showing packages and their relationships classes, their attributes and operations as well as the various types of relationships that exist among the classes

state diagram 5.1 - What is UML? the externally visible behaviour of a system or of an individual object a state of another state diagram start state A UML diagram showing states and transitions, used to describe the externally visible behaviour of a system or of an individual object states and events concerning only one class only one start state

subsystem diagram 9.4 - Software Architecture aspects of the architectural model note A UML diagram showing details of a subsystem, including aspects of its operations, its specification and its realization classes, their attributes and operations as well as the various types of relationships that exist among the classes

use case diagram 7.3 - Developing Use Case Models of Systems aspects of the architectural model to show the relationships among a set of use cases and actors note A UML diagram showing actors, use cases and their relationships a software engineer to convey a high level picture of the functionality of a system the system from the user's perspective classes, their attributes and operations as well as the various types of relationships that exist among the classes actor symbols and use case symbols with arrows indicating which actors perform which use cases

Next diagram: earned value chart Up: diagram Previous diagram: PERT chart

Subject	have part	model	have advantage	be	is a subtopic of	show that	describe	nest inside	create after	have purpose	generate by	has part	associate with	use	generate	has definition	help	represent	summarize	show	contain
activity diagram			it can represent concurrent activities		5.1 - What is UML?		aspects of the architectural model					rendezvous	several classes			A UML diagram showing sequences of activities, typically for multiple threads		the flow of work that an object or component performs the interaction between different use cases		the partition of activities among the existing classes using swimlanes
class diagram				an important tool for requirements analysis and design of object oriented software systems	5.1 - What is UML?	a class has no attributes or operations by showing an empty box	the data found in a software system					OCL statement in a class diagram			an infinite number of instance diagrams	A UML diagram that primarily indicates classes and the associations between those classes				the services offered by components and the main data to be stored	symbols for classes, associations, attributes, operations, generalizations
component diagram					5.1 - What is UML?		aspects of the architectural model					note				A UML diagram showing components and their relationships				how the various components of systems are arranged logically and physically
deployment diagram					5.1 - What is UML?		aspects of the architectural model					note				A UML diagram showing hardware nodes, how they are interconnected, and what components will exist on them at run time				where various instances of components reside at run time	nodes which represent computational units such as a computer, a processing card, a sensor or a device
instance diagram				similar to collaboration diagram except that it shows links of associations	5.5 - Instance Diagrams		aspects of the architectural model				class diagram which means that it contains instances and links that are present in the class diagram, and are consistent with that class diagram	note				A UML diagram that shows objects and the links between them				an instance of both classes that are joined by an association in the associated class diagram	a generalization
interaction diagram	object symbol	the dynamic aspects of a software system			5.1 - What is UML?		aspects of the architectural model		developing a class diagram and a use case model because you need to know the actors and objects involved in an interaction	to better understand the sequence of messages		note		to define the protocol used when two components communicate with each other		A sequence diagram or collaboration diagram used to model the dynamic aspects of a software system	you to visualize how the system runs			the behaviour of systems in terms of how objects interact with each other	more or less detail depending on what you wish to communicate
package diagram					9.4 - Software Architecture		aspects of the architectural model					note				A type of UML class diagram showing packages and their relationships				classes, their attributes and operations as well as the various types of relationships that exist among the classes
state diagram					5.1 - What is UML?		the externally visible behaviour of a system or of an individual object	a state of another state diagram				start state				A UML diagram showing states and transitions, used to describe the externally visible behaviour of a system or of an individual object				states and events concerning only one class	only one start state
subsystem diagram					9.4 - Software Architecture		aspects of the architectural model					note				A UML diagram showing details of a subsystem, including aspects of its operations, its specification and its realization				classes, their attributes and operations as well as the various types of relationships that exist among the classes
use case diagram					7.3 - Developing Use Case Models of Systems		aspects of the architectural model			to show the relationships among a set of use cases and actors		note				A UML diagram showing actors, use cases and their relationships	a software engineer to convey a high level picture of the functionality of a system		the system from the user's perspective	classes, their attributes and operations as well as the various types of relationships that exist among the classes	actor symbols and use case symbols with arrows indicating which actors perform which use cases