Technical Debt Inventory and Attributes

Assets. The Technical Debt Inventory consumes governed Asset identifiers, names, types, owners, criticality, lifecycle, and dependency context from the Assets Inventory and cross-references the Assets that carry, depend on, contribute to, or are materially affected by each Technical Debt Item. The relationship is carried by Primary Asset, Affected Assets [Multi-Value], Dependent Assets [Multi-Value], and Contributing Assets [Multi-Value]. Asset examples include Application, Software Technology, Computing Technology, Computer, Network Technology, Network, Storage Technology, and Storage.

Risks. The Technical Debt Inventory cross-references Risks that are created, increased, mitigated, accepted, or otherwise associated with a Technical Debt Item. Related Risk identifiers, residual Risk, Risk acceptance references, and Risk-related evidence carry the relationship; the Risk inventory remains authoritative for likelihood, impact, exposure, response, and Risk acceptance.

Architecture Exceptions. The Technical Debt Inventory cross-references Architecture Exceptions that create, authorize, evidence, constrain, or are affected by Technical Debt. Related Architecture Exception identifiers and relevant approval and expiration dates carry the relationship; the Architecture Exception record remains authoritative for the deviation, approval, authority, conditions, duration, and Architecture review history.

Issues. The Technical Debt Inventory cross-references Issues that identify, evidence, result from, or are influenced by Technical Debt. Defect, Problem, and Disruption are examples of Issue types. Related Issue identifiers and source evidence carry the relationship; the Issue inventory remains authoritative for the Issue lifecycle and Issue-specific resolution.

Security Findings. The Technical Debt Inventory cross-references Security Findings that identify, evidence, increase, or remain affected by Technical Debt. Related Security Finding identifiers, control references, remediation evidence, and residual Security obligations carry the relationship; the Security Findings inventory remains authoritative for the finding and Security control lifecycle.

Projects and Initiatives. The Technical Debt Inventory consumes Project and Initiative identifiers, owners, funding, milestones, and outcome context when debt is remediated or otherwise addressed through planned change. Related Project, Related Initiative, Remediation Plan, Funding Source, Milestones, and Target Outcomes carry these relationships; Project and Initiative records remain authoritative for delivery and investment governance.

Releases. The Technical Debt Inventory cross-references Releases that introduce, defer, mitigate, remediate, validate, or close Technical Debt. Related Release identifiers, planned and actual dates, deployment evidence, and validation evidence carry the relationship; Release records remain authoritative for Release scope and execution.

People. The Technical Debt Inventory consumes Person identifiers for Technical Debt Owners, Asset Owners, submitters, assessors, decision authorities, control owners, remediation owners, validators, closure authorities, and Subject Matter Experts. These role-typed relationships are carried by the corresponding ownership and stakeholder attributes; the People inventory remains authoritative for each Person.