Skip to content

0750 Data Passing

Describes relationships that show where data and control is passed between components. These relationships show the structure of the data processing. They can link Assets, or Ports or SchemaAttributes depending on the level of detail that is known.

UML

Deprecated types
  • ProcessInput
  • ProcessOutput

ControlFlow relationship

Shows that when one element completes processing, control passes to the next element.

  • label - type of request.
  • description - description of the request.
  • iscQualifiedName - qualified name of the associated information supply chain.
  • derivation - where did the lineage relationship come from?
  • guard - Function, or value that must be true to travel down this control flow.
  • mandatoryGuard - Is this guard mandatory for the next step to run.

DataFlow relationship

Shows that data flows in one direction from one element to another.

  • label - type of request.
  • description - description of the request.
  • iscQualifiedName - qualified name of the associated information supply chain.
  • derivation - where did the lineage relationship come from?
  • integrationStyle - Mechanism to flow data and control along the segment.
  • protocol - Name of the protocol used to connect to the endpoint.
  • frequency - How frequently is this expected to run? e.g.real-time, hourly, daily, on batch completion?
  • dataExchanged - A full explanation of what data flows and why.
  • oneWay - Is the data flowing one-way or bidirectional?
  • formula - Formula that describes the behaviour of the element. May include placeholders for queryIds.
  • formulaType - Format of the expression provided in the formula attribute.

ProcessCall relationship

Shows a request-response call between two elements.

  • label - type of request.
  • description - description of the request.
  • iscQualifiedName - qualified name of the associated information supply chain.
  • derivation - where did the lineage relationship come from?
  • integrationStyle - Mechanism to flow data and control along the segment.
  • protocol - Name of the protocol used to connect to the endpoint.
  • frequency - How frequently is this expected to run? e.g.real-time, hourly, daily, on batch completion?
  • dataExchanged - A full explanation of what data flows and why.
  • oneWay - Is the data flowing one-way or bidirectional?
  • formula - Formula that describes the behaviour of the element. May include placeholders for queryIds.
  • formulaType - Format of the expression provided in the formula attribute.
  • lineNumber - Location of the call in the implementation.

Raise an issue or comment below