At the end of this course you will:
- Understand the background, key concepts and applications of ArchiMate® for modeling and describing architectures
- Be able to use the ArchiMate® language and techniques to visualize and communicate architectures
- Understand the two ArchiMate® extensions, their viewpoints and their application to key concepts
- Be able to apply ArchiMate® in comlex modeling situations
- Be able to complete the ArchiMate® 2.1 Certified exam (in addition to some self-directed study)
What is ArchiMate?
ArchiMate is a visual language to represent end-to-end enterprise architecture in terms of business processes, applications and infrastructure(technology) . It provides a consistent framework for designing multiple architecture domains and relationships among them. An integrated representation approach, ArchiMate equips the IT architects with a powerful modeling standard for representing, communicating and analyzing enterprise architecture. Like any effective modeling language should ideally be doing, ArchiMate helps evaluate the impact of changes within multiple architecture domains and to communicate them effectively and with ease.
If you are interested in a little history, ArchiMate was a 30 months project undertaken and managed by Telematica Institute, which is essentially an international consortium of companies and several social / knowledge organizations. The project took 35 man years, and its approximate cost of 4 million euros was collectively funded by Dutch government and business partners like ABN AMRO and CWI. With due focus on the relationship between business and IT architectures, the project managed to come up with a comprehensive language for describing architecture models with precision to enable IT architecture designing solutions to standardize their techniques and offerings for effective visualization and analysis.
It is as much important to know what ArchiMate is not as to understand what it really is. ArchiMate is not software development meta language like UML, and it does not support representations in that level granularity. It is also not, like Zachman or TOGAF, an all-encompassing collection of architecture methods that can serve as a framework for the enterprise architecture to function within – its role is limited in enabling the visualization and analytical problem(s) associated with standard architecture frameworks.
Challenges in Architecture Representations
Depending on the size of the organization or the authority enjoyed by the architecture board in the enterprise, the tools being used to capture and manage architecture models in an enterprise can be anything from MS PowerPoint and MS Visio to feature-laden, metadata-driven tools like Rational Suit and Telelogic System Architect. However, even the representations produced by or controlled within very powerful, industry leading tools don’t guarantee ‘universal acceptance’ across the enterprise-wide stakeholders for reasons ranging from complexity of the model , lack of features supporting a certain requisite degree of abstraction or more simply, the comfort-level of in-house managerial, architectural and development staff.
Then comes the question of standards. Most MDA (Model-Driven Architecture) complied standards like UML, MOF, XMI are really meta-frameworks meant to drive software design as in SDLC, and not meant for enterprise architecture. They are obviously no substitutes for a representation standard with enough flexibility and abstractive possibilities that EA demands.
There are also standards for visual representation of certain architecture dimensions, like BPMN and IDEF1X .But they, again, are specialized at handling respective information domains like process or data. The methods that IDEF proposes are quite comprehensive in that respect – that covers everything from standards for User interface (IDEF8) to Implementation Architecture (IDEF10) and Data(IDEF1X ) to Process (IDEF3). But they are not still really enough for Enterprise Architecture. Here is why: We simply need an Integrated View of architecture. It is easier said than done, as enterprise IT architecture addresses a different problem at a different level of abstraction than what the above models attempt. But then, when needed there has be a flexibility to go further level down in terms of details covered in the model
Let us take a quick-and-dirty stock of the requirement for EA modeling standard:
- It should provide a comprehensive modeling framework
- It should support an integrated (end-to-end) architecture view
- It should be easily scalable and maintainable.
- It should be precise and accurate
- It should be tool-independent and conceptually portable.
- It should be simple enough to develop and maintain.
- It should provide representation framework for different types of enterprise architecture domains, and should support inter-domain relationships
- It should use standard symbols for concepts and relationships, but should also communicate the underlying idea nearly intuitively to stakeholders
- It should be capable to support major architecture life- cycle frameworks (such as TOGAF, Zachman)
Trademarks & Copyrights
This associated accredited course has been licensed to Paradigm Management Solutions UK Ltd from her partner and course ware creator Copyright © Good-eLearning. All rights reserved.
IT4IT™, ArchiMate® and TOGAF® are registered trademarks of The Open Group.
ITIL®, PRINCE® and The Swirl logo™ are registered trademarks of AXELOS Limited. COBIT® is a registered trademark of ISACA and the IT Governance Institute.
© Copyright 2014 Good e-Learning, all rights reserved. This e-Learning course is delivered by Good e-Learning, and accredited by The Open Group.