OGA-031: ArchiMate 3 Part 1

Based on the ArchiMate 3 documents or objectives, a communication network represents a set of structures that connects devices or system software for transmission, routing, and reception of dat a. A path models the relation between two or more technology internal active structure elements, through which these can exchange information. The diagram uses a flow relationship to indicate that data flows from server B to communication network E, then through path F to communication network I. The notation for a flow relationship is a dashed line with an open arrowhead at the end that points to the direction of the flow.

Reference: ArchiMate® 3.2 Specification, Chapter 11 Technology Layer, Section 11.2 Active Structure Elements 1; ArchiMate® 3.2 Specification, Chapter 5 Relationships, Section 5.4 Dynamic Relationships 1; ArchiMate communication network 2.

Based on the ArchiMate 3 documents or objectives, an application component represents a modular, deployable, and replaceable part of a software system that encapsulates its behavior and dat a. An application service represents an explicitly defined exposed application behavior. A data object represents data structured for automated processing. A realization relationship indicates that an entity plays a critical role in the creation, achievement, sustenance, or operation of a more abstract entity. An access relationship models the ability of behavior and active structure elements to observe or act upon passive structure elements. The diagram uses a realization relationship from the MEDINFO application component to the Medical Information service to indicate that the application component realizes the service. The diagram also uses an access relationship from the MEDINFO application component to the MEDBASE data object to indicate that the application component accesses the data object.

Reference: ArchiMate® 3.2 Specification, Chapter 10 Application Layer, Section 10.1 Active Structure Elements 1; ArchiMate® 3.2 Specification, Chapter 10 Application Layer, Section 10.3 Behavior Elements 1; ArchiMate® 3.2 Specification, Chapter 5 Relationships, Section 5.1 Structural Relationships 1; ArchiMate® 3.2 Specification, Chapter 5 Relationships, Section 5.3 Access Relationships 1; ArchiMate Example: Application Components - Visual Paradigm 2.

Based on the ArchiMate 3 documents or objectives, the ArchiMate standard provides a set of entities and relationships for representing Architecture Description. Architecture Description is a work product used to express an architecture for a system-of-interest. The ArchiMate language is an open and independent modeling language for Enterprise Architecture that is supported by different tool vendors and consulting firms.

Reference: The ArchiMate® Enterprise Architecture Modeling Language | The Open Group Website 1; ArchiMate® 3.2 Specification, Chapter 1 Introduction, Section 1.1 Objective 2.

Based on the ArchiMate 3 documents or objectives, an aggregation relationship indicates that an element groups a number of other concepts. The aggregation relationship has been inspired by the aggregation relationship in UML class diagrams. Unlike composition, aggregation does not imply an existence dependency between the aggregating and aggregated concepts. The notation for an aggregation relationship is a solid line with an empty diamond at the end that points to the whole element. The diagram uses an aggregation relationship from the bottom elements to the top element to indicate that the top element groups the bottom elements.

Reference: ArchiMate® 3.2 Specification, Chapter 5 Relationships, Section 5.1 Structural Relationships 1; Structural Relationship: Part 3 - ArchiMate Resources for FREE 2.