How many types of uml diagrams are there

Communication Diagram Communication diagrams model the interactions between objects in sequence. They describe both the static structure and the dynamic behavior of a system. In many ways, a communication diagram is a simplified version of a collaboration diagram introduced in UML 2. State Diagram Statechart diagrams , now known as state machine diagrams and state diagrams describe the dynamic behavior of a system in response to external stimuli.

State diagrams are especially useful in modeling reactive objects whose states are triggered by specific events. Component Diagram Component diagrams describe the organization of physical software components, including source code, run-time binary code, and executables.

Deployment Diagram Deployment diagrams depict the physical resources in a system, including nodes, components, and connections.

Class diagrams are perhaps one of the most common UML diagrams used and class diagram symbols center around defining attributes of a class. For example, there are symbols for active classes and interfaces.

A class symbol can also be divided to show a class's operations, attributes, and responsibilities. Lines are also important symbols to denote relationships between components. Generalization and Inheritance are denoted with empty arrowheads. Composition is shown with a filled in diamond. Aggregation is shown with an empty diamond. Dependencies are marked with a dashed line with an arrow. Activity diagrams have symbols for activities, states, including separate symbols for an initial state and a final state.

The control flow is usually shown with an arrow and the object flow is shown with a dashed arrow. For example, semantics of multiplicity of actors and multiplicity of use cases on use case diagrams is not defined precisely in the UML specification and could mean either concurrent or successive usage of use cases.

Name of an abstract classifier is shown in italics while final classifier has no specific graphical notation, so there is no way to determine whether classifier is final or not from the diagram. Activity diagrams and sequence diagrams were enhanced. Activities were redesigned to use a Petri-like semantics. Edges can now be contained in partitions. Partitions can be hierarchical and multidimensional. Explicitly modeled object flows are new.

Classes have been extended with internal structures and ports composite structures. Information flows were added. A collaboration now is a kind of classifier, and can have any kind of behavioral descriptions associated. Interactions are now contained within classifiers and not only within collaborations. It is now possible for use cases to be owned by classifiers in general and not just packages.

New notation for concurrency and branching using combined fragments. Components can no longer be directly deployed to nodes. Artifacts should be deployed instead. Implementation has been replaced by « manifest ». Artifacts can now manifest any packageable element not just components, as before. It is now possible to deploy to nodes with an internal structure. They organize the components and model diagrams into groups in the same manner as a namespace would encapsulate different names that are in some manner quite correlated.

Profile diagrams cannot be considered as the typical UML diagram type. Despite, it can be considered more like an extensibility mechanism and not a diagram type like any other. If we use stereotypes, constraints, and tagged values, we can easily extend as well as customize already existing notations of UML.

Profile diagrams, however, are like a language. For example, if you speak English you can easily create new sentences. In a similar way, if you speak profile diagrams, then you can easily and specifically create new properties as well as semantics for UML diagrams.

Thus, UML diagrams are useful whenever we are modeling business data. Class attributes map to abstract access methods for persistent fields, and association roles map to abstract access methods for relationship fields. Navigability predicts if relationship access methods appear in both related entity beans or just one.

Further, multiplicity notation determines the correct type for relationship fields, issues of a life cycle, and also cascading delete characteristics. This is a guide to types of UML diagrams.

Here we discuss the basic concepts with widest categories of UML diagram. You can also go through our other suggested articles to learn more —. Submit Next Question. By signing up, you agree to our Terms of Use and Privacy Policy.

Forgot Password? This website or its third-party tools use cookies, which are necessary to its functioning and required to achieve the purposes illustrated in the cookie policy. By closing this banner, scrolling this page, clicking a link or continuing to browse otherwise, you agree to our Privacy Policy.