Enterprise Architecture Modeling Foundation with ArchiMate 3

Explore Archimate, a visual language for describing enterprise architecture across strategy, business, application, technology, and implementation layers, using the core and full frameworks with the extended markup language exchange format.

Describe architecture descriptions using a viewpoint mechanism and architecture views to address stakeholder concerns, with Archimate language guiding the structure alongside the Toga standard and Segment Framework.

Explore the Archimate core language and metamodel, where a model comprises elements, relationships, and connectors, and abstract elements are specialized across business, application, and technology layers.

Compare the Archimate core and full framework, noting nine cells across three layers and three aspects, with the full framework adding two layers and a motivation aspect.

Explore how ArchiMate uses black box and white box views to abstract system behavior; examine nesting, color coding, and layer separation across business, application, and technology.

Explore Archimate’s metamodel: structure and behavior elements, active and passive elements, interfaces, and services. Grasp their shapes and key relationships like composition, aggregation, and realization.

Explore the metamodel fragment that specializes Archimate core elements across the business, application, technology, and physical layers, using composition and aggregation to model processes, functions, interactions, and collaborations.

Groupings and locations are Archimate composite elements that aggregate concepts or locate elements to structure architecture views and explain how processes realize a service.

Explore Archimate 3 generic relationships, including structural, dependency, dynamic, and other types, with from-to rules, relationship connectors, metamodel guidance, and roles like aggregation, realization, assignment, and composition.

Learn the four structural relationships in ArchiMate 3: composition, aggregation, assignment, and realization, and how they model whole part, combined, and behavioral links in enterprise architecture.

Explore dependency relationships in ArchiMate, detailing four subtypes—association, influence, access, and serving—and how each starts from a source element that supports, influences, accesses, or serves a target element.

Explore dynamic relationships in ArchiMate 3, distinguishing triggering and flow relations between behavior elements, where triggering expresses temporal or causal precedence and flow transfers information or money.

Explore specialization as the only other relationship in ArchiMate 3, showing how a generic element is specialized by a specific element, inspired by generalization, via notation or nesting.

Explore relationship connectors in ArchiMate, including end and or junctions, and how they connect concepts with participation and choice, illustrated by invoicing service realization and access request triggers.

Explore the motivation elements metamodel in Archimate 3, showing cross-functional driver, assessment, goal, outcome, principle, requirement, constraint, stakeholder, value, and meaning relationships across the core language.

Explore how stakeholders, drivers, and assessments steer enterprise architecture with Archimate and TOGAF, using SWOT insights and negation goals to align online portfolio management and profitability.

Explore how goals, outcomes, principles, requirements, and constraints relate in ArchiMate 3, showing how a goal yields outcomes and is realized through requirements and constraints within an enterprise system.

Stakeholders assign meanings to archimate elements, with motivation expressed as a noun phrase and value representing expected outcomes, such as push notifications delivering cost efficiency or peace of mind.

Explore how motivation elements connect to ArchiMate core elements through realization and influence, and how meaning and value relate to structure or behavior elements and stakeholders.

Explore the ArchiMate 3 strategy layer metamodel, detailing the four elements—course of action, value stream, capability, and resource—and how they realize goals by configuring resources and capabilities.

Identify resources as central elements across strategy, economics, technology, and portfolio management, alongside capabilities shaping competitive advantage. Classify resources as tangible, intangible, or human assets, and model them in archimate.

Examine behavior elements and value streams within the strategy layer, linking capabilities, courses of action, resources, and goals to outcomes in insurance product development.

Link the strategy layer to motivation and core elements. Show how internal and external behavior elements across business, application, and technology realize value streams and capabilities.

Explore the ArchiMate business layer metamodel to model an enterprise's operations with technology-independent elements, detailing active structure, internal behavior, and passive structure like actors, processes, events, services, and objects.

Explore how Archimate models depict active structure elements—business actors, roles, and collaborations—and how interfaces and services expose functionality to other actors or roles.

Explore Archimate internal and external behavior elements, including business processes, functions, and interactions, and how they trigger, realize, and deliver business services within an enterprise.

Explore the passive structure elements in the business layer, including business objects (abo), contracts, and representations, and see how they are realized by data objects and accessed across processes.

In ArchiMate, the composite element product sits in the business layer, aggregates services and passive structure elements under a contract, and can specify a product type offered to customers.

Explore how business, application, and technology elements connect through serving and realization relationships, interfaces, and services, with aggregation showing composites of technology and application elements.

Explore the application layer metamodel in Archimate 3, detailing elements including service, interface, event, and data object, and relationships: composition, aggregation, and specialization across passive structure, behavior, and active structure.

Explore active structure elements in ArchiMate, including application components, application collaborations, and interfaces, and learn how independently deployable units perform functions, expose services, and implement contracts.

this lecture outlines archimate application layer behaviors—functions, processes, and interactions—that realize application services, with verb-ing naming and examples like accounting and purchasing travel insurance.

Data object is the sole passive element on the application layer, a self-contained information unit such as a customer record or insurance claim, accessed by application functions, processes, and services.

Explore how application layer elements relate to business and technology layers through realization and serving relationships, with examples like customer data objects, payment processing, and artifacts.

Discover the Archimate technology layer metamodel, detailing six technology structure elements and five technology behavior concepts, and how their relationships model enterprise technology architecture.

Identify and model the active structure elements of the technology layer using ArchiMate, focusing on nodes, devices, and system software, and how paths and communication networks interconnect them.

Explore technology internal behavior elements—functions, processes, events, interactions, and services—in the ArchiMate metamodel. See how artifacts, passive structures, and technology events and services connect through time attributes and replication examples.

Explore passive structure elements in enterprise technology and how artifacts are realized by data objects, application components, or system software. See how web archive artifacts illustrate their Java archive composition.

Explore how business and application elements connect through serving and realization in ArchiMate 3. See an insurance workflow where CRM data management and payments are enabled by technology services.

Explore the metamodel of physical elements in ArchiMate, detailing material, equipment, facility, and distribution network as active or passive structures and their relations in a paperclip factory example.

Explore the active structure elements of the physical technology layer, including equipment, facility, and distribution network, with examples like MRI scanners, factories, and oil refineries.

Explore how passive structure elements model material, energy sources, and physical products in ArchiMate, with examples of material flows, equipment assembly lines, and intermodal distribution networks.

Explore the implementation and migration layer in Archimate, with red notation for elements like the implementation event, work package, deliverable, the metamodel, and the gap, noting the deprecated realization.

Model work packages as unique, one-off tasks within programs, project portfolios, or agile iterations to achieve goals under time and resource constraints, and link implementation events and milestones to deliverables.

Identify deliverables as results of work packages, depicted with ArchiMate shapes, and note gaps as differences between plateaus while applying TOGAF gap analysis in phases B–D to inform phase F.

Show how plateaus define stable ArchiMate models within a limited period and link work packages and programs to a stepwise migration, delivering business value and a strategic roadmap.

Map how implementation and migration elements relate to Archimate core elements via the metamodel. Link plateau, deliverables, and work packages to motivation elements like goals and requirements to realize architecture.