Thursday, February 12, 2009

TOGAF 9 Advances IT Maturity While Offering More Paths to Architecture-Level IT Improvement

Transcript of a podcast on the evolution of the TOGAF 9 architectural framework, announced at The Open Group's 21st Enterprise Architecture Practitioners Conference in San Diego, February 2009.

Listen to the podcast. Download the podcast. Find it on iTunes and Learn more. Sponsor: The Open Group.

Dana Gardner: Hi, this is Dana Gardner, principal analyst at Interarbor Solutions, and you're listening to BriefingsDirect.

Today, we welcome our listeners to a sponsored podcast discussion coming to you from The Open Group’s 21st Enterprise Architecture Practitioners Conference in San Diego, Feb. 3, 2009. Our topic for this podcast, which is part of a series of podcasts on events and major topics of this conference, centers on TOGAF 9, the newly released enterprise architecture framework.

The framework, the latest in the series, was released here Feb. 2 at the conference, and it really represents a departure for The Open Group and for enterprise architecture frameworks in general. It's larger, more mature, and modular to allow folks to enter it from a variety of perspectives. It takes on a much more significant business services and accomplishments perspective.

While IT practitioners and architects will be looking over TOGAF 9 deeply, it’s also going to be of interest to the business side of the enterprise and will be a way for them to understand more about how IT can service their business needs.

To guide us through our discussion on the evolution of TOGAF 9, where it's come from and where it is today, we're joined by Robert Weisman, CEO and principal consultant for Build The Vision, based in Ottawa. Welcome to show, Robert.

Robert Weisman: Delighted to be here.

Gardner: We're also joined by Mike Turner, an enterprise architect at Capgemini, based in London. Welcome to the show.

Mike Turner: Thanks, Dana.

Gardner: It's been my contention for some time now that architecture is destiny. How well you do architecture has a deep impact on your cost, your benefits, your quality of services, and ultimately, how competitive and well run you are as an enterprise.

Let’s go first to Robert. Do you agree that architecture is destiny, and is it perhaps more so now than ever?

Weisman: I can see architecture being an integral part of the business planning process. It structures the business plans and makes sure that the objectives are realizable. In other words, we can use the acronym SMART, specific, measurable, actionable, realizable, and time bound. What TOGAF 9 does is provide an overarching vision and capability with which to cooperate.

Gardner: Let’s take the same question over to you, Mike, this notion that how well you do architecture is a rather important aspect of your competencies of business. [Read more on a panel discussion about the importance of enterprise architecture.]

Turner: Architecture is definitely a factor. I see architecture as a set of tools and techniques that can help you achieve what you want to do as a business. Taking architecture in isolation is not necessarily going to achieve the right things for your organization, because you actually need to have the direction as an input for architecture to support achievement of a particular outcome.

Architecture is really a vital tool for is being able to assure that the correct business outcome is achieved. You need to have a structured approach to how you define the problem space that businesses are facing, then define the solution space, and define how you move from where you are right now to where you want to be.

If that’s not managed in a structured and traceable way that takes you from strategy through to realization, it’s very easy to go off track. It’s very easy for people to reinterpret what the business needs. It's very easy for technology projects, in particular, to take on a life of their own and deliver something, but not necessarily the thing that was originally intended.

So, in some way, architecture is that essential toolkit to make sure that the achievement of change is realized effectively from a content perspective.

Gardner: Change, of course, is a very important aspect of business nowadays, with a difficult economic climate and rapid change across many different industries, how they finance themselves, what their customers are doing, as well as the supply chain. Before we get more deeply into TOGAF 9 and frameworks, what does architecture bring to the ability of an organization to change rapidly?

Mergers and acquisitions

Weisman: When you're talking about change in this climate, there's going to be a great many mergers and acquisitions. Having been through them, there are two ways of going through them -- painful and less painful. Architecture is certainly a less painful way of doing it.

If you want to use knowledge in a knowledge-based economy, you want to make sure, when you actually acquire a company, that they stay acquired, that they don’t just walk. You have to know what they have. You have to also know the value of the soft assets within a company, and that’s what architecture brings to the fore. It brings out clearly the full value of the company, and make sure, before you do an acquisition or a merger, that you can compare the companies and do due diligence to determine whether there is actually a fit.

Gardner: Mike Turner, how about this change aspect and how architecture might be a serious foundation for good change management?

Turner: That question would have a different answer depending on the type of change that you are looking and dealing with. There are some changes that organizations are prepared to encounter and are anticipating. In those cases, architecture is a really good tool to help you to become more effective at dealing with those changes as they happen.

A good example of that would be a large organization that’s on an acquisition trail of buying up small organizations that operate in a similar business model as they do. Using architecture as a technique, you can actually say, "When we acquire a business, we expect it to have these capabilities. This is how we would take those capabilities into our environment." You can quite quickly absorb that change by having a repeatable approach to deal with it.

In those kind of spaces, architecture is really key, because you're anticipating the change, can plan for it, and can manage it strategically. If you don’t do that, then you end up having to face the problem afresh every time you encounter this situation and become ineffective at dealing with those kinds of repeatable processes.

Gardner: What about the discipline that’s required through adoption of a framework, that then puts you in a position to be able to be fleet and agile, when the unanticipated changes are required?

Turner: The other class of change is the change that you weren’t expecting. In those situations, your organization needs to be structured or siloed in ways that actually allow you to quickly reorganize and do things that are unexpected.

In those kind of situations, there's a component where architecture is helpful and then there's a piece where a architecture probably isn’t going to help you at all, because you're dealing with something that’s outside of what you understand today.

Architecture can help you structure your organization so that it's flexible. Outside of that, you're really into the space of a more agile-type approach, where you're not prepared to deal with things, and you just need to try something out, do something quickly, do something tactical, and build from that.

Plan for change

Weisman: There's an old adage that a plan is a common basis for change. If you don’t have the plan or your architectural framework, change is very difficult. Secondly, there is the old Roman adage, which basically says that luck is only where opportunity meets preparation. Architecture is that preparation or part of the preparation for that.

Gardner: Let’s take a brief trip down memory lane. I spoke to Allen Brown, the CEO of The Open Group, and he said that 9 coming out was, in a sense, like giving birth. It was a long gestation period and then a rather difficult last few days. So now that its out, tell us what the frameworks were like leading up to TOGAF 9, and then particularly what differentiates or distinguishes 9. We'll start with you Robert.

Weisman: TOGAF 9, first of all, is more business focused. Before that it was definitely in the IT realm, and IT was essentially defined as hardware and software. The definition of IT in TOGAF 9 is the lifecycle management of information and related technology within an organization. It puts much more emphasis on the actual information, its access, presentation, and quality, so that it can provide not only transaction processing support, but analytical processing support for critical business decisions.

The gestation took five years. I've been part of the forum for five years working on the TOGAF 9. Part of the challenge was that we had such an incredible take up of TOGAF 8. Once a standard has been taken up, you can’t change it on a dime. You don’t want to change it on a dime, but you want to keep it dynamic, update it, and incorporate best practices. That would explain some of the gestation period. TOGAF 8 was very successful, and to get TOGAF 9 right, it was a little longer cycle, but I think it’s been well worth the wait.

Gardner: Mike, what more generally has been the shift or change over time in how frameworks have been developed? Obviously, they've gotten larger and are more inclusive, but more generally, as a character of what they're trying to accomplish, how have frameworks changed over the past 20 years?

Turner: If you look at the industry in general, we're going through a process where the IT industry is maturing and becoming more stable, and change is becoming more incremental in the industry. What you see in architecture frameworks is a cycle of discovery, invention, and then consolidation that follows, as consensus is reached.

One thing that’s really key about TOGAF 9 is that it takes a lot of ideas and practices that exist within individual organizations or proprietary frameworks, building a consensus around it, and releasing it into a public-domain context.

Once that happens, the value you can get from that approach increases exponentially. Now, you're not talking about going to one vendor and having to deal with one particular set of concepts, and then going to a different vendor and having to deal with another set of concepts, and dealing with the interoperability between those.

You're in a situation where the industry agrees this is the way to do things. Suddenly, the economies of scale that you can get from that, as all the participants in the industry starts to converge on that consensus, mean that you get a whole set of new opportunities about how you can use architecture.

Vendor and technology neutral

Gardner: For those listeners who might not be familiar, The Open Group is a vendor-neutral and technology-neutral consortium. TOGAF, which is The Open Group Architecture Framework, is free in its online form, and there's a charge for the printed version.

About 7,500 individuals currently hold TOGAF certification, which is another important aspect of TOGAF, basically approving that you have the knowledge, experience, and understanding to carry it through. To date, 90,000 copies of TOGAF framework have been downloaded and 20,000 hard copies have been sold.

Let’s go back to Robert Weisman. Let’s look a little deeper at what distinguishes TOGAF 9. We mentioned the modularity. There is also the deeper use of the architecture development method. There is also a bit more inclusive comfort, if you will, with cloud computing and service-oriented architecture (SOA), and thinking more of security, start to finish and holistically. Maybe we could go through a laundry list of what distinguishes TOGAF 9.

Weisman: There are many particular factors. TOGAF 9 is, in certain ways, an evolutionary change and in certain other ways a revolutionary change. The architecture development methodology has basically remained similar. However, transforming the architecture from concept into a reality has basically been expanded pretty dramatically, with a great many lessons learned. So, architecture transformation is a large one. Various architectural frameworks have been incorporated into it.

A great many concepts that allow enterprise architecture to be molded with operations management, with system design, portfolio management, business planning, and the Governance Institute's COBIT guidelines and other industry standards have also been incorporated into TOGAF.

Also, there's been a major contribution by such companies as Capgemini, with respect to artifacts and structure. The content meta model is a huge contribution and as a core contribution, but Mike can elaborate upon that.

Overall, it’s much more extensive and it covers much more of the issues that most CIOs and IT architects have to confront on a daily basis. The nice thing about TOGAF is that you don’t have to use it all. You can use bits of it. You can use a large chunk of it, or you can basically choose to use in its entirety. It’s a very modular and flexible framework that way.

Gardner: As I understand it, with 9 they have made a pathway. If you've already adopted 8, you have a bit of a head start, but you don’t have to have gone to 8 in order to start adopting 9. You can work through different modules and start fresh, which I think is a bit of a departure from the past.

Let’s go over to Mike at Capgemini. Tell us about the meta model, and particularly how the use of repositories for policy driven governance and for the organization of assets across both IT and business become relevant now. [More on how Capgemini views cloud computing.]

Addressing challenges

Turner: If we rewind to TOGAF 8 and talk about some of our experiences using TOGAF 8, that's probably a good way to frame what we've tried to add into TOGAF 9 to address some of those challenges that we have encountered.

TOGAF 8, in our experience, was a very powerful process that you could follow to develop architectures. Where you started to hit limitations with TOGAF 8 was around the work products that you produced as a part of executing the architecture development method.

So TOGAF 8 has a lot of language that talks quite informally about the type of activities that an architect would carry out and the type of work products that they would create.

For example, it discusses creating business scenarios and process models and looking at logical data models and physical data models. There's a lot of language in TOGAF 8 that refers to modeling concepts, but then there is nothing actually in TOGAF 8 that says, "This is what a good deliverable looks like," or "This is actually how you would approach modeling those concepts formally."

What we find are organizations that are using TOGAF 8 effectively have two choices. They can adopt the process and leave the content side of things quite open-ended, or they can adopt the process and select something else to do with the content.

At Capgemini, we had a proprietary internal framework for content prior to TOGAF 9. We did a lot of work taking TOGAF 8 process and Capgemini content framework and putting the two together. We found that to be a really effective combination.

What we also found was that, because of the proprietary nature of the Capgemini framework, it became quite difficult for organizations to adopt that configuration. While we're working entirely within a Capgemini environment and we've got control over the people, the skills, the knowledge, and the approach, that works really well. But, when you're looking at multi-vendor sourcing models or looking at upskilling an end user organization, it becomes a lot more difficult.

What we wanted to do with TOGAF 9 was to address that problem head on and to try to create something equivalent to the Capgemini proprietary framework in a way that allows incremental evolution out of TOGAF 8. We took a lot of the informal concepts that were defined in TOGAF 8 and tried to formalize those around some of our internal thinking for content.

Gardner: What is the upside now, since we've made this transition to 9, for the strategic use of repositories?

Turner: One of the things that we've been working on quite heavily over the past few years is getting the various tool vendors to support the Capgemini framework. We've got quite a long list of tool vendors supporting this framework model. What we are expecting is a small incremental effort for those same vendors to transition and make what are essentially cosmetic changes to be able to support the TOGAF 9 content framework.

Very soon, we'll be in a position where we're looking at a market for enterprise architecture tools, where there is now a level of consensus about how to structure models and how to represent them in a way that didn’t exist before. That can only be a good thing for enterprise repositories, because we're moving closer and closer to that consensus point about how content should be structured.

The problem that we're unable to solve is then to take that model, go one step further, and look at the actual operating model within a particular enterprise, how that enterprise chooses to assign roles and responsibilities for carrying out architecture, and how it chooses to federate governance and those kind of concerns. This is fundamental to how you structure repository, because the repository needs to reflect the partitioning that you actually hold within your organizational structure.

We'll see a big improvement, but it’s not the solution in its entirety.

Gardner: Repositories will include a number of different types of artifacts and services, and each organization will have a unique way of approaching that, given their legacy and their history. We do seem to have reached somewhat of a tipping point in recognizing that to manage complexity, to adopt SOA principles effectively and extend them holistically to start dabbling in cloud computing and take advantage of resources and assets available through that particular model or set of models. Does this increasingly require this organizational framework of repository. Do you agree with that Robert?

Underlying rigor

Weisman: No. I've been an enterprise architect now since 1985, and many of these terms come and go. Underlying it is a certain degree of rigor that the frameworks provide.

It doesn’t matter what environment you go into, but if you have a client with 500 definitions of client, their customers, and you're trying to integrate that to take an overview of the customer throughout goodness knows how many databases, what happens is there is certainly a cogent case for consolidating that.

Many organizations carry orders of magnitude more information than they need. The implications for the information technology infrastructure are immense, and the quality of information because of that is pitiful, not allowing the business executives to make proper decisions.

Whether you do cloud computing or not is immaterial. Whatever paradigm you choose, as long as you apply it in a professional and effective manner, it will work. Trying to use a silver-bullet type of approach and a new name to circumscribe rigorous engineering and professional principles would be a grave error.

Gardner: Okay, fair enough. What is it about TOGAF 9, in particular, that does grease the skids a bit for organizations to better adopt and utilize SOA principles, services like software-as-a-service (SaaS), or infrastructure-as-a-service, what we loosely call cloud nowadays?

Weisman: TOGAF was based on a foundational architecture called the Technical Reference Model, which came out of the U.S. many years ago. It's all service oriented.

The term SOA is old wine in new bottles. It's been around for a long time. If you just have a service catalog, if you have duplicate services, it becomes very evident. That’s one of the advantages of the repositories -- you can have an insight into what you actually have.

TOGAF, from its outset in the early 1990s, has been service oriented for that. Just by applying TOGAF, you have a chance of doing your Gap Analysis, of having the visibility into what you have, which makes it not only efficient, but effective from a business perspective.

Gardner: Anything to offer, Mike?

Two points of view

Turner: When you look at SOA, there are probably two different ways that you can think about IT. One offers quite limited benefits to an organization, and the other offers much greater benefit. At a technical level, there are a bunch of standards and design approaches referred to as SOA, that really deal with standardizing the way the applications talk to one another at a software level.

Implementing SOA in this technical sense isn't necessarily a bad thing, and there are certainly benefits to be had in terms of interoperability at a software level from implementing SOA principles. But, just working at that level on its own is not going to give you any business advantages. It’s just going to make it easier to execute development projects.

The power of thinking about services is much more centered on how you look at your organizational capability and how you can more effectively break down your organization into discrete capabilities that are not replicating the same data, business processes, and IT systems in multiple silos.

If you can have a more granular business organization, where you are replicating capability less, it’s much easier to change more quickly, it’s much easier to use those capabilities to do different things, and you see a step change in the performance of your business.

We need to get those kinds of SOA benefits. The first and most important question to ask is, "What are the services that I need in my business? How should I structure my business to make it meet the goals of the industry?" That may be flexibility, but there are actually some organizations or some parts of your enterprise where you actually don’t desire flexibility. You want stability, cost efficiency, and effectiveness in a much more linear, repeatable sense.

TOGAF allows you to understand what makes your business good and then identify what your services are in a way that considers all the different angles. Once that’s defined, you can then put the right technology underneath that to realize what the business is actually looking for. That’s something that can have an absolutely transformational effect on your business.

Gardner: You mentioned that architecture and SOA by themselves don't necessarily aid a business in achieving its goals, but TOGAF 9 has taken steps over this past five years to increase its relevance to business. Robert, explain how that takes place and what that really means?

Weisman: We're talking about services here. The old TOGAF used to talk in terms of the Technical Reference Model. That's still in 9, but we're looking at business services, as Mike was alluding to. We're looking at rationalizing business services and making sure that they're basically well supported by that.

It also assumes that, when you're doing your preliminary planning, you come up with a framework that recognizes the business operation model within your organization and that you have identified your stakeholders and what they actually want to see in the enterprise architecture framework.

Lack of vision

Most projects fail, because they don’t have proper preliminary planning, and they don’t basically go through the problem. They don’t go through the effort of putting a vision in place. As a consequence, they just jump into the architecture -- usually into the applications and technology architecture -- and they find themselves in trouble very quickly for that. They get a great deal of dissatisfaction.

Outsourcing is an excellent example where a high degree of enterprise architecture maturity correlates to a high degree of satisfaction from both the client and vendor of outsourcing services.

Satisfaction, according to Peter Weill’s book, Enterprise Architecture as Strategy, essentially goes from 50-50 with poorer enterprise architecture maturity to 90-90 with enterprise architecture maturity, and that’s satisfaction both for a client and vendor.
So it ends up being a win-win.

When I talk about outsourced services, they are not necessarily all technology either. They can be business processes that are now being outsourced as well, and it will work its way up the stack.

Gardner: We've talked about architecture as important, of course, but the people who then implement the architecture are quite important. To what degree is certification now a particularly relevant aspect of success in a down economy?

Labor issues and getting good people have been a challenge. There have been significant layoffs, but there has also been an increase in the demand for strong IT to support change in a dynamic business environment. Let’s start with you Robert, the role of certification in the year 2009?

Weisman: First of all, there are two dimensions of certification. For example in The Open Group, you have certification with respect to knowledge of the TOGAF methodology, and then you have IT architecture certification. IT architecture is much broader. It includes business architects and enterprise architects as well, and that takes a look at competencies.

There are no international standards for IT architecture. There are many consultancies that work globally. So, all of a sudden, you're called upon, but this provide a global standard and a global level of confidence with respect to the individuals.

The IT Architect Certification (ITAC) and the IT Services Certification (ITSC) that The Open Group are doing, will provide a level of comfort and assurance to clients that basically they are getting people with a uniform degree of competence.

With respect to the downturn, this is going to become important. Right now, most architects call themselves architects, but there is no international standard against which to measure them. That’s led to a great many architecture failures, which, when you examine them, are not surprising.

Using a standard methodology will also enable RFPs to be written rapidly. What happens is now when you say, "I want a vision as per TOGAF," everybody knows what the baseline is. Then, both suppliers and clients can come up with the assurance, saying, "These guys know what they're talking about," and they can put in a reasonable bid for that.

You're talking about the standardization of product and competencies. This is becoming increasingly important. Globally, there's a huge decrease in enrollment in computer science and computer engineering programs, because of the fact that clients aren’t recognizing these professional designations. Many people say there's no business case in going through an expensive degree program, when you can take a short course and have a very deep but very narrow competency in a particular field?

Certification, both from a competency point of view and from a product point of view, is the wave of the future and extremely important.

Gardner: Mike, how does Capgemini look at the certification process and how important it is for your clients?

Demonstrating capability

Turner: It’s very important, and there are two reasons why. If you look externally in trying to source resources from the market -- whether that’s through a subcontractor or to recruit individuals -- having certification is a good way for candidates to be able to demonstrate that they have reached a level of capability and also for potential employers to put in place a benchmark that filters out the noise.

They can spend much more time looking at individual candidates and assessing them as potential fits to the roles that they're trying to source. I wouldn’t say that certification necessarily guarantees that you get the right person, but it gets you to a short list much quicker.

Gardner: How about practitioners themselves? Is there a significant boost in the pay or ability to find the right jobs as a result of this TOGAF certification?

Turner: If you look at the UK market, there is a correlation between certification and higher pay, but I wouldn’t that that’s the absolute overriding factor.

Another angle to this is, if you look within an organization -- and Capgemini as an organization has a large number of architects, but our client base has architects that work in their organizations -- certification starts to outline a career path for architects within an organization and to allow them to develop themselves and demonstrate that they are improving in capability.

Capgemini has a very active certification program, which we run internally and which is based on experience, engagement, and community. We find that to be a very effective way to build and maintain a community and show professional development and mentoring within our internal environment. That’s something that we help our clients do as well.

Ultimately, architecture is about a network of people. It's about communicating effectively within that network, and then that network having a good face to all the stakeholders for architecture. Having training certification, professional development, and those factors can only be a good thing for building that practice.

Gardner: We're going to be wrapping up in a bit. It’s clearly too soon to look into the future. We just got TOGAF 9 out of the gate. I wonder if there isn’t any extrapolation or looking from the vision point of view where we have come from TOGAF 8 to TOGAF 9, to perhaps give some indication to our listeners as to where TOGAF and enterprise architecture frameworks in general are headed.

Let’s start with you, Robert, for our last question. What can we say, given what we now know about TOGAF 9, as to where the next TOGAF might lead us?

Weisman: There are many working groups right now working on TOGAF, the next generation, whatever it’s going to be called, for example, the Information Architecture Working Group and the like. They've been established and they're looking towards the future and the strategy for that.

Working together

What I see eventually is a lot of these architectural frameworks will start emerging. One of the beauties of TOGAF is that it works very well in conjunction with other architectural frameworks. Let’s say that you're using another architectural framework, which a lot of the industry verticals have. Normally they're model based and TOGAF is mainly process based. They come together, extremely well together, and this is a major strength.

You can’t say, "I'm using this. I can’t use TOGAF." TOGAF will help you deliver the other framework. One of the major issues with many of the other frameworks is that they're wonderfully detailed models, but there is no methodology in place with which to deliver them in a systematic manner. So, I see TOGAF not in terms of an ├╝ber framework, but certainly a cooperative framework.

It’s also linked with other management frameworks and it’s going to be closer to project management, portfolio management, and the like, which should make it an easier transition. An integrative framework of choice might be a way of describing where TOGAF is going. It's going to be a pointer to other standards and how to integrate them within a company.

We're not there to duplicate the work of other wonderful organizations. It’s how to integrate all the wonderful work, because right now, for executives at the CIO and CEO level, it’s pretty confusing out there.

Gardner: Mike Turner, do you agree on that particular extrapolation in the future of more inclusivity and convergence across business types of frameworks, or are there other future elements of TOGAF we should consider?

Turner: Those are all valid points, and I'd add a few more. One thing we're going to see with TOGAF 9 being available now in the industry is that there would be a reaction to that. A lot of the frameworks and standards that sit around the edge of TOGAF are going to realign slightly to make themselves more consistent with how TOGAF works, which, as Bob mentioned, will help TOGAF integrate some of these different approaches. That will happen without changing TOGAF itself. It would just be that the industry will change to be more aligned around the TOGAF model.

In terms of TOGAF development, there's going to be a big focus on people and organizational aspects within TOGAF, trying to formalize the different skills that are required and the different places where you can use TOGAF within an organization.

Ultimately, that will lead to much greater specialization of the method that we have right now, because we have a single method that applies at a very strategic level and also at a very tactical level. As we understand the organizational context, we can start to be more specific about how the method is applied in different contexts.

Another trend is around the formalization of the specification content. We would expect to see, particularly around a standard for managing this kind of massive information that you are managing semantic content and mature, that TOGAF will start to embrace some of those standards. Looking at formal languages for specifying the methodology and putting the tool set itself within software tools that can be customized and configured is something that we would look to do.

Gardner: Well, that gives us quite a bit to look forward to, some more maturity, even though we have reached a significant milestone in the current level of maturity.

We have been talking about TOGAF 9, its introduction and where its come from and part of its evolution. Our conversation today comes to you through the support of The Open Group, and we are coming to you from the 21st Enterprise Architecture Practitioners Conference in San Diego, in February 2009.

I want to thank our panelists. We have been joined by Robert Weisman, CEO and principal consultant for Build The Vision. Thank you Robert.

Weisman: You're very welcome.

Gardner: Also Mike Turner, enterprise architect at Capgemini. Thanks so much, Mike.

Turner: Thanks.

Gardner: I'm Dana Gardner, principal analyst at Interarbor Solutions. You've been listening to BriefingsDirect. Thanks and come back next time.

Listen to the podcast. Download the podcast. Find it on iTunes and Learn more. Sponsor: The Open Group.

Transcript of a podcast on the development of the TOGAF 9 architectural framework, announced at The Open Group's 21st Enterprise Architecture Practitioners Conference in San Diego, February 2009. Copyright Interarbor Solutions, LLC, 2005-2009. All rights reserved.

View more podcasts and resources from The Open Group's recent conferences and TOGAF 9 launch:

The Open Group's CEO Allen Brown interview

Live panel discussion on enterprise architecture trends

Reporting on the TOGAF 9 launch

Panel discussion on security trends and needs

Panel discussion on cloud computing and enterprise architecture

Access the conference proceedings

General TOGAF 9 information

Introduction to TOGAF 9 whitepaper

Whitepaper on migrating from TOGAF 8.1.1 to version 9

TOGAF 9 certification information

TOGAF 9 Commercial Licensing program information

No comments:

Post a Comment