Karteikarten
Togaf-Vocab
Karten in diesem Stapel (30)
- 1AbstractionThe technique of providing summarized or generalized descriptions of detailed and complex content.
Abstraction, as in "level of abstraction", can also mean providing a focus for analysis that is concerned with a consistent and common level of detail or abstraction. Abstraction in this sense is typically used in architecture to allow a consistent level of definition and understanding to be achieved in each area of the architecture in order to support effective communication and decision-making. It is especially useful when dealing with large and complex architectures as it allows relevant issues to be identified before further detail is attempted. - 2ActorA person, organization, or system that has a role 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. In the automotive industry, an original equipment manufacturer would be considered an actor by an automotive dealership that interacts with its supply chain activities.
- 3ApplicationA 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.
- 4Application ArchitectureA description of the structure and interaction of the applications as groups of capabilities that provide key business functions and manage the data assets.
- 5Application PlatformThe collection of technology components of hardware and software that provide the services used to support applications.
- 6Application Platform Interface (API)The interface, or set of functions, between application software and/or the application platform.
- 7Architecture1. A formal description of a system, or a detailed plan of the system at component level, to guide its implementation (source: ISO/IEC 42010:2007).
2. The structure of components, their inter-relationships, and the principles and guidelines governing their design and evolution over time. - 8Architecture Building Block (ABB)A constituent of the architecture model that describes a single aspect of the overall model.
- 9Architecture ContinuumA part of the Enterprise Continuum. A repository of architectural elements with increasing detail and specialization. This Continuum begins with foundational definitions like 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.
- 10Architecture Development Method (ADM)The core of TOGAF. A step-by-step approach to develop and use an enterprise architecture.
- 11Architecture DomainThe architectural area being considered. There are four architecture domains within TOGAF: business, data, application, and technology.
- 12Architecture FrameworkA conceptual structure used to develop, implement, and sustain an architecture.
- 13Architecture GovernanceThe practice and orientation by which enterprise architectures and other architectures are managed and controlled at an enterprise-wide level. It is concerned with change processes (design governance) and operation of product systems (operational governance).
- 14Architecture LandscapeThe architectural representation of assets in use, or planned, by the enterprise at particular points in time.
- 15Architecture PrinciplesA qualitative statement of intent that should be met by the architecture. Has at least a supporting rationale and a measure of importance.
- 16Architecture VisionA 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.
- 17ArtifactAn architectural work product that describes an aspect of the architecture.
- 18BaselineA 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.
- 19Boundaryless Information Flow1.A trademark of The Open Group.
2. 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.
An infrastructure that provides Boundaryless Information Flow has open standard components that provide services in a customer's extended enterprise that:
>Combine multiple sources of information
>Securely deliver the information whenever and wherever it is needed, in the right context for the people or systems using that information. - 20Building BlockRepresents 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". - 21Business ArchitectureA description of the structure and interaction between the business strategy, organization, functions, business processes, and information needs.
- 22Business FunctionDelivers business capabilities closely aligned to an organization, but not necessarily explicitly governed by the organization.
- 23Business GovernanceConcerned with ensuring that the business processes and policies (and their operation) deliver the business outcomes and adhere to relevant business regulation.
- 24Business ServiceSupports business capabilities through an explicitly defined interface and is explicitly governed by an organization.
- 25CapabilityAn 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. For example, marketing, customer contact, or outbound telemarketing.
- 26Capability ArchitectureA highly detailed description of the architectural approach to realize a particular solution or solution aspect.
- 27Capability IncrementA discrete portion of a capability architecture that delivers specific value. When all increments have been completed, the capability has been realized.
- 28Communications and Stakeholder ManagementThe 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.
- 29ConcernsThe key interests that are crucially important to the stakeholders in a system, and determine the acceptability of the system. Concerns may pertain to any aspect of the system's functioning, development, or operation, including considerations such as performance, reliability, security, distribution, and evolvability.
- 30ConstraintAn 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.
Informationen
- Beschreibung
- This flash card is for learned vocabulary.
- Erstellt von
- sumit singh
- Aufrufe
- 54
- Tags
- Bewertung