Skip to end of metadata
Go to start of metadata

With the release 6.1, the iteraplan metamodel has been extended. In short: More powerful Business Mapping, Attributes for all relations between Building Block Types, Extended Domains, Interface became Information Flow, Connection of Project to all Building Block Types.

See here for a structure view of the new iteraplan Meta Model.

Information Flow (formerly Interface)

The former Interface Building Block Type has been redesigned:

  • It is now called Information Flow.
  • It's now a standalone Building Block type, so it can be created without any relations set.
  • It must have a unique name. 
  • It has the hierarchy and the predecessor/successor self relations.
  • It has relations to Information System (2 relations, distinguishable), Business Object and Technical Component. All four relations are attributable. The technical names of these releations have changed.
Before 6.1Starting with 6.1

 

Relations

These new relations are available between Building Block Types:

Project is now connected with

  • Business Object
  • Information Flow
  • IT Service
  • Technical Component
  • Infrastructure Element

Business Domain is now connected with

  • Information System
  • IT Service
  • Information Flow

Information System Domain is now connected with

  • Business Object
  • Information Flow
  • IT Service
  • Technical Component
  • Infrastructure Element
  • Business Function

Architectural Domain is now connected with

  • Infrastructure Element
  • Information Flow
  • IT Service
  • Information System

All elements are now hierarchical.
The hierarchy self relation has been added to

  • Information Flow
  • Technical component

The successor self relation has been added to

  • Infrastructure Element
  • Business Function
  • Business Prozess
  • IT Service
  • Information Flow

The usage self relation has been added to

  • Business Process
  • Business Function

Attributes configured for Relations

All relations between Building Block Types are now attributable. Self relations like parent-child relations stay as they are, they are not attributable.

Business Mapping

The Business Mapping has been extended: IT Service, Business Function and Business Object are now part of the Business Mapping. 

With the new Business Mapping any subset of the 7 building block types can form a business mapping. An Information System is no longer a mandatory part of a Business Mapping.

The following direct relations between Building Block types have been converted to Business Mappings with two elements.

  • Business Object - Business Function
  • Business Object - Information System
  • Information System - Business Function
  • IT Service - Information System
  • IT Service - Business Function

Custom Attributes configured for the Business Object to Information System relation have been migrated to Business Mapping attributes.

Information Systems & Technical Components

The release/version concept with Informations Systems and Technical Components has changed.

Before 6.1 there were Information Systems, which had only the name as an attribute. An Information System could contain one or more releases (Information System Releases), which held all other data, including a version number. A new Information System Release could be created in the Classic Client by using the New Release menu command. The distinction between Information Systems and Information System Releases was not very transparent in the Classic Client. Excel Export/Import and REST interfaces were not aware of this distinction at all.

With 6.1 this concept is dropped. There is no longer any differentiation between Information Systems and Information System Release. There are only Information Systems, which hold all data including the name. This is more flexible, because in the course of releases of a system/technology the name might also change.

The name of the Information System now contains also the version number. As good practice it should be separated by the hash sign, '#'. iteraplan is generally no longer aware, that after a hash sign in the name a version follows. Only within filter dialogs there's the option to according to version. This option matches to the string following the last hash sign in the name field.

All the above also applies to Technical Components. 

Please note: The successor relation is available (now with 6.1 and also before 6.1) to model the dependency between current, previous and future elements.

Attribute "Available for Interfaces" at Technical Components

Because the concept of releases at Technical Components changes, the system attribute "Available for Interfaces" is now handled differently. Before 6.1, there was one attribute for each Technical Component. This Technical Component might have contained several releases which then shared the same attribute value. Now, starting with 6.1, there are no longer Technical Components and Technical Component Releases. So there's an individual attribute for each Technical Component.

As of release 6.1, the attribute values of "Available for Interfaces" are not considered, when assigning Technical Components to Information Flows (formerly Interfaces). All Technical Components can be assigned to an Information Flow.

 

 

 

  • No labels