The IF4IT Enterprise Model and Modeling Best Practices - Glossary of Terms and Phrases
The IF4IT Enterprise Model and Modeling Best Practices
Chapter 2. Glossary of Terms and Phrases
The following glossary defines terms and phrases used throughout the IF4IT Enterprise Model and Modeling Best Practices document. Terms are listed alphabetically and definitions are intentionally concise so the glossary remains useful as a reference. Where a term requires deeper treatment, the relevant sections in the body of this document provide the fuller explanation. For terms that originate in the companion IF4IT Enterprise Inventory Management Best Practices document (EIM) — such as Inventory, Inventory Owner, or Enterprise Model — the definitions here either elaborate the EIM definition for the IF4IT EM context or note explicit cross-references to EIM where the canonical treatment lives.
Terms and Phrases and Their Definitions
| Term or Phrase | Abbreviation or Acronym | Definition |
|---|---|---|
| AI as the Graph Compiler | Thesis 2 | Thesis 2. AI reads the EM as a Semantic Model and compiles its Taxonomy, Ontology, inventories, attributes, relationships, and rules into data and knowledge graphs. Compilation may occur in AI memory for immediate use or as external graph output for downstream systems. |
| AI as the Graph Runtime | Thesis 3 | Thesis 3. After the graph is compiled, AI operates on it by traversing, querying, comparing, visualizing, reasoning, and producing reports, dashboards, or generated applications from the graph. |
| AI Code Generation | The use of AI to produce standalone application code. In this document, AI code generation supports generated-app runtime patterns in which generated applications operate over IF4IT EM graph outputs. | |
| Architecture Modeling Tool | AMT | A software platform for enterprise architecture modeling. AMTs typically use a built-in or configurable metamodel that defines the element types, relationships, views, reports, and integrations the tool supports. The EM is tool-independent and can be used with, alongside, or apart from AMTs. |
| Catalog of Noun Types | An operational synonym for the Taxonomy: the structured catalog of Noun Types the enterprise has chosen to govern. Equivalent to the Inventory of Inventories in IF4IT terminology. See Taxonomy. | |
| Data and Knowledge Graph | A graph representation of Noun Instances, attributes, typed relationships, reified relationships, and semantic context compiled from IF4IT EM source artifacts. AI can traverse and reason over this graph to produce outputs. | |
| Descriptive Attribute | An inventory attribute that describes a Noun Instance itself, such as name, version, status, date, or count, without directly naming a relationship. See also Predicate Attribute and Narrative Attribute. | |
| Domain-Space Controller Pattern | A repeatable IF4IT EM pattern in which the Noun Type Taxonomy defines the conceptual model of the domain space, the Ontology realizes and operationalizes each Noun Type, each Noun Type is linked to a homogeneous inventory set of instances, and AI compiles and reasons over the resulting model. Advanced implementations may scale this pattern into related taxonomies and ontology layers. | |
| Domain Space Scalability | The ability of the Enterprise Model to scale its conceptual Noun Type Taxonomy to fit any enterprise, industry, functional, product, operational, or problem-specific domain, including advanced implementations that organize multiple related taxonomies or ontology layers when warranted. | |
| Direct External Runtime | Pattern 2 | Thesis 3 Pattern 2. AI operates against graphs that have been generated externally and loaded into downstream systems such as graph databases, ontology platforms, or document stores. |
| Direct In-AI-memory Runtime | Pattern 1 | Thesis 3 Pattern 1. AI operates on the graph it has compiled into its own working context, without requiring a persistent external graph system. |
| Enterprise Model | EM | A connected representation of an enterprise as a knowledge graph. The IF4IT Enterprise Model is the specific IF4IT approach, extending enterprise inventory management with Taxonomy, Ontology, semantic rules, and AI-consumable graph compilation, that allows any enterprise to generate their own EM(s). |
| External Graph Generation | Mode B | Thesis 2 Mode B. AI or deterministic tooling transforms IF4IT EM source artifacts into external graph or graph-compatible outputs, such as Cypher, RDF, JSON-LD, CSV edge lists, GraphML, or other downstream formats. |
| Generated-app Runtime | Pattern 3 | Thesis 3 Pattern 3. AI generates standalone applications that operate over IF4IT EM graph outputs and expose model value to users through deployed reports, dashboards, visualizations, or applications. |
| Homogeneous Inventory Set | A coherent inventory, list, catalog, register, or source collection that contains instances of the same Noun Type. | |
| IF4IT Enterprise Model | IF4IT EM | The connected, governed, queryable representation of an enterprise as a Semantic Model designed for AI consumption. It is built from a Taxonomy, an Ontology, and the inventories that realize them. |
| In-AI-memory Compilation | Mode A | Thesis 2 Mode A. AI ingests IF4IT EM source artifacts directly into its working context and assembles a graph in memory for immediate use. |
| Inventory | The populated set of Noun Instances for one Noun Type. Each inventory is owned and governed by its Inventory Owner and ideally provides a coherent source of instances for the Noun Type it realizes. | |
| Inventory of Inventories | IOI | The IF4IT-native term for the enterprise catalog of governed inventories. Because each inventory realizes one Noun Type, the Inventory of Inventories is structurally equivalent to the Taxonomy, which controls all things that are in scope for an Enterprise Model. |
| IT Ontology | ITO | An Information Technology (IT) focused version of the broader term Ontology, acting as the definitional, relational, attribute, and rules layer that realizes and operationalizes the conceptual Noun Type Taxonomy as it pertains to the domain of IT. It defines what each IT Noun Type means, how it relates to other IT Noun Types, how technologies like AI should interpret it, what rules govern it, and how it links to its homogeneous inventory set of instances. In advanced environments, related ontology layers or sub-ontologies may be organized to support multiple domain spaces while preserving practical enterprise-modeling simplicity |
| Metamodel | In Architecture Modeling Tool (AMT) practice, the schema defining allowed element types, relationships, and properties. In the IF4IT EM, the comparable semantic role is very loosely served by the Taxonomy and Ontology together, but without requiring a single rigid tool schema before inventories can be ingested. | |
| Model Instance | MI | A separate and distinct instantiate of the same or different models. For example, the same Model Instance can be deployed to separate isolated environments or different Model Instances can be created to reflect different domain spaces. |
| Narrative Attribute | An attribute containing natural-language content about a Noun Instance, such as a description, rationale, context summary, or justification. AI can use narrative attributes to infer candidate relationships during compilation. | |
| Noun Domain Space | The scoped set of Noun Types (a.k.a. Data Types or Data Entities) that define the kinds of things the Enterprise Model recognizes, governs, and reasons over for a selected enterprise, industry, functional, product, operational, or problem-specific domain for any model development. | |
| Noun Instance | A specific record or item belonging to one Noun Type. For example, a specific deployed application is a Noun Instance of the Noun Type Application. | |
| Noun Type | A category of a singular governed thing in an IF4IT-compliant Enterprise Model, such as Application, Capability, Vendor, Claim, Member, Drug, Trial, or Adverse Event. Noun Types may be common enterprise concepts or domain-specific concepts defined for a selected Noun Domain Space. | |
| NOUNZ | The IF4IT-built deterministic compiler that implements core IF4IT EM concepts and can synthesize graphs, catalogs, traversals, visualizations, and dashboards from source artifacts without AI involvement. | |
| On-Demand Compilation | The ability to compile purpose-specific graph representations when needed, such as current, historical, projected, scoped, hypothetical, or format-specific graph views. | |
| Ontology | The definitional, relational, attribute, and rules layer that realizes and operationalizes the conceptual Noun Type Taxonomy. It defines what each Noun Type means, how it relates to other Noun Types, how technologies like AI should interpret it, what rules govern it, and how it links to its homogeneous inventory set of instances. In advanced environments, related ontology layers or sub-ontologies may be organized to support multiple domain spaces while preserving practical enterprise-modeling simplicity. | |
| Predicate Attribute | An attribute whose name acts like a predicate and whose value references another Noun Instance, thereby implying a semantic relationship. Example: Business Owner = Jane Doe. | |
| Reified Semantic Relationship | A relationship elevated into a first-class Noun Type with its own definition, attributes, lifecycle, governance, and inventory. Contracts, integrations, dependencies, obligations, and service agreements may be examples. | |
| Semantic Identifier | A stable, human-meaningful identifier for a Noun Instance. Semantic identifiers help preserve meaning across inventories, refresh cycles, AI processing, and downstream consumers. | |
| Semantic Model | A model that carries meaning through semantic structures rather than opaque keys alone. The IF4IT EM is means of designing and synthesizing a Semantic Model because it uses Taxonomy, Ontology, semantic identifiers, rich attributes, semantic relationships, and rules to make enterprise knowledge AI-consumable. | |
| Semantic Relationship | A typed, meaning-bearing connection between Noun Instances. Semantic relationships may be lightweight mappings or reified into first-class Noun Types when they require their own attributes, lifecycle, or governance. | |
| Specialization (Noun Type) | The decomposition of a general Noun Type into more specific child Noun Types when finer-grained governance is useful. Specialization creates Taxonomy depth. | |
| Taxonomy (a.k.a. Noun Type Taxonomy) | The conceptual model of the domain space and the catalog of governed Noun Types in any IF4IT-compliant Enterprise Model. It acts as the model’s domain-space definition construct, naming the kinds of things the model recognizes and allowing the modeler to scale the domain space up or down to fit the intended purpose. Each Noun Type in the Taxonomy is realized in the Ontology, where it is registered, defined, described, governed, related, associated with rules, and linked to a homogeneous inventory set of Noun Instances. In advanced environments, related taxonomies may themselves be organized into larger taxonomy structures. | |
| Taxonomy Depth | The presence of parent-child specialization relationships among Noun Types. A flat Taxonomy has no hierarchy; a deeper Taxonomy includes specialized child Noun Types. |
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 | The IF4IT Enterprise Model and Modeling Best Practices. https://if4it.org/best-practices/if4it-enterprise-model-and-modeling-best-practices/glossary-of-terms-and-phrases/ (accessed 2026-07-21).
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