Enterprise Architecture Concepts

Enterprise Architecture (EA) is a strategic planning framework that aligns business and IT resources to support organizational goals and strategies. It provides a comprehensive view of an organization’s processes, information systems, personnel, and technologies. The primary objectives of EA are to improve business agility, ensure efficient IT resource utilization, and foster alignment between IT and business functions.

There are four architecture domains that are commonly accepted as subsets of an overall Enterprise Architecture:

Business Architecture

A representation of holistic, multi-dimensional business views of: capabilities, end-to-end value delivery, information, and organisational structure; and the relationships among these business views and strategies, products, policies, initiatives, and stakeholders.
Business Architecture relates business elements to business goals and elements of other domains.

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.

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.

Solution Architecture

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.

 Source: TOGAF Definitions


Architecture Roles


Key Definitions


Concept  Name

Description

Application

A software solution that provides functionality to business users. It encapsulates its behavior and data, provides services, and makes them available through interfaces.

Application event

An application behavior element that denotes a state change. Application functions and other application behavior may be triggered or interrupted by an application event. Also, application behavior may raise events that trigger other application behavior. Unlike processes, functions, and interactions, an event is instantaneous; it does not have duration. Events may originate from the environment of the organization (e.g., from an external application), but also internal events may occur generated by, for example, other applications within the organization. The name of an application event should preferably be a verb in the perfect tense; e.g., “claim received”.

Application function

An application function refers to the specific tasks, features, or operations that an application performs.  It refers to the specific tasks, features, or operations that an application performs. It describes what the application does in terms of its technical or operational behavior. Application functions are typically granular and focus on the mechanics of how the application works.

Application service

An explicitly defined exposed application behavior. An application service exposes the functionality of components to their environment. This functionality is accessed through one or more application interfaces. An application service is realized by one or more application functions that are performed by the component. It may require, use, and produce data objects. The name of an application service should preferably be a verb ending with “ing”; e.g., “transaction processing”. Also, a name explicitly containing the word “service” may be used. 

Application data

Data structured for automated processing

Application interface

A point of access where application services are made available to a user, another application component, or a node. An application interface specifies how the functionality of a component can be accessed by other elements. An application interface exposes application services to the environment. The same application service may be exposed through different interfaces, and the same interface may expose multiple services. The name of an application interface should preferably be a noun.

Application reference model (arm)

The Application Reference Model (ARM) is a business-driven, functional framework that supports the enterprise. It classifies application capabilities with respect to how they support business and/or performance objectives. The ARM is envisioned being structured across horizontal service areas that, independent of the business functions, can provide a leverageable foundation for reuse of applications, application capabilities, components, and business service. The model aids in recommending applications to support the reuse of business components and services across the organisation.

Artefact

An artifact represents a tangible element in the IT world. Artifact is a specialization of technology object. It is typically used to model (software) products such as source files, executables, scripts, database tables, messages, documents, specifications, and model files. An instance (copy) of an artifact can be deployed on a node. An artifact could be used to represent a physical data component that realizes a data object. The name of an artifact should preferably be the name of the file it represents; e.g., “order.jar”. 

Business actor

A business entity that is capable of performing behavior. A business actor is a business entity as opposed to a technical entity; i.e., it belongs to the Business Layer. Actors may, however, include entities outside the actual organization; e.g., customers and partners. A business actor may be assigned to one or more business roles. It can then perform the behavior to which these business roles are assigned. A business actor can be aggregated in a location. The name of a business actor should preferably be a noun.

Business collaboration

An aggregate of two or more business internal active structure elements that work together to perform collective behavior. A collaboration is a (possibly temporary) collection of business roles or actors within an organization, which perform collaborative behavior (interactions). The name of a business collaboration should preferably be a noun. It is also common to leave a business collaboration unnamed.

Business event

A business behavior element that denotes an organizational state change. It may originate from and be resolved inside or outside the organization. Business processes and other business behavior may be triggered or interrupted by a business event. Also, business processes may raise events that trigger other business processes, functions, or interactions. Unlike business processes, functions, and interactions, a business event is instantaneous: it does not have duration. The name of a business event should preferably be a verb in the perfect tense; e.g., claim received.

Business function

A business function refers to a specific activity, process, or task that an organization performs to achieve its objectives. Business Functions are typically operational in nature and describe what the organization does in terms of day-to-day activities. They are often tied to specific departments or roles within the organization.

Business interface

A point of access where a business service is made available to the environment. A business interface exposes the functionality of a business service to other business roles or actors. It is often referred to as a channel (telephone, Internet, local office, etc.). The same business service may be exposed through different interfaces. The name of a business interface should preferably be a noun.

Business service

An explicitly defined exposed business behavior. A business service exposes the functionality of business roles or collaborations to their environment. This functionality is accessed through one or more business interfaces. The name of a business service should preferably Notation be a verb ending with “ing”; e.g., transaction processing. Also, a name explicitly containing the word “service” may be used.

Business process

A sequence of business behaviors that achieves a specific outcome such as a defined set of products or business services. A business process describes the internal behavior performed by a business role that is required to produce a set of products and services. For a consumer, the products and services are relevant and the behavior is merely a Notation black box, hence the designation “internal”. The name of a business process should clearly indicate a predefined sequence of actions, and may include the word “process”.

Business role

The responsibility for performing specific behavior, to which an actor can be assigned, or the part an actor plays in a particular action or event. Business roles with certain responsibilities or skills are assigned to business processes or business functions. A business role may be assigned to one or more business processes or business functions, while a business actor may be assigned to one or more business roles. The name of a business role should preferably be a noun.

Capability

Within The Open Group (TOGAF), a capability is defined as “an ability to do something”. An ability that an organization, person, or system possesses. A business capability represents the ability for a business to do something. Critically, a business capability delineates what a business does without attempting to explain how, why, or where the business uses the capability.

Communication network

A set of structures that connects computer systems or other electronic devices for transmission, routing, and reception of data or data-based communications such as voice and video. A communication network represents the physical communication infrastructure.

Contract

A formal or informal specification of an agreement between a provider and a consumer that specifies the rights and obligations associated with a product and establishes functional and non-functional parameters for interaction. The contract element may be used to model a contract in the legal sense, but also a more informal agreement associated with a product. It may also be or include a Service-Level Agreement (SLA), describing an agreement about the functionality and quality of the services that are part of a product. A contract is a specialization of a business object. The name of a contract is preferably a noun.

Cots

COTS stands for Commercial Off-The-Shelf. It refers to ready-made products that are available for purchase by the general public and can be used as-is, without the need for customization. These products are typically mass-produced and sold in large quantities, making them cost-effective and readily available.

Custom

Custom-built software, also known as bespoke software, is specifically designed and developed to meet the unique requirements of a particular organization or user.

Data entity

A self-contained piece of information that has a clear meaning to the business and can be defined with attributes. Example: Customer Account or Purchase Order. 

Device

A physical IT resource upon which system software and artifacts may be stored or deployed for execution. A device is a specialization of a node that represents a physical IT resource with processing capability. It is typically used to model hardware systems such as mainframes, PCs, or routers. Usually, they are part of a node together with system software. Devices may be composite; i.e., consist of sub-devices. The name of a device should preferably be a noun referring to the type of hardware; e.g., “IBM System z mainframe”.

Driver

An external or internal condition that motivates an organization to define its goals and implement the changes necessary to achieve them. Drivers may be internal, in which case they are usually associated with a stakeholder, and are often called “concerns”. Drivers of change may also be external; e.g., economic changes or changing legislation. The name of a driver should preferably be a noun.

Goal

A high-level statement of intent, direction, or desired end state for an organization and its stakeholders. Goals are generally expressed using qualitative words; e.g., “increase”, “improve”, or “easier”. Goals can also be decomposed. 

Infrastructure as a Service (iaas)

Infrastructure as a Service (IaaS) is a cloud computing model that provides virtualized computing resources over the internet.

Interface

A point of access that an application makes available to other applications.

Example: Customer Claims API.

Location

A geographical place, or physical space, where activity happens or where an element of the architecture exists. Example: London

Location

A geographical place, or physical space, where activity happens or where an element of the architecture exists. Example: London

Node

A computational or physical resource that hosts, manipulates, or interacts with other computational or physical resources. Nodes are active structure elements that perform technology behavior and execute, store, and process technology objects such as artifacts (or materials). Nodes can be interconnected by paths. The name of a node should preferably be a noun.

Objective

A measurable outcome that contributes to the achievement of a goal. Objectives are normally SMART (specific, measurable, achievable, relevant, and time-bound).

Example: Increase CSAT Score by 20% by end 2020.

On-premise

On-premise deployment refers to the installation and operation of software or hardware within the physical premises of an organization, such as in its own data centers or server rooms.

Outcome

An end result that has been achieved. Outcomes are high-level, business-oriented results produced by capabilities of an organization. Outcome names should unambiguously identify end results that have been achieved in order to avoid confusion with actions or goals. Outcome names should consist of a noun identifying the end result followed by a past tense verb or adjective indicating that the result has been achieved; e.g., “First-place ranking achieved” and “Key supplier partnerships in place”. 

Plateau

A stable state of the architecture that exists during a limited period of time

Platform as a Service (paas)

Platform as a Service (PaaS) is a cloud computing model that provides a platform allowing customers to develop, run, and manage applications without dealing with the underlying infrastructure

Principle

A guiding statement intended to structure and constrain architectural decision making, processes and operations. Example: Cloud first Technology Architecture 

Principle

A qualitative statement of intent that should be met by the architecture. Similar to requirements, principles define intended properties of systems. However, in contrast to requirements, principles are broader in scope and more abstract than requirements. A principle is motivated by some goal or driver. The name of a principle should be easily understood, whether with a word or two, or even a short sentence.

Process

A sequence of activates that describe how a business outcome is achieved.

Example: Invoice Customer.

Product

A coherent collection of services and/or passive structure elements, accompanied by a contract/set of agreements, which is offered as a whole to (internal or external) customers. This covers both intangible, services-based, or information products that are common in information-intensive organizations, and tangible, physical products. Notation “Buying” a product gives the customer the right to use the associated services. The name of a product is usually the name which is used in the communication with customers, or possibly a more generic noun (e.g., “travel insurance”).

Project

A package of work that is constrained by requirements and delivers or augments a capability.

Example: CRM Tool Implementation.

Requirement

A statement describing a condition that should be met by a project, or aspect of an architecture. Example: Conform to ISA 28001 Spec

Risk

A statement describing a possible hazard that may relate to an aspect of the architecture.

Example: Leak of sensitive Data.

Role

The responsibility for performing a function within a process or organization.

Example: Accountant.

Software as a Service (saas)

Software as a Service (SaaS) is a cloud computing model where software applications are delivered over the internet as a service.

System software

Software that provides or contributes to an environment for storing, executing, and using software or data deployed within it. System software is a specialization of a node that is used to model the software environment in which artifacts run. This can be, for example, an operating system, a JEE application server, a database system, or a workflow engine.

Technology

A software or hardware solution on which application run or other components run. Example: Microsoft SQL Server2022 

Technology category

 A classification element used to categorise Technology. It constitutes the technology reference model taxonomy as a hierarchical structure. Example: Enterprise Communication Application Architecture

Technology function

A collection of technology behavior that can be performed by a node. A technology function describes the internal behavior of a node; for the user of a node that performs a technology function, this function is invisible. If its behavior is exposed externally, this is done through one or more technology services.

Technology interface

A point of access where technology services offered by a node can be accessed. A technology interface specifies how the technology services of a node can be accessed by other nodes. A technology interface exposes a technology service to the environment. The same service may be exposed through different interfaces. The name of a technology interface should preferably be a noun.

Technology reference model (trm)

The Technology Reference Model defines a standard, layered view of the logical Technology Components in scope for the enterprise.

Technology service

An explicitly defined exposed technology behavior. A technology service exposes the functionality of a node to its environment. This functionality is accessed through one or more technology interfaces. It may require, use, and produce artifacts. The name of a technology service should preferably be a verb ending with “ing”; e.g., “messaging”. Also, a name explicitly containing the word “service” may be used.

Value stream

A sequence of activities that create an overall result for a customer, stakeholder, or end user

Work package

A series of actions identified and designed to achieve specific results within specified time and resource constraints



Source: Archimate Language






Comments