AM-1.1 | Purpose of the ArchiMate specification | 0 |
AM-1.2 | Why architectures and the language exist | 0 |
AM-1.3 | Conformance requirements for implementations | 0 |
AM-1.5 | Terminology and modal terms | 0 |
AM-10 | Technology Layer purpose and scope | 0 |
AM-10.1 | Technology metamodel permitted relationships | 0 |
AM-10.2 | Technology layer active structure types | 0 |
AM-10.3 | Technology behaviour elements | 0 |
AM-10.4 | Technology object passive structure | 0 |
AM-10.5 | Element definition summary | 0 |
AM-11.1 | Physical metamodel permitted relationships | 0 |
AM-11.2 | Physical active structure elements | 0 |
AM-11.3 | No separate physical behaviour elements | 0 |
AM-11.6 | Physical element definition summary | 0 |
AM-12.1 | Business and lower layer alignment | 0 |
AM-12.2 | Application and technology alignment | 0 |
AM-12.3 | Cross-layer integration view | 0 |
AM-13.1 | Non-exhaustive metamodel relationships | 0 |
AM-13.2 | Implementation and migration element semantics | 0 |
AM-13.3 | Standard relationships for implementation elements | 0 |
AM-13.4 | Links to core and motivation elements | 0 |
AM-14.1 | Purpose of architecture views | 0 |
AM-14.2 | Stakeholder concerns and ISO/IEC 42010 | 0 |
AM-14.3 | Views governed by viewpoints | 0 |
AM-14.4 | Two-step viewpoint creation | 0 |
AM-14.4.1 | Viewpoint purpose and content classification | 0 |
AM-14.4.2 | Constructing views under a viewpoint | 0 |
AM-15.1 | Attributes and profiles | 0 |
AM-15.2 | Profiles and specialization | 0 |
AM-2 | Definitions of core terms | 0 |
AM-3.1 | Language design considerations | 0 |
AM-3.2 | Top level organisation of the language | 0 |
AM-3.3 | Core language layers | 0 |
AM-3.4 | Cells of the ArchiMate core framework | 0 |
AM-3.5 | Framework coverage beyond the core cells | 0 |
AM-3.6 | Modeling abstraction and refinement | 0 |
AM-3.7 | Concepts kept separate from notation | 0 |
AM-3.8 | Nesting as alternative notation | 0 |
AM-3.9 | Colors and notational cues | 0 |
AM-4.1 | Generic behavior and structure metamodel | 0 |
AM-4.1.1 | Internal and external active structure elements | 0 |
AM-4.1.2 | Behaviour, services and events as dynamic elements | 0 |
AM-4.1.3 | Passive structure elements | 0 |
AM-4.3 | Concrete element types in models | 0 |
AM-4.4 | Motivation element context | 0 |
AM-4.5 | Composite elements | 0 |
AM-4.5.1 | Grouping membership and meaning | 0 |
AM-4.5.2 | Location through aggregation | 0 |
AM-5 | Relationship validity and clarity | 0 |
AM-5.1 | Structural link endpoints | 0 |
AM-5.1.1 | Composition and existence dependency | 0 |
AM-5.1.2 | Aggregation without ownership | 0 |
AM-5.1.3 | Assignment direction and allocation | 0 |
AM-5.1.4 | Realization and critical contribution | 0 |
AM-5.1.5 | Structural link transitivity | 0 |
AM-5.2 | Dependency relationship types | 0 |
AM-5.2.1 | Serving direction and legacy label | 0 |
AM-5.2.2 | Access to passive structure | 0 |
AM-5.2.3 | Influence on motivation elements | 0 |
AM-5.2.4 | Association use and direction | 0 |
AM-5.2.5 | Dependency scope and derivation | 0 |
AM-5.3 | Dynamic relationship types | 0 |
AM-5.3.1 | Triggering precedence | 0 |
AM-5.3.2 | Flow as transfer only | 0 |
AM-5.3.3 | Triggering and flow semantics | 0 |
AM-5.4.1 | Specialization hierarchy | 0 |
AM-5.5.1 | Junction validity and meaning | 0 |
AM-5.6 | Relationship reference table | 0 |
AM-5.7 | Derived relationships only summarise, never add detail | 0 |
AM-6 | Role of the motivation elements | 0 |
AM-6.1 | Motivation element set and permitted relationships | 0 |
AM-6.2 | Stakeholders, drivers and assessments | 0 |
AM-6.3 | Intent concepts: goals, outcomes, principles, requirements and constraints | 0 |
AM-6.4 | Recording meaning and value for concepts | 0 |
AM-6.6 | Connecting motivation elements with core elements | 0 |
AM-7 | Role of the strategy elements | 0 |
AM-7.1 | Strategy element set and permitted relationships | 0 |
AM-7.2 | Resources as strategy structure elements | 0 |
AM-7.3 | Strategy behaviour: capability, value stream and course of action | 0 |
AM-7.6 | Linking strategy elements to motivation and core elements | 0 |
AM-8 | Purpose of the business layer | 0 |
AM-8.1 | Business layer types and their abstract base elements | 0 |
AM-8.2 | Internal active structure types used in the business layer | 0 |
AM-8.3 | Separating external from internal business behaviour | 0 |
AM-8.4 | Passive structure types in the business layer | 0 |
AM-8.6 | Business layer element summary table | 0 |
AM-9 | Application layer scope | 0 |
AM-9.1 | Application metamodel relationship legality | 0 |
AM-9.2 | Application active structure elements | 0 |
AM-9.3 | Level of detail for application behaviour | 0 |
AM-9.4 | Application passive structure scope | 0 |
AM-9.5 | Application layer element summary table | 0 |
AM-B.1 | Limits on derivation rule use | 0 |
AM-B.2 | Rules for universally valid derivations | 0 |
AM-B.2.1 | Transitivity of specialization relationships | 0 |
AM-The-Open-Group-p.-15 | Publisher profile | 0 |
AM-p.-1 | Reference card scope and edition | 0 |
AM-p.-12 | Implementation and migration element set | 0 |
AM-p.-13 | Grouping and location elements | 0 |
AM-p.-2 | Relationship types and junction connectors | 0 |
AM-p.-3-4 | Motivation element set | 0 |
AM-p.-5 | Strategy layer element set | 0 |
AM-p.-6-7 | Business layer element set | 0 |
AM-p.-8 | Application layer element set | 0 |
AM-p.-9-11 | Technology layer element set | 0 |