Click here to close now.


Microservices Expo Authors: Yeshim Deniz, SmartBear Blog, Tim Hinds, Sanjeev Sharma, Elizabeth White

Related Topics: Microservices Expo, Java IoT, Containers Expo Blog, IoT User Interface, Apache

Microservices Expo: Blog Feed Post

TOGAF 9.1 Released – What Does It Imply?

Here are the simple guidelines

If you are planning to take up TOGAF certification examination, you would definitely want to know how the release of TOGAF 9.1 impacts you. You would want to which version you need to study.

Here is the simple guideline. If you are planning to appear for the exam…

  1. …before June 2012 the you should study TOGAF 9
  2. …between June 2012 and May 2013 then you can study either TOGAF 9 of 9.1
  3. …after June 2013 it is only TOGAF 9.1

In a nutshell, if you have already done most of the studying using TOGAF 9.0 then you have slightly more than a year to clear the exam. However, if you have yet to begin the study you better start with 9.1.

What are the main differences between TOGAF 9 and 9.1?

The Open Group has published a presentation in the form of a PDF which provides an overview of the differences – here is the link.

If you would prefer to have a look at the difference as a two pager then I recommend that you go through this post of Mike Walker.

However, I think the biggest difference between the two is how the objectives of each of the ADM phase are written. The latest version seems to be significant improvement. This is also the most important change for those of you who want to appear for the foundation level exam.

You may also need to go through Phase E and F more carefully as they have been reworked.

Comparison of ADM Objectives – TOGAF 9 vs. TOGAF 9.1

Phase Objective as per TOGAF 9 Objective as per TOGAF 9.1
  • To review the organizational context for conducting enterprise architecture
  • To identify the sponsor stakeholder(s) and other major stakeholders impacted by the business directive to create an enterprise architecture and determine their requirements and priorities from the enterprise, their relationships with the enterprise, and required working behaviors with each other
  • To ensure that everyone who will be involved in, or benefit from, this approach is committed to the success of the architectural process
  • To enable the architecture sponsor to create requirements for work across the affected business areas
  • To identify and scope the elements of the enterprise organizations affected by the business directive and define the constraints and assumptions (particularly in a federated architecture environment)
  • To define the ‘‘architecture footprint’’ for the organization — the people responsible for performing architecture work, where they are located, and their responsibilities
  • To define the framework and detailed methodologies that are going to be used to develop enterprise architectures in the organization concerned (typically, an adaptation of the generic ADM)
  • To confirm a governance and support framework that will provide business process and resources for architecture governance through the ADM cycle; these will confirm the fitness-for-purpose of the Target Architecture and measure its ongoing effectiveness (normally includes a pilot project)
  • To select and implement supporting tools and other infrastructure to support the architecture activity
  • To define the architecture principles that will form part of the constraints on any architecture work
  1. Determine the Architecture Capability desired by the organization:
    • Review the organizational context for conducting enterprise architecture
    • Identify and scope the elements of the enterprise organizations affected by the Architecture Capability
    • Identify the established frameworks, methods, and processes that intersect with the Architecture Capability
    • Establish Capability Maturity target
  2. Establish the Architecture Capability:
    • Define and establish the Organizational Model for Enterprise Architecture
    • Define and establish the detailed process and resources for architecture governance
    • Select and implement tools that support the Architecture Capability
    • Define the Architecture Principles
Phase A
  • To ensure that this evolution of the architecture development cycle has proper recognition and endorsement from the corporate management of the enterprise, and the support and commitment of the necessary line management
  • To define and organize an architecture development cycle within the overall context of the architecture framework, as established in the Preliminary phase
  • To validate the business principles, business goals, and strategic business drivers of the organization and the enterprise architecture Key Performance Indicators (KPIs)
  • To define the scope of, and to identify and prioritize the components of, the Baseline Architecture effort
  • To define the relevant stakeholders, and their concerns and objectives
  • To define the key business requirements to be addressed in this architecture effort, and the constraints that must be dealt with
  • To articulate an Architecture Vision and formalize the value proposition that demonstrates a response to those requirements and constraints
  • To create a comprehensive plan that addresses scheduling, resourcing, financing, communication, risks, constraints, assumptions, and dependencies, in line with the project management frameworks adopted by the enterprise (such as PRINCE2 or PMBOK)
  • To secure formal approval to proceed
  • To understand the impact on, and of, other enterprise architecture development cycles ongoing in parallel
  1. Develop a high-level aspirational vision of the capabilities and business value to be delivered as a result of the proposed enterprise architecture
  2. Obtain approval for a Statement of Architecture Work that defines a program of works to develop and deploy the architecture outlined in the Architecture Vision


Phase B
  • To describe the Baseline Business Architecture
  • To develop a Target Business Architecture, describing the product and/or service strategy, and the organizational, functional, process, information, and geographic aspects of the business environment, based on the business principles, business goals, and strategic drivers
  • To analyze the gaps between the Baseline and Target Business Architectures
  • To select and develop the relevant architecture viewpoints that will enable the architect to demonstrate how the stakeholder concerns are addressed in the Business Architecture
  • To select the relevant tools and techniques to be used in association with the selected viewpoints
  1. Develop the Target Business Architecture that describes how the enterprise needs to operate to achieve the business goals, and respond to the strategic drivers set out in the Architecture Vision, in a way that addresses the Request for Architecture Work and stakeholder concerns
  2. Identify candidate Architecture Roadmap components based upon gaps between the Baseline and Target Business Architectures


Phase C The objective of Phase C is to develop Target Architectures covering either or both (depending on project scope) of the data and application systems domains.Information Systems Architecture focuses on identifying and defining the applications and data considerations that support an enterprise’s Business Architecture; for example, by defining views that relate to information, knowledge, application services, etc.
  1. Develop the Target Information Systems (Data and Application) Architecture, describing how the enterprise’s Information Systems Architecture will enable the Business Architecture and the Architecture Vision, in a way that addresses the Request for Architecture Work and stakeholder concerns
  2. Identify candidate Architecture Roadmap components based upon gaps between the Baseline and Target Information Systems (Data and Application) Architectures


Phase D The Technology Architecture phase seeks to map application components defined in the Application Architecture phase into a set of technology components, which represent software and hardware components, available from the market or configured within the organization into technology platforms.As Technology Architecture defines the physical realization of an architectural solution, it has strong links to implementation and migration planning.Technology Architecture will define baseline (i.e., current) and target views of the technology portfolio, detailing the roadmap towards the Target Architecture, and to identify key work packages in the roadmap. Technology Architecture completes the set of architectural information and therefore supports cost assessment for particular migration scenarios.



  1. Develop the Target Technology Architecture that enables the logical and physical application and data components and the Architecture Vision, addressing the Request for Architecture Work and stakeholder concerns
  2. Identify candidate Architecture Roadmap components based upon gaps between the Baseline and Target Technology Architectures


Phase E
  • To review the target business objectives and capabilities, consolidate the gaps from Phases B to D, and then organize groups of building blocks to address these capabilities
  • To review and confirm the enterprise’s current parameters for and ability to absorb change
  • To derive a series of Transition Architectures that deliver continuous business value (e.g., capability increments) through the exploitation of opportunities to realize the building blocks
  • To generate and gain consensus on an outline Implementation and Migration Strategy
  1. Generate the initial complete version of the Architecture Roadmap, based upon the gap analysis and candidate Architecture Roadmap components from Phases B, C, and D
  2. Deter mine whether an incremental approach is required, and if so identify Transition Architectures that will deliver continuous business value


Phase F
  • To ensure that the Implementation and Migration Plan is coordinated with the various management frameworks in use within the enterprise
  • To prioritize all work packages, projects, and building blocks by assigning business value to each and conducting a cost/business analysis
  • To finalize the Architecture Vision and Architecture Definition Documents, in line with the agreed implementation approach
  • To confirm the Transition Architectures defined in Phase E with relevant stakeholders
  • To create, evolve, and monitor the detailed Implementation and Migration Plan providing necessary resources to enable the realization of the Transition Architectures, as defined in Phase E
  1. Finalize the Architecture Roadmap and the supporting Implementation and Migration Plan
  2. Ensure that the Implementation and Migration Plan is coordinated with the enterprise’s approach to managing and implementing change in the enterprise’s overall change portfolio
  3. Ensure that the business value and cost of work packages and Transition Architectures is understood by key stakeholders


Phase G
  • To formulate recommendations for each implementation project
  • To govern and manage an Architecture Contract covering the overall implementation and deployment process
  • To perform appropriate governance functions while the solution is being implemented and deployed
  • To ensure conformance with the defined architecture by implementation projects and other projects
  • To ensure that the program of solutions is deployed successfully, as a planned program of work
  • To ensure conformance of the deployed solution with the Target Architecture
  • To mobilize supporting operations that will underpin the future working lifetime of the deployed solution
  1. Ensure conformance with the Target Architecture by implementation projects
  2. Perform appropriate Architecture Governance functions for the solution and any implementation-driven architecture Change Requests


Phase H
  • To ensure that baseline architectures continue to be fit-for-purpose
  • To assess the performance of the architecture and make recommendations for change
  • To assess changes to the framework and principles set up in previous phases
  • To establish an architecture change management process for the new enterprise architecture baseline that is achieved with completion of Phase G
  • To maximize the business value from the architecture and ongoing operations
  • To operate the Governance Framework
  1. Ensure that the architecture lifecycle is maintained
  2. Ensure that the Architecture Governance Framework is executed
  3. Ensure that the enterprise Architecture Capability meets current requirements


Here are the links to the material from The Open Group

More Stories By Udayan Banerjee

Udayan Banerjee is CTO at NIIT Technologies Ltd, an IT industry veteran with more than 30 years' experience. He blogs at
The blog focuses on emerging technologies like cloud computing, mobile computing, social media aka web 2.0 etc. It also contains stuff about agile methodology and trends in architecture. It is a world view seen through the lens of a software service provider based out of Bangalore and serving clients across the world. The focus is mostly on...

  • Keep the hype out and project a realistic picture
  • Uncover trends not very apparent
  • Draw conclusion from real life experience
  • Point out fallacy & discrepancy when I see them
  • Talk about trends which I find interesting

@MicroservicesExpo Stories
Ten years ago, there may have been only a single application that talked directly to the database and spit out HTML; customer service, sales - most of the organizations I work with have been moving toward a design philosophy more like unix, where each application consists of a series of small tools stitched together. In web example above, that likely means a login service combines with webpages that call other services - like enter and update record. That allows the customer service team to writ...
The APN DevOps Competency highlights APN Partners who demonstrate deep capabilities delivering continuous integration, continuous delivery, and configuration management. They help customers transform their business to be more efficient and agile by leveraging the AWS platform and DevOps principles.
There once was a time when testers operated on their own, in isolation. They’d huddle as a group around the harsh glow of dozens of CRT monitors, clicking through GUIs and recording results. Anxiously, they’d wait for the developers in the other room to fix the bugs they found, yet they’d frequently leave the office disappointed as issues were filed away as non-critical. These teams would rarely interact, save for those scarce moments when a coder would wander in needing to reproduce a particula...
In today's digital world, change is the one constant. Disruptive innovations like cloud, mobility, social media, and the Internet of Things have reshaped the market and set new standards in customer expectations. To remain competitive, businesses must tap the potential of emerging technologies and markets through the rapid release of new products and services. However, the rigid and siloed structures of traditional IT platforms and processes are slowing them down – resulting in lengthy delivery ...
Last month, my partners in crime – Carmen DeArdo from Nationwide, Lee Reid, my colleague from IBM and I wrote a 3-part series of blog posts on We titled our posts the Simple Math, Calculus and Art of DevOps. I would venture to say these are must-reads for any organization adopting DevOps. We examined all three ascpects – the Cultural, Automation and Process improvement side of DevOps. One of the key underlying themes of the three posts was the need for Cultural change – things like t...
Several years ago, I was a developer in a travel reservation aggregator. Our mission was to pull flight and hotel data from a bunch of cryptic reservation platforms, and provide it to other companies via an API library - for a fee. That was before companies like Expedia standardized such things. We started with simple methods like getFlightLeg() or addPassengerName(), each performing a small, well-understood function. But our customers wanted bigger, more encompassing services that would "do ...
In a report titled “Forecast Analysis: Enterprise Application Software, Worldwide, 2Q15 Update,” Gartner analysts highlighted the increasing trend of application modernization among enterprises. According to a recent survey, 45% of respondents stated that modernization of installed on-premises core enterprise applications is one of the top five priorities. Gartner also predicted that by 2020, 75% of
It is with great pleasure that I am able to announce that Jesse Proudman, Blue Box CTO, has been appointed to the position of IBM Distinguished Engineer. Jesse is the first employee at Blue Box to receive this honor, and I’m quite confident there will be more to follow given the amazing talent at Blue Box with whom I have had the pleasure to collaborate. I’d like to provide an overview of what it means to become an IBM Distinguished Engineer.
SYS-CON Events announced today that G2G3 will exhibit at SYS-CON's @DevOpsSummit Silicon Valley, which will take place on November 3–5, 2015, at the Santa Clara Convention Center in Santa Clara, CA. Based on a collective appreciation for user experience, design, and technology, G2G3 is uniquely qualified and motivated to redefine how organizations and people engage in an increasingly digital world.
The cloud has reached mainstream IT. Those 18.7 million data centers out there (server closets to corporate data centers to colocation deployments) are moving to the cloud. In his session at 17th Cloud Expo, Achim Weiss, CEO & co-founder of ProfitBricks, will share how two companies – one in the U.S. and one in Germany – are achieving their goals with cloud infrastructure. More than a case study, he will share the details of how they prioritized their cloud computing infrastructure deployments ...
If you are new to Python, you might be confused about the different versions that are available. Although Python 3 is the latest generation of the language, many programmers still use Python 2.7, the final update to Python 2, which was released in 2010. There is currently no clear-cut answer to the question of which version of Python you should use; the decision depends on what you want to achieve. While Python 3 is clearly the future of the language, some programmers choose to remain with Py...
Opinions on how best to package and deliver applications are legion and, like many other aspects of the software world, are subject to recurring trend cycles. On the server-side, the current favorite is container delivery: a “full stack” approach in which your application and everything it needs to run are specified in a container definition. That definition is then “compiled” down to a container image and deployed by retrieving the image and passing it to a container runtime to create a running...
Somebody call the buzzword police: we have a serious case of microservices-washing in progress. The term “microservices-washing” is derived from “whitewashing,” meaning to hide some inconvenient truth with bluster and nonsense. We saw plenty of cloudwashing a few years ago, as vendors and enterprises alike pretended what they were doing was cloud, even though it wasn’t. Today, the hype around microservices has led to the same kind of obfuscation, as vendors and enterprise technologists alike ar...
“All our customers are looking at the cloud ecosystem as an important part of their overall product strategy. Some see it evolve as a multi-cloud / hybrid cloud strategy, while others are embracing all forms of cloud offerings like PaaS, IaaS and SaaS in their solutions,” noted Suhas Joshi, Vice President – Technology, at Harbinger Group, in this exclusive Q&A with Cloud Expo Conference Chair Roger Strukhoff.
Clearly the way forward is to move to cloud be it bare metal, VMs or containers. One aspect of the current public clouds that is slowing this cloud migration is cloud lock-in. Every cloud vendor is trying to make it very difficult to move out once a customer has chosen their cloud. In his session at 17th Cloud Expo, Naveen Nimmu, CEO of Clouber, Inc., will advocate that making the inter-cloud migration as simple as changing airlines would help the entire industry to quickly adopt the cloud wit...
As the world moves towards more DevOps and microservices, application deployment to the cloud ought to become a lot simpler. The microservices architecture, which is the basis of many new age distributed systems such as OpenStack, NetFlix and so on, is at the heart of Cloud Foundry - a complete developer-oriented Platform as a Service (PaaS) that is IaaS agnostic and supports vCloud, OpenStack and AWS. In his session at 17th Cloud Expo, Raghavan "Rags" Srinivas, an Architect/Developer Evangeli...
Culture is the most important ingredient of DevOps. The challenge for most organizations is defining and communicating a vision of beneficial DevOps culture for their organizations, and then facilitating the changes needed to achieve that. Often this comes down to an ability to provide true leadership. As a CIO, are your direct reports IT managers or are they IT leaders? The hard truth is that many IT managers have risen through the ranks based on their technical skills, not their leadership ab...
Apps and devices shouldn't stop working when there's limited or no network connectivity. Learn how to bring data stored in a cloud database to the edge of the network (and back again) whenever an Internet connection is available. In his session at 17th Cloud Expo, Bradley Holt, Developer Advocate at IBM Cloud Data Services, will demonstrate techniques for replicating cloud databases with devices in order to build offline-first mobile or Internet of Things (IoT) apps that can provide a better, ...
Despite all the talk about public cloud services and DevOps, you would think the move to cloud for enterprises is clear and simple. But in a survey of almost 1,600 IT decision makers across the USA and Europe, the state of the cloud in enterprise today is still fraught with considerable frustration. The business case for apps in the real world cloud is hybrid, bimodal, multi-platform, and difficult. Download this report commissioned by NTT Communications to see the insightful findings – registra...
Application availability is not just the measure of “being up”. Many apps can claim that status. Technically they are running and responding to requests, but at a rate which users would certainly interpret as being down. That’s because excessive load times can (and will be) interpreted as “not available.” That’s why it’s important to view ensuring application availability as requiring attention to all its composite parts: scalability, performance, and security.