ArchiSurance – Application Layer Example In this example below, both structural and behavioral concepts of the Application Layer are illustrated. “(1) Web front end” is the application interface that provides access to the application service called “(2) Policy creation service”. It is a composite part of the Home & Away policyRead More →
Active Structure Concept Notation Application component A modular, deployable, and replaceable part of a software system that encapsulates its behavior and data and exposes these through a set of interfaces. Application collaboration An aggregate of two or more application components that work together to perform collective behavior. ApplicationRead More →
The metamodel gives an overview of the application layer concepts and their relationships. Many of the concepts have been inspired by the UML 2.0 standard, as this is the dominant language and the de facto standard for describing software applications. As I mentioned before, ArchiMate core framework has 3 layers x 3 aspects:Read More →
ArchiMate Notation ArchiMate 3 – Technology Layer Notations Name Representation Definition * Node A computational or physical resource that hosts, manipulates, or interacts with other computational or physical resources. Device A physical IT resource upon which system software and artifacts may be stored or deployed for execution. System Software SoftwareRead More →
Informational Concepts are passive entities which provide a way to link the operational side of an organization to its business goals and the products (through behavior entities) that it offers to its customers. In the Metamodel above, you can see that: The contract entity is a kind of business objectRead More →
A behavior element is defined as a unit of activity performed by one or more active structure elements. The active structure concepts are assigned to behavioral concepts, to show who or what performs the behavior as shown in the metamodel below: Internal vs External Behavioral Concepts While the internal business services offerRead More →
The structure aspect at the business layer refers to the static structure of an organization, in terms of the entities that make up the organization and their relationships. Two types of entities are distinguished: Activity and passive entities Active Entity – Perform some behavior such as business process or functions, theyRead More →
This layer includes a number of additional informational concepts which are relevant in the business domain: a product and associated contract, the meaning of business objects, and the value of products and business services. The Figure shows the metamodel of business layer concepts. In the Figure above, we use colorsRead More →
The purpose of the motivation extension is to model the motivation behind the core elements in some enterprise architecture. Therefore, it should be possible to relate motivational elements to core elements as shown in Figure below: Meaning and value can be associated with any structure or behavior element. Relating Core ElementsRead More →
The metamodels and examples from show the different types of relationships that can be used: between two motivational elements between one motivational element and one core element. The Table below provides a description of these relationships: Intentional Relationships Notation Association Association models that some intention is related to a sourceRead More →