87 terms

TOGAF 9.2 (The Open Group Architecture Framework) - Paul Colmer

STUDY
PLAY
Abstraction
The technique of providing summarized or generalised descriptions of detailed and complex content.
Actor
A person, organization, or system that has one or more roles that initiates or interacts with activities. For example, a sales representative who travels to visit customers. Actors may be internal or external to an organization.
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.
Application Component
An encapsulation of application functionality aligned to implementation structure, which is modular and replaceable. It encapsulates its behavior and data, provides services, and makes them available through interfaces.
Application Platform
The collection of technology components of hardware and software that provide the services used to support applications.
Architectural Style
The combination of distinctive features related to the specific context within which architecture is performed or expressed; a collection of principles and characteristics that steer or constrain how an architecture is formed.
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.
(Source: ISO/IEC/IEEE 42010: 2011)

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 Domain
The architectural area being considered. The TOGAF framework has four primary architecture domains: business, data, application, and technology.

Security, risk and requirements should be considered throughout all these phases.
Architecture Framework
A conceptual structure used to plan, develop, implement, govern, and sustain an architecture.
Architecture Governance
The practice of monitoring and directing architecture-related work. The goal is to deliver desired outcomes and adhere to relevant principles, standards, and roadmaps.
Architecture Landscape
The architectural representation of assets in use, or planned, by the enterprise at particular points in time.
Architecture Model
A representation of a subject of interest.
Architecture Principle
A qualitative statement of intent that should be met by the architecture.
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.
Using a template in a modelling tool is an example of an architecture viewpoint.
Architecture Vision
A succinct description of the Target Architecture that describes its business value and the changes to the enterprise that will result from its successful deployment. It serves as an aspirational vision and a boundary for detailed architecture development.
Artifact
An architectural work product that describes an aspect of the architecture.
Baseline
A specification that has been formally reviewed and agreed upon, that serves as the basis for further development or change. The specification can be changed through change control processes.
Boundaryless Information Flow
A shorthand representation of "access to integrated information to support business process improvements" representing a desired state of an enterprise's infrastructure specific to the business needs of the organization.
Building Block
A (potentially re-usable) component of enterprise capability that can be combined with other building blocks to deliver architectures and solutions.
Business Architecture
A representation of holistic, multi-dimensional business views of: capabilities, end-to-end value delivery, information, and organizational structure.
It includes the relationships among these business views and strategies, products, policies, initiatives, and stakeholders.
Business Capability
A particular ability that a business may possess or exchange to achieve a specific purpose.
Business Function
Delivers business capabilities closely aligned to an organization, but not necessarily explicitly governed by the organization.
Business Governance
Concerned with ensuring that the business processes and policies (and their operation) deliver the business outcomes and adhere to relevant business regulation.
Business Model
A model describing the rationale for how an enterprise creates, delivers, and captures value.
Business Service
Supports business capabilities through an explicitly defined interface and is explicitly governed by an organization.
Capability
An ability that an organization, person, or system possesses.
Capability Architecture
A highly detailed description of the architectural approach to realise 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 realised.
Communications & Stakeholder Management
The management of needs of stakeholders of the Enterprise Architecture practice. It also manages the execution of communication between the practice and the stakeholders and the practice and the consumers of its services.
Concern
An interest in a system relevant to one or more of its stakeholders.
Course of Action
Direction and focus provided by strategic goals and objectives, often to deliver the value proposition characterised in the business model.
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.
Deliverable
An architectural work product that is contractually specified and in turn formally reviewed, agreed, and signed off by the stakeholders.
Enterprise
The highest level of a description of an organization. It typically covers all missions and functions. An enterprise will often span multiple organizations.
Enterprise Continuum
A categorisation mechanism useful for classifying architecture and solution artifacts, both internal and external to the Architecture Repository. Artifacts can evolve from generic Foundation Architectures to Organization-Specific Architectures.
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.
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 to deliver
the business outcomes required, in-line with clear ethical and legal boundaries.
Information
Any communication or representation of facts, data, or opinions, in any medium or form, including textual, numerical, graphic, cartographic, narrative, or audio-visual forms.
Information System Service
1. A discrete behavior requestable from an application. Examples include: a login, booking a seat on an airplane or transferring money.

2. The automated elements of a business service.
Information Technology (IT)
1. The lifecycle management of information and related technology used by an organization.
2. An umbrella term that includes all or some of the subject areas relating to the computer industry.
3. A term commonly assigned to a department within an organization tasked with
provisioning various technology-related services.
Interoperability
1. The ability to share information and services.
2. The ability of two or more systems or components to exchange and use information.
3. 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.
Logical
An implementation-independent definition of the architecture, often grouping related physical entities according to their purpose and structure.
Metadata
Data about data, of any sort in any media, that describes the characteristics of an entity.
Metamodel
A model that describes the object components and how they interact within an architecture. It provides a blueprint for how architectures can be constructructed, allowing components and relationships to be traceable across the architecture continuum.
Method
A defined, repeatable approach to address a particular type of problem.
Modeling
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.
Model Kind
Conventions for a type of modeling.
Objective
A time-bounded milestone for an organization used to demonstrate progress towards a goal; for example, "Increase capacity utilization by 30% by the end of 2019 to support the planned increase in market share".
Organisation Map
An articulation of the relationships between the primary entities that make up the enterprise, its
partners, and stakeholders.
Pattern
A technique for putting building blocks into context. For example: to describe a re-usable
solution to a problem.
Physical
A description of a real-world entity. Physical elements in an Enterprise Architecture may still be
considerably abstracted from Solution architecture, design, or implementation views.
Reference Model (RM)
An abstract framework for understanding significant relationships among the entities of an
environment, and for the development of consistent standards or specifications supporting that environment.
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.
Roadmap
An abstracted plan for business or technology change, typically operating across multiple disciplines over multiple years.
Role
1. The usual or expected function of an actor, or the part somebody or something plays in a particular action or event. An actor may have a number of roles.
2. The part an individual plays in an organization and the contribution they make through the application of their skills, knowledge, experience, and abilities.
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
1. A repeatable activity; a discrete behavior that a building block may be requested or otherwise triggered to perform.
2. An element of behavior that provides specific functionality in response to requests from actors or other services.
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.
Service Portfolio
A collection of services, potentially an interface definition.
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 re-usable solutions for future implementation efforts. It contains implementations of the corresponding definitions in the Architecture Continuum.
Stakeholder
An individual, team, organisation, or class thereof, having an interest in a system.
Standards Information Base (SIB)
A database of standards that can be used to define the particular services and other components
of an Organisation-Specific Architecture.
Strategic Architecture
A summary formal description of the enterprise, providing an organising framework for operational and change activity, and an executive-level, long-term view for direction setting.
Target Architecture
The description of a future state of the architecture being developed for an organisation.
Taxonomy of Architecture Views
The organised collection of all architecture views pertinent to an architecture.
Technology Architecture
A description of the structure and interaction of the technology services and technology components.
Technology Component
1. A technology building block. A generic infrastructure technology that supports and enables application or data components (directly or indirectly) by providing technology services.
2. An encapsulation of technology infrastructure that represents a class of technology product or specific technology product.
Technology Service
A technical capability required to provide enabling infrastructure that supports the delivery of applications.
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.
Viewpoint Library
A collection of the specifications of architecture viewpoints contained in the Reference Library
portion of the Architecture Repository.
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.
Principle
A qualitative statement of intent that should be met by the architecture.
View
A representation of a system from the perspective of a related set of concerns.
Viewpoint
A specification of the conventions for a particular kind of architecture view. Using a template in a modelling tool is an example of an architecture viewpoint.
Microservices
An architectural style, similar to service-oriented architecture, that structures a system as a group of loosely coupled components, services are fine-grained and protocols are lightweight.

https://en.wikipedia.org/wiki/Microservices
Loose Coupling
A method of architecting a system to ensure that services are interdependent of each other. Services are defined as loosely coupled, when the outputs of one service can be stored temporarily, until the receiving service can process.

Techniques to ensure loose coupling include the use of queues, datastores and stacks.
Architecture Development Method
Describes a method for developing an enterprise architecture, and forms the core of TOGAF.
YOU MIGHT ALSO LIKE...