The TOGAF Glossary is intended to define terms essential to the understanding of TOGAF. It is not intended as a general-purpose open systems glossary and does not contain terms considered to be in common use.
Architecture Building Block
Access Control
Association Control Service Element
Activity Models (also called Business Process Models) describe the functions associated with the enterprise's business activities, the data and/or information exchanged between activities (internal exchanges), and the data and/or information exchanged with other activities that are outside the scope of the model (external exchanges). Activity models are hierarchical in nature. They capture the activities performed in a business process, and the ICOMs (inputs, controls, outputs, and mechanisms/resources used) of those activities. Activity models can be annotated with explicit statements of business rules, which represent relationships among the ICOMs. For example, a business rule can specify who can do what under specified conditions, the combination of inputs and controls needed, and the resulting outputs. One technique for creating activity models is the IDEF (Integrated Computer Aided Manufacturing (ICAM) DEFinition) modeling technique.
The Business Process Management Initiative (www.bpmi.org) is an organization that is defining standards for business process modeling, including a language with which to specify business processes, their tasks/steps, and the documents produced.
High-level computer programming language developed by the US Department of Defense (DoD). Ada is used as the standard programming language for the DoD. It is used for real-time processing, is modular in nature, and includes object-oriented features.
Architecture Development Method
American National Standards Institute
See Application Program Interface.
See Application Portability Profile.
A classification of computer programs designed to perform specific tasks, such as word processing, database management, or graphics.
The collection of hardware and software components that provide the services used by support and mission-specific software applications.
The NIST APP is the structure that integrates US federal, national, international, and other specifications to provide the functionality necessary to accommodate the broad range of US federal information technology requirements.
The interface, or set of functions, between the Application Software and the Application Platform.
The most common means by which a software programmer invokes other software functions.
Software entities which have a specific business purpose.
Ada Programming Support Environment
Architecture has two meanings depending upon its contextual usage:
A formal description of a system, or a detailed plan of the system at component level to guide its implementation.
The structure of components, their inter-relationships, and the principles and guidelines governing their design and evolution over time.
The existing system architecture before entering a cycle of architecture review and redesign.
Refer to Change Request.
A part of the Enterprise Continuum. The Architecture Continuum provides a repository of architectural elements with increasing detail and specialization. This Continuum begins with foundational definitions like reference models, core strategies, and basic building blocks. From there it spans to Industry Architectures and all the way to an organization's specific architecture.
Refer to Architecture Contract.
The logical view of the data models, data standards, and data structure. It includes a definition of the physical databases for the information system, their performance requirements, and their geographical distribution.
Refer to Architecture Framework.
Refer to Architecture Principles.
Refer to Architecture Report.
Depicts the configuration of the target information system.
Refer to Architecture Vision.
A perspective from which an architecture may be viewed in order to ensure that a specific topic is considered in a coherent manner; e.g., security.
See Business Scenario.
An input to or output from an instance of the ADM.
Abstract Syntax Notation
Active Server Pages
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.
Initial or basic functions.
A specification or product that has been formally reviewed and agreed upon, that thereafter serves as the basis for further development and that can be changed only through formal change control procedures or a type of procedure such as configuration management.
Processing data or the accomplishment of jobs accumulated in advance in such a manner that each accumulation thus formed is processed or accomplished in the same computer run.
Refer to Business Architecture.
A detailed, recursive step involving successive decomposition of major functional areas into sub-functions.
Refer to Business Policies.
Refer to Architecture Principles.
See Activity Model.
Refer to Business Scenario.
The services that each enterprise unit provides to its customers, both internally and externally.
Refer to Roles.
Refer to Business Strategy.
Hardware, software, policy statements, procedures, and people which together implement a business function.
Consultative Committee on International Telegraph and Telephone
Refer to Roles.
Class models are similar to logical data models. A class model describes static information and relationships between information. A class model also describes informational behaviors. Like many of the other models, it can also be used to model various levels of granularity. Depending on the intent of the model, a class model can represent business domain entities or systems implementation classes. A business domain model represents key business information (domain classes), their characteristics (attributes), their behaviors (methods or operations), and relationships (often referred to as multiplicity, describing how many classes typically participate in the relationship), and cardinality (describes required or optional participation in the relationship). Specifications further elaborate and detail information that cannot be represented in the class diagram.
An application component which requests services from a server.
Common Management Information Service
Common Management Information Protocol
Control OBjectives for Information and related Technology
Acronym for Common Business-Oriented Language. COBOL is a computer programming language used extensively in mainframes and minicomputers for business applications.
Hardware and software functions which allow Application Platforms to exchange information.
A set of products, concepts, and services that enable the connection of computer systems for the purpose of transmitting data and other forms (e.g., voice and video) between the systems.
A node that is either internal to the communications network (e.g., routers, bridges, or repeaters) or located between the end device and the communications network to operate as a gateway.
A set of assets (transmission media, switching nodes, interfaces, and control devices) that will establish linkage between users and devices.
A discipline applying technical and administrative direction and surveillance to:
Identify and document the functional and physical characteristics of a configuration item
Control changes to those characteristics
Record and report changes to processing and implementation status
A service area of the External Environment entity of the Technical Reference Model (TRM) that provides end-to-end connectivity for communications through three transport levels (global, regional, and local). It provides general and application-specific services to platform end devices.
Common Object Request Broker Architecture
Refer to Cultural Requirements.
A specialized type of database containing metadata, which is managed by a data dictionary system; 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 of data dictionary systems.
A basic unit of information having a meaning and that may have subcategories (data items) of distinct units and values.
Structured or organized collection of information, which may be accessed by the computer.
Computer application program that accesses or manipulates the database.
A service of the Platform entity of the Technical Reference Model that provides specialized support for the interchange of data between applications on the same or different platforms.
A service of the Platform entity of the Technical Reference Model that provides support for the management, storage, access, and manipulation of data in a database.
Refer to Architecture Principles.
Database Management System
Distributed Computing Environment
Data Definition Language
Command which is automatically executed if none is specifically indicated.
Part of the network services of the Application Platform entity of the Technical Reference Model (TRM) that provides locator services that are restricted to finding the location of a service, location of data, or translation of a common name into a network-specific address. It is analogous to telephone books and supports distributed directory implementations.
US Department of Defense Information Systems Agency
A database that is not stored in a central location but is dispersed over a network of interconnected computers.
A database under the overall control of a central Database Management System (DBMS) but whose storage devices are not all attached to the same processor.
A database that is physically located in two or more distinct locations.
Data Management Facility
European Computer Manufacturers Association
Electronic Data Interchange
External Environment Interface
Person who ultimately uses the computer application or output.
The highest level in an organization; includes all missions and functions.
Refer to Roles.
Refer to Enterprise Architecture Measures.
Refer to Enterprise Context Report.
Refer to Enterprise Continuum.
A high-level model of an organization's mission, function, and information architecture. The model consists of a function model and a data model.
Refer to Roles.
Enterprise Resource Planning
End System
Ability to resize objects to produce better organization of on-screen material, usually a graphic or a window.
The interface that supports information transfer between the Application Platform and the External Environment.
Any specifically identified collection of information stored in the computer.
Federal Information Processing Standard
Acronym for FORmula TRANslator, which is a high-level computer language used extensively in scientific and engineering applications.
File Transfer, Access, and Management
A useful capability provided by one or more components of a system.
Refer to Gap Analysis.
Government Network Management Profile
Government Open System Interconnection Profile
General Security Service
Graphical User Interface
Physical equipment, as opposed to programs, procedures, rules, and associated documentation.
Contrast with software.
Human Computer Interface hardware and software allowing information exchange between the user and the computer.
The International Electrotechnical Commission, the international standards body which is responsible for electrical standards.
Institute of Electrical and Electronic Engineers
Integrated Information Infrastructure
Integrated Information Infrastructure Reference Model
Refer to Impact Analysis.
Data in context: any communication or representation of knowledge such as facts, data, or opinions, in any medium or form, including textual, numerical, graphic, cartographic, narrative, or audio-visual forms.
Refer to Information System Architecture.
A set of commonly and unambiguously labeled information objects with a common security policy that defines the protections to be afforded the objects by authorized users and information management systems.
The computer-based portion of a business system.
This is a combination of the Data Architecture and Applications Architecture.
The technology included in hardware and software used for information, regardless of the technology involved, whether computers, communications, micro graphics, or others.
Interconnection and inter-relationships between two devices, two applications, or the user and an application or device.
The ability of two or more systems or components to exchange and use information.
The ability of systems to provide and receive services from other systems and to use the services so interchanged to enable them to operate effectively together.
Refer to Investment Requirements.
Information System
Information System Architecture
International Standards Organization
Information Technology
Information Technology Infrastructure Library
Refer to IT Strategy Requirements.
A Joint Technical Committee established by ISO and IEC to take responsibility for their shared interests in IT standardization.
Local Area Network
The period of time that begins when a system is conceived and ends when the system is no longer available for use.
Metropolitan Area Network
A specification of the conventions for constructing and using a view. A metaview acts as a pattern or template of the view, from which to develop individual views. A metaview 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).
Management Information Systems
Multi-Level Security
Message Transfer Agent
A service of the Technical Reference Model (TRM) that provides the capability to manipulate and manage information products consisting of text, graphics, images, video, and audio.
Refer to New Technology Report.
US National Institute of Standards and Technology
Network Layer Security Protocol
Office Document Architecture
Office Document Interchange Format
Organization for Economic Co-operation and Development
OSI Implementors' Workshop
Object-Oriented Database Management System
Public specifications that are maintained by an open, public consensus process to accommodate new technologies over time and that are consistent with international standards.
A system that implements sufficient open specifications for interfaces, services, and supporting formats to enable properly engineered Application Software:
To be ported with minimal changes across a wide range of systems
To interoperate with other applications on local and remote systems
To interact with users in a style that facilitates user portability
The comprehensive set of interfaces, services, and supporting formats, plus user aspects for interoperability or for portability of applications, data, or people, as specified by IT standards and profiles.
A core service of the Application Platform entity of the Technical Reference Model (TRM) that is needed to operate and administer the Application Platform and provide an interface between the Application Software and the Platform (e.g., file management, input/output, print spoolers).
Object Request Broker
Operating System
Open System Environment
Open Systems Interconnection
PHIGS Extension to X Windows
Programmer's Hierarchical Interactive Graphics System
See Application Platform.
The ease with which a system or component can be transferred from one hardware or software environment to another.
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.
The ease with which a system, component, data, or user can be transferred from one hardware or software environment to another.
Portable Operating System Interface (for Computer Environments)
Refer to Product Information.
A set of one or more base standards and, where applicable, the identification of those classes, subsets, options, and parameters of those base standards, necessary for accomplishing a particular function.
Selecting standards for a particular application.
Refer to Roles.
Remote Access Services
Remote Database Access
Relational Database Management System
Refer to Relationship Profiles.
A system that manages all of the data of an enterprise, including data and process models and other enterprise information. Hence, the data in a repository is much more extensive than that in a data dictionary, which generally defines only the data making up a database.
Refer to Request for Architecture Work.
Refer to Request for Change.
Refer to Requirements Impact Statement.
Anything other than artifacts, required and delivered via the domain, that may assist the development of architecture artifacts.
Reference Model
Remote Procedure Call
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.
Services which protect data, ensuring its confidentiality, availability, and integrity.
An application component which responds to requests from a client.
Standard Generalized Markup Language
Standards Information Base
Security Management Application Process
Simple Mail Transfer Protocol
System Network Architecture
Simple Network Management Protocol
Services-Oriented Architecture. Includes the following services:
Refer to Roles.
A part of the Enterprise Continuum. The Solutions Continuum contains implementations of the corresponding definitions in the Architecture Continuum. In this way it becomes a repository of re-usable solutions for future implementation efforts.
Structured Query Language
Refer to Stakeholder Profiles.
Refer to Statement of Architecture Work.
Special Working Group
A collection of components organized to accomplish a specific function or set of functions (taken from Draft Recommended Practice for Architectural Description IEEE P1471/D5.2).
A cross-category service of the Application Platform entity of the Technical Reference Model (TRM) that provides for the administration of the overall information system. These services include the management of information, processors, networks, configurations, accounting, and performance.
An individual, team, or organization (or classes thereof) with interests in, or concerns relative to, a system (taken from ANSI/IEEE Std 1471-2000).
Technical Architecture Framework for Information Management
The organized collection of all views pertinent to an architecture.
Transmission Control Protocol/Internet Protocol
Trusted Computer System Evaluation Criteria
A structure which allows the components of an information system to be described in a consistent manner.
Refer to Technical Requirements.
Refer to Technology Architecture.
Transparent File Access
Transport Layer Security Protocol
Trusted Network Interpretation
Transaction Processing
Interaction between a user and a computer in which the user inputs a command to receive a specific result from the computer.
Order of transactions required to accomplish the desired results.
Refer to Transitional Architecture.
Technical Reference Model
Trusted Systems Interoperability Group
User Interface Definition Language
User Interface Management System
User Interface System Reference Model
Use-case models can describe either business processes or systems functions, depending on the focus of the modeling effort. A use-case model describes the business processes of an enterprise in terms of use-cases and actors corresponding to business processes and organizational participants (people, organizations, etc.). The use-case model is described in use-case diagrams and use-case specifications.
Any person, organization, or functional unit that uses the services of an information processing system.
In a conceptual schema language, any person or any thing that may issue or receive commands and messages to or from the information system.
A service of the Application Platform entity of the Technical Reference Model (TRM) that supports direct human-machine interaction by controlling the environment in which users interact with applications.
Refer to Views.
A viewpoint addresses key stakeholder concerns.
A viewpoint is a specification of the conventions for constructing and using a view. A metaview acts as a pattern or template of the view, from which to develop individual views. A metaview 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).
Wide Area Network