Customizing Requirement Types

You can customize a requirement type by changing its icon, by setting options for test coverage and risk analysis, and by defining which fields are available and which are required for each requirement type. You can also define a rich text template for each requirement type.

Cross Project Customization - Working with a Linked Project: If you are working with a project that is linked to a template project, you cannot modify the default requirement types or requirement types defined by the template project. For requirement types defined by the template project, you can choose which user-defined fields defined in the project are available to requirements of the type.

ALM Editions: Cross project customization is not available for Quality Center Enterprise Edition. For more information about ALM editions and their functionality, see the Micro Focus Application Lifecycle Management User Guide: ALM Editions.

To customize a requirement type:

  1. In the Project Customization window, in the left pane, click Requirement Types. The Requirement Types page opens.

  2. Select a requirement type.

  3. In the Details tab, you can set the following:

    • Type Icon. To change the icon that is displayed in Requirements module tree views, next to the requirements of the selected type, select an icon from the Type Icon list. The icon is changed accordingly.

      Note: You cannot change the icon for the default requirement types Folder and Group.

    • Risk-Based Quality Management. To set risk-based quality management for the requirements of the selected type, select one of the following options from the Risk-Based Quality Management box:

      • Perform Analysis.

      • Perform Assessment.

      • None. Select this one if you do not want to enable risk-based quality management for requirements of the selected type.

    • Test Coverage. To enable or disable test coverage of the requirements of the selected type, select or clear the Test Coverage check box.

      Note: You cannot clear the Testing Coverage check box for a requirement type if there are requirements of that type which already have test coverage. To clear, you must either delete the requirements of that type with test coverage, remove the test coverage from those requirements, or change their type.

  4. In the System Fields tab, you can make a system field a required field for the type. Select the check box in the Required column for the field. Note that all system fields are automatically included in every type, and that some system fields cannot be set as optional.

    Tip: To set all system fields as required fields at one time, select the check box next to the Required column heading.

  5. In the User Defined Fields tab, you can choose which user fields are available for requirements of the type, and which of these fields are required:

    • To make a user-defined field available for the type, select the check box in the In Type column for the field. For details on user-defined fields, see Customizing Project Entities.

    • To make a user-defined field that is available for the type a required field, select the check box in the Required column for the field.

  6. In the Rich Text Template tab, use the HTML editor to define a page layout to be displayed as the initial view in the Rich Text tab of the Requirements module. For details on the Rich Text tab, see the Micro Focus Application Lifecycle Management User Guide: Requirements Module Window.

    Note:

    • You can only define one template per requirement type.

    • You cannot include graphics in the template. You can only add graphics from within the Rich Text tab of the Requirements module.

    • The template is applied automatically to all newly created requirements of the type.

    • The template can also by applied manually to existing requirements from within the Rich Text tab. Applying the template overwrites any existing content.

  7. Click Save to save your changes to the Requirement Types page.

Back to top