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

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

A representation of a subject of interest. Note: An architecture model provides a smaller scale, simplified, and/or abstract representation of the subject matter.

An architectural work product that describes an aspect of the 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, processes, initiatives, and stakeholders. Note: Business Architecture relates business elements to business goals and elements of other domains. Business Architecture is described in the TOGAF Standard — Architecture Development Method.

A model describing the rationale for how an enterprise creates, delivers, and captures value.

An ability that an organization, person, or system possesses. Note: This a general-purpose definition. See 4.28 Business Capability for how this concept is refined for usage in Business Architecture.

An architecture that describes the abilities that an enterprise possesses.

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

An architectural work product that is contractually specified and in turn formally reviewed, agreed, and signed off by the stakeholders. Note: Deliverables represent the output of projects and those deliverables that are in documentation form will typically be archived at completion of a project, or transitioned into an Architecture Repository as a reference model, standard, or snapshot of the Architecture Landscape at a point in time.

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.

A model that describes the entities used in building an Architecture Description, their characteristics, and the key relationships between those entities.

A technique through construction of models which enables a subject to be represented in a form that enables reasoning, insight, and clarity concerning the essence of the subject matter.

A statement of need, which is unambiguous, testable or measurable, and necessary for acceptability.

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. The part an individual plays in an organization and the contribution they make through the application of their skills, knowledge, experience, and abilities.

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

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

A summary formal description of the enterprise, providing an organizing framework for operational and change activity, and an executive-level, long-term view for direction setting.

A description of the structure and interaction of the technology services and technology components.

A formal description of one state of the architecture at an architecturally significant point in time. Note: One or more Transition Architectures may be used to describe the progression in time from the Baseline to the Target Architecture.

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.