Notations in Deployment Diagram
Refers to the symbols, shapes, and conventions used to represent different elements within the diagram, like:
1. Component
A component represents a modular and reusable part of a system, typically implemented as a software module, class, or package. It encapsulates its behavior and data and can be deployed independently.
Typically represented as a rectangle with two smaller rectangles protruding from its sides, indicating ports for connections. The component’s name is written inside the rectangle.
2. Artifact
An artifact represents a physical piece of information or data that is used or produced in the software development process. It can include source code files, executables, documents, libraries, configuration files, or any other tangible item.
Typically represented as a rectangle with a folded corner, labeled with the artifact’s name. Artifacts may also include additional information, such as file extensions or versions.
3. Interface
An interface defines a contract specifying the methods or operations that a component must implement. It represents a point of interaction between different components or subsystems.
Represented as a circle or ellipse labeled with the interface’s name. Interfaces can also include provided and required interfaces, denoted by “+” and “-” symbols, respectively.
4. Node
A node represents a physical or computational resource, such as a hardware device, server, workstation, or computing resource, on which software components can be deployed or executed.
Represented as a box with rounded corners, usually labeled with the node’s name. Nodes can also include nested nodes to represent hierarchical structures.
5. Communication path
A straight line that represents communication between two device nodes. Dashed lines in deployment diagrams often signify relationships or dependencies between elements, indicating that one element is related to or dependent on another.
Deployment Diagram in Unified Modeling Language(UML)
A Deployment Diagram in software engineering is a type of Structural UML Diagram that shows the physical deployment of software components on hardware nodes. It illustrates the mapping of software components onto the physical resources of a system, such as servers, processors, storage devices, and network infrastructure.
Important Topics for the Deployment Diagram
- What is a Deployment Diagram?
- Key elements of a Deployment Diagram
- Notations in Deployment Diagram
- Use Cases of Deployment Diagrams
- Steps for creating a Deployment Diagram:
- Deployment Patterns
- Real-World Examples For Deployment Diagram
- Example 1
- Example 2
- Integration of Deployement Diagrams with Other UML Diagrams
- Benefits of Deployement Diagrams
- Challenges of Deployement Diagrams