ArchiMate 2 Tool Certification Available

The Open Group is now accepting applications for ArchiMate 2 Tool Certification.

For tooling vendors out there the details are below with a link to the certification site.

How to Apply for ArchiMate 2 Tool Certification

  • Read the Architecture Tool Certification Policy, ArchiMate 2 Tools Conformance Requirements , the Certification Agreement and the Trademark License Agreement (TMLA).

These documents are all available using the links at the referenced page above (under the ArchiMate 2 Tool Certification).

  • Download, print, sign and return the Certification Agreement and the TMLA.
  • Contact The Open Group ArchiMate Certification Authority to confirm your organization in the program
  • You need to prepare a Conformance Statement Questionnaire (CSQ) for each Tool you wish to have certified. The CSQ can be downloaded from the link below.
  • When you are done, pay the certification fees.
  • Next you must submit the CSQ.
  • The Certification Authority will then carry out an audit of the CSQ and you will be informed of the result.


For details on the program and the supporting documentation please see


What can Enterprise Architects Learn from Steve Jobs?


I was at the Architecture Summit this weekend and we spun up a roundtable topic based on Steve Jobs. I quickly stepped back and reflected more precisely on the topic of what we as Enterprise Architects can learn from Steve Jobs.

I think the learnings are less about his actions or lack there of, but more to his core in his principles and values. Like many CIO’s their demeanor and tenacity isn’t for the faint of heart.

Below are the key principles that I think EA’s can learn from Steve Jobs:

  1. Focus and clarity – Know your business and focus on what is important. Job’s established rules that there will be a core focus and spent hours declining projects because they didn’t align to the priority areas. It’s so easy for EA’s to be randomized by things that frankly don’t matter to the business of EA. In an EA program or an engagement/project determine what architecture models, descriptions or even meetings align to your business goals and objectives.
  2. Purposefulness – Uniquely, Jobs was able to get to the root of “why” or the purpose behind all things he did. Likewise with EA we must make sure we always get to the root of our purpose and how to fulfill it.
  3. Simplicity – We all know that Apple products are simple but this is a real art to take something complex and make it really intuitive and easy to use. I always fall back to, "Everything should be made as simple as possible but not simpler" by Albert Einstein.
  4. Results Driven – By combining the focus, clarity and purposefulness with performance based and intuitiveness Jobs really stood out. EA’s could leverage this principle to go back and make sure they are producing results and not just pontificating.
  5. Discipline – Jobs and the overall apple team is known for their extreme rigor and discipline. This shows in their products as the quality is extremely high. The overall EA industry is maturity but there are still well adopted practices that we as EA’s could be more rigorous in our delivery. This comes down to predictable and repeatable results that generates high business value. Discipline + the others we build on make a powerful combination as it ensure we create things of high quality and they matter.
  6. Big Bets – Go big or go home! This principle is all about knowing what to bet big on and executing on it without backing down. Obviously we don’t pull this card often but when we need to we should. This is especially true when we see how disruptive technologies will enable our business.
  7. No Compromise – When it came to quality and meeting the vision there was no compromise. EA’s could use this principle to protect the business such as regulatory compliance, non-functional and functional requirements. This one needs careful balance though, EA’s don’t want to be viewed as stonewalling the organization either. However, you could also argue that if our business model of EA was perfected and we had better traceability to what the business wants we could execute on this principle more?
  8. Emotional Attachment – Jobs had it with his products we as EA’s have it with the designs we create and the relationships we build. For me this really boils down to emotional intelligence. It’s all about having an emotional connection with the businesses we serve.


Recap: Penn State Enterprise Architecture Education & Research Initiative

Mike Walker's Blog: PennState Center for EA

In this session at the Open Group Conference, Dr. Brian Cameron walked us through Penn State Enterprise Architecture Initiative at the College of ISTEA IST. I have blogged about this program before (Enterprise Architecture Goes To College, EA Becoming Academically Recognized and Offered) where I provide a listing of the other college institutions that offer EA in some form or another.

I learned a few additional interesting facts about the program. Specifically some of the key areas that Dr. Cameron is planning on expanding:

  • Launch of online Professional Masters in EA
  • Launch of undergraduate focus in EA
  • Growth of the research portfolio
  • Expansion of the Center for Enterprise Architecture


Below is the recap of the session.



Mike Walker's Blog: PennState Center for EA

The holistic nature of research endeavors aimed at understanding and improving the craft and practice of EA would mean that a number of disciplines will be implicated in defining the problem domain as well as contribute perspectives, approaches and techniques that will be valuable for addressing EA research concerns. Research on EA can benefit from these perspectives contributed by a number of allied disciplines.

  • Enterprise Architecture Advisory Board, over seventy organizations from seven countries
  • First Advisory Board Meeting conducted September 2009
  • Creation of an undergraduate EA degree focus
  • Creation of an online Professional Masters Program
  • Creation of a professional development portfolio
  • Creation of an EA Research Center


Dr. Cameron also established the Federation of Enterprise Architecture Professional Organizations (FEAPO) that is an association of professional organizations whose members have an active interest in the practice and professionalism of Enterprise Architecture.

FEAPO provides a forum to facilitate collaboration and coordination of activities of among Enterprise Architecture (EA) related professional organizations, to work toward a better integrated community and “one face”for the advancement of the profession of Enterprise Architecture. The advent of FEAPO has been welcomed the world over because there is a strong desire among practitioners and organizations in many countries to professionalize and advance the field of enterprise architecture.

This group consists of the following members:

  • Data Management International
  • International Association of Software Architects
  • International Council on Systems Engineering
  • International Standards Organization (ISO)
  • The Association for Enterprise Information
  • The Association for Enterprise Architects
  • The Association of Business Process Management Professionals International
  • The British Computer Society
  • The Business Architecture Guild
  • The Business Architects Association
  • The Center for the Advancement of the EA Profession
  • The EA Shared Interest Group from the Industry Advisory Council
  • The Integration Consortium
  • The Object Management Group
  • The Open Group
  • The National Association of State CIOs


Four Main Areas of the Program

  • Undergraduate Education committee
    • Defining the competencies that an undergraduate student graduating with a focus in Enterprise Architecture should possess.
  • Masters Education committee
    • Defining what competencies should be built into the new online Enterprise Architecture Professional Masters Program.
  • Professional Development committee
    • Defining what type of continuing education offering should be developed in the area of enterprise architecture. Offerings could include certificate programs, executive education, and customized programs for specific organizations.
  • Research committee
    • Defining what research streams should be developed and enhanced in relation to Enterprise Architecture.
    • Helped develop a straw man participation model for the new EA Center.


Key Research Areas

  1. EA career path development
  2. EA framework development and usage
  3. EA maturity assessments
  4. EA Stakeholder analysis & engagement
  5. Understanding EA styles
  6. Value measurement frameworks for EA
  7. Application of EA to areas outside of IT (e.g.: supply chain)



Organizations Involved

Alfabet, Germany

Applied Research Lab/ Penn State

Air Force Research Laboratory

Armstrong Process Group

Assoc. of Enterprise Architects (AEA)

Association for Enterprise Information

BAE Systems Inc

Bllue Cross Blue Shield Association


Booz Allen Hamilton

Business Architecture Guild

Center for the Advancement of the Enterprise Architecture

Profession (CAEAP)


Computer Aid Inc. (CAI)

Computer Sciences Corporation

Cutter Consortium


Department of Homeland Security

Data Management International (DAMA International)

Defense Intelligence Agency

Deloitte Consulting

EMC Corporation

Ernst & Young


Forrester Research




Innoveer Solutions

Integration Consortium

Iteraplan, Germany

International Organization for Standardization (ISO)

Johnson & Johnson

Kaiser Permanente

Kingdee Research Institute, China


Lockheed Martin

Mathet Consulting, Inc.

Meraka Institute, South Africa


Northrop Grumman

Object Management Group (OMG)


PA. State System of Higher Education (PASSHE)


Pinnacle Business Group

PNC Financial Services Group


Progressive Insurance


Smartsphere PPM and EAM Solutions

State Farm Insurance Company

TATA Consultancy Services , India

The Confiance Group

The Enterprise Architecture Shared

Interest Group from the

Industry Advisory Council

The National Defense University

The MITRE Corporation

The Open Group


Trout Technologies

Unisys Corporation

U.S. Department of Defense

U.S. Department of Interior

U.S. General Services Administration


U.S. Office of Management and Budget (OMB)

U.S. Air Force, Chief, Enterprise Architecture Division,

Office of Warfighting Integration and CIO

Verizon Telecom -Information Systems

Virginia Information Technologies Agency

Wipro Technologies

ArchiMate 2.0 Highlights

Mike Walker's Blog: ArchiMate 2.0 Highlights

I am really excited about the new release of ArchiMate.  The reason I am so excited is that for the first time ArchiMate complements TOGAF with a compelling, versatile and unambiguous visual modeling language that covers the end to end enterprise architecture development method and not just solution architecture. Not only do we have the next evolution of the standard but it also comes backed with the training and certification aspects as well that makes this a very real and implementable standard.

This post is centered around some of the key highlights distilled from the my previous two posts (The Open Group Releases ArchiMate 2.0 , ArchiMate 2.0 Certification Released) and some additional analysis of the recent release of ArchiMate.

In general, the  ArchiMate 2.0 aids in the following ways:

  • Helps model the enterprise architecture
  • Works in a manner aligned with TOGAF
  • Supports the preparation and management of:
    • Business change
    • Application rationalization
    • Program and portfolio management
    • Outsourcing scenarios
  • Improves business and IT alignment
  • Performs cost analysis and business case calculations


Additionally, there are six key aspect you should know about the new Archimate 2.0 specification.


#1 Improved and Expanded

Mike Walker's Blog: ArchiMate 2.0 Highlights

  • Based on many years of practical experience of modeling and analysis of Enterprise Architecture by a world-wide user base
  • ArchiMate 2.0 now enables the creation of fully integrated models of the organization’s enterprise architecture, the motivation for it, and the programs, projects and migration paths to implement it


#2 Now fully aligned with TOGAF

Mike Walker's Blog: ArchiMate 2.0 Highlights

With ArchiMate 2.0, it’s the first fully integrated version with TOGAF. With the updates of TOGAF 9.1 (clean up of the spec) and ArchiMate 2.0 we finally have a real modeling notation for EA. It promises to provide a vendor-independent set of concepts, that helps to create a consistent, integrated model “below the waterline”, which can be depicted in the form of TOGAF views.

  • Integrated, consistent and coherent modeling in various phases
  • Specifically designed for enterprise architecture
  • Full support for viewpoints (predefined and user-defined) that supports generation of compelling views for various stakeholders from a central repository
  • Not just the ‘boxes’, but also their interrelationships
  • Explicit support for the service paradigm that defines business, application and infrastructure services with concrete, visible results for various stakeholders can be generated from a repository
  • Impact-of-change, gap analysis, etc.
  • Easy reuse of models, maintained in shared repository


#3 Improved TOGAF ADM alignment

  • The language structure of the ArchiMate Core corresponds with the three main architectures as addressed in phases B, C & D in the TOGAF ADM
  • The extensions to the Core closely correspond with the main aspects to be addressed in the Preliminary phase, Phase A and the Central Requirements management repository, as well as Phases E, F, G and H

The largest alignment area is the Architecture Metamodel as shown below:

Mike Walker's Blog: ArchiMate 2.0 Highlights


However, there are great examples for each phase are shown below:

Preliminary Phase

Team Organization

Mike Walker's Blog: ArchiMate 2.0 Highlights


Building Architecture Principles

Mike Walker's Blog: ArchiMate 2.0 Highlights


A – Vision

Stakeholder Analysis

Mike Walker's Blog: ArchiMate 2.0 Highlights


Business Goals

Mike Walker's Blog: ArchiMate 2.0 Highlights


Architecture Vision

Mike Walker's Blog: ArchiMate 2.0 Highlights


B – Business Architecture

Business Architecture

Mike Walker's Blog: ArchiMate 2.0 Highlights


Realization of Requirements

Mike Walker's Blog: ArchiMate 2.0 Highlights


C – Information Systems Architecture

Baseline / Current State Architecture

Mike Walker's Blog: ArchiMate 2.0 Highlights


Target / Future State Architecture

Mike Walker's Blog: ArchiMate 2.0 Highlights


Gap Analysis

Mike Walker's Blog: ArchiMate 2.0 Highlights


Process Application Support

Mike Walker's Blog: ArchiMate 2.0 Highlights


Information Structure View

Mike Walker's Blog: ArchiMate 2.0 Highlights


Data Dissemination Diagram

Mike Walker's Blog: ArchiMate 2.0 Highlights


D – Technology Architecture

Baseline Technology Architecture Model

Mike Walker's Blog: ArchiMate 2.0 Highlights


Target Technology Architecture

Mike Walker's Blog: ArchiMate 2.0 Highlights


Technology Architecture Gap Analysis

Mike Walker's Blog: ArchiMate 2.0 Highlights


Platform Decomposition Diagram

Mike Walker's Blog: ArchiMate 2.0 Highlights


Application / Technology Support Map

Mike Walker's Blog: ArchiMate 2.0 Highlights


E – Opportunities and Solutions

Transition Architectures

Mike Walker's Blog: ArchiMate 2.0 Highlights


F – Migration Planning

Projects for the Transitions between Plateaus

Mike Walker's Blog: ArchiMate 2.0 Highlights


H & RM – Architecture Change Management & Requirements Management

Traceability Model

Mike Walker's Blog: ArchiMate 2.0 Highlights



#4 ArchiMate 2.0 improves collaboration

By promoting a growth in shared understanding across multiple information roles including business executives, enterprise architects, systems analysts, software engineers, business process consultants and infrastructure engineers


#5 New Core extensions Mike Walker's Blog: ArchiMate 2.0 Highlights

  • The Motivation extension to model stakeholders, drivers for change, business goals, principles and requirements
  • The Implementation & Migration extension to support project portfolio management, gap analysis and transition and migration planning


#6 Inconsistencies have been removed

  • Examples have been improved
  • Additional text has been inserted
  • Certain aspects clarified



ArchiMate 2.0 Certification Released


Along side the release of the ArchiMate 2.0 specification, a new certification for the ArchiMate has been released this week.

Mike Walker's Blog: ArchiMate 2.0ArchiMate, an Open Group Standard, is an open and independent modelling language for enterprise architecture that is supported by different tool vendors and consulting firms. ArchiMate provides instruments to enable enterprise architects to describe, analyze and visualize the relationships among business domains in an unambiguous way.

The ArchiMate Certification Program provides certification for people, training courses and for tools that meet The Open Group standards:

  • The ArchiMate 2 Certification for People Program is a market-driven education and certification program to support ArchiMate 2, and ensures that individuals are knowledgeable about ArchiMate.
  • The ArchiMate 2 Tool Certification Program ensures that a tool meets the mandatory requirements to support the ArchiMate modeling language.
  • The ArchiMate 2 Accredited Training Course Program provides an assurance mark for training courses including an assessment both of the course and also the personnel and organization. In addition, all accredited training course include in their course fee the examination.

This section contains links to the key program documentation, including Datasheets, Policies and Conformance Requirements for each aspect of the certification program, together with the CSQ templates where applicable

Program Datasheets

The following datasheets are available describing the ArchiMate 2 for People Certification program.

Certification for Individuals
Accreditation of ArchiMate 2 Training Courses
Archimate Tool Support Certification




Open Group Conference Presentation–Why EA’s Must Drive Cloud Strategy and Planning

Mike Walker's Blog: Why EA's Must Drive Cloud Strategy and Planning

First and foremost, a big thank you to the attendees of my session.  We filled the room! All the interaction and questions were top notch. I really enjoyed presenting to all of you.

Mike Walker's Blog: Mike Walker presenting Why EA's Must Drive Cloud Strategy and Planning 

In my session,  Why EA’s Must Drive Cloud Strategy and Planning I drove the core message around why the EA should lead Cloud Strategy efforts but then quickly diving into how EA’s can drive this. I use a real world example and show a framework and method I created to provide a repeatable and predictable set of outcomes.

For those that would like to view my presentation you can find it below:


I will continue to provide more detail in future posts.