ArchiMate 3 Practitioner flashcards
ArchiMate 3 Practitioner · Build recall with a focused review session.
32 cards. Read the term and the definition here. The deck at the top of this page is optional.
- ArchiMate core layers
- Business, Application, and Technology are the three core structural layers; Strategy and Physical extend them, while Motivation and Implementation & Migration are cross-cutting aspects.
- Active structure element
- An element representing the subject that performs behavior, such as a business actor, application component, or technology node. It is assigned to behavior.
- Passive structure element
- An element representing the object that behavior acts upon, such as a business object, data object, or artifact. Behavior accesses it via access relationships.
- Composition relationship
- A structural relationship in which a whole owns its parts exclusively; each part has exactly one composing parent and cannot be shared.
- Aggregation relationship
- A structural relationship in which a whole groups parts that may be shared with other wholes and may exist independently of the whole.
- Realization relationship
- A relationship in which a concrete element realizes a more abstract element, such as an application component realizing an application service.
- Serving relationship
- A dependency in which one element provides functionality to another; it is the weakest cross-element dependency and is used for service provision.
- Access relationship type
- A relationship from behavior or active structure to passive structure, qualified as read, write, or read-write to express data usage.
- Junction element
- An AND or OR connector used where a relationship splits into multiple paths, making the split semantics explicit in process or event models.
- Grouping element
- A container that groups elements of any layer without adding semantics; used to demarcate domains or boundaries, never to imply ownership.
- Cross-layer service chain
- Business service realized by a process, served by an application service realized by a component, which is assigned to a technology node.
- Business interface usage
- An access point that exposes a service provided by a business role or actor; it represents a point of access, not behavior itself.
- Application interface usage
- An access point through which an application component exposes an application service to other components or to business behavior.
- Data object realization
- A business object may be realized by an application data object, which in turn may be realized by a technology artifact, tracing data across layers.
- Triggering vs flow
- Triggering links an event or behavior to the behavior it causes; flow links behaviors and carries value or messages between them.
- Capability realization
- A strategy-layer capability is realized by a course of action, which is realized by business processes or functions, connecting strategy to operations.
- Serving in process support
- A business process is served by an application service, which is realized by an application component assigned to a technology node.
- Assignment relationship
- A relationship connecting an active structure to the behavior it performs or to another active structure it contains responsibility for.
- View versus viewpoint
- A viewpoint defines selection criteria and allowed element types; a view is the actual selection of model elements produced using that viewpoint.
- Derivation direction rule
- Concrete elements realize abstract elements; the abstract element is the derived target and the concrete element is the source of the derivation.
- Logical component aggregation
- Detailed application components are composed into a logical component, which the detailed components then realize in a higher-level derived view.
- Process to function collapse
- When deriving a capability-level view, a business process is represented by a business function that realizes the corresponding capability.
- Plateau and gap
- A plateau is a stable implementation state; a gap is a missing element between plateaus; a work package delivers a deliverable realizing a plateau.
- Derived view traceability
- Every relationship in a derived view must trace to a source-model relationship or be explicitly justified as a new abstraction.
- Derivation mechanisms
- Specialization and realization are the two derivation mechanisms; composition and aggregation are structural decomposition and must not replace realization.
- Business-to-application derivation
- Deriving an application view keeps serving relationships but replaces business actors with application components assigned to the corresponding application services.
- Viewpoint selection by concern
- Management concerns map to capability and value views; architects to cross-layer traceability; operations to technology and application usage views.
- Layered viewpoint purpose
- Shows services per layer and their dependencies, communicating cross-layer coherence without exposing internal process detail.
- Application usage viewpoint
- Shows how applications support business processes; it is the standard view for business-IT alignment discussions with stakeholders.
- Motivation element role
- Goals, requirements, constraints, drivers, and assessments justify model choices; they influence rather than structure, attaching via influence or realization.
- Implementation migration view
- Communicates plateaus, gaps, and work packages to program managers; motivation elements appear only when a goal-driven roadmap is needed.
- Traceability matrix use
- A matrix derived from realization and serving relationships provides the evidence base for impact analysis during stakeholder change requests.