Most work with Information Systems is done by creating or modifying their releases. Each Information System Release is one version of a specific Information System. The search results page shows the name of Information Systems in two different representations. The first column contains simple names, while second column shows complete hierarchical names, together with release information. The format is as follows:
Alongside its simple Name (which may contain a release identifier) and Description, an Information System Release has the following main properties and relationships:
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. Any inconsistency in entries (e.g. a conflict with the set status) can be revealed by consistency checks (see Consistency Checks).
The status of an Information System Release must have one of the following values:
- 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;
- 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;
- 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;
- Inactive denotes an Information System Release that was in productive operation at an earlier time but is no longer in use.
iteraplan provides a convenient mechanism for handling different strategic scenarios based on your Target-information systems. Have a look.
Seals are used to mark verified Information System states and can be used as a means of data quality assurance. All iteraplan users can see seals and their current states, but for creating a new seal the functional permission 'Create Seal' is required. The seals can be set and renewed at any time.
By clicking on the Seal-Entry, a table will pop up, showing all current and past seals.
The seal can have one of the following states:
(Not available) denotes an Information System Release that does not have any seals yet;
(Valid) denotes an Information System Release that has a valid seal set. This means, that this Information System was not modified since this valid seal was set;
(Invalid) denotes an information system release that was modified since the last valid seal was set;
(Outdated) denotes an information system release that has a valid, but outdated seal set. The seal expiration period is configurable in iteraplan.properties. The default period is 180 days.
The current seal status can be exported in spreadsheet and diagram reports. Users can filter Information System Releases by seal state.
Sub Information System of
Each Information System Release can be part of another one. You specify a superordinate release by selecting herein its name. The drop-down list presents then the Information System Release prefaced by the name of its superordinate release. The elements of the name are separated by a colon ':'.
Once you have created an Information System Release, you can view and modify the properties in the general area of the edit forms (visible whichever tab you have open). Relationships and other user-defined attributes are managed on separate sections which you open by clicking specific tabs.
To modify information, click the Edit button at the top. Then you can make your changes. You can save your changes by clicking Save, or click Cancel to discard them without saving. Bear in mind that deleting an Information System Release will have the effect of deleting its substructure, i.e. all its subordinate releases.
The Hierarchy tab presents an overview of Interfaces of this Information Release.
The Building Blocks are grouped by different architectures:
Information System Architecture
- 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.
- 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.
- 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
- 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.
- Technical Components :The Technical Components comprise elements (e.g. application servers or frameworks) on which the Information System Release is based.
- Infrastructure Elements : The Infrastructure Elements describe the operating platform (e.g. servers) that runs the Information System Release.
- Projects : Use this section to manage information about the Projects concerning the Information System Release.
- Business Objects : Use this section to manage information about the main Business Objects handled by the Information System Release. This association can get attributes. Find more informations about attributable associations here.
- Business Functions : Use this section to manage information about the main Business Functions supported by the Information System Release.
- Business Mapping :
- 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.
- 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.
- 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 ("-").
- 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 ("-").
The Attributes tab provides functions for editing attribute values (see Attribute Groups and Attributes). The Permissions tab provides functions for assigning explicit Building Block Permissions (see [Users, Roles and Permissions]). You create a new Information System, and by implication a new Information System Release for this system, with the New button. The button opens a form (see below) where you can enter all the properties, interfaces, relationships and permissions for the new Information System. An asterisk preceding a field indicates that an entry is mandatory.
Creating a new Information System via the "New Release" button
Similar to the copy function, a new release can be created. This will also take over the values from the actual release, but the name can't be changed, because the new release references an Information System which already exists. To create a new Information System Release based on an existing one, click on the New Release button. You can find more information's about copying building blocks here: Copying a Building Block.
In both cases the following information will be copied in the new Information System (Release):
Not only does this permit you to use much of the data already entered for an existing release, you can also enter the release name of your choice and create a new Information System.
Since Interfaces are a separate BuildingBlock they are not copied within here, but can be copied on their own, providing you with a great flexibility.