Glossary and Acronyms

ABB

Architecture Building Block

ADM

Architecture Development Method

Agile

To move/change quickly and easily, often to provide value-generating outcomes.

Agile Architecture
  1. The “act” – the development of architecture that reacts quickly and easily to changes through the delivery of iterative architectures that provides incremental value-generating outcomes.

  2. The “thing” – an architecture that is flexible; i.e., easy to change or adapt.

Agile Product Owner

A member of an Agile Product team responsible for defining user stories and prioritizing the backlog, ensuring these are understood by other team members while maintaining the conceptual integrity of the features or components for the Delivery team. In the TOGAF framework, product has a wider context, but is used here in the Agile product context.

API

Application Programming Interface

Application Architecture

A description of the structure and interaction of the applications as groups of capabilities that provide key business functions and manage the data assets.

Architecture
  1. The fundamental concepts or properties of a system in its environment embodied in its elements, relationships, and in the principles of its design and evolution.

  2. The structure of components, their inter-relationships, and the principles and guidelines governing their design and evolution over time.

Architecture Building Block (ABB)

A constituent of the architecture model that describes a single aspect of the overall model.

Architecture Continuum

A part of the Enterprise Continuum. A repository of architectural elements with increasing detail and specialization.

Architecture Development Method (ADM)

The core of the TOGAF framework. A multi-phase, iterative approach to develop and use an Enterprise Architecture to shape and govern business transformation and implementation projects.

Architecture Framework

A conceptual structure used to plan, develop, implement, govern, and sustain an architecture.

Architecture Landscape

The architectural representation of assets in use, or planned, by the enterprise at particular points in time.

Architecture Principle

A qualitative statement of intent that should be met by the architecture.

Architecture Project

An endeavor undertaken to define and describe the Enterprise Architecture to be implemented. In TOGAF terms, it encompasses all activities undertaken within the ADM Phases A to F, and Requirements Management for these phases. Practically, it can be a stand-alone project or part of a larger effort (e.g., a program).

Architecture View

A representation of a system from the perspective of a related set of concerns.

Architecture Viewpoint

A specification of the conventions for a particular kind of architecture view.

Artifact

An architectural work product that describes an aspect of the architecture.

Backlog

An ever-evolving list of requirements, prioritized by the stakeholders, that conveys to an Agile team which requirements to handle first. Business change design and development typically employ a top-level backlog, known as a business change backlog, and each Agile team working on a sprint typically creates a backlog for each sprint, known as a sprint backlog.

Baseline

A specification that has been formally reviewed and agreed upon, that thereafter serves as the basis for further development or change and that can be changed only through formal change control procedures or a type of procedure such as configuration management.

BDUF

Big Design Up Front

Business Architecture

A representation of holistic, multi-dimensional business views of: capabilities, end-to-end value delivery, information, and organizational structure; and the relationships among these business views and strategies, products, policies, initiatives, and stakeholders.

Capability

An ability that an organization, person, or system possesses.

Capability Architecture

A highly detailed description of the architectural approach to realize a particular solution or solution aspect.

Capability Increment

A discrete portion of a capability architecture that delivers specific value. When all increments have been completed, the capability has been realized.

C-MDM

Customer Master Data Management

CMM

Capability Maturity Model

CSF

Critical Success Factor

Data Architecture

A description of the structure and interaction of the enterprise’s major types and sources of data, logical data assets, physical data assets, and data management resources.

DBRM

Digital Business Reference Model

DoDAF

Department of Defense Architecture Framework

DTRA

Digital Transformation Readiness Assessment

Enterprise

The highest level (typically) of description of an organization and typically covers all missions and functions. An enterprise will often span multiple organizations.

Enterprise Architecture
  1. The process of translating business vision and strategy into effective enterprise change by creating, communicating, and improving the key principles and models that describe the enterprise’s future state and enable its evolution. (Source: Gartner®)

  2. A set of abstractions and models that simplify and communicate complex structures, processes, rules, and constraints to improve understanding, implementation, forecasting, and resourcing. (Source: DoDAF)

Enterprise Continuum

A categorization mechanism for classifying architecture and solution artifacts as they evolve from generic to specific applicability.

ERD

Entity Relationship Diagram

ERM

Enterprise Risk Management

Foundation Architecture

Generic building blocks, their inter-relationships with other building blocks, combined with the principles and guidelines that provide a foundation on which more specific architectures can be built.

Framework

A structure for content or process that can be used as a tool to structure thinking, ensuring consistency and completeness.

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.

Governance

The discipline of monitoring, managing, and steering a business (or Information Systems/Information Technology (IS/IT) landscape) to deliver the business outcome required.

GRM

Government Reference Model

IS/IT

Information Systems/Information Technology

ISM

Information Security Management

KPI

Key Performance Indicator

Metamodel

A model that describes how and with what the architecture will be described in a structured way.

Minimum Viable Architecture (MVA)

The minimum (Enterprise) Architecture that is realizable and adds business value. An architecture that enables the delivery of product features with just enough content to be deployed in a given phase of a project and satisfies known requirements (especially quality attribute requirements), and no more.

Minimum Viable Business Development (MVBD)

The minimum set of business change that delivers significant value to the stakeholders.

Minimum Viable Product (MVP)

An output that satisfies a minimum set of functional and non-functional requirements and can be realized when implemented in a live operational environment. The smallest possible outcome that generates acceptable learning, delivery of value to the customer (internal or external), and is a basis for future extension.

Practitioner

The person tasked to develop, maintain, and use an Enterprise Architecture.

Product

An outcome generated by the business to be offered to customers. Products include materials and/or services.

Project Management

The planning, delegating, monitoring, and control of all aspects of the project, and the motivation of those involved to achieve the project objectives within the expected performance targets for time, cost, quality, scope, benefits, and risks. Market-leading methods include PRINCE2 and PMBOK.

Repository

A system that manages all of the data of an enterprise, including data and process models and other enterprise information.

Requirement

A statement of need that must be met by a particular architecture or work package.

Retrospective

A time-boxed meeting held at the end of a sprint, in which the Sprint team examines its processes to determine what succeeded and what could be improved; key to an Agile team’s ability to “inspect and adapt” in the pursuit of “continuous improvement”.

Risk Management

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

Segment Architecture

A detailed, formal description of areas within an enterprise, used at the program or portfolio level to organize and align change activity.

Service

A repeatable activity; a discrete behavior that a building block may be requested or otherwise triggered to perform.

Service-Orientation

Viewing an enterprise, system, or building block in terms of services provided and consumed.

Service-Oriented Architecture (SOA)

An architectural style that supports service-orientation.

SLA

Service-Level Agreement

Solution Architecture

A description of a discrete and focused business operation or activity and how IS/IT supports that operation.

Solution Building Block (SBB)

A candidate solution which conforms to the specification of an Architecture Building Block (ABB).

Solutions Continuum

A part of the Enterprise Continuum. A repository of solution implementation elements with increasing detail and specialization.

Sprint

A short, time-boxed period, at the very heart of Agile methodologies, when an Agile team works to complete a set amount of work supporting the delivery of a working solution.

Stakeholder

An individual, team, organization, or class thereof, having an interest in a system.

TAFIM

Technical Architecture Framework for Information Management

Target Architecture

The description of a future state of the architecture being developed for an organization.

Technical Reference Model (TRM)

A structure which allows the components of an information system to be described in a consistent manner.

Technology Architecture

A description of the structure and interaction of the technology services, and logical and physical technology components.

Transition Architecture

A formal description of one state of the architecture at an architecturally significant point in time.

Value Stream

A representation of an end-to-end collection of value-adding activities that create an overall result for a customer, stakeholder, or end user.

View

See Architecture View.

Viewpoint

See Architecture Viewpoint.

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.