TOGAF Definitionen

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.

A representation of a subject of interest. A model provides a smaller scale, simplified, and/or abstract representation of the subject matter. A model is constructed as a "means to an end". In the context of enterprise architecture, the subject matter is a whole or part of the enterprise and the end is the ability to construct "views" that address the concerns of particular stakeholders; i.e., their "viewpoints" in relation to the subject matter.

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 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".

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.

The monitoring, control, and reporting of the enterprise architecture practice performance. Also concerned with continuous improvement.

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.

A combination of technology infrastructure products and components that provides that prerequisites to host application software.

A technical capability required to provide enabling infrastructure that supports the delivery of applications.

A reference model is 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. A reference model is based on a small number of unifying concepts and may be used as a basis for education and explaining standards to a non-specialist. A reference model is not directly tied to any standards, technologies, or other concrete implementation details, but it does seek to provide common semantics that can be used unambiguously across and between different implementations.

A system that manages all of the data of an enterprise, including data and process models and other enterprise information. Hence, the data in a repository is much more extensive than that in a data dictionary, which generally defines only the data making up a database.

A statement of need that must be met by a particular architecture or work package.

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.

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.

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

A way of thinking in terms of services and service-based development and the outcomes of services.

An architectural style that supports service orientation. It has the following distinctive features: - It is based on the design of the services - which mirror real-world business activities - comprising the enterprise (or inter-enterprise) business processes. - Service representation utilizes business descriptions to provide context (i.e., business process, goal, rule, policy, service interface, and service component) and implements services using service orchestration. - It places unique requirements on the infrastructure - it is recommended that implementations use open standards to realize interoperability and location transparency. - Implementations are environment-specific - they are constrained or enabled by context and must be described within that context. - It requires strong governance of service representation and implementation. - It requires a "Litmus Test", which determines a "good service".

A description of a discrete and focused business operation or activity and how IS/IT supports that operation. A Solution Architecture typically applies to a single project or project release, assisting in the translation of requirements into a solution vision, high-level business and/or IT system specifications, and a portfolio of implementation tasks.

A candidate solution which conforms to the specification of an Architecture Building Block (ABB).

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.

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.

A database of standards that can be used to define the particular services and other components of an Organization-Specific 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.

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.

The organized collection of all views pertinent to an architecture.

A description of the structure and interaction of the platform services, and logical and physical technology components.

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.

The representation of a related set of concerns. A view is what is seen from a viewpoint. An architecture view may be represented by a model to demonstrate to stakeholders their areas of interest in the architecture. A view does not have to be visual or graphical in nature.

A definition of the perspective from which a view is taken. It is a specification of the conventions for constructing and using a view (often by means of an appropriate schema or template). A view is what you see; a viewpoint is where you are looking from - the vantage point or perspective that determines what you see.

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.