The most effective use of ArchiMate is in the production of viewpoints. In this article, we will investigate the relationship between ArchiMate and TOGAF.
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.
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?
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...
The ArchiMate language defines three main layers based on specializations of the core concepts presented in our previous ArchiMate article.
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.
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.
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...
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!
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.
12Page 1 of 2