Share this page

# Customize weight boundaries

You can customize how OpenText Application Quality Management uses the values assigned to risk-based quality management criteria to determine the Business Criticality, Failure Probability, and Functional Complexity for a requirement.

In this topic:

## Customize weight boundaries for Business Criticality

For each requirement, OpenText Application Quality Management calculates the total of the weights (TW) of the values assigned to each of the Business Criticality criteria. OpenText Application Quality Management then uses this total to categorize the Business Criticality of the requirement as either C- Nice to Have, B - Important, or A - Critical. OpenText Application Quality Management automatically calculates the highest and lowest possible total weight and uses these to define the upper boundary of the Critical category and the lower boundary of the Nice to Have category. You define the boundaries between the Nice to Have and Important categories, and between the Important and Critical categories.

Example

Suppose there are two criteria for Business Criticality, each with three possible values whose weights are 20, 60, and 100. The minimum total weight is therefore 40 (if both criteria are assigned the value with weight 20) and the maximum total weight is 200 (if both criteria are assigned the value with weight 100). OpenText Application Quality Management automatically calculates these totals and uses them to determine the lower and upper boundaries for the categories. You determine the boundaries between the categories by typing 100 in the Nice to Have field and 160 in the Critical field.

In this example, OpenText Application Quality Management determines the Business Criticality for a requirement as follows:

- If the sum of the weights of each of the criteria for a requirement is less than or equal to 100, the requirement will have the Nice to Have Business Criticality. This could happen, for example, if the criteria have values with weights 20 and 60, so the total weight is 80.

- If the sum is greater than 100 but less than 160, the requirement will have the Important Business Criticality. This could happen, for example, if the criteria have values with weights 60 and 60, so the total weight is 120.

- If the sum is greater than or equal to 160, the requirement will have the Critical Business Criticality. This could happen, for example, if the criteria have values with weights 100 and 60, so the total weight is 160.

To customize weight boundaries for Business Criticality:

1. In the Project Customization window, in the left pane, click Risk-Based Quality Management. The Risk-Based Quality Management page opens.

2. Click the Business Criticality tab. This tab displays criteria used to determine Business Criticality.

3. Under Calculation of Business Criticality value based on total weights, define the boundaries between different Business Criticality values. To define these boundaries, type the relevant values in the Nice to Have and Critical fields.

4. Click Save to save your changes to the Risk-Based Quality Management page.

Back to top

## Customize weight boundaries for Failure Probability

For each requirement, OpenText Application Quality Management calculates the total of the weights (TW) of the values assigned to each of the Failure Probability criteria. OpenText Application Quality Management then uses this total to categorize the Probability of the requirement as either 3 - Low, 2 - Medium, or 1- High.

OpenText Application Quality Management automatically calculates the highest and lowest possible total weight and uses these to define the upper boundary of the High category and the lower boundary of the Low category. You define the boundaries between the Low and Medium categories, and between the Medium and High categories.

Example

Suppose there are two criteria for Failure Probability, each with three possible values whose weights are 20, 60, and 100. The minimum total weight is therefore 40 (if both criteria are assigned the value with weight 20) and the maximum total weight is 200 (if both criteria are assigned the value with weight 100). OpenText Application Quality Management automatically calculates these totals and uses them to determine the lower and upper boundaries for the categories. You determine the boundaries between the categories by typing 100 in the Low field and 160 in the High field.

In this example, OpenText Application Quality Management determines the Failure Probability for a requirement as follows:

- If the sum of the weights of each of the criteria for a requirement is less than or equal to 100, the requirement will have the Low Failure Probability. This could happen, for example, if the criteria have values with weights 20 and 60 so the total weight is 80.

- If the sum is greater than 100 but less than 160, the requirement will have the Medium Failure Probability. This could happen, for example, if the criteria have values with weights 60 and 60 so the total weight is 120.

- If the sum is greater than or equal to 160, the requirement will have the High Failure Probability. This could happen, for example, if the criteria have values with weights 100 and 60 so the total weight is 160.

To customize weight boundaries for Failure Probability:

1. In the Project Customization window, in the left pane, click Risk-Based Quality Management.

2. Click the Failure Probability tab. This tab displays criteria used to determine Failure Probability.

3. Under Calculation of Failure Probability value based on total weights, define the boundaries between different Failure Probability values. To define these boundaries, type the relevant values in the Low and High fields.

4. Click Save to save your changes to the Risk-Based Quality Management page.

Back to top

## Customize weight boundaries for Functional Complexity

For each requirement, OpenText Application Quality Management calculates the total of the weights (TW) of the values assigned to each of the Functional Complexity criteria. OpenText Application Quality Management then uses this total to categorize the Functional Complexity of the requirement as either 3 - Low, 2 - Medium, or 1- High.

OpenText Application Quality Management automatically calculates the highest and lowest possible total weight and uses these to define the upper boundary of the High category and the lower boundary of the Low category. You define the boundaries between the Low and Medium categories, and between the Medium and High categories.

Example

Suppose there are two criteria for Functional Complexity, each with three possible values whose weights are 20, 60, and 100. The minimum total weight is therefore 40 (if both criteria are assigned the value with weight 20) and the maximum total weight is 200 (if both criteria are assigned the value with weight 100). OpenText Application Quality Management automatically calculates these totals and uses them to determine the lower and upper boundaries for the categories. You determine the boundaries between the categories by typing 100 in the Low field and 160 in the High field.

In this example, OpenText Application Quality Management determines the Functional Complexity for a requirement as follows:

- If the sum of the weights of each of the criteria for a requirement is less than or equal to 100, the requirement will have the Low Functional Complexity. This could happen, for example, if the criteria have values with weights 20 and 60 so the total weight is 80.

- If the sum is greater than 100 but less than 160, the requirement will have the Medium Functional Complexity. This could happen, for example, if the criteria have values with weights 60 and 60 so the total weight is 120.

- If the sum is greater than or equal to 160, the requirement will have the High Functional Complexity. This could happen, for example, if the criteria have values with weights 100 and 60 so the total weight is 160.

To customize weight boundaries for Functional Complexity:

1. In the Project Customization window, in the left pane, click Risk-Based Quality Management.

2. Click the Functional Complexity tab. This tab displays criteria used to determine Functional Complexity.

3. Under Calculation of Functional Complexity value based on total weights, define the boundaries between different Functional Complexity values. To define these boundaries, type the relevant values in the Low and High fields.

4. Click Save to save your changes to the Risk-Based Quality Management page.

Back to top

See also:

- Customize risk-based quality management

https://admhelp.microfocus.com Application Quality Management 8942
Tips to improve your search results... OpenText™ Application Quality Management Help Center OpenText™ Application Quality Management Help Center OpenText™ Application Quality Management Help 26.1 All View Local Help Center View Online Help Center Version: