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.
TOGAF and ArchiMate come from the same stable as they are both EA standards managed and maintained by The Open Group.But to what extent do they overlap or complement each other? How can they be used in combination? And how can we overcome any limitations they might impose? Read this blog to find out!
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.
Save 15% on Good e-Learning 'ArchiMate 3 Bridging' course!
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 ArchiMate language defines three main layers based on specializations of the core concepts presented in our previous ArchiMate article.
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.
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.
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 is a valuable modeling language for developing enterprise architectures but exactly how important is it as part of an Enterprise Architect’s tool box?
12Page 1 of 2