TOGAF® Standard — Introduction - TOGAF Content Framework and Enterprise Metamodel

2. TOGAF Content Framework and Enterprise Metamodel

2.1 Overview

The TOGAF ADM provides a process lifecycle to create and manage architectures within an enterprise. At each phase within the ADM, a discussion of inputs, outputs, and steps describes a number of architectural work products or artifacts, such as process and application.

The Content Framework and Enterprise Metamodel provided here define a formal structure for these terms to ensure consistency within the ADM and also to provide guidance for organizations that wish to implement their architecture within an architecture tool.

The Content Framework defines a categorization framework to be used to structure the Architecture Description, the work product used to express an architecture, and the collection of models that describe the architecture.

The Enterprise Metamodel defines the types of entities to appear in the models that describe the enterprise, together with the relationships between these entities.

2.2 TOGAF Enterprise Metamodel Vision

The TOGAF Standard includes the TOGAF Enterprise Metamodel which captures the entities and relationships that are likely to be encountered in the majority of enterprises. This may be used as the basis for developing an Organization-Specific Metamodel when establishing the Enterprise Architecture Capability in the Preliminary Phase and also provides the context for the specific artifacts referenced in the descriptions of the ADM phases and described in detail in 3. Architectural Artifacts .

When developing an Organization-Specific Metamodel, architects may choose not to include entities and relationships from the TOGAF Enterprise Metamodel which are not relevant and/or add additional entities and relationships.

This section provides an overview of the TOGAF Enterprise Metamodel. Subsequent sections discuss each area of the metamodel in more detail.

2.2.1 Overview of the TOGAF Enterprise Metamodel

The TOGAF Enterprise Metamodel includes a set of entities, defined in 2.4 TOGAF Enterprise Metamodel Entities , that allow architectural concepts to be captured, stored, filtered, queried, and represented in a way that supports consistency, completeness, and traceability.

The categorization mechanism of the Content Framework may be used to structure a representation of the TOGAF Enterprise Metamodel, as shown in Figure 2-1 .

Figure 2-1: Using the Content Framework to Structure the TOGAF Enterprise Metamodel

2.3 TOGAF Enterprise Metamodel in Detail

The relationships between entities in the TOGAF Enterprise Metamodel are shown in Figure 2-2 .

Figure 2-2: Relationships between Entities in the TOGAF Enterprise Metamodel

2.4 TOGAF Enterprise Metamodel Entities

The following table lists and describes the entities within the Enterprise Metamodel.

Metamodel Entity	Description
Actor	A person, organization, or system that has a role that initiates or interacts with activities; for example, a sales representative who travels to visit customers. Actors may be internal or external to an organization. In the automotive industry, an original equipment manufacturer would be considered an actor by an automotive dealership that interacts with its supply chain activities.
Application Service	The automated elements of a business service. An application service may deliver or support part or all of one or more business services.
Assumption	A statement of probable fact that has not been fully validated at this stage, due to external constraints. For example, it may be assumed that an existing application will support a certain set of functional requirements, although those requirements may not yet have been individually validated.
Business Capability	A particular ability that a business may possess or exchange to achieve a particular purpose.
Business Information	Represents a concept and its semantics used within the business.
Business Service	Supports the business by encapsulating a unique element of business behavior; a service offered external to the enterprise may be supported by business services.
Capability	An ability that an organization, person, or system possesses. Note: This a general-purpose definition. See Business Capability for how this concept is refined for usage in Business Architecture.
Constraint	An external factor that prevents an organization from pursuing particular approaches to meet its goals. For example, customer data is not harmonized within the organization, regionally or nationally, constraining the organization's ability to offer effective customer service.
Contract	An agreement between a consumer and a provider that establishes functional and non-functional parameters for interaction. This applies to all types of service interactions within the metamodel.
Control	A decision-making step with accompanying decision logic used to determine execution approach for a process or to ensure that a process complies with governance criteria. For example, a sign-off control on the purchase request processing process that checks whether the total value of the request is within the sign-off limits of the requester, or whether it needs escalating to higher authority.
Course of Action	Direction and focus provided by strategic goals and objectives, often to deliver the value proposition characterized in the business model.
Data Entity	Represents data that is recognized by the business as a distinct concept.
Driver	An external or internal condition that motivates the organization to define its goals. An example of an external driver is a change in regulation or compliance rules which, for example, require changes to the way an organization operates; i.e., Sarbanes-Oxley in the US.
Event	An organizational state change that triggers processing events; may originate from inside or outside the organization and may be resolved inside or outside the organization.
Function	A set of business behaviors based on a chosen set of criteria. Functions are usually close-coupled to/with organizational units.
Gap	A statement of difference between two states. Used in the context of gap analysis, where the difference between the Baseline and Target Architecture is identified. Note: Gap analysis is described in the TOGAF Standard — ADM Techniques.
Goal	A high-level statement of intent or direction for an organization. Typically used to measure success of an organization.
Location	A place where activities occur. Locations can be composed and decomposed.
Logical Application Component	An encapsulation of application functionality that is definable by services offered and data maintained, independently of implementation and technology.
Logical Data Component	A data structure composed of logically-related data entities.
Logical Technology Component	An implementation-independent encapsulation of technology services.
Measure	An indicator or factor that can be tracked, usually on an ongoing basis, to determine success or alignment with objectives and goals.
Objective	An organizational aim that is declared in a Simple, Measurable, Actionable, Realistic, and Timebound (SMART) way. For example, "Increase capacity utilization by 30% by the end of the year, to support the planned increase in market share".
Organization Unit	A self-contained unit of resources with goals, objectives, and measures. Organization units may include external parties and business partner organizations.
Physical Application Component	A realization of logical application functionality using components of functionality in applications that may be hired, procured, or built.
Physical Data Component	A data structure that realizes related logical data components represented in the format or schema required by a particular technology.
Physical Technology Component	A realization of logical technology functionality using a particular technology product that may be deployed.
Principle	A qualitative statement of intent that should be met by the architecture. It has at least a supporting rationale and a measure of importance. Note: A sample set of Architecture Principles is defined in the TOGAF Standard — ADM Techniques.
Process	A process represents a sequence of activities that together achieve a specified outcome, can be decomposed into sub-processes, and can show operation of a business capability or service (at next level of detail). Processes may also be used to link organizations, business capabilities, services, and processes. A process may realize one service and/or orchestrate subordinate services.
Product	An outcome generated by the business to be offered to customers. Products include materials and/or services.
Requirement	A quantitative statement of business need that must be met by a particular architecture or work package.
Role	The usual or expected behavior of an actor, or the part somebody or something plays in a particular process or event. An actor may have a number of roles. See also Actor.
Service Quality	A configuration of non-functional requirements or attributes that may be assigned to a business, application, or technology service.
Technology Service	A technical capability required to provide enabling infrastructure that supports the delivery of applications.
Value Stream	A representation of an end-to-end collection of activities that create an overall result for a customer, stakeholder, or end-user.
Work Package	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.

2.5 TOGAF Enterprise Metamodel Attributes

The following table shows typical attributes for each of the metamodel entities described previously.

Metamodel Entity	Attribute	Description
All Metamodel Entities	ID	Unique identifier for the architecture entity.
	Name	Brief name of the architecture entity.
	Description	Textual description of the architecture entity.
	Category	User-definable categorization taxonomy for each metamodel entity.
	Source	Location from where the information was collected.
	Owner	Owner of the architecture entity.
Capability	Business value	Describes how this capability provides value to the enterprise.
	Increments	Lists possible maturity/quality levels for the capability.
Constraint	No additional attributes	This metamodel entity has only basic attributes.
Gap	No additional attributes	This metamodel entity has only basic attributes.
Location	Category	The following categories of Location apply: Region (applies to a grouping of countries or territory; e.g., South East Asia, UK, and Ireland), Country (applies to a single country; e.g., US), Building (applies to a site of operation; where several offices are collected in a single city, this category may represent a city), and Specific Location (applies to any specific location within a building, such as a server room). The nature of the business may introduce other Locations: Ship or Port for a ferry company, Mine for a gold company, Car for a police force, Hotel for any firm's traveling workers, and so on.
Principle	Category	The following categories of principle apply: Guiding Principle, Business Principle, Data Principle, Application Principle, Integration Principle, Technology Principle.
	Priority	Priority of this principle relative to other principles.
	Statement of principle	Statement of what the principle is.
	Rationale	Statement of why the principle is required and the desired outcome to be reached.
	Implication	Statement of what the principle means in practical terms.
	Metric	Identifies mechanisms that will be used to measure whether the principle has been met or not.
Requirement	Statement of requirement	Statement of what the requirement is, including a definition of whether the requirement shall be met, should be met, or may be met.
	Rationale	Statement of why the requirement exists.
	Acceptance criteria	The parameters that will be fulfilled if the requirement is being met, together with the tests that will be carried out to assess the state of the parameters.
Actor	# FTEs	Estimated number of FTEs that operate as this actor.
	Actor goal	Objectives that this actor has, in general terms.
	Actor tasks	Tasks that this actor performs, in general terms.
Business Service	Standards class	Non-Standard, Proposed Standard, Provisional Standard, Standard, Phasing-Out Standard, Retired Standard.
	Standard creation date	If the business service is a standard, when the standard was created.
	Last standard review date	Last date that the standard was reviewed.
	Next standard review date	Next date for the standard to be reviewed.
	Retire date	Date when the standard was/will be retired.
Contract	Behavior characteristics	Functional behavior to be supported within the scope of the contract.
	Service name "caller"	Consuming service.
	Service name "called"	Providing service.
	Service quality characteristics	Non-functional behavior to be supported within the scope of the contract.
	Availability characteristics	Degree to which something is available for use.
	Service times	Hours during which the service must be available.
	Manageability characteristics	Ability to gather information about the state of something and control it.
	Serviceability characteristics	Ability to identify problems and take corrective action, such as to repair or upgrade a component in a running system.
	Performance characteristics	Ability of a component to perform its tasks in an appropriate time.
	Response requirements	Response times that the service provider must meet for particular operations.
	Reliability characteristics	Resistance to failure.
	Quality of information required	Contracted requirements on accuracy and completeness of information.
	Contract control requirements	Level of governance and enforcement applied to the contractual parameters for overall service.
	Result control requirements	Measures in place to ensure that each service request meets contracted criteria.
	Recoverability characteristics	Ability to restore a system to a working state after an interruption.
	Locatability characteristics	Ability of a system to be found when needed.
	Security characteristics	Ability of a system to prevent unauthorized access to functions and data.
	Privacy characteristics	Protection of data from unauthorized access.
	Integrity characteristics	Ability of a system to ensure that data has not been corrupted.
	Credibility characteristics	Ability of a system to ensure that the service request originates from an authorized source.
	Localization characteristics	Ability of a service to support localized variants for different consumer groups.
	Internationalization characteristics	Ability of a service to support international variations in business logic and data representation (such as character set).
	Interoperability characteristics	Ability of the service to interoperate with different technical environments, inside and outside of the organization.
	Scalability characteristics	Ability of the service to grow or shrink its performance or capacity appropriately to the demands of the environment in which it operates.
	Portability characteristics	Of data, people, applications, and components.
	Extensibility characteristics	Ability to accept new functionality.
	Capacity characteristics	Contracted capacity of the service provider to meet requests.
	Throughput	Required throughput capacity.
	Throughput period	Time period needed to deliver throughput capacity.
	Growth	Expected future growth rate of service request.
	Growth period	Time period needed to reach the expected growth rate.
	Peak profile short term	Short-term profile of peak service traffic.
	Peak profile long term	Long-term profile of peak service traffic.
Control	No additional attributes	This metamodel entity has only basic attributes.
Driver	No additional attributes	This metamodel entity has only basic attributes.
Event	No additional attributes	This metamodel entity has only basic attributes.
Function	Standards class	Non-Standard, Proposed Standard, Provisional Standard, Standard, Phasing-Out Standard, Retired Standard.
	Standard creation date	If the product is a standard, when the standard was created.
	Last standard review date	Last date that the standard was reviewed.
	Next standard review date	Next date for the standard to be reviewed.
	Retire date	Date when the standard was/will be retired.
Goal	No additional attributes	This metamodel entity has only basic attributes.
Measure	No additional attributes	This metamodel entity has only basic attributes.
Objective	No additional attributes	This metamodel entity has only basic attributes.
Organization Unit	Headcount	Number of FTEs working within the organization.
Process	Standards class	Non-Standard, Proposed Standard, Provisional Standard, Standard, Phasing-Out Standard, Retired Standard.
	Standard creation date	If the product is a standard, when the standard was created.
	Last standard review date	Last date that the standard was reviewed.
	Next standard review date	Next date for the standard to be reviewed.
	Retire date	Date when the standard was/will be retired.
	Process criticality	Criticality of this process to business operations.
	Manual or automated	Whether this process is supported by IT or is a manual process.
	Process volumetrics	Data on frequency of process execution.
Product	No additional attributes	This metamodel entity has only basic attributes.
Role	Estimated number of FTEs that operate in this Role	This metamodel entity has only basic attributes.
Service Quality	No additional attributes	This metamodel entity has only basic attributes.
Service	Standards class	Non-Standard, Proposed Standard, Provisional Standard, Standard, Phasing-Out Standard, Retired Standard.
	Standard creation date	If the product is a standard, when the standard was created.
	Last standard review date	Last date that the standard was reviewed.
	Next standard review date	Next date for the standard to be reviewed.
	Retire date	Date when the standard was/will be retired.
Application Component	Standards class	Non-Standard, Proposed Standard, Provisional Standard, Standard, Phasing-Out Standard, Retired Standard.
	Standard creation date	If the product is a standard, when the standard was created.
	Last standard review date	Last date that the standard was reviewed.
	Next standard review date	Next date for the standard to be reviewed.
	Retire date	Date when the standard was/will be retired.
Application Service	Standards class	Non-Standard, Proposed Standard, Provisional Standard, Standard, Phasing-Out Standard, Retired Standard.
	Standard creation date	If the product is a standard, when the standard was created.
	Last standard review date	Last date that the standard was reviewed.
	Next standard review date	Next date for the standard to be reviewed.
	Retire date	Date when the standard was/will be retired.
Logical Application Component	Standards class	Non-Standard, Proposed Standard, Provisional Standard, Standard, Phasing-Out Standard, Retired Standard.
	Standard creation date	If the product is a standard, when the standard was created.
	Last standard review date	Last date that the standard was reviewed.
	Next standard review date	Next date for the standard to be reviewed.
	Retire date	Date when the standard was/will be retired.
Physical Application Component	Lifecycle status	Proposed, In Development, Live, Phasing Out, Retired.
	Standards class	Non-Standard, Proposed Standard, Provisional Standard, Standard, Phasing-Out Standard, Retired Standard.
	Standard creation date	If the product is a standard, when the standard was created.
	Last standard review date	Last date that the standard was reviewed.
	Next standard review date	Next date for the standard to be reviewed.
	Retire date	Date when the standard was/will be retired.
	Initial live date	Date when the first release of the application was/will be released into production.
	Date of last release	Date when the last release of the application was released into production.
	Date of next release	Date when the next release of the application will be released into production.
	Retirement date	Date when the application was/will be retired.
	Availability characteristics	Degree to which something is available for use.
	Service times	Hours during which the application must be available.
	Manageability characteristics	Ability to gather information about the state of something and control it.
	Serviceability characteristics	Ability to identify problems and take corrective action, such as to repair or upgrade a component in a running system.
	Performance characteristics	Ability of a component to perform its tasks in an appropriate time.
	Reliability characteristics	Resistance to failure.
	Recoverability characteristics	Ability to restore a system to a working state after an interruption.
	Locatability characteristics	Ability of a system to be found when needed.
	Security characteristics	Ability of a system to prevent unauthorized access to functions and data.
	Privacy characteristics	Protection of data from unauthorized access.
	Integrity characteristics	Ability of a system to ensure that data has not been corrupted.
	Credibility characteristics	Ability of a system to ensure that the service request originates from an authorized source.
	Localization characteristics	Ability of a service to support localized variants for different consumer groups.
	Internationalization characteristics	Ability of a service to support international variations in business logic and data representation (such as character set).
	Interoperability characteristics	Ability of the service to interoperate with different technical environments, inside and outside of the organization.
	Scalability characteristics	Ability of the service to grow or shrink its performance or capacity appropriately to the demands of the environment in which it operates.
	Portability characteristics	Of data, people, applications, and components.
	Extensibility characteristics	Ability to accept new functionality.
	Capacity characteristics	Contracted capacity of the service provider to meet requests.
	Throughput	Required throughput capacity.
	Throughput period	Time period needed to deliver throughput capacity.
	Growth	Expected future growth rate of service request.
	Growth period	Time period needed to reach the expected growth rate.
	Peak profile short term	Short-term profile of peak service traffic.
	Peak profile long term	Long-term profile of peak service traffic.
Data Entity	Category	The following categories of data entity apply: Message, Internally Stored Entity.
	Privacy classification	Level of restriction placed on access to the data.
	Retention classification	Level of retention to be placed on the data.
Logical Data Component	Standards class	Non-Standard, Proposed Standard, Provisional Standard, Standard, Phasing-Out Standard, Retired Standard.
	Standard creation date	If the product is a standard, when the standard was created.
	Last standard review date	Last date that the standard was reviewed.
	Next standard review date	Next date for the standard to be reviewed.
	Retire date	Date when the standard was/will be retired.
Physical Data Component	Standards class	Non-Standard, Proposed Standard, Provisional Standard, Standard, Phasing-Out Standard, Retired Standard.
	Standard creation date	If the product is a standard, when the standard was created.
	Last standard review date	Last date that the standard was reviewed.
	Next standard review date	Next date for the standard to be reviewed.
	Retire date	Date when the standard was/will be retired.
Logical Technology Component	Standards class	Non-Standard, Proposed Standard, Provisional Standard, Standard, Phasing-Out Standard, Retired Standard.
	Standard creation date	If the product is a standard, when the standard was created.
	Last standard review date	Last date that the standard was reviewed.
	Next standard review date	Next date for the standard to be reviewed.
	Retire date	Date when the standard was/will be retired.
	Category	Logical Technology Components are categorized according to the defined taxonomy (such as the TOGAF Technical Reference Model (TRM)), adapted to meet the needs of an individual organization.
Physical Technology Component	Standards class	Non-Standard, Proposed Standard, Provisional Standard, Standard, Phasing-Out Standard, Retired Standard.
	Standard creation date	If the product is a standard, when the standard was created.
	Last standard review date	Last date that the standard was reviewed.
	Next standard review date	Next date for the standard to be reviewed.
	Retire date	Date when the standard was/will be retired.
	Category	Physical Technology Components are categorized according to the defined taxonomy (such as the TOGAF TRM), adapted to meet the needs of an individual organization.
	Product name	Name of the product making up the technology component.
	Module name	Module, or other sub-product, name making up the technology component.
	Vendor	Vendor providing the technology component.
	Version	Version of the product making up the technology component.
Technology Service	Standards class	Non-Standard, Proposed Standard, Provisional Standard, Standard, Phasing-Out Standard, Retired Standard.
	Category	Technology Services are categorized according to the defined taxonomy (such as the TOGAF TRM), adapted to meet the needs of an individual organization.
Business Capability	No additional attributes	This metamodel entity has only basic attributes.
Technology Component	Standards class	Non-Standard, Proposed Standard, Provisional Standard, Standard, Phasing-Out Standard, Retired Standard.
Course of Action	No additional attributes	This metamodel entity has only basic attributes.
Value Stream	No additional attributes	This metamodel entity has only basic attributes.
Work Package	Category	The following categories of work package apply: Work Package, Work Stream, Project, Program, Portfolio.
	Capability delivered	Describes the contribution this work package makes to capability delivery.

2.6 TOGAF Enterprise Metamodel Relationships

Source Entity	Target Entity	Name
Actor	Actor	Decomposes
Actor	Business Service	Consumes
Actor	Data Entity	Supplies or consumes
Actor	Event	Generates
Actor	Event	Resolves
Actor	Function	Interacts with
Actor	Function	Performs
Actor	Organization Unit	Belongs to
Actor	Process	Participates in
Actor	Process	Triggers
Actor	Role	Performs task in
Actor	Value Stream	Performs a task in
Application Service	Business Service	Automates some or all of
Application Service	Data Entity	Used by
Application Service	Logical Application Component	Is realized through
Application Service	Technology Service	Is served by
Business Capability	Business Information	Uses
Business Capability	Course of Action	Is influenced by
Business Capability	Function	Is delivered by
Business Capability	Organization Unit	Is used by
Business Capability	Process	Is operationalized by
Business Capability	Value Stream	Enables
Business Information	Business Capability	Is used by
Business Information	Business Service	Used to derive
Business Information	Course of Action	Is influenced by
Business Information	Data Entity	Is realized by
Business Information	Process	Uses
Business Service	Actor	Is provided to
Business Service	Application Service	Uses
Business Service	Business Information	Is derived from
Business Service	Business Service Quality	Meets
Business Service	Business Service	Consumes
Business Service	Business Service	Decomposes
Business Service	Contract	Is governed and measured by
Business Service	Data Entity	Is accessed and updated through
Business Service	Event	Resolves
Business Service	Function	Provides governed interface to access
Business Service	Logical Technology Component	Is implemented on
Business Service	Organization Unit	Is owned and governed by
Business Service	Process	Is realized by
Business Service	Process	Supports
Capability	Work Package	Is delivered by
Contract	Business Service	Governs, measures
Contract	Service Quality	Meets
Control	Process	Ensures correct operation of
Course of Action	Business Capability	Influences
Course of Action	Business Information	Influences
Course of Action	Function	Influences
Course of Action	Goal	Realizes
Course of Action	Organization Unit	Influences
Course of Action	Product	Influences
Course of Action	Value Stream	Influences
Data Entity	Actor	Is supplied or consumed by
Data Entity	Application Service	Used by
Data Entity	Business Information	Realizes
Data Entity	Business Service	Is accessed and updated through
Data Entity	Data Entity	Decomposes
Data Entity	Data Entity	Relates to
Data Entity	Logical Data Component	Resides within
Driver	Driver	Decomposes
Driver	Goal	Creates
Driver	Organization Unit	Motivates
Event	Actor	Is generated by
Event	Actor	Is resolved by
Event	Business Service	Is resolved by
Event	Process	Is generated by
Event	Process	Is resolved by
Function	Actor	Supports
Function	Business Capability	Delivers
Function	Business Service	Is bounded by
Function	Course of Action	Is influenced by
Function	Function	Communicates with
Function	Function	Decomposes
Function	Organization Unit	Is owned by
Function	Process	Orchestrates
Function	Process	Decomposes
Goal	Course of Action	Is realized by
Goal	Driver	Addresses
Goal	Goal	Decomposes
Goal	Objective	Is made specific
Logical Application Component	Application Service	Implements
Logical Application Component	Logical Application Component	Decomposes
Logical Application Component	Logical Application Component	Communicates with
Logical Application Component	Logical Data Component	Used by
Logical Application Component	Logical Technology Component	Is served by
Logical Application Component	Physical Application Component	Is realized by
Logical Data Component	Data Entity	Encapsulates
Logical Data Component	Logical Application Component	Uses
Logical Data Component	Physical Data Component	Is realized by
Logical Technology Component	Business Service	Provides platform for
Logical Technology Component	Logical Application Component	Serves
Logical Technology Component	Logical Technology Component	Decomposes
Logical Technology Component	Logical Technology Component	Is dependent on
Logical Technology Component	Physical Technology Component	Is realized by
Logical Technology Component	Technology Service	Supplies
Measure	Measure	Decomposes
Measure	Objective	Sets performance criteria for
Objective	Goal	Realizes
Objective	Measure	Is tracked against
Objective	Objective	Decomposes
Organization Unit	Actor	Contains
Organization Unit	Business Capability	Delivers
Organization Unit	Business Service	Owns and governs
Organization Unit	Course of Action	Participates in
Organization Unit	Driver	Is motivated by
Organization Unit	Function	Enables
Organization Unit	Organization Unit	Decomposes
Organization Unit	Product	Delivers
Physical Application Component	Logical Application Component	Realizes
Physical Application Component	Physical Application Component	Decomposes
Physical Application Component	Physical Application Component	Communicates with
Physical Application Component	Physical Data Component	Used by
Physical Application Component	Physical Technology Component	Is served by
Physical Data Component	Logical Data Component	Realizes
Physical Data Component	Physical Application Component	Used by
Physical Data Component	Physical Data Component	Decomposes
Physical Technology Component	Logical Technology Component	Realizes
Physical Technology Component	Physical Application Component	Serves
Physical Technology Component	Physical Technology Component	Decomposes
Physical Technology Component	Physical Technology Component	Is dependent on
Process	Actor	Is produced by
Process	Actor	Supports
Process	Business Capability	Operationalizes
Process	Business Information	Is used by
Process	Business Service	Orchestrates
Process	Business Service	Decomposes
Process	Control	Is guided by
Process	Event	Generates
Process	Event	Resolves
Process	Function	Supports
Process	Function	Is realized by
Process	Process	Decomposes
Process	Process	Precedes, follows
Process	Product	Delivers
Process	Role	Involves
Process	Role	Is performed by
Process	Value Stream	Operationalizes
Product	Course of Action	Is produced by
Product	Organization Unit	Is produced by
Product	Process	Is produced by
Role	Actor	Is performed by
Role	Process	Participates in
Role	Process	Performs
Role	Role	Decomposes
Service Quality	Contract	Applies to
Service Quality	Service	Applies to
Technology Service	Application Service	Serves
Technology Service	Logical Technology Component	Is supplied by
Value Stream	Actor	Involves
Value Stream	Actor	Is triggered by
Value Stream	Business Capability	Is enabled by
Value Stream	Course of Action	Is influenced by
Value Stream	Process	Is operationalized by
Work Package	Capability	Delivers

return to top of page

<<< Previous

Home

Next >>>

Search