Key Terms Flashcards
Application
(Syllabus Reference: Unit 3, Learning Outcome 1)
A deployed and operational IT system that supports business functions and services; for example, a payroll. Applications use data and are supported by multiple technology components but are distinct from the technology components that support the application.
Application Architecture
(Syllabus Reference: Unit 3, Learning Outcome 2)
A description of the major logical grouping of capabilities that manage the data objects necessary to process the data and support the business.
Architecture
(Syllabus Reference: Unit 3, Learning Outcome 3)
Architecture has two meanings depending upon its contextual usage:
1. A formal description of a system, or a detailed plan of the system at component level to guide its implementation
2. The structure of components, their inter-relationships, and the principles and guidelines governing their design and evolution over time
Architecture Continuum
A part of the Enterprise Continuum. A repository of architectural elements with increasing detail and specialization. This Continuum begins with foundational definitions such as 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.
Architecture Building Block (ABB)
(Syllabus Reference: Unit 3, Learning Outcome 4)
A constituent of the architecture model that describes a single aspect of the overall model.
See also Building Block and Chapter 11.
Architecture Development Method (ADM)
(Syllabus Reference: Unit 3, Learning Outcome 5)
The core of the TOGAF standard. A step-by-step approach to develop and use an enterprise architecture.
Architecture Domain
(Syllabus Reference: Unit 3, Learning Outcome 6)
The architectural area being considered. There are four architecture domains within the TOGAF standard: Business, Data, Application, and Technology (BDAT).
Architecture Framework
(Syllabus Reference: Unit 3, Learning Outcome 7)
A conceptual structure used to develop, implement, and sustain an architecture.
Architecture Principles
(Syllabus Reference: Unit 3, Learning Outcome 8)
A qualitative statement of intent that should be met by the architecture. Has at least a supporting rationale and a measure of importance.
Architecture Vision
(Syllabus Reference: Unit 3, Learning Outcome 9)
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.
Baseline
(Syllabus Reference: Unit 3, Learning Outcome 10)
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.
Building Block
(Syllabus Reference: Unit 3, Learning Outcome 11) Represents a (potentially re-usable) component of business, IT, or architectural capability that can be combined with other building blocks to deliver architectures and solutions. Building blocks can be defined at various levels of detail, depending on what stage of architecture development has been reached. For instance, at an early stage, a building block can simply consist of a name or an outline description. Later on, a building block may be decomposed into multiple supporting building blocks and may be accompanied by a full specification. Building blocks can relate to “architectures” or “solutions”.
Business Architecture
(Syllabus Reference: Unit 3, Learning Outcome 12)
A description of the structure and interaction between the business strategy, organization, functions, business processes, and information needs.
Business Governance
(Syllabus Reference: Unit 3, Learning Outcome 13)
Concerned with ensuring that the business processes and policies (and their operation) deliver the business outcomes and adhere to relevant business regulation.
Capability
(Syllabus Reference: Unit 3, Learning Outcome 14)
An ability that an organization, person, or system possesses. Capabilities are typically expressed in general and high-level terms and typically require a combination of organization, people, processes, and technology to achieve; or example, marketing, customer contact, or outbound telemarketing.
Concerns
(Syllabus Reference: Unit 3, Learning Outcome 14)
An ability that an organization, person, or system possesses. Capabilities are typically expressed in general and high-level terms and typically require a combination of organization, people, processes, and technology to achieve; or example, marketing, customer contact, or outbound telemarketing.
Constraint
(Syllabus Reference: Unit 3, Learning Outcome 16)
An external factor that prevents an organization from pursuing particular approaches to meet its goals; for example, customer data is not harmonized within the organization, regionally or nationally, constraining the organization’s ability to offer effective customer service.
Data Architecture
(Syllabus Reference: Unit 3, Learning Outcome 18)
An architectural work product that is contractually specified and in turn formally reviewed, agreed, and signed off by the stakeholders. 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.
