1. This freeware, non-commercial mind map (aligned with the newest version of Archimate®) was created for promotion the Archimate® standard and as a learning tool for candidates wanting to gain Archimate® qualifications. (please share and give feedback - your feedback and comments are my main motivation for further elaboration. THX!)
1.1. Questions / issues / errors? What do you think about my work? Your comments are highly appreciated. Please don't hesitate to contact me for :-) Mirosław Dąbrowski, Poland/Warsaw.
1.1.1. http://www.linkedin.com/in/miroslawdabrowski
1.1.2. https://www.google.com/+MiroslawDabrowski
1.1.3. https://play.spotify.com/user/miroslawdabrowski/
1.1.4. http://www.miroslawdabrowski.com
1.1.5. https://twitter.com/mirodabrowski
1.1.6. miroslaw_dabrowski
2. Map is under development, current state is an early ALPHA
3. Recommended Reading
3.1. Mastering ArchiMate Edition II
3.1.1. http://masteringarchimate.com/
4. Enterprise Architecture / Archimate modelling software
4.1. ARIS Archimate Modeller
4.1.1. http://www.softwareag.com/pl/products/aris_platform/reference_content/archimate/default.asp
4.2. ARIS IT Architect & Designer
4.2.1. http://www.softwareag.com/pl/products/aris_platform/aris_design/it_architect/overview/default.asp
4.3. Archi
4.3.1. http://www.archimatetool.com/
4.4. Astah
4.4.1. http://astah.net/editions/community
4.5. Avolution
4.5.1. http://www.avolution.com.au/index.html
4.6. BOC Management Office
4.6.1. http://www.boc-group.com/products/
4.7. BiZZdesign Architect
4.7.1. http://www.bizzdesign.com/tools/bizzdesign-architect/
4.8. Enterprise Architect
4.8.1. http://www.sparxsystems.com/products/ea/
4.9. Essential Project
4.9.1. http://www.enterprise-architecture.org/
4.10. IterPlan
4.10.1. http://www.iteraplan.de/en
4.11. OmniGraffle
4.11.1. http://www.omnigroup.com/omniGraffle
4.12. System Architecture Management Utility (SAMU)
4.12.1. http://www.atollgroup.eu/
4.13. Troux Architect
4.13.1. http://www.troux.com/products/troux_architect/
4.14. Visual Paradigm
4.14.1. http://www.visual-paradigm.com/
4.15. iGrafx
4.15.1. http://www.igrafx.com/
5. Motivation extension
5.1. The ArchiMate® Motivation extension can be used to model the principles, drivers, goals, and requirements of the architecture.
5.2. Motivational Concepts
5.2.1. Stakeholder
5.2.1.1. A stakeholder is defined as the role of an individual, team, or organization (or classes thereof) that represents their interests in, or concerns relative to, the outcome of the architecture.
5.2.2. Driver
5.2.2.1. A driver is defined as something that creates, motivates, and fuels the change in an organization.
5.2.3. Assessment
5.2.3.1. An assessment is defined as the outcome of some analysis of some driver.
5.2.4. Goal
5.2.4.1. A goal is defined as an end state that a stakeholder intends to achieve.
5.2.5. Requirement
5.2.5.1. A requirement is defined as a statement of need that must be realized by a system.
5.2.6. Constraint
5.2.6.1. A constraint is defined as a restriction on the way in which a system is realized.
5.2.7. Principle
5.2.7.1. A principle is defined as a normative property of all systems in a given context, or the way in which they are realized.
5.3. Motivation Extension Relationships
5.3.1. Association
5.3.2. Aggregation
5.3.3. Realization
5.3.4. Influence
5.4. Motivation Extension Viewpoints
5.4.1. Stakeholder Viewpoint
5.4.2. Goal Realization Viewpoint
5.4.3. Goal Contribution Viewpoint
5.4.4. Principles Viewpoint
5.4.5. Requirements Realization Viewpoint
5.4.6. Motivation Viewpoint
6. Elements Relationships
6.1. Relationships can be classified as either:
6.1.1. Structural
6.1.1.1. Which model the structural coherence of concepts of the same or different types.
6.1.1.2. Derived Relationships
6.1.2. Dynamic
6.1.2.1. Which are used to model (temporal) dependencies between behavioral concepts.
6.1.3. Other
6.1.3.1. Which do not fall into one of the two above categories.
6.2. Structural Relationships
6.2.1. Association
6.2.1.1. Association models a relationship between objects that is not covered by another, more specific relationship.
6.2.1.2. weight
6.2.1.2.1. 1
6.2.1.3. weakest structural relationship
6.2.2. Access
6.2.2.1. The access relationship models the access of behavioral concepts to business or data objects.
6.2.2.2. weight
6.2.2.2.1. 2
6.2.3. Used By
6.2.3.1. The used by relationship models the use of services by processes, functions, or interactions and the access to interfaces by roles, components, or collaborations.
6.2.3.2. weight
6.2.3.2.1. 3
6.2.4. Realization
6.2.4.1. The realization relationship links a logical entity with a more concrete entity that realizes it.
6.2.4.2. weight
6.2.4.2.1. 4
6.2.5. Assignment
6.2.5.1. The assignment relationship links units of behavior with active elements (e.g., roles, components) that perform them, or roles with actors that fulfill them.
6.2.5.2. weight
6.2.5.2.1. 5
6.2.6. Aggregation
6.2.6.1. The aggregation relationship indicates that an object groups a number of other objects.
6.2.6.2. weight
6.2.6.2.1. 6
6.2.7. Composition
6.2.7.1. The composition relationship indicates that an object is composed of one or more other objects.
6.2.7.2. weight
6.2.7.2.1. 7
6.2.7.3. strongest structural relationship
6.3. Dynamic Relationships
6.3.1. Flow
6.3.1.1. The flow relationship describes the exchange or transfer of, for example, information or value between processes, function, interactions, and events.
6.3.2. Triggering
6.3.2.1. The triggering relationship describes the temporal or causal relationships between processes, functions, interactions, and events.
6.4. Other Relationships
6.4.1. Grouping
6.4.1.1. The grouping relationship indicates that objects, of the same type or different types, belong together based on some common characteristic.
6.4.2. Junction
6.4.2.1. A junction is used to connect relationships of the same type.
6.4.3. Specialization
6.4.3.1. The specialization relationship indicates that an object is a specialization of another object.
7. Implementation and Migration extension
7.1. The ArchiMate® Implementation and Migration extension is used to stage the work packages that are needed to implement the architecture.
7.2. Implementation and Migration Concepts
7.2.1. Work Package
7.2.2. Deliverable
7.2.3. Plateau
7.2.4. Gap
7.3. Implementation and Migration Relationships
7.3.1. The Implementation and Migration extension re-uses the standard ArchiMate relationships.
7.4. Implementation and Migration Extension Viewpoints
7.4.1. Project Viewpoint
7.4.2. Migration Viewpoint
7.4.3. Implementation and Migration Viewpoint
8. ArchiMate® 2.1 Specification
8.1. consists of:
8.1.1. ArchiMate® Core (the core language)
8.1.2. Motivation extension
8.1.3. Implementation and Migration extension
9. Layering and Elements
9.1. The ArchiMate® language defines 3 main layers:
9.1.1. Business Layer
9.1.1.1. What is it?
9.1.1.1.1. Offers products and services to external customers, which are realized in the organization by business processes performed by business actors.
9.1.1.2. Active Structure Concepts (formerly Structural Concepts)
9.1.1.2.1. Business actor
9.1.1.2.2. Business role
9.1.1.2.3. Business collaboration
9.1.1.2.4. Business interface
9.1.1.2.5. Location
9.1.1.3. Behavioral Concepts
9.1.1.3.1. Business process
9.1.1.3.2. Business function
9.1.1.3.3. Business interaction
9.1.1.3.4. Business event
9.1.1.3.5. Business service
9.1.1.4. Passive Structure Concepts (formerly Informational Concepts)
9.1.1.4.1. Business object
9.1.1.4.2. Representation
9.1.1.4.3. Meaning
9.1.1.4.4. Value
9.1.1.4.5. Product
9.1.1.4.6. Contract
9.1.2. Application Layer
9.1.2.1. What is it?
9.1.2.1.1. Supports the business layer with application services which are realized by (software) applications.
9.1.2.2. Active Structure Concepts (formerly Structural Concepts)
9.1.2.2.1. Application component
9.1.2.2.2. Application collaboration
9.1.2.2.3. Application interface
9.1.2.2.4. Data object
9.1.2.3. Behavioral Concepts
9.1.2.3.1. Application function
9.1.2.3.2. Application interaction
9.1.2.3.3. Application service
9.1.3. Technology Layer
9.1.3.1. What is it?
9.1.3.1.1. Offers infrastructure services (e.g., processing, storage, and communication services) needed to run applications, realized by computer and communication hardware and system software.
9.1.3.2. Active Structure Concepts (formerly Structural Concepts)
9.1.3.2.1. Node
9.1.3.2.2. Device
9.1.3.2.3. System software
9.1.3.2.4. Infrastructure interface
9.1.3.2.5. Network
9.1.3.2.6. Communication path
9.1.3.3. Behavioral Concepts
9.1.3.3.1. Infrastructure function
9.1.3.3.2. Infrastructure service
9.1.3.4. Passive Structure Concepts (formerly Informational Concepts)
9.1.3.4.1. Artifact
9.2. Elements (aka. Concepts)
9.2.1. Each layer has dedicated set of Elements called Concepts
9.2.2. ArchiMate® Core language consists of 3 types of elements (aka. Aspects):
9.2.2.1. Active Structure Concepts (formerly Structural Concepts)
9.2.2.1.1. see Active Structure Concepts (formerly Structural Concepts)
9.2.2.2. Behavior elements
9.2.2.2.1. see Behavioral Concepts
9.2.2.3. Passive Structure Concepts (formerly Informational Concepts)
9.2.2.3.1. see Passive Structure Concepts
9.2.3. Elements can interact and collaborate.
9.2.4. Elements have relationships of different types.
10. ArchiMate® Framework
10.1. The aspects (passive structure, behavior, and active structure) and layers (business, application, and technology) can be organized as a framework of 9 “cells”,
11. Architecture Viewpoints
11.1. Views
11.1.1. A “view” is what you see
11.2. Viewpoints
11.2.1. A “viewpoint” is where you are looking from.
11.2.2. Introductory Viewpoint
11.2.3. Organization Viewpoint
11.2.4. Actor Co-operation Viewpoint
11.2.5. Business Function Viewpoint
11.2.6. Business Process Viewpoint
11.2.7. Business Process Co-operation Viewpoint
11.2.8. Product Viewpoint
11.2.9. Application Behavior Viewpoint
11.2.10. Application Co-operation Viewpoint
11.2.11. Application Structure Viewpoint
11.2.12. Application Usage Viewpoint
11.2.13. Infrastructure Viewpoint
11.2.14. Infrastructure Usage Viewpoint
11.2.15. Implementation and Deployment Viewpoint
11.2.16. Information Structure Viewpoint
11.2.17. Service Realization Viewpoint
11.2.18. Layered Viewpoint
11.2.19. Landscape Map Viewpoint
11.3. Viewpoint Classification
11.3.1. by purpose
11.3.1.1. 3 classifications
11.3.1.1.1. Designing
11.3.1.1.2. Deciding
11.3.1.1.3. Informing
11.3.2. by content
11.3.2.1. 3 classifications
11.3.2.1.1. Details
11.3.2.1.2. Coherence
11.3.2.1.3. Overview
12. Stakeholders
12.1. End user
12.2. Architect
12.3. Upper-level management
12.4. Operational manager
12.5. Project manager
12.6. Developer
13. Profiles
13.1. 2 types of profiles:
13.1.1. Pre-defined profiles
13.1.2. User-defined profiles
14. Behaviors
14.1. Performed by a single structure element.
14.2. Collective behavior (interaction) that is performed by a collaboration of multiple structure elements.
14.3. Collaboration
14.3.1. A collaboration is defined as a (temporary) grouping (or aggregation) of two or more structure elements, working together to perform some collective behavior.
14.4. Interaction
14.4.1. An interaction is defined as a unit of behavior performed by a collaboration of two or more structure elements.