Glossary A.6.

Application Component
An encapsulation of application functionality aligned to implementation
A.1. Abstraction structure. For example, a purchase request processing application. See
The technique of providing summarized or generalized descriptions of also Section A.50 and Section A.64.
detailed and complex content. Abstraction, as in ‘‘level of
abstraction’’, can also mean providing a focus for analysis that is A.7. Application Software
concerned with a consistent and common level of detail or abstraction. Software entities which have a specific business purpose.
Abstraction in this sense is typically used in architecture to allow a
consistent level of definition and understanding to be achieved in each A.8. Availability
area of the architecture in order to support effective communication In the context of IT systems, the probability that system functional
and decision-making. It is especially useful when dealing with large and capabilities are ready for use by a user at any time, where all time is
complex architectures as it allows relevant issues to be identified considered, including operations, repair, administration, and logistic
before further detail is attempted. time. Availability is further defined by system category for both routine
and priority operations.
A.2. Access Control (AC)
A security service that ensures only those users with the correct rights A.9. Application
can access a specific device, application, or data. A deployed and operational IT system that supports business functions
and services; for example, a payroll. Applications use data and are
A.3. Activity supported by multiple technology components but are distinct from the
A task or collection of tasks that support the functions of an technology components that support the application.
organization. For example, a user entering data into an IT system or
traveling to visit customers. A.10. Application Architecture
A description of the major logical grouping of capabilities that manage
A.4. Actor the data objects necessary to process the data and support the
A person, organization, or system that has a role that initiates or business.
interacts with activities; for example, a sales representative who Note: Application Architecture is described in Par t II, Chapter 11.
travels to visit customers. Actors may be internal or external to an
organization. In the automotive industry, an original equipment A.11. Application Platform
manufacturer would be considered an actor by an automotive The collection of technology components of hardware and software
dealership that interacts with its supply chain activities. that provide the services used to support applications.

A.5. Ada A.12. 12 Application Platform Interface (API)

A high-level computer programming language developed by the US The interface, or set of functions, between application software and/or
Department of Defense (DoD) and widely used within the DoD and NATO the application platform.
countries. It is used for real-time processing, is modular in nature, and
includes object-oriented features. A.13. Architectural Style
The combination of distinctive features in which architecture is
performed or expressed.

Glossary and Definitions Page 1

A.14. Architecture A.20. Architecture Governance
1. A formal description of a system, or a detailed plan of the system at The practice and orientation by which enterprise architectures and
component level, to guide its implementation (source: ISO/IEC 42010: other architectures are managed and controlled at an enterprise-wide
2007). level. It is concerned with change processes (design governance) and
2. The structure of components, their inter-relationships, and the operation of product systems (operational governance). See also
principles and guidelines governing their design and evolution over Section 3.45.
time.
A.21. Architecture Landscape
A.15. Architecture Building Block (ABB) The architectural representation of assets deployed within the
A constituent of the architecture model that describes a single aspect operating enterprise at a particular point in time. The views are
of the overall model. See also Section 3.24. segmented into strategic, segment, and capability levels of abstraction
to meet diverse stakeholder needs.
A.16. Architecture Continuum
A par t of the Enterprise Continuum. A repository of architectural A.22. Architecture Principles
elements with increasing detail and specialization. This Continuum A qualitative statement of intent that should be met by the
begins with foundational definitions like reference models, core architecture. Has at least a supporting rationale and a measure of
strategies, and basic building blocks. From there it spans to Industry importance. Note: A sample set of architecture principles is defined in
Architectures and all the way to an organization’s specific architecture. Part III, Chapter 23.
See also Section 3.39.
A.23. Architecture Vision
A.17. Architecture Development Method (ADM) 1. A high-level, aspirational view of the Target Architecture.
The core of TOGAF. A step-by-step approach to develop and use an 2. A phase in the ADM which delivers understanding and definition
enterprise architecture. of the Architecture Vision.
Note: The ADM is described in Par t II: Architecture Development 3. A specific deliverable describing the Architecture Vision.
Method (ADM).
Note: Phase A (Architecture Vision) is described in Part II, Chapter 7.
A.18. Architecture Domain
A.24. Artifact
The architectural area being considered. There are four architecture
An architectural work product that describes an architecture from a
domains within TOGAF: business, data, application, and technology.
specific viewpoint. Examples include a network diagram, a server
specification, a use-case specification, a list of architectural
A.19. Architecture Framework
requirements, and a business interaction matrix. Artifacts are generally
A foundational structure, or set of structures, which can be used for
classified as catalogs (lists of things), matrices (showing relationships
developing a broad range of different architectures. It should contain a
between things), and diagrams (pictures of things). An architectural
method for designing an information system in terms of a set of
deliverable may contain multiple artifacts and artifacts will form the
building blocks, and for showing how the building blocks fit together. It
content of the Architecture Repository.
should contain a set of tools and provide a common vocabulary. It
See also Section 3.24.
should also include a list of recommended standards and compliant
products that can be used to implement the building blocks.

Glossary and Definitions Page 2

A.25. Baseline defined at various levels of detail, depending on what stage of
A specification that has been formally reviewed and agreed upon, that architecture development has been reached. For instance, at an early
thereafter serves as the basis for further development or change and stage, a building block can simply consist of a name or an outline
that can be changed only through formal change control procedures or description. Later on, a building block may be decomposed into
a type of procedure such as configuration management. multiple supporting building blocks and may be accompanied by a full
specification. Building blocks can relate to ‘‘architectures’’ or
A.26. Baseline Architecture ‘‘solutions’’. See also Section 3.20.
The existing defined system architecture before entering a cycle of
architecture review and redesign. Note: Building blocks are described in Part IV, Chapter 37.

A.27. Batch Processing A.31. Business Architecture

Processing data or the accomplishment of jobs accumulated in advance The business strategy, governance, organization, and key business
in such a manner that each accumulation thus formed is processed or processes information, as well as the interaction between these
accomplished in the same computer run. concepts.
Note: Business Architecture is described in Par t II, Chapter 8.
A.28. Business System
Hardware, software, policy statements, processes, activities, A.32. Business Domain
standards, and people which together implement a business function. A grouping of coherent business functions and activities (in the context
of a business sector) over which meaningful responsibility can be taken.
A.29. Boundaryless Information Flow For example, Finance, Human Resources (HR), Automobile
1. A trademark of The Open Group. Manufacturing, Retail, etc. The phrase is often used to identify specific
2. A shorthand representation of ‘‘access to integrated business knowledge (a business domain expert).
information to support business process improvements’’
representing a desired state of an enterprise’s infrastructure A.33. Business Function
specific to the business needs of the organization. Delivers business capabilities closely aligned to an organization, but not
An infrastructure that provides Boundaryless Information Flow has open necessarily explicitly governed by the organization.
standard components that provide services in a customer’s extended
enterprise that: A.34. Business Governance
• Combine multiple sources of information Concerned with ensuring that the business processes and policies (and
• Securely deliver the information whenever and wherever it is their operation) deliver the business outcomes and adhere to relevant
needed, in the right context for the people or systems using business regulation.
that information.
Note: The need for Boundaryless Information Flow is described in Part A.35. Business Service
VI, Chapter 44. Supports business capabilities through an explicitly defined interface
and is explicitly governed by an organization.
A.30. Building Block
Represents a (potentially re-usable) component of business, IT, or A.36. Capability
architectural capability that can be combined with other building An ability that an organization, person, or system possesses.
blocks to deliver architectures and solutions. Building blocks can be Capabilities are typically expressed in general and high-level terms and
typically require a combination of organization, people, processes, and

Glossary and Definitions Page 3

technology to achieve. For example, marketing, customer contact, or operation, including considerations such as performance, reliability,
outbound telemarketing. security, distribution, and evolvability.
See also Section 3.80.
A.37. Capability Architecture
A highly detailed description of the architectural approach to realize a A.45. Constraint
particular solution or solution aspect. An external factor that prevents an organization from pursuing
particular approaches to meet its goals. For example, customer data is
A.38. Capability Increment not harmonized within the organization, regionally or nationally,
The output from a business change initiative that delivers an increase constraining the organization’s ability to offer effective customer
in performance for a particular capability of the enterprise. service.

A.39. Catalog A.46. Communications System

A structured list of architectural outputs of a similar kind, used for A set of assets (transmission media, switching nodes, interfaces, and
reference. For example, a technology standards catalog or an control devices) that will establish linkage between users and devices.
application portfolio.
A.47. Composite Application
A.40. Client An application component that is created by composing other atomic or
An application component which requests services from a server. composite applications.

A.41. COBIT A.48. Configuration Management

An acronym for Control OBjectives for Information and related A discipline applying technical and administrative direction and
Technology, created by the Information Systems Audit and Control surveillance to:
Association (ISACA) and the IT Governance Institute (ITGI), which • Identify and document the functional and physical
provides a set of recommended best practices for the characteristics of a configuration item
governance/management of information systems and technology. • Control changes to those characteristics
• Record and report changes to processing and implementation
A.42. Communications Network status
A set of products, concepts, and services that enable the connection of Also, the management of the configuration of enterprise architecture
computer systems for the purpose of transmitting data and other for ms practice (intellectual property) assets and baselines and the control of
(e.g., voice and video) between the systems. change over of those assets.

A.43. Communications Node A.49. Connectivity Service

A node that is either internal to the communications network (e.g., A ser vice area of the external environment entity of the Technical
routers, bridges, or repeaters) or located between the end device and Reference Model (TRM) that provides end-to-end connectivity for
the communications network to operate as a gateway. communications through three transport levels (global, regional, and
local). It provides general and application-specific services to platform
A.44. Concerns end devices.
The key interests that are crucially important to the stakeholders in a
system, and determine the acceptability of the system. Concerns may
pertain to any aspect of the system’s functioning, development, or

Glossary and Definitions Page 4

A.50. Contract A.57. Data Interchange Service
An agreement between a service consumer and a service provider that A service of the platform entity of the Technical Reference Model
establishes functional and non-functional parameters for interaction. (TRM) that provides specialized support for the interchange of data
between applications on the same or different platforms.
A.51. Control
A decision-making step with accompanying decision logic used to A.58. Data Management Service
determine execution approach for a process or to ensure that a process A ser vice of the platform entity of the Technical Reference Model
complies with governance criteria. For example, a signoff control on (TRM) that provides support for the management, storage, access, and
the purchase request processing process that checks whether the total manipulation of data in a database.
value of the request is within the sign-off limits of the requester, or
whether it needs escalating to higher authority. A.59. Database
A structured or organized collection of data entities, which is be
A.52. CxO accessed by a computer
The chief officer within a particular function of the business; e.g.,
Chief Executive Officer, Chief Financial Officer, Chief Information A.60. Database Management System
Officer, Chief Technology Officer. A computer application program that accesses or manipulates the
database.
A.53. Data Dictionary
A specialized type of database containing metadata; a repository of A.61. Directory Service
information describing the characteristics of data used to design, A technology component that provides locator services that find the
monitor, document, protect, and control data in information systems location of a service, or the location of data, or translation of a
and databases; an application system supporting the definition and common name into a network-specific address. It is analogous to
management of database metadata. telephone books and may be implemented in centralized or distributed
schemes.
A.54. Data Element
A basic unit of information having a meaning and that may have A.62. Distributed Database
subcategories (data items) of distinct units and values. 1. A database that is not stored in a central location but is dispersed
over a network of interconnected computers.
A.55. Data Entity 2. A database under the overall control of a central Database
An encapsulation of data that is recognized by a business domain Management System (DBMS) but whose storage devices are not all
expert as a thing. Logical data entities can be tied to applications, attached to the same processor.
repositories, and services and may be structured according to 3. A database that is physically located in two or more distinct
implementation considerations. locations.

A.56. Data Architecture A.63. Driver

The structure of an organization’s logical and physical data assets and An external or internal condition that motivates the organization to
data management resources. define its goals. An example of an external driver is a change in
regulation or compliance rules which, for example, require changes to
Note: Data Architecture is described in Part II, Chapter 10.
the way an organization operates; i.e., Sarbanes-Oxley in the US.

Glossary and Definitions Page 5

A.64. End User A.72. FORTRAN
Person who ultimately uses the computer application or output. An acronym for FORmula TRANslator, which is a high-level computer
language used extensively in scientific and engineering applications.
A.65. Enterprise
The highest level (typically) of description of an organization and A.73. Functional Decomposition
typically covers all missions and functions. An enterprise will often A hierarchy of the functions of an enterprise or organization.
span multiple organizations.
A.74. Foundation Architecture
A.66. Enterprise Continuum An architecture of generic services and functions that provides a
A categorization mechanism useful for classifying architecture and foundation on which more specific architectures and architectural
solution artifacts, both internal and external to the Architecture components can be built. The TOGAF Foundation Architecture includes
Repository, as they evolve from generic Foundation Architectures to a Technical Reference Model (TRM).
Organization-Specific Architectures.
See also Section 3.11 and Section 3.79. A.75. Framework
A structure for content or process that can be used as a tool to
A.67. Enterprise Resource Planning (ERP) System structure thinking, ensuring consistency and completeness.
A complete suite of integrated applications that support the major
business support functions of an organization; e.g., Financial A.76. Gap
(AP/AR/GL), HR, Payroll, Stock, Order Processing and Invoicing, A statement of difference between two states. Used in the context of
Purchasing, Logistics, Manufacturing, etc. gap analysis, where the difference between the Baseline and Target
Architecture is identified.
A.68. Environment Management Note: Gap analysis is described in Part III, Chapter 27.
The provision and management of the environment required to support
the operations of the enterprise architecture practice, including A.77. Governance
facilities, equipment, tools, and information systems. The discipline of monitoring, managing, and steering a business (or
IS/IT landscape) to deliver the business outcome required.
A.69. Event See also Section 3.15, Section 3.28, and Section A.60 in Appendix A.
An organizational state change that triggers processing events may
originate from inside or outside the organization and may be resolved A.78. Goal
inside or outside the organization. A high-level statement of intent or direction for an organization.
Typically used to measure success of an organization.
A.70. External Environment Interface (EEI)
The interface that supports information transfer between the A.79. Guideline
application platform and the external environment. An architectural document that provides guidance on the optimal ways
to carry out design or implementation activities.
A.71. Financial Management
The management of the financial aspects of the enterprise architecture A.80. Hardware
practice; e.g., budgeting and forecasting. The physical infrastructure needed to run software; e.g., servers,
workstations, network equipment, etc.

Glossary and Definitions Page 6

A.81. Human Computer Interface (HCI) A.88. Interaction Model
Hardware and software allowing information exchange between the An architectural view, catalog, or matrix that shows a particular type
user and the computer. of interaction. For example, a diagram showing application integration.

A.82. Information A.89. Interface

Any communication or representation of facts, data, or opinions, in any Interconnection and inter-relationships between, for example, people,
medium or form, Including textual, numerical, graphic, cartographic, systems, devices, applications, or the user and an application or
narrative, or audio-visual forms. device.

A.83. Information Domain A.90. Interoperability

Grouping of information (or data entities) by a set of criteria such as 1. The ability to share information and services.
security classification, ownership, location, etc. In the context of 2. The ability of two or more systems or components to exchange and
security, information domains are defined as a set of users, their use information.
information objects, and a security policy. 3. The ability of systems to provide and receive ser vices from other
systems and to use the services so interchanged to enable them to
A.84. Information System (IS) operate effectively together.
The computer (or IT)-based portion of a business system.
A.91. ITIL
A.85. Information Technology (IT) An acronym for Information Technology Infrastructure Library, which
1. The lifecycle management of information and related provides a set of recommended best practices for the
technology used by an organization. governance/management of information systems and technology.
2. An umbrella term that includes all or some of the subject areas
relating to the computer industry, such as Business Continuity, A.92. Key Performance Indicator (KPI)
Business IT Interface, Business Process Modeling and A way of quantifying the performance of the business or project.
Management, Communication, Compliance and Legislation,
Computers, Content Management, Hardware, Information A.93. Knowledge
Management, Internet, Offshoring, Networking, Programming The awareness and understanding of facts, truths, or information
and Software, Professional Issues, Project Management, gained in the form of experience or learning (a posteriori), or through
Security, Standards, Storage, Voice and Data Communications. introspection (a priori). Knowledge is an appreciation of the possession
Various countries and industries employ other umbrella terms of interconnected details which, in isolation, are of lesser value.
to describe this same collection.
A.94. Lifecycle
A.86. Information System Service The period of time that begins when a system is conceived and ends
The automated elements of a business service. An information system when the system is no longer available for use.
service may deliver or support part or all of one or more business
services. A.95. Logical
An implementation-independent definition of the architecture, often
A.87. Interaction grouping related physical entities according to their purpose and
A relationship between architectural building blocks (i.e., services or structure. For example, the products from multiple infrastructure
components) that embodies communication or usage.

Glossary and Definitions Page 7

software vendors can all be logically grouped as Java application server A.104. Method
platforms. A defined, repeatable approach to address a particular type of
problem.
A.96. Location See also Section 3.54.
A place where business activity takes place and can be hierarchically
decomposed. A.105. Methodology
A defined, repeatable series of steps to address a particular type of
A.97. Logical Application Component problem, which typically centers on a defined process, but may also
An encapsulation of application functionality that is independent of a include definition of content. See also Section 3.53.
particular implementation. For example, the classification of all
purchase request processing applications implemented in an enterprise. A.106. Measure
An indicator or factor that can be tracked, usually on an ongoing basis,
A.98. Logical Data Component to determine success or alignment with objectives and goals.
A boundary zone that encapsulates related data entities to for m a
logical location to be held. For example, external procurement A.107. Metaview
information. A metaview acts as a pattern or template of the view, from which to
develop individual views. A metaview establishes the purposes and
A.99. Logical Technology Component audience for a view, the ways in which the view is documented (e.g.,
An encapsulation of technology infrastructure that is independent of a for visual modeling), and the ways in which it is used (e.g., for
particular product. A class of technology product. For example, supply analysis). See also Section 3.89 in Chapter 3.
chain management software as part of an Enterprise Resource Planning
(ERP) suite or a Commercial Off-The-Shelf (COTS) purchase request A.108. Model
processing enterprise service. A representation of a subject of interest. A model provides a smaller
scale, simplified, and/or abstract representation of the subject matter.
A.100. Managing Successful Programs (MSP) A model is constructed as a ‘‘means to an end’’. In the context of
A best practice methodology for program management, developed by enterprise architecture, the subject matter is a whole or part of the
the UK Office of Government Commerce (OGC). enterprise and the end is the ability to construct ‘‘views’’ that address
the concerns of particular stakeholders; i.e., their ‘‘viewpoints’’ in
A.101. Matrix relation to the subject matter. See also Section 3.80, Section 3.88, and
A format for showing the relationship between two (or more) Section 3.89.
architectural elements in a grid format.
A.109. Modeling
A.102. Metadata A technique through construction of models which enables a subject to
Data about data, of any sort in any media, that describes the be represented in a form that enables reasoning, insight, and clarity
characteristics of an entity. concerning the essence of the subject matter.
A.110. Multimedia Service
A.103. Metamodel A ser vice of the Technical Reference Model (TRM) that provides the
A model that describes how and with what the architecture will be capability to manipulate and manage information products consisting of
described in a structured way. text, graphics, images, video, and audio.

Glossary and Definitions Page 8

A.111. Objective A.117. Packaged Services
A time-bounded milestone for an organization used to demonstrate Services that are acquired from the market from a Commercial Off-
progress towards a goal; for example, ‘‘Increase Capacity Utilization by The-Shelf (COTS) vendor, rather than being constructed via code build.
30% by the end of 2009 to support the planned increase in market
share’’. A.118. Patterns
A technique for putting building blocks into context; for example, to
A.112. Open Specifications describe a re-usable solution to a problem. Building blocks are what
Public specifications that are maintained by an open, public consensus you use: patterns can tell you how you use them, when, why, and what
process to accommodate new technologies over time and that are trade-offs you have to make in doing so. See also Section 3.24.
consistent with international standards.
A.119. Performance Management
A.113. Open System The monitoring, control, and reporting of the enterprise architecture
A system that implements sufficient open specifications for interfaces, practice performance. Also concerned with continuous improvement.
services, and supporting formats to enable properly engineered
application software: A.120. Physical
• To be ported with minimal changes across a wide range of A description of a real-world entity. Physical elements in an enterprise
systems architecture may still be considerably abstracted from Solution
• To interoperate with other applications on local and remote Architecture, design, or implementation views.
systems
• To interact with users in a style that facilitates user portability A.121. Physical Application Component
An application, application module, application service, or other
A.114. Operational Governance deployable component of functionality. For example, a configured and
Operational governance looks at the operational performance of deployed instance of a Commercial Off-The-Shelf (COTS) Enterprise
systems against contracted performance levels, the definition of Resource Planning (ERP) supply chain management application.
operational performance levels, and the implementation of systems
that ensure effective operation of systems. See also Section 3.45 in
Chapter 3. A.122. Physical Data Component
A boundary zone that encapsulates related data entities to for m a
A.115. Operating System Service physical location to be held. For example, a purchase order business
A core service of the application platform entity of the Technical object, comprising purchase order header and item business object
Reference Model (TRM) that is needed to operate and administer the nodes.
application platform and provide an interface between the application
software and the platform (for example, file management, A.123. Physical Technology Component
input/output, print spoolers). A specific technology infrastructure product or technology
infrastructure product instance. For example, a particular product
A.116. Organization version of a Commercial Off-The-Shelf (COTS) solution, or a specific
A self-contained unit of resources with line management responsibility, brand and version of server.
goals, objectives, and measures. Organizations may include external
par ties and business partner organizations. A.124. Platform

Glossary and Definitions Page 9

A combination of technology infrastructure products and components A.131. Profile
that provides that prerequisites to host application software. A set of one or more base standards and, where applicable, the
identification of those classes, subsets, options, and parameters of
A.125. Platform Services those base standards, necessary for accomplishing a particular
A technical capability required to provide enabling infrastructure that function.
supports the delivery of applications.
A.132. Profiling
A.126. Portability Identifying standards and characteristics of a particular system.
1. The ease with which a system or component can be transferred
from one hardware or software environment to another.
2. A quality metric that can be used to measure the relative effort A.133. Program
to transport the software for use in another environment or to A coordinated set of change projects that deliver business benefit to
convert software for use in another operating environment, the organization.
hardware configuration, or software system environment.
3. The ease with which a system, component, data, or user can be A.134. Project
transferred from one hardware or software environment to A single change project which delivers business benefit to the
another. organization.

A.127. Portfolio A.135. Quality Management

The complete set of change activities or systems that exist within the The management of the quality aspects of the enterprise architecture
organization or part of the organization. For example, application practice; e.g., management plans, quality criteria, review processes.
portfolio and project portfolio.
A.136. Reference Model (RM)
A.128. PRINCE2 A reference model is an abstract framework for understanding
An acronym for PRojects IN Controlled Environments, which is a significant relationships among the entities of [an] environment, and
standard project management method. for the development of consistent standards or specifications
supporting that environment. A reference model is based on a small
A.129. Process number of unifying concepts and may be used as a basis for education
A process represents a sequence of activities that together achieve a and explaining standards to a non-specialist. A reference model is not
specified outcome, can be decomposed into sub-processes, and can directly tied to any standards, technologies, or other concrete
show operation of a function or service (at next level of detail). implementation details, but it does seek to provide common semantics
Processes may also be used to link or compose organizations, functions, that can be used unambiguously across and between different
services, and processes. implementations.
Note: The source of this definition is OASIS; refer to http://docs.oasis-
A.130. Product
open.org/soa-rm/v1.0/soa-rm.html
Output generated by the business. The business product of the
execution of a process.
A.137. Repository
A system that manages all of the data of an enterprise, including data
and process models and other enterprise information. Hence, the data

Glossary and Definitions Page 10

in a repository is much more extensive than that in a data dictionary, A.144. Security
which generally defines only the data making up a database. Services which protect data, ensuring its confidentiality, availability,
and integrity.
A.138. Requirement
A quantitative statement of business need that must be met by a A.145. Server
particular architecture or work package. An application component which responds to requests from a client.

A.139. Resource Management A.146. Service

The acquisition, development, and management of human resources A logical representation of a repeatable business activity that has a
within the enterprise architecture practice in response to demand for specified outcome. A service is self-contained, may be composed of
enterprise architecture services and financial constraints. other services, and is a ‘‘black box’’ to its consumers. Examples are
Note: The Architecture Skills Framework is described in Part VII, ‘‘check customer credit’’, ‘‘provide weather data’’, and ‘‘consolidate
Chapter 52. drilling reports’’.

A.140. Risk Management A.147. Service Quality

The management of risks and issues that may threaten the success of A preset configuration of non-functional attributes that may be
the enterprise architecture practice and its ability to meet is vision, assigned to a service or service contract.
goals, and objectives, and, importantly, its service provision. Note:
Risk management is described in Part III, Chapter 31. A.148. SMART
An acronym for Specific, Measurable, Attainable, Realistic, and Time-
A.141. Roadmap bound, which is an approach to ensure that targets and objectives are
An abstracted plan for business or technology change, typically set in a way that can be achieved and measured.
operating across multiple disciplines over multiple years. Normally used
in the phrases Technology Roadmap, Architecture Roadmap, etc. A.149. Supplier Management
The management of suppliers of products and services to the enterprise
A.142. Role architecture practice in concert with larger corporate procurement
1. The usual or expected function of an actor, or the part somebody or activities.
something plays in a particular action or event. An Actor may have a
number of roles. A.150. System
2. The part an individual plays in an organization and the contribution A collection of components organized to accomplish a specific function
they make through the application of their skills, knowledge, or set of functions (source: ISO/IEC 42010: 2007).
experience, and abilities. See also Section 3.3.
A.151. System and Network Management Service
A.143. Scalability A cross-category service of the application platform entity of the
The ability to use the same application software on many different Technical Reference Model (TRM) that provides for the administration
classes of hardware/software platforms from PCs to super-computers of the overall information system. These services include the
(extends the portability concept). The capability to grow to management of information, processors, networks, configurations,
accommodate increased work loads. accounting, and
performance.

Glossary and Definitions Page 11

A.152. System Stakeholder A.161. Service Management
An individual, team, or organization (or classes thereof) with interests The management of the execution and performance of the enterprise
in, or concerns relative to, a system (source: ISO/IEC 42010: 2007). architecture practice services. This includes managing the ‘‘pipeline’’
plus current service portfolio.
A.153. Technology Component
An encapsulation of technology infrastructure that represents a class of A.162. Service Orientation
technology product or specific technology product. A way of thinking in terms of services and service-based development
and the outcomes of services.
A.154. Time Period See also Section 3.75.
The timeframe over which the potential impact is to be measured.
A.163. Service Oriented Architecture (SOA)
A.155. Transaction An architectural style that supports service orientation. It has the
Interaction between a user and a computer in which the user inputs a following distinctive features:
command to receive a specific result from the computer. • It is based on the design of the services — which mirror real-
world business activities — comprising the enterprise (or inter-
A.156. Transaction Sequence enterprise) business processes.
Order of transactions required to accomplish the desired results. • Service representation utilizes business descriptions to provide
context (i.e., business process, goal, rule, policy, service
A.157. User interface, and service component) and implements services
1. Any person, organization, or functional unit that uses the services of using service orchestration. It places unique requirements on
an information processing system. the infrastructure — it is recommended that implementations
2. In a conceptual schema language, any person or any thing that may use open standards to realize interoperability and location
issue or receive commands and messages to or from the information transparency.
system. • Implementations are environment-specific — they are
A.158. User Interface Service constrained or enabled by context and must be described
A ser vice of the application platform entity of the Technical Reference within that context.
Model (TRM) that supports direct human-machine interaction by • It requires strong governance of service representation and
controlling the environment in which users interact with applications. implementation.
• It requires a ‘‘Litmus Test’’, which determines a ‘‘good
A.159. Use-Case service’’.
A view of organization, application, or product functionality that See also Section 3.8 and Section 3.74.
illustrates capabilities in context with the user of that capability.
A.164. Skill
A.160. Segment Architecture The ability to perform a job-related activity, which contributes to the
A detailed, for mal description of areas within an enterprise, used at effective performance of a task.
the program or portfolio level to organize and align change activity.
See also Section 3.82. A.165. Solution Architecture
A description of a discrete and focused business operation or activity
and how IS/IT supports that operation. A Solution Architecture typically
applies to a single project or project release, assisting in the

Glossary and Definitions Page 12

translation of requirements into a solution vision, high-level business A.172. Taxonomy of Architecture Views
and/or IT system specifications, and a portfolio of implementation The organized collection of all views pertinent to an architecture.
tasks.
A.173. Technical Reference Model (TRM)
A.166. Solution Building Block (SBB) A structure which allows components of an information system to be
A candidate physical solution for an Architecture Building Block (ABB); described in a consistent manner (i.e., the way in which you describe
e.g., a Commercial Off-The-Shelf (COTS) package, that is a component the components).
of the Acquirer view of the architecture. See also Section 3.66.

A.167. Solutions Continuum A.174. Technology Architecture

A part of the Enterprise Continuum. A repository of re-usable solutions The logical software and hardware capabilities that are required to
for future implementation efforts. It contains implementations of the support deployment of business, data, and application services. This
corresponding definitions in the Architecture Continuum. See also includes IT infrastructure, middleware, networks, communications,
Section 3.39 and Section 3.11. processing, and standards.
Note: Technology Architecture is described in Par t II, Chapter 12.
A.168. Stakeholder
An individual, team, or organization (or classes thereof) with interests A.175. Transition Architecture
in, or concerns relative to, the outcome of the architecture. Different A for mal description of the enterprise architecture showing periods of
stakeholders with different roles will have different concerns. transition and development for particular parts of the enterprise.
See also Section A.86 in Appendix A. Transition Architectures are used to provide an overview of current and
target capability and allow for individual work packages and projects to
A.169. Standards Information Base (SIB) be grouped into managed portfolios and programs.
A database of standards that can be used to define the particular Note: Transition Architectures are described in Part IV, Section
services and other components of an Organization-Specific 36.2.22.
Architecture.
Note: The Standards Information Base is described in Part V, Section A.176. View
41.4. The representation of a related set of concerns. A view is what is seen
from a viewpoint. An architecture view may be represented by a model
A.170. Strategic Architecture to demonstrate to stakeholders their areas of interest in the
A summary formal description of the enterprise, providing an architecture. A view does not have to be visual or graphical in nature.
organizing framework for operational and change activity, and an See also Section 3.80 and Section 3.89.
executive-level, long-term view for direction setting.
A.177. Viewpoint
A.171. Target Architecture A definition of the perspective from which a view is taken. It is a
The description of a future state of the architecture being developed specification of the conventions for constructing and using a view
for an organization. There may be several future states developed as a (often by means of an appropriate schema or template). A view is what
roadmap to show the evolution of the architecture to a target state. you see; a viewpoint is where you are looking from — the vantage point
or perspective that determines what you see.
See also Section A.56 in Appendix A.

Glossary and Definitions Page 13

A.178. 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.

Glossary and Definitions Page 14

Abbreviations DDL Data Definition Language
DISA US Department of Defense Information Systems Agency
ABB Architecture Building Block DMF Data Management Facility
AC Access Control DML Data Manipulation Language
ACL Access Control List DMTF Distributed Management Task Force
ACMM Architecture Capability Maturity Model DNS Domain Name System
ACSE Association Control Service Element DoC US Department of Commerce
ADM Architecture Development Method DoD US Department of Defense
ANSI American National Standards Institute DoDAF Department of Defense Architecture Framework
API Application Platform Interface DRDA Distributed Relational Database Architecture
ARTS Association for Retail Technology Standards EA Enterprise Architecture
BMM Business Motivation Model EAI Enterprise Application Integration
BPM Business Process Management EDI Electronic Data Interchange
BPMN Business Process Modeling Notation EEI External Environment Interface
BTEP The Canadian Government Business Transformation ERP Enterprise Resource Planning
Enablement Program ES End System
CAB Change Advisory Board ESB Enterprise Service Bus
CCITT Consultative Committee on International Telegraph and ETL Extract, Transform, Load
Telephone, now known as the International FEAF Federal Enterprise Architecture Framework
Telecommunication Union (ITU) FICO Fair Isaac Corporation
CI Configuration Item FORTRAN FORmula TRANslator
CIPR Central Information Process FTE Full-Time Equivalent
CM Configuration Management GOTS Government Off-The-Shelf applications
CMIP Common Management Information Protocol GUI Graphical User Interface
CMIS Common Management Information Service HIPAA Health Insurance Portability and Accountability Act
CMM Capability Maturity Models ICAM Integrated Computer Aided Manufacturing
CMMI Capability Maturity Model Integration ICD Interface Control Document
CN Communications Network ICOM Inputs, Controls, Outputs, and Mechanisms/Resources
COBIT Control Objectives for Information and related IDEF Integrated Computer Aided Manufacturing (ICAM)
Technology DEFinition
CODASYL Conference on Data Systems Languages IDL Interface Description Language
CORBA Common Object Request Broker Architecture IEC International Electro-technical Commission
COTS Commercial Off-The-Shelf applications IEEE Institute of Electrical and Electronic Engineers
CRM Customer Relationship Management III Integrated Information Infrastructure
CRUD Create/Read/Update/Delete III-RM Integrated Information Infrastructure Reference Model
CSF Critical Success Factor IMS Information Management System
DAI Data Access Interface ISA Information Systems Architecture
DBA Database Administrator ISACA Information Systems Audit and Control Association
DBMS Database Management System ISACF Information Systems Audit and Control Foundation
DCE Distributed Computing Environment ISAM Indexed Sequential Access Method

Glossary and Definitions Page 15

ISO International Standards Organization PHIGS Programmer’s Hierarchical Interactive Graphics System
IT Information Technology PMI Project Management Initiative
ITGI IT Governance Institute PMBOK Project Management Body of Knowledge
ITIL Information Technology Infrastructure Library PRINCE Projects in Controlled Environments
ITPMF IT Portfolio Management Facility QoS Quality of Service
ITU International Telecommunication Union RACI Responsible, Accountable, Consulted, Informed
JMS Java Message Service RAS Remote Access Services
JVM Java Virtual Machine RDA Remote Database Access
KPI Key Performance Indicator RDBMS Relational Database Management System
LAN Local Area Network REA Resource-Event-Agent
LCS Local Communications System RFC Request For Change
LIPR Local Information Process RFI Request for Information
LSE Local Subscriber Network RFP Request for Proposal
MAN Metropolitan Area Network RFQ Request for Quotation
MDA Model Driven Architecture RM Reference Model
MIB Management Information Bases RM-ODP ISO Reference Model for Open Distributed Processing
MIS Management Information Systems RPC Remote Procedure Call
MLS Multi-Level Security RS Relay System
MTA Message Transfer Agent SA-CMM Software Acquisition Capability Maturity Model
NASCIO National Association of State Chief Information Officers SBB Solution Building Block
NIST National Institute of Standards and Technology SCAMPI Standard CMMI Appraisal Method for Process
OAG Open Applications Group Improvement
OAGIS Open Applications Group Integration Specification SDO Service Data Objects
ODBC Open Database Connectivity SEI Software Engineering Institute
OECD Organization for Economic Co-operation and SGML Standard Generalized Markup Language
Development SIB Standards Information Base
OGC UK Office of Government Commerce SCA Service Component Architecture
OLA Operational Level Agreement SCAMPI CMMI Appraisal Method for Process Improvement
OMB Office of Management and Budget SLA Service Level Agreement
OMG Object Management Group SMAP Security Management Application Process
OODBMS Object-Oriented Database Management System SMART Specific, Measurable, Attainable, Realistic, and Time-
ORB Object Request Broker bound
OS Operating System SMTP Simple Mail Transfer Protocol
OSE Open System Environment SNA System Network Architecture
OSI Open Systems Interconnection SNMP Simple Network Management Protocol
OSOA Open Service Oriented Architecture SOA Service Oriented Architecture
P-CMM People Capability Maturity Model SPEM Software Processing Engineering Metamodel
PDA Personal Digital Assistant SQL Structured Query Language
PDF Portable Document For mat STEP STandard for the Exchange of Product model data
PEX PHIGS Extension to the X Window system SWG Special Working Group

Glossary and Definitions Page 16

SysML Systems Modeling Language
TADG Treasury Architecture Development Guidance
TAFIM Technical Architecture Framework for Information
Management
TCP/IP Transmission Control Protocol/Internet Protocol
TISAF Treasury Information System Architecture Framework
TRM Technical Reference Model
TFA Transparent File Access
TLSP Transport Layer Security Protocol
TMF TeleManagement Forum
TP Transaction Processing
UML Unified Modeling Language
UN/CEFACT United Nations Centre for Trade Facilitation and
Electronic Business
UN/EDIFACT United Nations/Electronic Data Interchange For
Administration, Commerce, and Transport
WAN Wide Area Network
WSDL Web Services Description Language
XML Extensible Markup Language
XSD XMLSchema Definition

Glossary and Definitions Page 17