Linked.Archi TOGAF Content Metamodel

Abstract

OWL representation of the TOGAF Content Metamodel entity types and relationships. All entity classes extend arch:Element from the Linked.Archi core ontology. Relationship properties follow the Linked.Archi convention using arch:domainIncludes / arch:rangeIncludes.

Cross-reference for Linked.Archi TOGAF Content Metamodel classes, object properties and data properties back to ToC

This section provides details for each class and property defined by Linked.Archi TOGAF Content Metamodel.

Classes

Actor
Application Interface
Assumption
Business Event
Business Function
Business Process
Business Service
Capability
Constraint
Contract
Data Entity
Deliverable
Driver
Gap
Goal
Information System Service
Location
Logical Application Component
Logical Data Component
Logical Technology Component
Measure
Objective
Organization
Physical Application Component
Physical Data Component
Physical Technology Component
Plateau
Platform
Principle
Product
Requirement
Role
Technology Interface
Technology Service
Vision
Work Package

Actor^c back to ToC or Class ToC

IRI: https://meta.linked.archi/togaf/onto#Actor

A person, organization, or system that has behavior — such as performing business functions, using application services, or consuming technology services. An actor may be assigned to one or more roles.

has super-classes: element ^c

Application Interface^c back to ToC or Class ToC

IRI: https://meta.linked.archi/togaf/onto#ApplicationInterface

A point of access where application services are made available to a user, another application component, or a business process. Defines the boundary and protocol for interaction.

has super-classes: element ^c

Assumption^c back to ToC or Class ToC

IRI: https://meta.linked.archi/togaf/onto#Assumption

A statement of belief about the future state of the environment or enterprise that is taken as true for the purposes of architecture development. Assumptions carry risk and should be validated.

has super-classes: element ^c

Business Event^c back to ToC or Class ToC

IRI: https://meta.linked.archi/togaf/onto#BusinessEvent

An organizational state change that triggers or constrains business processes. Events may be external (market change) or internal (threshold reached).

has super-classes: element ^c

Business Function^c back to ToC or Class ToC

IRI: https://meta.linked.archi/togaf/onto#BusinessFunction

A unit of internal business capability that delivers business value. Business functions are typically aligned to an organization but may span multiple organizational units.

has super-classes: element ^c

Business Process^c back to ToC or Class ToC

IRI: https://meta.linked.archi/togaf/onto#BusinessProcess

A sequence of activities that produces a defined outcome. Business processes may decompose into sub-processes and are orchestrated by business events.

has super-classes: element ^c

Business Service^c back to ToC or Class ToC

IRI: https://meta.linked.archi/togaf/onto#BusinessService

An externally visible unit of business functionality that is meaningful to the consumer and supports business capabilities. Business services are supported by business processes and may be consumed by actors or other organizations.

has super-classes: element ^c

Capability^c back to ToC or Class ToC

IRI: https://meta.linked.archi/togaf/onto#Capability

An ability that an organization, person, or system possesses. Capabilities are typically expressed in general and high-level terms and require a combination of organization, people, processes, and technology to achieve.

has super-classes: element ^c

Constraint^c back to ToC or Class ToC

IRI: https://meta.linked.archi/togaf/onto#Constraint

An external factor that prevents an organization from pursuing particular approaches to meet its goals. Constraints narrow the solution space and must be accommodated by the architecture.

has super-classes: element ^c

Contract^c back to ToC or Class ToC

IRI: https://meta.linked.archi/togaf/onto#Contract

An agreement between a service provider and a consumer that specifies the terms, conditions, and service levels under which a service is delivered.

has super-classes: element ^c

Data Entity^c back to ToC or Class ToC

IRI: https://meta.linked.archi/togaf/onto#DataEntity

An encapsulation of data that is recognized by a business domain expert as a discrete concept. Data entities can be bound to any number of logical and physical data components.

has super-classes: element ^c

Deliverable^c back to ToC or Class ToC

IRI: https://meta.linked.archi/togaf/onto#Deliverable

An architecturally significant work product that is contractually specified and delivered as part of a work package. Deliverables may be documentation, models, or other artifacts.

has super-classes: element ^c

Driver^c back to ToC or Class ToC

IRI: https://meta.linked.archi/togaf/onto#Driver

An external or internal condition that motivates the organization to define its goals and implement changes. Drivers create the context for architecture work.

has super-classes: element ^c

Gap^c back to ToC or Class ToC

IRI: https://meta.linked.archi/togaf/onto#Gap

A statement of difference between two states — typically the baseline and target architectures. Gaps are identified through gap analysis and drive the definition of work packages.

has super-classes: element ^c

Goal^c back to ToC or Class ToC

IRI: https://meta.linked.archi/togaf/onto#Goal

A high-level statement of intent or direction for the organization. Goals are typically qualitative and long-term, providing the context for objectives and measures.

has super-classes: element ^c

Information System Service^c back to ToC or Class ToC

IRI: https://meta.linked.archi/togaf/onto#InformationSystemService

An externally visible unit of application functionality provided by one or more application components. Also known as Application Service in some TOGAF references.

has super-classes: element ^c

Location^c back to ToC or Class ToC

IRI: https://meta.linked.archi/togaf/onto#Location

A place where business activity takes place and can be hierarchically decomposed. Locations are used to describe the geographical distribution of business and technology elements.

has super-classes: element ^c

Logical Application Component^c back to ToC or Class ToC

IRI: https://meta.linked.archi/togaf/onto#LogicalApplicationComponent

An encapsulation of application functionality that is independent of a particular implementation. Logical application components are used to describe the required application capabilities.

has super-classes: element ^c

Logical Data Component^c back to ToC or Class ToC

IRI: https://meta.linked.archi/togaf/onto#LogicalDataComponent

A boundary zone that encapsulates related data entities to form a logical location to be held. Logical data components are technology- and implementation-independent.

has super-classes: element ^c

Logical Technology Component^c back to ToC or Class ToC

IRI: https://meta.linked.archi/togaf/onto#LogicalTechnologyComponent

An encapsulation of technology infrastructure that is independent of a particular product or vendor. Represents a category of technology required to support the application architecture.

has super-classes: element ^c

Measure^c back to ToC or Class ToC

IRI: https://meta.linked.archi/togaf/onto#Measure

An indicator or factor that can be tracked, usually on an ongoing basis, to determine success or alignment with objectives. Measures are associated with goals and objectives.

has super-classes: element ^c

Objective^c back to ToC or Class ToC

IRI: https://meta.linked.archi/togaf/onto#Objective

A time-bounded, measurable target that supports the achievement of a goal. Objectives are typically quantitative and have defined success criteria.

has super-classes: element ^c

Organization^c back to ToC or Class ToC

IRI: https://meta.linked.archi/togaf/onto#Organization

A self-contained unit of resources with goals, objectives, and measures. Organizations may be decomposed into sub-organizations and may participate in business functions and services.

has super-classes: element ^c

Physical Application Component^c back to ToC or Class ToC

IRI: https://meta.linked.archi/togaf/onto#PhysicalApplicationComponent

An application, application module, application service, or other deployable component of functionality. Physical application components realize logical application components.

has super-classes: element ^c

Physical Data Component^c back to ToC or Class ToC

IRI: https://meta.linked.archi/togaf/onto#PhysicalDataComponent

A boundary zone that encapsulates related data entities to form a physical location to be held. Physical data components are bound to specific technology and implementation choices.

has super-classes: element ^c

Physical Technology Component^c back to ToC or Class ToC

IRI: https://meta.linked.archi/togaf/onto#PhysicalTechnologyComponent

A specific technology infrastructure product or component used to implement part of the technology architecture. Physical technology components realize logical technology components.

has super-classes: element ^c

Plateau^c back to ToC or Class ToC

IRI: https://meta.linked.archi/togaf/onto#Plateau

A relatively stable state of the architecture that exists for a defined period of time. Plateaus represent intermediate target architectures on the migration roadmap between baseline and target states.

has super-classes: element ^c

Platform^c back to ToC or Class ToC

IRI: https://meta.linked.archi/togaf/onto#Platform

A combination of technology infrastructure and software that provides the environment in which application components are deployed and executed.

has super-classes: element ^c

Principle^c back to ToC or Class ToC

IRI: https://meta.linked.archi/togaf/onto#Principle

A qualitative statement of intent that should be met by the architecture. Principles define the underlying general rules and guidelines for the use and deployment of all IT resources and assets across the enterprise.

has super-classes: element ^c

Product^c back to ToC or Class ToC

IRI: https://meta.linked.archi/togaf/onto#Product

A coherent collection of services, accompanied by a contract or set of agreements, that is offered as a whole to a (type of) consumer. A product bundles business services and technology services.

has super-classes: element ^c

Requirement^c back to ToC or Class ToC

IRI: https://meta.linked.archi/togaf/onto#Requirement

A quantitative statement of business need that must be met by a particular architecture or work package. Requirements may be functional, non-functional, or architectural in nature.

has super-classes: element ^c

Role^c back to ToC or Class ToC

IRI: https://meta.linked.archi/togaf/onto#Role

An actor assumes a role to perform a task. Roles are used to distinguish the different responsibilities and authorities that actors may have within the organization.

has super-classes: element ^c

Technology Interface^c back to ToC or Class ToC

IRI: https://meta.linked.archi/togaf/onto#TechnologyInterface

A point of access where technology services are made available. Defines the boundary, protocol, and format for interaction with technology components.

has super-classes: element ^c

Technology Service^c back to ToC or Class ToC

IRI: https://meta.linked.archi/togaf/onto#TechnologyService

An externally visible unit of technology functionality provided by one or more technology components. Technology services support application components and information system services.

has super-classes: element ^c

Vision^c back to ToC or Class ToC

IRI: https://meta.linked.archi/togaf/onto#Vision

A high-level, aspirational view of the target architecture that outlines the strategic direction and key objectives of the architecture engagement.

has super-classes: element ^c

Work Package^c back to ToC or Class ToC

IRI: https://meta.linked.archi/togaf/onto#WorkPackage

A set of actions identified to achieve one or more objectives for the business. A work package can be a part of a project, a complete project, or a program.

has super-classes: element ^c

accesses^op back to ToC or Object Property ToC

IRI: https://meta.linked.archi/togaf/onto#accesses

Indicates that a process, function, or service accesses a data entity or data component — for reading, writing, or both.

communicates with^op back to ToC or Object Property ToC

IRI: https://meta.linked.archi/togaf/onto#communicatesWith

Indicates a communication or data exchange relationship between two elements — typically between application components or technology components.

contains^op back to ToC or Object Property ToC

IRI: https://meta.linked.archi/togaf/onto#contains

Indicates a containment relationship where one element wholly contains another — for example, a location contains organizations, or a plateau contains architecture elements.

decomposes into^op back to ToC or Object Property ToC

IRI: https://meta.linked.archi/togaf/onto#decomposesInto

Indicates that an element is decomposed into finer-grained elements of the same or related type — for example, a business function decomposes into sub-functions.

depends on^op back to ToC or Object Property ToC

IRI: https://meta.linked.archi/togaf/onto#dependsOn

Indicates that one element depends on another for its correct functioning or delivery — for example, a work package depends on another work package.

governs^op back to ToC or Object Property ToC

IRI: https://meta.linked.archi/togaf/onto#governs

Indicates that a principle, constraint, or requirement governs the design or behavior of an architecture element.

is realized through^op back to ToC or Object Property ToC

IRI: https://meta.linked.archi/togaf/onto#isRealizedThrough

Indicates that an abstract or logical element is realized through a physical or implementation element — the inverse perspective of the realizes relationship.

migrates from^op back to ToC or Object Property ToC

IRI: https://meta.linked.archi/togaf/onto#migratesFrom

Indicates the source plateau or baseline state from which a migration path originates. Used in transition architecture planning.

migrates to^op back to ToC or Object Property ToC

IRI: https://meta.linked.archi/togaf/onto#migratesTo

Indicates the target plateau or state to which a migration path leads. Used in transition architecture planning.

realizes^op back to ToC or Object Property ToC

IRI: https://meta.linked.archi/togaf/onto#realizes

Indicates that a physical component or implementation element realizes a logical or abstract element — for example, a physical application component realizes a logical application component.

supports^op back to ToC or Object Property ToC

IRI: https://meta.linked.archi/togaf/onto#supports

Indicates that one element provides support for another — for example, a business function supports a business service, or a technology service supports an application component.

tracks^op back to ToC or Object Property ToC

IRI: https://meta.linked.archi/togaf/onto#tracks

Indicates that a measure or objective tracks the progress or achievement of a goal, capability, or other target element.

used by^op back to ToC or Object Property ToC

IRI: https://meta.linked.archi/togaf/onto#usedBy

Indicates that an element is used by another element — for example, a data entity is used by a business process, or a technology service is used by an application component.

Legend back to ToC

^c: Classes
^op: Object Properties

Linked.Archi TOGAF Content Metamodel

Release: 2025-07-14

Abstract