Relationship between Defect and Capability

The relationship between a defect and a Capability or Subsystem determines the prioritization for the auto-scheduler in terms of the order of tasks created to fix the defect.

Prioritization is determined by the capability's numeric business weight, taking into account all business weights to which the entity belongs.

• Relationship is Optional: A defect may or may not be linked to a Capability.

Types of Relationships:

There are two types of relationships:

1. Breaks:
   • Critical Relationship: The detected defect breaks critically important functions/capabilities of the product. For example, if a defect affects the ability to log in to the application, the relationship type for Defect to Capability would be "Breaks."
   • Priority Calculation Logic: Adds +1 to the existing business weight of the Capability.
2. Degrade:
   • Minor Relationship: The detected defect affects the functionality/capabilities of the product, but these functions/capabilities are rarely used or seen; hence, fixing the defect is not critically necessary.
   • Priority Calculation Logic: Subtracts -1 from the existing business weight of the Capability.

Impact of Changing Business Weights:

Changes in business weights affect the auto-scheduler's determination of the importance and order of task execution for fixing the defect.