Viewpoint as template This viewpoint serves as a starting point and template for the architecture models within {Organization}. That is why they are locked and managed by the model managers. If you have a suggestion for improvement, please contact the model managers Within the viewpoints we work with:

• Primary elements (green border), these are elements that should in principle be elaborated in these diagrams are
• Secondary elements (orange border) are elements that maybe used in these diagrams

Architecture Building Block.

The technique of providing summarized or generalized descriptions of detailed and complex content.

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.

Architecture Development Method.

A description of the structure and interaction of the applications as groups of capabilities that provide key business functions and manage the data assets.

Naming Conventions Usage: Noun (name of the package). For example: MsWord, Autonomy Federator

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.

Naming Conventions Usage: verb. Example: Billing, Search, Indexing.

Naming Conventions Usage: Noun. Example: Search Gui, VM—search service Web service.

The collection of technology components of hardware and software that provide the services used to support applications.

Naming Conventions Usage: Noun in the ing form. For example: Transaction processing, Indexing.

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.

A constituent of the architecture model that describes a single aspect of the overall model.

A part of the Enterprise Continuum. A repository of architectural elements with increasing detail and specialization.

The core of the TOGAF framework. A multi-phase, iterative approach to develop and use an Enterprise Architecture to shape and govern business transformation and implementation projects.

The architectural area being considered. The TOGAF framework has four primary architecture domains: business, data, application, and technology. Other domains may also be considered (e.g., security).

A conceptual structure used to plan, develop, implement, govern, and sustain an architecture.

The practice of monitoring and directing architecture-related work. The goal is to deliver desired outcomes and adhere to relevant principles, standards, and roadmaps.

The architectural representation of assets in use, or planned, by the enterprise at particular points in time.

A representation of a subject of interest.

A qualitative statement of intent that should be met by the architecture.

A representation of a system from the perspective of a related set of concerns.

A specification of the conventions for a particular kind of architecture view.

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.

An architectural work product that describes an aspect of the architecture.

Usage: noun based on the organization naming the organization of tables in databases, XML files, etc.

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.

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.

A (potentially re-usable) component of enterprise capability that can be combined with other building blocks to deliver architectures and solutions.

Naming conventions: Usage Noun e.g. Government employee, Company, Citizen. Avoid User, system.

A representation of holistic, multi-dimensional business views of: capabilities, end-to-end value delivery, information, and organizational structure; and the relationships among these business views and strategies, products, policies, initiatives, and stakeholders.

A particular ability that a business may possess or exchange to achieve a specific purpose.

Naming Conventions Usage: verb. Example: Support, Manage Service.

Delivers business capabilities closely aligned to an organization, but not necessarily explicitly governed by the organization.

Concerned with ensuring that the business processes and policies (and their operation) deliver the business outcomes and adhere to relevant business regulation.

Naming Conventions Usage: Noun. For example: Counter, telephone, e-mail, form and internet.

A model describing the rationale for how an enterprise creates, delivers, and captures value.

Naming Conventions Usage: Singular noun. For example: Invoice, policy, Fault report Logical name. Avoid technical names.

Naming conventions Usage: Verb in the imperative mood followed by a noun (singular), for example: Check order, make quotation, Report malfunction. Avoid Manage, process, register ……

Naming Conventions Usage: Noun. For example: Collaboration, Message Exchange Extra: Name from the PDC (ing form).

Supports business capabilities through an explicitly defined interface and is explicitly governed by an organization.

An ability that an organization, person, or system possesses.

A highly detailed description of the architectural approach to realize a particular solution or solution aspect.

A discrete portion of a capability architecture that delivers specific value. When all increments have been completed, the capability has been realized.

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.

An interest in a system relevant to one or more of its stakeholders.

Direction and focus provided by strategic goals and objectives, often to deliver the value proposition characterized in the business model.

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.

Naming Conventions Usage: Singular noun. For example: Search query, Search result Logical name. Avoid technical names such as file, database.

An architectural work product that is contractually specified and in turn formally reviewed, agreed, and signed off by the stakeholders.

The highest level (typically) of description of an organization and typically covers all missions and functions. An enterprise will often span multiple organizations.

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.

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.

A structure for content or process that can be used as a tool to structure thinking, ensuring consistency and completeness.

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.

The discipline of monitoring, managing, and steering a business (or IS/IT landscape) to deliver the business outcome required.

Any communication or representation of facts, data, or opinions, in any medium or form, including textual, numerical, graphic, cartographic, narrative, or audio-visual forms.

An implementation-independent definition of the architecture, often grouping related physical entities according to their purpose and structure.

Data about data, of any sort in any media, that describes the characteristics of an entity.

A model that describes how and with what the architecture will be described in a structured way.

A defined, repeatable approach to address a particular type of problem.

Conventions for a type of 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.

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

An articulation of the relationships between the primary entities that make up the enterprise, its partners, and stakeholders.

A technique for putting building blocks into context; for example, to describe a re-usable solution to a problem.

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.

Architecture Principle.

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 system that manages all of the data of an enterprise, including data and process models and other enterprise information.

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

Reference Model.

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.

Solution Building Block.

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

Viewing an enterprise, system, or building block in terms of services provided and consumed.

A collection of services, potentially an interface definition.

An architectural style that supports service orientation.

Standards Information Base.

Service-Oriented Architecture.

A description of a discrete and focused business operation or activity and how IS/IT supports that operation.

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

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, organization, or class thereof, having an interest in a system.

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.

The organized collection of all architecture views pertinent to an architecture.

A description of the structure and interaction of the technology services and technology components.

Naming Conventions Usage: noun. For example, Backup and Restore, Printing, Scanning, Searching (ing form).

Naming Conventions Usage: Noun. For example: Sybase Open Client, CPS, GFX, MQ, EWMS, XML.

Naming Conventions Usage: Noun. For example: Application Server, machine name.

Naming Conventions Usage: Noun in the ing form. For example: Messaging, Broadcasting.

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

A formal description of one state of the architecture at an architecturally significant point in time.

A representation of an end-to-end collection of value-adding activities that create an overall result for a customer, stakeholder, or end user.

Architecture View.

Architecture Viewpoint.

A collection of the specifications of architecture viewpoints contained in the Reference Library portion of the Architecture Repository.

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.