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.
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.
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.
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?
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.
The ArchiMate language defines three main layers based on specializations of the core concepts presented in our previous ArchiMate article.
Earlier this year The Open Group released the latest version of the ArchiMate standard - ArchiMate 3.0. What's new and why do we Need it? Now...
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.
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...
Like ArchiMate 2.1, ArchiMate 3.0 is a modelling language for enterprise architecture, allowing enterprise architects to visualize, analyse, and describe the relationships among architecture...
12Page 1 of 2