Although very similar to the UML 2.0 component, the ArchiMate component concept strictly models the structural aspect of an application: its behavior is modeled by an explicit relationship to the behavioral concepts.
Each of the ArchiMate concepts have specific relationships to each other that represent flow, dependencies, realizations, and others. Relationships usually have specific pairings, but not always.
ArchiMate is a valuable modeling language for developing enterprise architectures but exactly how important is it as part of an Enterprise Architect’s tool box?
One of the most effective uses of ArchiMate is in the production of viewpoints. A single function/process/service in the architecture can be represented in many ways, depending on which stakeholders are reviewing the EA status.
The most effective use of ArchiMate is in the production of viewpoints. In this article, we will investigate the relationship between ArchiMate and TOGAF.
Business Layer Structural Concepts: The Business Layer identifies the concepts and relationships of the highest level of the architecture: the end product, and the customer delivery system.
Both TOGAF and ArchiMate have been developed by The Open Group. TOGAF describes the process of developing an enterprise architecture and ArchiMate is a modeling language which compliments TOGAF. This blog outlines the difference between these standards.
ArchiMate establishes a wide set of symbols used to graphically represent these various elements in meaningful ways to the various interested parties. Here's how...
Business Layer Behavior Concepts: Based on service orientation, a crucial design decision for the behavioral part of the ArchiMate metamodel is the distinction between “external” and “internal” behavior of an organization.
This second of three articles concentrate on the relationships associated with each of the elements in the Business Concept library. Certain relationships apply to each concept and should be understood by EA practitioners.
12Page 1 of 2