Skip to end of metadata
Go to start of metadata

The Technical Component describes which Technical Components are in use by an Information System, e.g. databases or application servers, also programming languages or frameworks.


In most cases elements listed in standardization catalogs (also called blueprints) are modeled as Technical Components.

Alongside its name (which might contain a release identifier) and description, a Technical Component has the following properties and relations:

  • Productive : The productive timespan of a technical component is defined by two items of data: productive from and productive until. The lack of a start date indicates it is not yet known when the release in question is due to go into productive operation; if the end date is missing, the end of the release's productive operation has not yet been set.
  • Status : The status of the Technical Component can have any of the following values:
    • Current designates a Technical Component that is productive at the present time;
    • Planned designates Technical Component that is either being developed or whose rollout is planned;
    • Target denotes a Technical Component which is part of the future vision of the technical landscape. The component in question is still at draft planning phase, and there are as yet no firm plans for rollout;
    • Inactive denotes a Technical Component that was in productive operation at an earlier time but is no longer in use;
    • Not assigned denotes a Technical Component for which no status has yet been defined.
  • Predecessors : A predecessor-successor relation exists as the basis for relationships connecting Technical Components. To assign a particular component as a predecessor to the one you are working with, select the name of the predecessor from the drop-down list.
  • Architectural Domains : Each Technical Component can be assigned to one or more Architectural Domains. To make this assignment, select the domain from the drop-down list.
  • Infrastructure Elements : Each Technical Component can be assigned to one or more infrastructure elements. To make this assignment, select the element from the drop-down list. This association can get attributes, which works in a similar way than the association between Information Systems and Business Objects.
  • IT Services : Use this section to manage information about the IT Services supported by the Technical Component.
  • Uses the following technical components : Technical Components may in turn use other Technical Components. You can specify these by entering their names.
  • Is the basis of the following Information Systems : Technical Components can form a part of Information System Releases. This can be modelled by entering the releases here.



The relation Uses the following Technical Components can be helpful in modeling connections between different Technical Components within a portal.

  • No labels