E-mail
|
Key
This line was removed.
This word was removed. This word was added.
This line was added.
|
Changes (15)
View Page HistoryMost 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 the _Name_ (which may contain a release identifier) and _Description_, an Information System has the following main properties:
* _System size_ : Please use the drop-down list in order to pick your option.
* _Maintenance activity_ : You can enter the specifics in the text field.
* _Parent_ : A hierarchical relation exists for the Information Systems. To assign a particular Information System as a parent to the one you are working with, select the name of the parent from the drop-down list.
* _System size_ : Please use the drop-down list in order to pick your option.
* _Maintenance activity_ : You can enter the specifics in the text field.
* _Parent_ : A hierarchical relation exists for the Information Systems. To assign a particular Information System as a parent to the one you are working with, select the name of the parent from the drop-down list.
{code}[ superordinate information system release's hierarchical name : ] <name of information system > # <release information>
E.g: SAP Classic-P10 : SAP Fi-P10 # 6.0
{code}
E.g: SAP Classic-P10 : SAP Fi-P10 # 6.0
{code}
You can edit these properties, and the following relations and attributes, by switching to Edit mode and opening the tabs in question (*Hierarchy* and *Relation*):
* _Children :_ To assign particular Information Systems as children to the one you are working with, select their names from the drop-down list.
* _Uses and Used by_ : Information Systems may in turn use other Information Systems. You can specify these by entering their names.
* _Belongs to the following Business Domains_ : Each Information System can be assigned to one or more Business Domains. To make this assignment, select the domain from the drop-down list.
* _Belongs to the following Business Functions_ : Use this section to manage information about the main Business Functions supported by the Information System.
* _Belongs to the following Business Object Associations_ : Use this section to manage information about the main Business Objects handled by the Information System. This association can get attributes. Find more informations about attributable associations [here|Business Objects].
* _Belongs to the following IS-Domains_ : Each Information System can be assigned to one or more Information System Domains. To make this assignment, select the domain from the drop-down list.
* _Belonging interfaces_ : Here you can indicate the Interfaces set up for the current Information System.
* _Runs on the following Infrastructure Elements_ : The Infrastructure Elements describe the operating platform (e.g. servers) that runs the Information System.
* _Belongs to the following Business Mappings_ : In this section you can manage all the Business Mappings that involve the current Information System.
* _Is based on the following Technical Components_ : The Technical Components comprise elements (e.g. application servers or frameworks) on which the Information System is based.
* _Is affected by the following projects_ : All projects involving the Information System can be listed in this section.
* _Belongs to the following Technical Domains_ : Each Information System can be assigned to one or more Technical Domains. To make this assignment, select the domain from the drop-down list.
* _Children :_ To assign particular Information Systems as children to the one you are working with, select their names from the drop-down list.
* _Uses and Used by_ : Information Systems may in turn use other Information Systems. You can specify these by entering their names.
* _Belongs to the following Business Domains_ : Each Information System can be assigned to one or more Business Domains. To make this assignment, select the domain from the drop-down list.
* _Belongs to the following Business Functions_ : Use this section to manage information about the main Business Functions supported by the Information System.
* _Belongs to the following Business Object Associations_ : Use this section to manage information about the main Business Objects handled by the Information System. This association can get attributes. Find more informations about attributable associations [here|Business Objects].
* _Belongs to the following IS-Domains_ : Each Information System can be assigned to one or more Information System Domains. To make this assignment, select the domain from the drop-down list.
* _Belonging interfaces_ : Here you can indicate the Interfaces set up for the current Information System.
* _Runs on the following Infrastructure Elements_ : The Infrastructure Elements describe the operating platform (e.g. servers) that runs the Information System.
* _Belongs to the following Business Mappings_ : In this section you can manage all the Business Mappings that involve the current Information System.
* _Is based on the following Technical Components_ : The Technical Components comprise elements (e.g. application servers or frameworks) on which the Information System is based.
* _Is affected by the following projects_ : All projects involving the Information System can be listed in this section.
* _Belongs to the following Technical Domains_ : Each Information System can be assigned to one or more Technical Domains. To make this assignment, select the domain from the drop-down list.
Alongside its simple _Name_ (which may contain a release identifier) and _Description_, an Information System Release 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. Any inconsistency in entries (e.g. a conflict with the set status) can be revealed by consistency checks (see [Consistency Checks|iteraplan:Consistency Checks]).
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|iteraplan:Consistency Checks]).
*Status*
The status of an Information System Release must have one of the following values:
The status of an Information System Release must have one of the following values:
In order to edit the attributes for Information Systems, switch to the tab *Attributes* in the Edit mode. The attribute _Type of Status_ is mandatory for all Information Systems. It can have any of the following values:
* _Current_ denotes an Information System 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 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 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 that was in productive operation at an earlier time but is no longer in use.
* _Current_ denotes an Information System 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 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 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 that was in productive operation at an earlier time but is no longer in use.
# _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.
# _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.
After making your changes, you can save them permanently by clicking *Save*, or click *Cancel* to discard without saving.
{tip:title=EAM-Tip}iteraplan provides a convenient mechanism for handling different strategic scenarios based on your _Target_\-information systems. [Have a look|iteraplan:Configuration].{tip}
*Seal*
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|iteraplan:Functional permissions] '_Create Seal_' is required. The seals can be set and renewed at any time.
!SS-2012-03-20_13.50.28.png|border=1!
By clicking on the Seal-Entry, a table will pop up, showing all current and past seals.
!SS-2012-03-20_13.51.38.png|border=1!
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|iteraplan config files]. 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.
*Seal*
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|iteraplan:Functional permissions] '_Create Seal_' is required. The seals can be set and renewed at any time.
!SS-2012-03-20_13.50.28.png|border=1!
By clicking on the Seal-Entry, a table will pop up, showing all current and past seals.
!SS-2012-03-20_13.51.38.png|border=1!
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|iteraplan config files]. 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.
{anchor:_Figure 1}
!SS-2012-03-20_13.54.56.png|border=1,width=587,height=503!
*Hierarchy tab on the screen for managing information system releases*
*Use* the *Relations* tab to edit relationships for the following building blocks.
{anchor:_Figure 2}
!SS-2012-03-20_13.58.05.png|border=1,width=592,height=273!
*Hierarchy tab on the screen for managing information system releases*
*Use* the *Relations* tab to edit relationships for the following building blocks.
{anchor:_Figure 2}
!SS-2012-03-20_13.58.05.png|border=1,width=592,height=273!
!isrelations.png|border=1!
*Relations tab on the page for editing Information System Releases* Systems*
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 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.
*{_}Project Portfolio{_}*
# _Projects_ : Use this section to manage information about the Projects concerning the Information System Release.
*{_}Business Architecture{_}*
# _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 information's about attributable associations [here|iteraplan:Business Objects].
# _Business Functions_ : Use this section to manage information about the main Business Functions supported by the Information System Release.
# _Business Mapping_ :
## _{+}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.
## _{+}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.
# _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|iteraplan:Attribute Groups and Attributes]__). The_ *Permissions* tab provides functions for assigning explicit Building Block Permissions (see _[Users, Roles and Permissions|iteraplan: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|#_Figure 3]) 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.
{anchor:_Figure 3}
!SS-2012-03-20_14.55.43.png|border=1!
*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: [iteraplan:Copying a Building Block].
In both cases the following information will be copied in the new Information System (Release):
* Relations
* Attributes
* Permissions
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.