Help
Options
Didn't know it?
click below
click below
Knew it?
click below
click below
Don't Know
Remaining cards (0)
Know
retry
shuffle
restart
0:00
Embed Code - If you would like this activity on your web page, copy the script below and paste it into your web page.
Normal Size Small Size show me how
Normal Size Small Size show me how
TOGAF 9 Definitions
TOGAF 9.1 Definitions (Chapter 3)
| Question | Answer |
|---|---|
| Abstraction | A summarized or generalized description of detailed and complex content. Helps achieve consistent understanding to support communication and decision making. |
| Actor | An external or internal entity with a role that initiates or participates in activities. |
| Application | Deployed and operational IT system using data, and supported by tech components, supporting business functions and services. |
| 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 Platform | The collection of technology components of hardware and software that provide the services used to support applications. |
| Application Platform Interface (API) | "The interface, or set of functions, between application software and/or the application platform." |
| Architectural Style | The combination of distinctive features in which architecture is performed or expressed. |
| Architecture | Formal description, or detailed plan of system to guide implementation. Structure of components, inter-relationships, principles, guidelines governing design and evolution. |
| Architecture Building Block (ABB) | A constituent of the architecture model that describes a single aspect of the overall model. |
| Architecture Continuum | Repository of architectural elements with increasing detail and specialization; part of Enterprise Continuum. |
| Architecture Development Method (ADM) | The core of TOGAF. A step–by–step approach to develop and use an enterprise architecture. |
| Architecture Domain | "The architectural area being considered. There are four architecture domains within TOGAF: business, data, application, and technology." |
| Architecture Framework | "A conceptual structure used to develop, implement, and sustain an architecture." |
| Architecture Governance | Practice of controlling and managing enterprise and other architectures, including change management and operational governance. |
| Architecture Landscape | "The architectural representation of assets in use, or planned, by the enterprise at particular points in time." |
| Architecture Principles | 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 | Succinct definition of target architecture, describing business value and resulting enterprise changes. Communicates vision and and boundary for detailed architecture development. |
| Artifact | An architectural work product that describes an aspect of the architecture. |
| Baseline | Specification formally agreed upon, which serves as basis for further development or change, which must go through formal change management. |
| Boundaryless Information Flow | Representation of access to integrated information to support business improvements, of desired state of infrastructure specific to business needs or org. |
| Building Block | Potentially reusable component of business, IT or architectural capability which can be used to deliver architectures or solutions. |
| Business Architecture | "A description of the structure and interaction between the business strategy, organization, functions, business processes, and information needs." |
| 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 Service | Supports business capabilities through an explicitly defined interface and is explicitly governed by an organization. |
| Capability | Ability of organization, business or system process. |
| 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." |
| Communications and 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. |
| Concerns | Key, crucial interests to stakeholders in a system, which determine acceptability. |
| Constraint | External factor preventing organization from pursuing particular approaches to meet its goals. |
| 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 | Architectural work product that is contractually specified and formally reviewed. |
| 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 Continuum | "A categorization mechanism useful for classifying architecture and solution artifacts, both internal and external to the Architecture Repository, as they 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, 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 IS/IT landscape) to deliver the business outcome required." |
| 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 Technology (IT) | Lifecycle management of information and related technology within org. Also refers to all computer stuff. |
| Interoperability | Ability of two or more systems to work effectively together. |
| Logical | Implementation-independent definition of architecture, often grouping physical entities by purpose and structure (e.g., Java app server). |
| Metadata | "Data about data, of any sort in any media, that describes the characteristics of an entity." |
| Metamodel | A model that describes how and with what the architecture will be described in a structured way. |
| Method | "A defined, repeatable approach to address a particular type of problem." |
| Methodology | "A defined, repeatable series of steps to address a particular type of problem, which typically centers on a defined process, but may also include definition of content." |
| Model | Representation of subject of interest, which may be smaller, simplified or abstract. |
| 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." |
| 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 2009 to support the planned increase in market share"".""" |
| Patterns | "A technique for putting building blocks into context; for example, to describe a re–usable solution to a problem. Building blocks are what you use: patterns can tell you how you use them, when, why, and what trade–offs you have to make in doing so." |
| Performance Management | "The monitoring, control, and reporting of the enterprise architecture practice performance. Also concerned with continuous improvement." |
| 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." |
| Platform | A combination of technology infrastructure products and components that provides the prerequisites to host application software. |
| Platform Service | A technical capability required to provide enabling infrastructure that supports the delivery of applications. |
| Reference Model (RM) | Abstract framework for understanding significant relationships among entities of environment, for development of consistent standards or specs 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. Normally used in the phrases Technology Roadmap, Architecture Roadmap, etc." |
| Role | The usual or expected function of an actor, or the part somebody or something plays in a particular action or event. |
| 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 Orientation | A way of thinking in terms of services and service–based development and the outcomes of services. |
| Solution Architecture | Description of discrete and focused business operation or activity, and how IT supports it. Typically applies to single project/release. |
| 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, or organization (or classes thereof) with interests in, or concerns relative to, the outcome of the architecture. Different stakeholders with different roles will have different concerns." |
| Standards Information Base (SIB) | A database of standards that can be used to define the particular services and other components of an Organization–Specific Architecture. |
| Strategic Architecture | "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." |
| Target Architecture | The description of a future state of the architecture being developed for an organization. There may be several future states developed as a roadmap to show the evolution of the architecture to a target state. |
| Taxonomy of Architecture Views | The organized collection of all views pertinent to an architecture. |
| Technology Architecture | "A description of the structure and interaction of the platform 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. One or more Transition Architectures may be used to describe the progression in time from the Baseline to the Target Architecture. |
| View | Representation of related set of concerns (what you see). |
| Viewpoint | Definition of perspective from which view is taken (where you are looking from). |
| 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." |
Created by:
dhruvar427
Popular Computers sets