International

ArchiMate 3.2 Specification

105 controls. 0 other frameworks in our corpus share controls with it. Here is all of it, and how much of it you are already doing.

Page built . This page is derived from the framework corpus, which changes when the corpus is extended rather than daily.

105 controls 0 frameworks share controls with it International verified against its source document

Every control below is one this framework asks for. The right hand column counts how many other frameworks in our corpus carry the same control, which is the difference between doing this work once and doing it again for the next standard.

There is no implementation kit for this framework yet. The control list and the overlap above are free and complete.

What you already have

Frameworks whose controls overlap this one, most first. If you run any of them, the count is roughly what you have already evidenced.

No measured overlap with another framework in the corpus.

Every control

CodeControlAlso in
AM-1.1Purpose of the ArchiMate specification0
AM-1.2Why architectures and the language exist0
AM-1.3Conformance requirements for implementations0
AM-1.5Terminology and modal terms0
AM-10Technology Layer purpose and scope0
AM-10.1Technology metamodel permitted relationships0
AM-10.2Technology layer active structure types0
AM-10.3Technology behaviour elements0
AM-10.4Technology object passive structure0
AM-10.5Element definition summary0
AM-11.1Physical metamodel permitted relationships0
AM-11.2Physical active structure elements0
AM-11.3No separate physical behaviour elements0
AM-11.6Physical element definition summary0
AM-12.1Business and lower layer alignment0
AM-12.2Application and technology alignment0
AM-12.3Cross-layer integration view0
AM-13.1Non-exhaustive metamodel relationships0
AM-13.2Implementation and migration element semantics0
AM-13.3Standard relationships for implementation elements0
AM-13.4Links to core and motivation elements0
AM-14.1Purpose of architecture views0
AM-14.2Stakeholder concerns and ISO/IEC 420100
AM-14.3Views governed by viewpoints0
AM-14.4Two-step viewpoint creation0
AM-14.4.1Viewpoint purpose and content classification0
AM-14.4.2Constructing views under a viewpoint0
AM-15.1Attributes and profiles0
AM-15.2Profiles and specialization0
AM-2Definitions of core terms0
AM-3.1Language design considerations0
AM-3.2Top level organisation of the language0
AM-3.3Core language layers0
AM-3.4Cells of the ArchiMate core framework0
AM-3.5Framework coverage beyond the core cells0
AM-3.6Modeling abstraction and refinement0
AM-3.7Concepts kept separate from notation0
AM-3.8Nesting as alternative notation0
AM-3.9Colors and notational cues0
AM-4.1Generic behavior and structure metamodel0
AM-4.1.1Internal and external active structure elements0
AM-4.1.2Behaviour, services and events as dynamic elements0
AM-4.1.3Passive structure elements0
AM-4.3Concrete element types in models0
AM-4.4Motivation element context0
AM-4.5Composite elements0
AM-4.5.1Grouping membership and meaning0
AM-4.5.2Location through aggregation0
AM-5Relationship validity and clarity0
AM-5.1Structural link endpoints0
AM-5.1.1Composition and existence dependency0
AM-5.1.2Aggregation without ownership0
AM-5.1.3Assignment direction and allocation0
AM-5.1.4Realization and critical contribution0
AM-5.1.5Structural link transitivity0
AM-5.2Dependency relationship types0
AM-5.2.1Serving direction and legacy label0
AM-5.2.2Access to passive structure0
AM-5.2.3Influence on motivation elements0
AM-5.2.4Association use and direction0
AM-5.2.5Dependency scope and derivation0
AM-5.3Dynamic relationship types0
AM-5.3.1Triggering precedence0
AM-5.3.2Flow as transfer only0
AM-5.3.3Triggering and flow semantics0
AM-5.4.1Specialization hierarchy0
AM-5.5.1Junction validity and meaning0
AM-5.6Relationship reference table0
AM-5.7Derived relationships only summarise, never add detail0
AM-6Role of the motivation elements0
AM-6.1Motivation element set and permitted relationships0
AM-6.2Stakeholders, drivers and assessments0
AM-6.3Intent concepts: goals, outcomes, principles, requirements and constraints0
AM-6.4Recording meaning and value for concepts0
AM-6.6Connecting motivation elements with core elements0
AM-7Role of the strategy elements0
AM-7.1Strategy element set and permitted relationships0
AM-7.2Resources as strategy structure elements0
AM-7.3Strategy behaviour: capability, value stream and course of action0
AM-7.6Linking strategy elements to motivation and core elements0
AM-8Purpose of the business layer0
AM-8.1Business layer types and their abstract base elements0
AM-8.2Internal active structure types used in the business layer0
AM-8.3Separating external from internal business behaviour0
AM-8.4Passive structure types in the business layer0
AM-8.6Business layer element summary table0
AM-9Application layer scope0
AM-9.1Application metamodel relationship legality0
AM-9.2Application active structure elements0
AM-9.3Level of detail for application behaviour0
AM-9.4Application passive structure scope0
AM-9.5Application layer element summary table0
AM-B.1Limits on derivation rule use0
AM-B.2Rules for universally valid derivations0
AM-B.2.1Transitivity of specialization relationships0
AM-The-Open-Group-p.-15Publisher profile0
AM-p.-1Reference card scope and edition0
AM-p.-12Implementation and migration element set0
AM-p.-13Grouping and location elements0
AM-p.-2Relationship types and junction connectors0
AM-p.-3-4Motivation element set0
AM-p.-5Strategy layer element set0
AM-p.-6-7Business layer element set0
AM-p.-8Application layer element set0
AM-p.-9-11Technology layer element set0

Tell me when ArchiMate 3.2 Specification files something new

One email when a public company newly discloses something this framework governs, naming the company and what our corpus says it puts in scope. Nothing else, and one click to stop.

What this page is

A control-level reference for ArchiMate 3.2 Specification, drawn from our framework corpus. Control codes and titles are references to the standard, not reproductions of it. The overlap counts and the auditor artefacts are our own work and are the part you will not find elsewhere.

Measure this against what you already run · All frameworks · Today's edition