EA Diagrams: The Enterprise Architect with Archi 5.2 part 1

Organize architecture concepts and the modeling language hierarchy, using UML diagrams to identify element, relationship, and connector types, and understand active versus passive structure elements and dependencies.

Explore how models consist of concepts—either relationships or elements—and how a metamodel defines semantics and the allowed relationships, such as a business actor assigned to a business process.

Explore the core of the modeling language—the central part that defines concepts and relationships to model enterprise architectures using active, passive, and behavior elements.

Define the core framework of the enterprise architecture modeling language, detailing its layered structure and the active, behavior, and passive aspects across business, application, and technology.

Broaden your view of the enterprise architecture modeling framework by adding new layers—strategy, physical, implementation, and migration—with active and passive elements and a motivation aspect to model the enterprise vision.

Explore how abstraction in enterprise architecture separates internal and external elements, contrasts active structure with behavior, and links conceptual to physical levels, emphasizing types over instances in non-executable models.

Clarify how concepts are abstract definitions and notation is their graphical implementation, using business objects as representations, and acknowledge multiple modeling languages and personal language definitions.

Explore nesting in enterprise modeling, placing one element inside another to abstract relationships. See how composition, aggregation, or specialization of the same type enable equivalent diagrams and simplify architecture.

Standardize colors across enterprise diagrams to denote business, application, and technology layers, using yellow, blue, and green, with purple as a business element example; Arche is preconfigured to this scheme.

Define the metamodel and its rules for elements and relationships across the business, application, and technology layers, including capability, course of action, events, resources, external/internal behavior, services, and active/passive elements.

Define aspect in enterprise architecture modeling as a grouping of elements. Classify them as active, behavior, or passive by how they act or are acted upon, noting motivation elements.

Explore external active structural elements and interfaces, services, and external behavior, plus flow relationships and events, then examine internal active structure, composition and serving relationships, with real-world examples.

Identify active structure elements across business, application, and technology layers. Learn how internal elements perform or consume behavior and how external interfaces provide access, using color-coded notations for each layer.

Explore behavior elements in enterprise architecture: processes, functions, services and events; distinguish internal versus external behavior, and see how services hide internal processes while events trigger state changes.

Identify passive structure elements as objects that can be created, modified, read, or deleted during execution, and that receive the consequences of behavior rather than executing it.

Clarify how enterprise collaborations form aggregates of active elements, distinguishing aggregation from composition, and connect collaborations to interactions across business, application, and technology layers in Archi 5.2.

Examine active structure and behavior elements across the strategy, business, application, technology, and physical layers, and identify core elements in the core layers—business, application, and technology.

Identify the motivation and composite elements that extend enterprise architecture beyond the core model, show grouping and location elements, and explain how drivers and locations shape architecture.

Explore the overview of modeling relationships in enterprise architectures, including structural relationships (realization, assignment, aggregation, composition), dependency relationships (association, influence, access, serving), and dynamic relationships, with relationship connectors (and/or junctions).

Explore Archi's structural relationships—composition (strongest, same-type elements, black diamond), aggregation, assignment, and realization—and their use in runtime realization with a business service example.

Explore dependency relationships in enterprise architecture diagrams, including serving, access, influence, and association, with examples like online customer registration and invoice processes.

Explore dynamic relationships in enterprise architecture, focusing on triggering relationships where business events cause processes, and flow relationships that model information, money, or goods moving between elements.

Explore specialization as a subtype within other relationships in UML notation, modeling an element and its concrete or abstract counterpart, such as an invoice with physical and digital representations.

Explore relationship connectors, including split and join, and end, or, and or junctions for realization and triggering. See how multiple inputs and outputs affect a business service and invoice specialization.

Learn to define the enterprise architecture vision and its rationale, linking vision, mission, objectives, principles, requirements, and constraints in Archi 5.2 modeling.

Explore the metamodel of the motivational aspect in enterprise architecture, detailing how stakeholders, meanings and values relate to drivers, assessments, goals, outcomes, principles, requirements, and constraints.

Explore the notation for each element—stakeholders, drivers, assessments, goals, outcomes, principles, requirements, constraints, meanings, and values—defined in the enterprise motivation metamodel.

Discover how drivers and assessments shape enterprise architecture vision by linking stakeholders to drivers like government regulation and customer satisfaction, using aggregation to reveal sub-motivational elements.

Define goals from assessments to drive outcomes and capabilities, then apply principles, requirements, and constraints across the enterprise architecture to realize measurable improvements.

Explore how value and meaning from the stakeholder perspective shape enterprise architecture elements, with an online buying service and its data objects illustrating tangible and intangible benefits.

Link vision to enterprise architecture by tying stakeholders, business actors, and application services to strategy, business, and technology elements. Explore composites, realization, and context-driven value for decision making.

Identify stakeholders from the governing board and derive the Archimate diagram using motivational elements; map drivers such as expanding to Europe and data center needs with aggregation relationships.

This study case traces how customers’ interest in optimizing fleet management prompts an assessment that reveals unsupported processes, leading to a future state with a new, scalable information technology design.

Explore how the governing board's move to a cloud based platform drives enterprise architecture, with risk assessment and goals to boost market share by 15% and customer satisfaction by 10%.

Discover where the strategy layer sits in enterprise architecture. Link the vision to active structure, behavior, and motivation elements via the strategy elements metamodel, and learn to adapt to change.

Explore the strategy metamodel in EA, detailing resources, behavior elements like value streams and capabilities, and the triggering and flowing relationships that realize courses of action, with flexible, non-mandatory connections.

Explore how resources, active or passive structure elements, enable capabilities, guide courses of action, support weaknesses and strengths analysis, and drive outcomes through CRM and project management in strategy.

Model value streams as activities delivering customer value, realized by processes and behavior elements. A tracking company example shows software development, marketing, terms, and delivery forming a value chain.

Model the strategy layer and map how actions realize outcomes and requirements across motivation, capability, resource, and core behavior elements in business, application, and technology layers, including assets.

Model the strategy layer in Archimate by building a view that links resources, capabilities, value streams, and courses of action from a car company case study.

Model the strategy in Archimate by nesting engineering and business teams under human resources to align collaboration, capabilities, and information system requirements for online attention and payment.

Explore the business architecture, modeling organizational structure, information flows, and processes, and map them to services and interfaces while aligning with strategy and IT collaboration to serve customers.

Explore the meta-model of business architecture, showing how the business interface and actors relate through composition and serving relationships. Learn how business services, events, and flows connect actors to processes.

Simplify the business meta-model with a realistic architecture notation, showing how a business actor and business role form collaborations, trigger interactions, and map to processes, services, and interfaces.

Explore active structure elements in business architecture, including business actors and roles that perform behavior, and how collaborations and interfaces model shared responsibilities and access to services.

Differentiate internal and external elements and model behavior through business processes, functions, events, and interactions that realize and expose business services accessed by external actors.

Explore passive elements in business architecture, including the business object, its representation, the contract, and the product, and learn how representations realize objects without executing behavior.

Explore how motivation, vision modeling, strategy, and business architecture connect across two layers and one aspect to form strategic plans, creating views from metamodels addressing stakeholder concerns.

Set up an Archi 5.2 project, organize elements into folders, and create finance, business, and motivation elements to translate information into stakeholder-focused architecture diagrams.

Analyze the enterprise vision to map stakeholders, concerns, and drivers for transformation, linking customer satisfaction, usability, security, scalability, and government regulations to drive architectural changes.

Learn to build an Archi motivation view and a second view: create a governing board with CEO, CIO, and executives; connect drivers to assessments using composition and association.

Add goals to the enterprise architecture by linking goals to outcomes through realization in a goals view, using time-bound metrics like 5% sales growth and 70–90% customer satisfaction.

Explore architecture principles as high-level guidelines to guide day-to-day decisions, with customer-facing constraints, a service-oriented focus, and goal alignment, plus validating diagrams against architecture standards using viewpoints.

Identify and model requirements within an enterprise architecture context, linking goals to requirements via realization, and set constraints to boost sales by 5% and improve usability.

Learn to model motivation elements in Archi: add the business architect as a stakeholder, define vision and mission, and connect them to goals with aggregation and influence.

Create the motivation view to display the enterprise architecture vision, adding governing board, business architect, concerns, assessments, goals, constraints, and requirements to drive customer satisfaction and sales.

Define the strategy layer and outline two actions: a hybrid system and a microservices architecture, with elasticity and renewed information services.

Migrate the system to a new version to improve the online buying experience by defining a new course of action and capability, and assigning resources across strategy views.

Define the organization structure by identifying business actors such as information services, human resources, inbound and outbound operations, sales, finance, and legal, and assign related business functions.

Build a business process view with two customer interfaces, an order submitted event, and an exclusive or split to model payment outcomes and order approval or rejection.

Explore building a comprehensive business process view, assigning roles like sales manager and inventory manager, evaluating orders, managing replenishment, and coordinating shipment and customer confirmation.

Master enterprise architecture vision diagrams, describe how resources support goals and operations, and prepare for part 2 with application components, technology architecture, and migration planning.