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
  • Understanding Deployed Artifact
  • Creating a Deployed Artifact
  1. UML Designer
  2. Deployment Diagrams

Deployed Artifact

PreviousCommunication PathNextInternet

Last updated 7 months ago

A Deployed Artifact in a Deployment Diagram represents a concrete piece of software or data that is deployed on a Node. It can be an executable file, a library, a database, or any other software component that is part of the system deployment.

With Deployed Artifacts in Modeldraw's Deployment Diagram, you can:

  • Show what software components are deployed on each Node

  • Represent specific files, databases, or applications in your system

  • Illustrate how software is distributed across different hardware or environments

  • Provide a detailed view of what runs on each part of your system

  • Map software components to their physical or virtual locations

Understanding Deployed Artifact

A Deployed Artifact in Modeldraw's Deployment Diagram tool is typically represented by a rectangle with the artifact's name inside, placed within a Node. Key points to understand about Deployed Artifacts include:

  • Deployed Artifacts are always contained within Nodes, showing where they are deployed.

  • Can represent various types of software or data (e.g., executables, libraries, databases, configuration files).

  • Each artifact should be named to clearly identify what software component it represents.

  • A Node can contain multiple Deployed Artifacts.

  • Artifacts can have dependencies on other artifacts, though this may not be directly represented in the diagram.

Creating a Deployed Artifact

To create a Deployed Artifact in Modeldraw's Deployment Diagram:

  1. Select the Deployed Artifact tool from the shape toolbox.

  2. Click on the Node where you want to add the Deployed Artifact. The Artifact will appear inside the Node.

Remember that Deployed Artifacts should represent actual software components or data that are deployed on the Nodes in your system.

A Node with Deployed Artifacts