Software Technologies Inventory and Attributes - Descriptive attributes for the Software Technologies Inventory
Software Technologies Inventory and Attributes
Chapter 10. Descriptive attributes for the Software Technologies Inventory
Executive Summary: Chapter Overview
IF4ITThe Bottom Line
Core Concepts
| Concept | Definition & Strategic Role |
|---|---|
| Semantic Identifier | The structured, permanent, human-readable identifier that lets a software technology be referenced unambiguously across every other inventory in the Enterprise Model. |
| Version as Identity | For software technologies, version is part of what identifies the governed thing. Support dates, vulnerabilities, and compatibility are version-specific, not product-specific. |
| Product Family | The grouping that ties related technologies from one supplier together, so portfolio decisions can be made across a family rather than one component at a time. |
Quick Q&A
Question: Should each version of a software technology be a separate record?
Read More Below
Descriptive attributes capture the identity of each software technology — what it is called, what it does, and which version the enterprise runs.
| Attribute Name | Maturity | Description and Notes |
|---|---|---|
| UID | Crawl | Description — Machine-readable identifier generated by whatever system created or imported the record. Benefit(s) — Allows the record to be reconciled against discovery tooling, asset platforms, and configuration data without relying on name matching. Source — Derived. Examples — CI-0084412, swtech-7f3a91c2 Notes — Optional. Where several source systems hold their own identifier, record the authoritative one and note its system of origin. |
| Semantic ID | Crawl | Description — Structured natural-language identifier assigned per the enterprise naming convention. Benefit(s) — The connective tissue of the Enterprise Model; lets applications, integrations, and agents reference this technology unambiguously. Source — Manual. Examples — SWTECH-DB-RELATIONAL-PRIMARY, SWTECH-MSG-BROKER-ENTERPRISE Notes — Mandatory. Once assigned, permanent and never reused, even after retirement. |
| Display Name | Crawl | Description — The plain-English name people actually use for the technology. Benefit(s) — Makes reports, catalogs, and dashboards readable without decoding identifiers. Source — Manual. Examples — Enterprise Relational Database Platform Notes — Mandatory. Distinct from Semantic ID; this one is human-first. |
| Description | Crawl | Description — A comprehensive statement of what the technology is, what it does, and how it differs from adjacent technologies in the inventory. Benefit(s) — Lets both practitioners and AI agents understand the record without external context; the single most valuable field for catalog usefulness. Source — Manual. Notes — Mandatory. Write it so someone unfamiliar with the technology could tell whether it is the right one for a given need. |
| Version | Crawl | Description — The version or versions of the technology the enterprise recognizes for this record. Benefit(s) — Support status, vulnerability exposure, and compatibility all attach to version; without it the record cannot answer the questions the inventory exists to answer. Source — Manual or Derived. Examples — 19c, 3.11, LTS 22.04 Notes — Where multiple versions are deployed, this attribute carries the governed or standard version and the Technical category records the full deployed set. |
Aliases and Alternative Names [Multi-Value] | Walk | Description — Other names by which the technology is known, including former names, internal shorthand, and acronyms. Benefit(s) — Prevents duplicate registration and makes catalog search find the record regardless of which name someone uses. Source — Manual. Notes — Particularly valuable for technologies renamed after acquisition, where teams continue using the prior name for years. |
| Product Family | Walk | Description — The broader family or suite the technology belongs to, where one exists. Benefit(s) — Enables portfolio decisions across a family rather than component by component, and surfaces bundled licensing and support relationships. Source — Manual. Notes — Leave empty for standalone technologies rather than inventing a family. |
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. Descriptive attributes for the Software Technologies Inventory | Software Technologies Inventory and Attributes. https://if4it.org/best-practices/software-technologies-inventory-and-attributes/descriptive-attributes-for-the-software-technologies-inventory/ (accessed 2026-07-28).
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