A short video guide detailing the benefits of the ArchiMate modelling language and how ArchiMate can help to develop your organizations Enterprise Architecture.
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.
A value can be associated with business services and, indirectly, with the products they are part of, and the roles or actors that use them.
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.
The next 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. The relationships were stated in the previous articles; this article expands on those aspects.
Business Layer Informational Concepts: Structural and behavioral concepts are mainly concerned with the operational perspective on an enterprise. Informational concepts focus on the “intentional” perspective.
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.
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.
The most effective use of ArchiMate is in the production of viewpoints. In this article, we will investigate the relationship between ArchiMate and TOGAF.
The ArchiMate language defines three main layers based on specializations of the core concepts presented in our previous ArchiMate article.
12Page 1 of 2