Home The TOGAF® Standard

Provide feedback on this page

TOGAF® Fundamental Content

Extended Guidance

General How-To

Establishing an EA Team

Domains
Agile Methods
Business Architecture
Data/Information Architecture
Security Architecture

Reference Models & Method

B. Glossary of Supplementary Definitions

This appendix contains additional definitions to supplement the definitions contained in 4. Definitions .

B.1 Application Software

Software entities which have a specific business purpose.

B.2 Availability

In the context of IT systems, the probability that system functional capabilities are ready for use by a user at any time, where all time is considered, including operations, repair, administration, and logistic time. Availability is further defined by system category for both routine and priority operations.

B.3 Business System

Hardware, software, policy statements, processes, activities, standards, and people which together implement a business capability.

B.4 Catalog

A structured list of architectural outputs of a similar kind, used for reference. For example, a technology standards catalog or an application portfolio.

B.5 Client

An application component which requests services from a server.

B.6 COBIT

An acronym for Control OBjectives for Information and related Technology, created by the Information Systems Audit and Control Association (ISACA) and the IT Governance Institute (ITGI), which provides a set of recommended best practices for the governance/management of information systems and technology.

B.7 Configuration Management

A discipline applying technical and administrative direction and surveillance to:

Also, the management of the configuration of Enterprise Architecture practice (intellectual property) assets and baselines and the control of change over of those assets.

B.8 CxO

The chief officer within a particular function of the business; e.g., Chief Executive Officer, Chief Financial Officer, Chief Information Officer, Chief Technology Officer.

B.9 Data Dictionary

A specialized type of database containing metadata; a repository of information describing the characteristics of data used to design, monitor, document, protect, and control data in information systems and databases; an application system supporting the definition and management of database metadata.

B.10 Data Element

A basic unit of information having a meaning and that may have subcategories (data items) of distinct units and values.

B.11 Database

A structured or organized collection of data entities, which is to be accessed by a computer.

B.12 Database Management System

A computer application program that accesses or manipulates the database.

B.13 End User

Person who ultimately uses the computer application or output.

B.14 Enterprise Resource Planning (ERP) System

A complete suite of integrated applications that support the major business support functions of an organization; e.g., Financial (AP/AR/GL), HR, Payroll, Stock, Order Processing and Invoicing, Purchasing, Logistics, Manufacturing, etc.

B.15 Hardware

The physical infrastructure needed to run software; e.g., servers, workstations, network equipment, etc.

B.16 Information Domain

Grouping of information (or data entities) by a set of criteria such as security classification, ownership, location, etc. In the context of security, information domains are defined as a set of users, their information objects, and a security policy.

B.17 Information System (IS)

The computer (or IT)-based portion of a business system.

B.18 Interaction

A relationship between architectural building blocks (i.e., services or components) that embodies communication or usage.

B.19 Interaction Model

An architectural view, catalog, or matrix that shows a particular type of interaction. For example, a diagram showing application integration.

B.20 Interface

Interconnection and inter-relationships between, for example, people, systems, devices, applications, or the user and an application or device.

B.21 Key Performance Indicator (KPI)

A way of quantifying the performance of the business or project.

B.22 Lifecycle

The period of time that begins when a system is conceived and ends when the system is no longer available for use.

B.23 Managing Successful Programs (MSP)

A best practice methodology for program management, developed by the UK Office of Government Commerce (OGC).

B.24 Matrix

A format for showing the relationship between two (or more) architectural elements in a grid format.

B.25 Metaview

A pattern or template of the view, from which to develop individual views. Establishes the purposes and audience for a view, the ways in which the view is documented (e.g., for visual modeling), and the ways in which it is used (e.g., for analysis).

See also 4.21 Architecture Viewpoint in 4. Definitions .

B.26 Open System

A system that implements sufficient open specifications for interfaces, services, and supporting formats to enable properly engineered application software:

B.27 Operational Governance

The operational performance of systems against contracted performance levels, the definition of operational performance levels, and the implementation of systems that ensure effective operation of systems.

See also 4.48 Governance in 4. Definitions .

B.28 Packaged Services

Services that are acquired from the market from a Commercial Off-The-Shelf (COTS) vendor, rather than being constructed via code build.

B.29 Portability

  1. The ease with which a system, component, data, or user can be transferred from one hardware or software environment to another.
  2. A quality metric that can be used to measure the relative effort to transport the software for use in another environment or to convert software for use in another operating environment, hardware configuration, or software system environment.

B.30 Portfolio

A collection of programs, projects, and/or operations managed as a group to achieve strategic objectives. For example, project portfolio, application portfolio, technology portfolio, or service portfolio.

Note:
Portfolio management is the act of managing portfolios.

B.31 PRINCE2

An acronym for PRojects IN Controlled Environments, which is a standard project management method.

B.32 Program

A co-ordinated set of change projects that deliver business benefit to the organization.

B.33 Project

A single change project which delivers business benefit to the organization.

B.34 Risk Management

The management of risks and issues that may threaten the success of the Enterprise Architecture practice and its ability to meet its vision, goals, and objectives, and, importantly, its service provision.

Note:
Risk management is described in the TOGAF Standard — Architecture Content.

B.35 Scalability

The ability to use the same application software on many different classes of hardware/software platforms from PCs to super-computers (extends the portability concept). The capability to grow to accommodate increased work loads.

B.36 Security

Services which protect data, ensuring its confidentiality, availability, and integrity.

B.37 Server

An application component which responds to requests from a client.

B.38 Service Quality

A preset configuration of non-functional attributes that may be assigned to a service or service contract.

B.39 SMART

An acronym for Specific, Measurable, Actionable, Realistic, and Timebound, which is an approach to ensure that targets and objectives are set in a way that can be achieved and measured.

B.40 Supplier Management

The management of suppliers of products and services to the Enterprise Architecture practice in concert with larger corporate procurement activities.

B.41 System

A combination of interacting elements organized to achieve one or more stated purposes. (Source: ISO/IEC/IEEE 15288:2015)

B.42 Time Period

The timeframe over which the potential impact is to be measured.

B.43 Use-Case

A view of organization, application, or product functionality that illustrates capabilities in context with the user of that capability.

B.44 User

  1. Any person, organization, or functional unit that uses the services of an information processing system.
  2. In a conceptual schema language, any person or any thing that may issue or receive commands and messages to or from the information system.
return to top of page