Input to a flow element, e.g. activity, or an output from a flow element. Artifacts can be stored in resources.

For example, Development activity takes a design document as input and outputs source code. Source code is stored in a version control system, e.g. Git. Build activity takes source code as input and produces a binary, e.g. a jar file. That binary can be stored in/published to a binary repository, e.g. Maven Central.

Supertypes

Referrers

Uses

  • Artifact

If true, this composite artifact shall be displayed as a partition on the parent component diagram.

Type EBoolean
Cardinality 0..1
Changeable true
Derived false

Keys of artifact’s repositories relative to the containing package resources/ reference.

Type EString
Cardinality 0..*
Changeable true
Derived false

Keys of artifact’s templates relative to the artifact URI.

Type EString
Cardinality 0..*
Changeable true
Derived false

Artifacts can be organized into a hierarchy (Product Breakdown Structure).

Type ArtifactEntry
Cardinality 0..*
Changeable true
Derived false

Relationships which have this artifact as a target.

Type Relationship
Cardinality 0..*
Changeable false
Derived true
Opposite target

Flow elements which take this artifact as an input.

Type FlowElement<?>
Cardinality 0..*
Changeable false
Derived true
Opposite inputArtifacts

Artifacts for which this artifact is a template. Derived opposite to templates.

Type Artifact
Cardinality 0..*
Changeable false
Derived true
Opposite templates

Outbound relationships to other artifacts. Artifact relationships can be used for modeling composite artifacts, e.g. modular/distributed systems such as cloud applications.

Type RelationshipEntry
Cardinality 0..*
Changeable true
Derived false

Flow elements which output this artifact.

Type FlowElement<?>
Cardinality 0..*
Changeable false
Derived true
Opposite outputArtifacts

Transitions for which this artifact is a part of their payload. Derived opposite to Transition payload.

Type Transition
Cardinality 0..*
Changeable false
Derived true
Opposite payload

Resources in which this artifact can be stored. E.g. source code artifact can be stored in Git resource, and jar artifact can be stored in Maven repository resource.

Type Resource
Cardinality 0..*
Changeable false
Derived true
Opposite artifacts

Calls for which this artifact is a part of their response. Derived opposite to Call response.

Type Call
Cardinality 0..*
Changeable false
Derived true
Opposite response

Responsibilities for this artifact at a flow element level if different from the flow element responsibilities. E.g. a participant responsible for an activity may delegate work on some artifact to another participant. In this case the activity responsible becomes accountable for the artifact and the delegate participant becomes responsible.

Type ArtifactParticipantResponsibility
Cardinality 0..*
Changeable false
Derived true
Opposite artifact

Diagram element style for component diagrams. If specified, the style diagram element is used as a template for a diagram element created to represent this artiact on a diagram.

Type DiagramElement
Cardinality 0..1
Changeable true
Derived false

Artifacts can be organized into an inheritance hierarchy using templates reference. Artifacts inherit visual representation of templates. E.g. there might be an artifact “Cloud Cache” with multiple instances in different cloud solutions.

Type Artifact
Cardinality 0..*
Changeable false
Derived true
Opposite instances

Participants which use this artifact in their activities.

Type Participant
Cardinality 0..*
Changeable false
Derived true
Opposite artifacts