ArchiMate 3 Foundation flashcards

32 cards. Read the term and the definition here. The deck at the top of this page is optional.

Active structure element

An element that represents a subject capable of performing behavior, such as an actor, role, component, or node. It is the 'who' or 'what' in a model.

Behavior element

An element representing something that happens over time, such as a process, function, service, event, or interaction. It is performed by active structure elements.

Passive structure element

An element representing an object that is acted upon but does not itself perform behavior, such as a business object, data object, or artifact.

Composition relationship

A structural relationship indicating a whole is composed of parts, drawn with a filled diamond at the whole end. The parts cannot exist independently of the whole.

Aggregation relationship

A structural relationship indicating a weak whole-part grouping, drawn with an open diamond at the whole end. Parts may exist independently of the whole.

Realization relationship

A relationship meaning a more concrete element realizes a more abstract one, drawn as a dashed line with a hollow triangle. Often links a service to its implementing behavior.

Serving relationship

A dependency relationship showing one element provides functionality to another, drawn as a dashed line with an open arrowhead from provider to consumer.

Assignment relationship

A relationship linking an active structure element to the behavior it performs or the passive element it holds, drawn as a solid line with an open arrowhead.

Specialization relationship

A relationship meaning one element is a more specific kind of another, drawn as a solid line with a hollow triangle. It supports inheritance and reuse in models.

Framework rows and columns

The ArchiMate framework arranges aspects as rows (active structure, behavior, passive structure) and layers as columns (Business, Application, Technology, and extensions).

Business layer elements

The layer containing business actors, roles, collaborations, interfaces, services, processes, functions, events, objects, and representations used to model the enterprise's business behavior and structure.

Application layer elements

The layer containing application components, collaborations, interfaces, services, functions, processes, events, data objects, and interactions used to model software behavior and structure.

Technology layer elements

The layer containing nodes, devices, system software, communication networks, services, functions, processes, events, artifacts, and paths used to model infrastructure.

Strategy layer elements

An extension layer modeling capability, resource, value stream, and course of action concepts to describe how an enterprise intends to achieve its goals.

Motivation layer elements

An extension layer containing stakeholder, driver, assessment, goal, requirement, constraint, and value concepts used to explain why architecture decisions are made.

Implementation and migration elements

An extension layer with work package, deliverable, implementation event, plateau, and gap concepts used to model change programs and transition states.

Generic metamodel types

The abstract element types (active structure element, behavior element, passive structure element) that every concrete layer element specializes within the ArchiMate metamodel.

View versus viewpoint

A view is the actual selected model content shown to a stakeholder; a viewpoint is the specification or convention that determines how that view is built.

Layered viewpoint

A viewpoint showing vertical alignment across business, application, and technology layers, illustrating how higher-layer services are supported by lower-layer elements.

Organization viewpoint

A viewpoint focused on the internal structure of an enterprise, showing actors, roles, collaborations, and their relationships without emphasizing processes.

Process viewpoint

A viewpoint modeling business processes, their sub-processes, and the business objects and services they use or produce, emphasizing behavior.

Application usage viewpoint

A viewpoint showing how applications support business processes and how applications relate to each other through application services.

Technology usage viewpoint

A viewpoint showing how technology infrastructure elements such as nodes and devices support applications and business processes.

Implementation and migration viewpoint

A viewpoint showing programs, projects, work packages, plateaus, and gaps that describe the transition from a current to a target state.

Stakeholder concern in views

Each view should address a specific stakeholder concern; including elements unrelated to that concern reduces clarity and is discouraged in modeling practice.

ArchiMate purpose

An open, vendor-neutral modeling language standardized by The Open Group for describing, analyzing, and visualizing enterprise architecture across domains.

Combining with BPMN

ArchiMate can be combined with BPMN for detailed process modeling and with UML for software design, complementing rather than replacing those notations.

Model interchange format

ArchiMate models can be exchanged between tools using an XML-based interchange format, supporting portability and tool interoperability.

Certification levels

The certification program offers Foundation and Practitioner levels; Foundation tests knowledge of concepts, notation, and basic modeling rather than advanced application.

Impact analysis use

ArchiMate models support impact analysis by tracing relationships so changes to one element can be assessed against dependent elements across layers.

Gap analysis use

Using current and target state models plus gap elements, ArchiMate supports identifying differences and planning the work packages needed to close them.

Motivation-to-implementation traceability

Tracing goals and requirements through behavior and structure to work packages supports architecture governance and controlled change management.