Home Tags Posts tagged with "ArchiMate"
Articles Tagged with: ArchiMate
Enterprise Architecture (EA) is a comprehensive framework designed to map out and govern the alignment between IT investment and wider organizational strategies to develop a clear understanding of potential threats and opportunities.
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...
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...
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!
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.
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.