TRM Technical Debt calculation

  • Release version: Washingtondc
  • Updated February 1, 2024
  • 1 minute to read

    • A TRM technical debt indicates the unapproved usage of a software. The technical debts table [sn_apm_trm_standards_technical_debt], displays the TRM products and associated business applications details, and the reason for the technical debt.

    Technical debts are created at two levels if any of the following conditions are met. The Level 2 is checked only if the system property sn_apm_trm.is_product_life_cycle_tech_debt_enabled is set to True.
    • Level 1
      • If a product is associated with a business application, but isn’t part of the TRM product list. (OR)
      • If a product is associated with a business application and part of the TRM products list, but has the TRM phase's production unapproved.
    • Level 2
      • If a product is associated with a business application, is part of the TRM products list, and has the TRM phase's production approved but doesn’t have any associated TRM Product life cycles. (OR)
      • If a product is associated with a business application and part of the TRM products list, has the TRM phase with production approved, and the TRM product lifecycle exists, one of the following cases is considered:

        Case 1: If the lifecycle full version of the Application Service Software Model is not empty.

        A technical debt is created if the following condition isn’t met for a TRM Product lifecycle:
        • TRM phase with production approved AND
        • TRM product's TRM phase with production approved AND
        • Version matching the lifecycle full version of the application service software model record AND
        • Phase start date <= Today's date <=phase end date.

        Case 2: If the life cycle full version of the Application Service Software Model is empty.

        Technical debt is created if the following condition isn’t met for a TRM Product Lifecycle:
        • TRM phase with production approved AND
        • TRM product's TRM phase with production approval AND
        • Version is/starts with (based on version operator and isSampPluginInstalled) version of the associated software model AND
        • The edition is/starts with (based on edition operator and isSampPluginInstalled) edition of associated software model AND
        • Phase start date <= Today's date <=phase end date.