Skip to end of metadata
Go to start of metadata

Most work with Information Systems is done by creating or modifying releases. A release is denoted via the hash sign '#' after the name, followed by the eelease number: E.g. "SAP CO-P10 # 6.0"

Alongside its name (which may or may not contain a release identifier) and description, an Information System has the following main properties and relationships:

Productive
The productive timespan of an Information System Release is defined by two items of data: productive from and productive until. The lack of a start date for a release 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 an Information System Release must have one of the following values:

  1. Current denotes an Information System Release that is productive at the present time, i.e. the release is in productive operation and supports a Business Process;
  2. Planned denotes an Information System Release that is either being developed or whose rollout is planned. This means there is an approved IT project addressing the implementation and/or introduction of this release;
  3. Target denotes an Information System Release that is part of the future vision of the business landscape. The Information System in question is still at a draft planning phase. As yet there is no approved project which specifically addresses its implementation or introduction;
  4. Inactive denotes an Information System Release that was in productive operation at an earlier time but is no longer in use.

Sub Information System of
Each Information System Release can be part of another one. You specify a superordinate release.

Information System Architecture

  1. Sub-Information Systems : An Information System can consist of several sub-Information Systems. Such sub-Information Systems realise a part of the current Information System's functionality.
  2. Predecessors and Successors : A predecessor-successor relation exists as a basis for relationships connecting Information Releases. To assign a particular release as a predecessor/successor to the release you are working with, select its name from the drop-down list. 
  3. Information System Domains : Each Information System Release can be assigned to one or more Information System Domains. To make this assignment, select the domain from the drop-down list
  4. Uses and Used by : A uses-used by relation is another relationship connecting Information Releases. Values for this relation can be added from the drop-down list in a similar way to the predecessor-successor relation.
  5. IT Services : Use this section to manage information about the main IT Services supported by the Information System Release.

Technical Architecture

Technical Components: The Technical Components comprise elements (e.g. application servers or frameworks) on which the Information System Release is based.

Infrastructure Architecture

Infrastructure Elements: The Infrastructure Elements describe the operating platform (e.g. servers) that runs the Information System Release. This association can have attributes. Find more informations about attributable associations here.

Project Portfolio

Projects: Use this section to manage information about the Projects concerning the Information System Release.

Business Architecture

  1. Business Objects : Use this section to manage information about the main Business Objects handled by the Information System Release. This association can have attributes.
  2. Business Functions : Use this section to manage information about the main Business Functions supported by the Information System Release.
  3. Business Mapping :
    1. Particular Business Units specified : the Business Process is only supported for the units specified. If there are no Business Units specified, the Business Process assignment is applicable without restriction in every Business Unit.
    2. Particular Products specified : the Business Process is only supported for the Products specified. If there are no Products specified, the Business Process assignment is applicable without restriction for every Product.
  4. Business Units : To indicate that a Business Unit uses this Information Release (irrespective of which Business Process is involved), a new business support relationship must first be created for the release in question. Since the new relationship is to be valid irrespective of Business Process, you can model this with the virtual Business Process ("-").
  5. Products : To indicate that a Product uses this Information Release (irrespective of which Business Process is involved), a new business support relationship must first be created for the release in question. Since the new relationship is to be valid irrespective of Business Process, you can model this with the virtual Business Process ("-").

 

  • No labels