ArchimateConcept
type: Concept
preferred label: Archimate Concept
broader: ArchComponent

ArchimateElement
type: Concept
broader: ArchimateConcept

ArchimateRelationship
type: Concept
broader: ArchimateConcept

ArchimateRelationship
type: Concept
broader: ArchimateRelationship
narrower: Realization
narrower: Assignment
narrower: Aggregation
narrower: Composition

ArchimateRelationship
type: Concept
broader: ArchimateRelationship
narrower: Influence
narrower: Access
narrower: Serving

ArchimateRelationship
type: Concept
broader: ArchimateRelationship
narrower: Triggering
narrower: Flow

ArchimateRelationship
type: Concept
broader: ArchimateRelationship
narrower: Specialization
narrower: Association

ArchimateRelationshipConnector
type: Concept
broader: ArchimateConcept
narrower: Junction And
narrower: Junction Or

ArchimateElementByLayer
type: Concept
broader: ArchimateElement

ArchimateElementByLayer
type: Concept
broader: ArchimateElement

BusinessLayer
type: Concept
broader: ArchimateElementByLayer
narrower: Resource
narrower: Capability
narrower: CourseOfAction

BusinessLayer
type: Concept
broader: ArchimateElementByLayer
narrower: BusinessActor
narrower: BusinessRole
narrower: BusinessCollaboration
narrower: BusinessInterface
narrower: BusinessProcess
narrower: BusinessFunction
narrower: BusinessInteraction
narrower: BusinessEvent
narrower: BusinessService
narrower: BusinessObject
narrower: Contract
narrower: Representation
narrower: Product

ApplicationLayer
type: Concept
broader: ArchimateElementByLayer
narrower: ApplicationComponent
narrower: ApplicationCollaboration
narrower: ApplicationInterface
narrower: ApplicationFunction
narrower: ApplicationInteraction
narrower: ApplicationProcess
narrower: ApplicationEvent
narrower: ApplicationService
narrower: DataObject

TechnologyLayer
type: Concept
broader: ArchimateElementByLayer
narrower: Node
narrower: Device
narrower: SystemSoftware
narrower: TechnologyCollaboration
narrower: TechnologyInterface
narrower: Path
narrower: CommunicationNetwork
narrower: TechnologyFunction
narrower: TechnologyProcess
narrower: TechnologyInteraction
narrower: TechnologyEvent
narrower: TechnologyService
narrower: Artifact

PhysicalLayer
type: Concept
broader: ArchimateElementByLayer
narrower: Equipment
narrower: Facility
narrower: DistributionNetwork
narrower: Material

ImplementationAndMigrationLayer
type: Concept
broader: ArchimateElementByLayer
narrower: WorkPackage
narrower: Deliverable
narrower: ImplementationEvent
narrower: Plateau
narrower: Gap

MotivationElement
type: Concept
broader: ArchimateElement
narrower: Stakeholder
narrower: Driver
narrower: Assessment
narrower: Goal
narrower: Outcome
narrower: Principle
narrower: Requirement
narrower: Constraint
narrower: Meaning
narrower: Value

ActiveStructureElement
type: Concept
comment: represents the structural elements (the business actors, application components, and devices that display actual behavior; i.e., the 'subjects' of activity)
broader: ArchimateElementByLayer
narrower: Resource

ActiveStructureElement
type: Concept
comment: represents the structural elements (the business actors, application components, and devices that display actual behavior; i.e., the 'subjects' of activity)
broader: ActiveStructureElement
narrower: Stakeholder
narrower: Path
narrower: Location
narrower: CommunicationNetwork
narrower: Node
narrower: SystemSoftware
narrower: Device
narrower: Equipment
narrower: Facility
narrower: DistributionNetwork

ExternalActiveStructureElement
type: Concept
comment: also called interfaces
broader: ActiveStructureElement
narrower: BusinessInterface
narrower: ApplicationInterface
narrower: InfrastructureInterface

InternalActiveStructureElement
type: Concept
broader: ActiveStructureElement
narrower: BusinessRole
narrower: BusinessActor
narrower: BusinessCollaboration
narrower: ApplicationComponent
narrower: ApplicationCollaboration

PassiveStructureElement
type: Concept
comment: represents the objects on which behavior is performed. These are usually information objects in the Business Layer and data objects in the Application Layer, but they may also be used to represent physical objects
broader: ActiveStructureElement
narrower: BusinessObject
narrower: Contract
narrower: Representation
narrower: DataObject
narrower: Meaning
narrower: TechnologyObject
narrower: Artifact
narrower: Value
narrower: Material

BehaviorElement
type: Concept
comment: represents the behavior (processes, functions, events, and services) performed by the actors. Structural elements are assigned to behavioral elements, to show who or what displays the behavior
broader: ArchimateElementByLayer
narrower: Capability
narrower: CourseOfAction

ExternalBehaviorElement
type: Concept
preferred label: BehaviorElement
comment: also called services
broader: BehaviorElement
narrower: BusinessService
narrower: ApplicationService
narrower: InfrastructureService

InternalBehaviorElement
type: Concept
broader: BehaviorElement
narrower: BusinessFunction
narrower: BusinessInteraction
narrower: BusinessProcess
narrower: ApplicationFunction
narrower: ApplicationInteraction
narrower: ApplicationProcess
narrower: InfrastructureFunction

Event - BehaviorElement
type: Concept
broader: BehaviorElement
narrower: BusinessEvent
narrower: ApplicationEvent
narrower: TechnologyEvent

MotivationElement
type: Concept
comment: A composite element is an element that does not necessarily fit in a single aspect (column) of the framework, but may combine two or more aspects.
broader: ArchimateElementByLayer
narrower: Product
narrower: Grouping
narrower: Location

ViewpointByContent
type: Concept
broader: ArchimateViewpoint

Details
type: Concept
definition: views on the detailed level typically consider one layer and one aspect from the ArchiMate Core Framework Typical stakeholders are a software engineer responsible for design and implementation of a software component or a process owner responsible for effective and efficient process execution
broader: ViewpointByContent

Coherence
type: Concept
definition: at the coherence abstraction level, multiple layers or multiple aspects are spanned Extending the view to more than one layer or aspect enables the stakeholder to focus on architecture relationships like process-uses-system (multiple layer) or application-uses-object (multiple aspect). Typical stakeholders are operational managers responsible for a collection of IT services or business processes.
broader: ViewpointByContent

Overview
type: Concept
definition: the overview abstraction level addresses both multiple layers and multiple aspects Typically, such overviews are addressed to Enterprise Architects and decision-makers, such as CEOs and CIOs.
broader: ViewpointByContent