This documentation supports the 9.1 to 9.1 Service Pack 3 version and its patches of BMC Atrium Core. The documentation for version 9.1.04 and its patches is available here.

To view the latest version, select the version from the Product version menu.

About qualification sets

The Qualification Builder uses a dynamic tree-like structure for selecting classes and attributes. You can create multiple levels of classes and each class can have multiple related classes.

Note

Related classes only apply to qualification sets.

This section contains the following topics:

Using classes

The following scenarios are supported.

Scenario A

Class A has two related classes: Class B and Class C

CLASS A

  • RELATED TO Class B
  • RELATED TO Class C

You could also say, Class B and Class C are related to Class A.

Scenario B

Class A has one related class, which in turn, has its own related class.

CLASS A

  • RELATED TO Class B
    • RELATED TO Class C

      Class A has one related class, Class B and Class B has one related class, Class C.

Scenario C

This scenario is a combination of scenario A and B.

CLASS A

  • RELATED TO Class B
    • RELATED TO Class C
  • RELATED TO Class D
    • RELATED TO Class E

      Class A has two related classes, Class B and Class D, which in turn have their own related classes.

Guidelines for using classes

Keep the following guidelines in mind when using classes in a qualification set:

  • Classes can be added in any order.
  • A new related class can be added anywhere in the tree, but the related class is always added as the last child of its parent.

    Note

    You can not reorder classes.

  • From each class and related class, any number of attributes, attribute values, and conditions can be specified.
  • Related classes apply only to qualifications sets.
  • When a related class is added to a selected class, the comparison service checks for a relationship between the two classes. If there is no specific relationship between the two classes, the comparison service uses the Base Relationship class.

Guidelines for using attributes in a qualification set

Be aware of the following guidelines when using attributes in a qualification set:

  • A newly added attribute, like related class, is always added as the last child of its parent class.
  • The attribute name, operator, and value are mandatory.
  • The value entered for an attribute must be appropriate for the selected operator.
  • Valid operators for attributes in a qualification set are as follows.

    Operators in a qualification set

    Attribute operator Description

    ==

    equal to, numeric or a string

    !=

    not equal to, numeric or a string

    <

    less than, numeric only

    >

    greater than, numeric only

    <=

    less than or equal to, numeric only

    >=

    greater than or equal to, numeric only

    LIKE

    • numeric
    • string
    • supports SQL %

    IN or NOT IN

    • numeric
    • string
    • comma delimited list
    • range--the range operator is .. with no spaces before or after. For example, 10..50.

    Note

    These attribute operator values are only valid in a qualification set. Different operators are used in an include set.

Best practice

When creating qualifications sets for the BMC_Product class, be sure to qualify the baseline and target with the name of the product. Using the name of a product prevents the comparison of unlike products, for example, comparing Adobe Acrobat Reader with Windows Word.

Qualifications on other CI types should follow a similar approach.

Was this page helpful? Yes No Submitting... Thank you

Comments