Show TOC

Procedure documentationEditing TBOM Criticality


You can assign criticality values to the objects in the TBOM. For example, you can give tables a higher criticality than user interface elements. You can set a different criticality for each object classification type.

Depending on the setting, Business Process Change Analyzer can restrict the list of objects affected by a change, to objects with a specified criticality. This restriction then filters TBOM objects with this criticality.

You can edit the TBOM criticality for one TBOM (of one executable entity) or for all TBOMs. You can also define TBOM criticality for one user or for all users.


Editing Criticality for a TBOM

Note Note

You can only assign criticality values to individual TBOMs if the user parameter AGS_TBOM_EXPERT has at least the value 2.

End of the note.

If you edit the TBOM criticality for a TBOM, the TBOM identifier (TBOM GUID) is specified automatically.

If you specify a user name, the criticality only applies when this user performs a change impact analysis.

  1. Open the attributes of the executable entity whose TBOM you wish to edit.

  2. Choose the TBOM tab.

  3. Choose Criticality.

  4. Choose Display <−−> Change to switch to editing mode.

  5. Specify to which objects in the TBOM each criticality applies.

  6. Check the criticality information.

  7. Save your entries.

Editing Criticality for all TBOMs

If you edit the TBOM criticality for all TBOMs, the TBOM identifier (TBOM GUID) is not specified automatically. If the field remains empty, the criticality applies to all TBOMs.

As is the case when you edit the criticality for a TBOM, you can also specify a user name if the criticality is to apply to this user only.

Unlike in other fields, you cannot use wildcard characters in the fields for the TBOM identifier (TBOM GUID) and the user name.

  1. In the Test Management work center, choose the Administration view.

  2. Choose Edit TBOM Criticality Table.

  3. Choose Display <−−> Change to switch to editing mode.

  4. Specify to which objects in the TBOM each criticality applies.

  5. Check the criticality information.

  6. Save your entries.

Checking Criticality Information
  1. To check a row, double-click on it.

    To check all rows, choose Check.

    The result of the check displays all the questionable or invalid criticality values. These can be due to, for example, an incorrect TBOM ID, the wrong user name or double entries.

    Note Note

    Criticality information is processed from the top down. This is why lines that are formulated in more general terms than lines above them in the table also lead to a warning.

    End of the note.
  2. Choose Delete Warnings and Continue to delete the invalid entries.

If you save the TBOM criticality, the check is also called. However, you can also save invalid criticality values. In the change impact analysis, the invalid criticality will be ignored.

Edit criticality

You can use the following functions for the TBOM criticality:

  • Copy text of selected cell

  • Append new rows with criticality information to the end of the table, or insert them at the selected point

  • Delete rows with criticality information

  • Find a search term in the criticality information

  • Restrict the displayed criticality information with a filter

You can use wildcard characters for almost all parameters. Only the TBOM (TBOM GUID) identifier and the user name must be either fully-specified or blank.

Generating Criticality from Object Lists

You can also use an object list in the TBOM content display to generate TBOM criticality easily. When you create criticality in this way, many field values are predefined. Proceed as follows:

  1. Open one of the following displays:

  2. In the table overview, select one or more rows at logical component or package level. You can also select one or more rows in the detail report.

  3. Choose Add to Criticality.

    The system creates a suitable criticality automatically from the selected rows. A dialog box displays the new criticality as default value.

    If you have selected logical components or packages, values are predefined in these fields only. If you have selected individual objects, values are predefined for all fields with the exception of User Name and TBOM Validity.

    The TBOM Validity field is only displayed if you opened the dialog box from the TBOM content display. You can use this field to specify whether the criticality information is to apply to all TBOMs or to the current TBOM only.

  4. To adjust the individual fields for the criticality, edit the values directly in the current dialog box.

    For example, if you want to generalize a criticality, you can replace a fixed value with a wildcard character. Define the criticality information as generally as possible.

  5. To change multiple criticality values simultaneously, proceed as follows:

    1. Choose Mass Change.

      If you had selected just one row, the fields are filled automatically with the values for this criticality. If you had selected multiple rows, the fields are filled automatically with wildcard characters.

    2. Change the criticality.

    3. Ensure that the checkboxes on the right of the dialog box are selected for those fields whose values you want to apply.

    4. To apply the values to the previously selected rows, choose Apply.

      To apply the values to all rows, choose Apply to All.

  6. Select all criticality values that you want to save.

  7. Choose Check.

    The system checks all selected criticality values. The Status column indicates whether a criticality is valid.

    The system notifies you, for example, if an identical TBOM criticality already exists in the system. If there is already an identical TBOM criticality, you can expand the redundant row to show the existing criticality below the redundant row, in read-only mode. If the criticality contains errors, the system generates a warning.

  8. Save.

    The system saves all selected criticality values. Criticality values for which warnings are issued are also saved. However, the system ignores these values in the change impact analysis.