Please enable JavaScript.
Coggle requires JavaScript to display documents.
UML 2.5 Diagram (Structure Diagram (Class Diagram (a Class diagram in the…
UML 2.5 Diagram
Structure Diagram
Class Diagram
a Class diagram in the Unified Modeling Language (UML) is a type of static structure diagram that describes the structure of a system by showing the system's classes, their attributes, operations (or methods), and the relationships among objects
Purpose: Shows static structure of classifiers in a system; Diagram provides basic notation for other structure diagrams prescribed by UML; Helpful for developers and other team members too; Business Analysts can use class diagrams to model systems from business perspective
Object Diagram
A static UML object diagram is an instance of a class diagram; it shows a snapshot of the detailed state of a system at a point in time, thus an object diagram encompasses objects and their relationships at a point in time. It may be considered a special case of a class diagram or a communication diagram.
Purpose
During the analysis phase of a project, you might create a class diagram to describe the structure of a system and then create a set of object diagrams as test cases to verify the accuracy and completeness of the class diagram.
Before you create a class diagram, you might create an object diagram to discover facts about specific model elements and their links, or to illustrate specific examples of the classifiers that are required.
Package Diagram
Package diagram a kind of structural diagram, shows the arrangement and organization of model elements in middle to large scale project. Package diagram can show both structure and dependencies between sub-systems or modules, showing different views of a system, for example, as multi-layered (aka multi-tiered) application - multi-layered application model.
Purpose: Package Diagram can be used to simplify complex class diagrams, it can group classes into packages; A package is a collection of logically related UML elements; Packages are depicted as file folders and can be used on any of the UML diagrams
-
Component Diagram
Component diagrams are used in modeling the physical aspects of object-oriented systems that are used for visualizing, specifying, and documenting component-based systems and also for constructing executable systems through forward and reverse engineering. Component diagrams are essentially class diagrams that focus on a system's components that often used to model the static implementation view of a system.
Purpose: describes how a software system is split up into components and shows the dependencies among these components
Deployment Diagram
Deployment Diagram: describes the hardware used in system implementations and the execution environments and artifacts deployed on the hardware.
Purpose: Visualize the hardware topology of a system; Describe the hardware components used to deploy software components; Describe the runtime processing nodes.
Profile Diagram
Profile diagram provides a generic extension mechanism for customizing UML models for particular domains and platforms. Extension mechanisms allow refining standard semantics in strictly additive manner, preventing them from contradicting standard semantics.
Purpose: allows you to extend and customize UML by adding new building blocks, creating new properties and specifying new semantics in order to make the language suitable to your specific problem domain.
Behavior Diagram
UseCase Diagram
A use case diagram at its simplest is a representation of a user's interaction with the system that shows the relationship between the user and the different use cases in which the user is involved
Purpose: describes the functionality provided by a system in terms of actors, their goals represented as use cases, and any dependencies among those use cases
-
Activity Diagram
Activity diagram is basically a flowchart to represent the flow from one activity to another activity. The activity can be described as an operation of the system. The control flow is drawn from one operation to another.
Purpose: Draw the activity flow of a system; Describe the sequence from one activity to another; Describe the parallel, branched and concurrent flow of the system.
-
State Machine Diagram
State machine diagram is a behavior diagram which shows discrete behavior of a part of designed system through finite state transitions. State machine diagrams can also be used to express the usage protocol of part of a system
Purpose: Used for modeling discrete behavior through finite state transitions. In addition to expressing the behavior of a part of the system, state machines can also be used to express the usage protocol of part of a system. These two kinds of state machines are referred to as behavioral state machines and protocol state machines.
-
-
Interaction Diagram
Interaction diagrams is a subset of behavior diagrams, emphasize the flow of control and data among the things in the system being modeled:
Sequence Diagram: shows how objects communicate with each other in terms of a sequence of messages. Also indicates the lifespans of objects relative to those messages.
Communication Diagram: shows the interactions between objects or parts in terms of sequenced messages.
Interaction Overview Diagram: provides an overview in which the nodes represent communication diagrams
-
Purpose: To capture the dynamic behaviour of a system; To describe the message flow in the system; To describe the structural organization of the objects; To describe the interaction among objects.