Glossary of Terms and Phrases - Technical Debt Inventory and Attributes
Glossary of Terms and Phrases
(Chapter 2 of Technical Debt Inventory and Attributes)
The following terms are used throughout this document with specific meanings. Terms defined in the IF4IT Enterprise Inventory Management Best Practices document or in discipline-specific Best Practices documents (APM, TPM, etc.) are not duplicated here — refer to those documents for broader inventory governance and discipline-specific vocabulary.
| Term | Abbreviations and Acronyms | Definition |
|---|---|---|
| Assessment Confidence | The degree of reliability assigned to the evidence, assumptions, estimates, and conclusions used to assess a Technical Debt Item, expressed as High, Moderate, Low, or Unknown. | |
| Awareness | The classification describing when or how the enterprise became aware of a Technical Debt condition: Known at Creation, Discovered Later, Suspected, Hidden Until a Triggering Event, or Unknown Origin. | |
| Catalog | A discovery and exposure construct built over an Inventory/Registry that surfaces registered Noun Instances and their associated data, content, and services at both the catalog level and the individual instance level. Serves as a knowledge management user interface into the Enterprise Model — letting a person find, learn about, and engage with instances, browse and filter them by their governed attribute values, and traverse their relationships to related Noun Instances. | |
| Catalog of Catalogs | The enterprise-wide federated discovery surface spanning every Noun Type Catalog, exposing registered instances and their associated data, content, and services across the Enterprise Model. The discovery-layer counterpart to the Inventory of Inventories. | |
| Consequence Category | A controlled classification of the current or potential effect created by a Technical Debt Item, such as Financial, Delivery, Operational, Service, Security, Compliance, Resilience, Maintainability, Changeability, Scalability, Interoperability, Data, Knowledge, Strategic, or Customer-Related. | |
| Disposition | The authorized decision describing how a Technical Debt Item will be handled, such as remediation, mitigation, temporary acceptance, deferral, Asset retirement, rejection, or closure as resolved. | |
| Intent | The classification describing whether Technical Debt is Intentional, Unintentional, Inherited, Emergent, or of Unknown origin. | |
| Item Boundary | The defined scope that makes one Technical Debt condition independently identifiable, assignable, assessable, remediable, validatable, and closable from other conditions. | |
| Materiality | The governance significance of a Technical Debt Item, expressed as Level 1 Local, Level 2 Significant, Level 3 Portfolio, or Level 4 Enterprise/Critical. | |
| Priority | The relative order in which a Technical Debt Item should receive attention, expressed as P1 Immediate, P2 High, P3 Moderate, P4 Low, or P5 Monitor. | |
| Progressive Completeness | The practice of requiring a minimum viable record at capture and progressively requiring more attributes as a Technical Debt Item advances through qualification, assessment, decision, remediation, validation, closure, and reopening. | |
| Registry | A governed, authoritative collection in which every instance of a Noun Type is formally registered, either manually or through automation. Equivalent to a Noun Inventory — the two terms name the same construct. | |
| Technical Debt Inventory | TDI | The authoritative system of record for Technical Debt Items and their ownership, classification, affected Assets, lifecycle, decisions, plans, evidence, and outcomes. |
| Technical Debt Item | TDI | The smallest independently identifiable, recordable, assessable, assignable, prioritizable, and closable instance of Technical Debt that an enterprise governs. |
| Technical Debt Type | A controlled classification identifying the primary technical domain in which a Technical Debt condition or unresolved obligation exists. |
How to cite this page
When referencing this page in academic work, internal standards, or external publications, include the page title, IF4IT as author and publisher (The International Foundation for Information Technology (IF4IT), LLC), the URL, and your access date.
Example (informal web citation):
The International Foundation for Information Technology (IF4IT), LLC. Glossary of Terms and Phrases | Technical Debt Inventory and Attributes. https://if4it.org/best-practices/technical-debt-inventory-and-attributes/glossary-of-terms-and-phrases/ (accessed 2026-10-05).
See About Us for content governance and site-wide citation guidance.
Copyright for The International Foundation for Information Technology (IF4IT), LLC: 2008 - Present
Legal Disclaimers