Modeldraw
  • Welcome to Modeldraw
  • Getting Started
    • Quickstart Guide
  • FAQ
  • UML Designer
    • Common Elements
      • Comment
      • Comment Link
      • Dependency
      • Realization
      • Frame
    • Class Diagrams
      • Class
      • Association
      • Generalization
      • Composition
      • Aggregation
      • Enumeration
      • Interface
      • Association Class Link
      • Ball (Interface Realization)
      • Socket (Required Interface)
    • Sequence Diagrams
      • Lifeline
      • Activation Bar
      • Synchronous Message
      • Asynchronous Message
      • Return Message
      • Found Message
      • Interaction Frame
    • Use Case Diagrams
      • Actor
      • Use Case
      • Association
      • System Boundary
      • Generalization
      • Include Relationship
      • Extend Relationship
    • State Machine Diagrams
      • State
      • Initial State
      • Final State
      • Transition
      • Superstate
      • Concurrent Boundary
      • History Pseudostate
      • History Transition
    • Package Diagrams
      • Package
    • Deployment Diagrams
      • Node
      • Communication Path
      • Deployed Artifact
      • Internet
    • Activity Diagrams
      • Initial Node
      • Activity Final
      • Action
      • Flow
      • Decision / Merge
      • Fork / Join
      • Partitions
      • Flow Final
      • Send Signal
      • Accept Signal
      • Time Signal
    • Component Diagrams
      • Component
      • Ball (Interface Realization)
      • Socket (Required Interface)
    • Communication Diagrams
      • Object
      • Link
  • Wireframes
    • Views
    • Layouts
    • Components
Powered by GitBook
On this page
  1. UML Designer
  2. Deployment Diagrams

Node

PreviousDeployment DiagramsNextCommunication Path

Last updated 7 months ago

A Node in a Deployment Diagram represents a physical device or execution environment in which components of the system are deployed. It can be hardware devices, servers, or software systems that host and run parts of the application.

With Nodes in Modeldraw's Deployment Diagram, you can:

  • Represent physical or virtual processing resources in your system

  • Show where software components are deployed and executed

  • Illustrate the hardware topology of your system

  • Demonstrate the distribution of system components across different devices or environments

  • Create a clear picture of the physical architecture of your application

Understanding Node

A Node in Modeldraw's Deployment Diagram tool is typically represented by a three-dimensional cube. Key points to understand about Nodes include:

  • Nodes represent actual hardware or virtual environments where software runs.

  • Nodes can contain deployed artifacts, showing what software runs on each device.

  • Nodes can be connected by communication paths to show how they interact.

  • Nodes can represent various types of devices or environments (e.g., servers, workstations, mobile devices, cloud environments).

  • Each node should be named to clearly identify what it represents in the system architecture.

Remember that Nodes should represent actual physical or virtual environments in your system deployment. Use clear, descriptive names that accurately represent the role of each Node in your system architecture.

A Node with artifacts and a tagged value