Here’s some brand new content from the SoftwareArchitect.ca YouTube channel that you might find interesting.
TOGAF 9.2 What’s New
In this video, we look at the brand new TOGAF® 9.2 standard that was just released in April 2018, and go over the four main differences from the version 9.1 of the standard.
In this video, I show you how to create a Windows Web App in Microsoft Azure. Windows Web App. We go through the Azure Portal, and see how form fields get filled in. If you can’t afford to create resources in Azure, but want to see how it’s done in 2018, this is the video for you.
Or you can see the video directly on YouTube.
Well hi there. My name is Scott Duffy from Software Architect dot ca and in this video I’m going to talk about the brand new TOGAF 9.2 standard and tell you the differences between that and TOGAF 9.1. If you’re not aware the open group just released the TOGAF 9.2 standard in April of 2018. Now I’ve gone through it and I’m highlighting the differences between that and TOGAF 9.1 for you. So you might be wondering what is the difference. Well I’m going to pull out four things specifically that I’ll talk about today. The four things are number one they’re starting to treat the TOGAF standard as a modular standard or a modular structure so the TOGAF 9.1 standard came up to 650 printed pages and so the TOGAF 9.2 standard is now 500 pages. They’ve been able to pull out 150 pages. Some of those pages have just been removed and some of them have put into other documents that are called TOGAF series guides. To give you an example, the TRM which is a technical reference model and the III-RM, are both now in a series guide and is not part of the core specification.
Now why are they making it modular? Well first of all there were a few things in there that are examples and they were not part of the core standard so they were putting in reference models and some examples with other standards and it wasn’t really contributing to the standard itself. It was just basically extra content, so they started removing some of this extra content and one of the problems they found with the TOGAF 9.1 standard was that it was so big 650 pages it’s hard to make substantive changes to that. Because it a big monolithic document going in there and starting to make changes, there were just pages and pages, hundreds of change requests that were being submitted and they were just not able to go through and deal with all of this and so they’re breaking up the document into the core standard and into series guides and it’s going to make it easier in the future like if they do come out with the major change, if they come out with TOGAF 10, it’ll be easier to create that if things are modular.
The second difference between TOGAF 9.2 and TOGAF 9.1 is that they’re starting to make some changes to the way that the business phases are handled and so right now in the TOGAF 9.1 standard you go into the architect’s revision phase and you come up with an architect’s revision, but you’re not really dealing with the business problems. So now, in the architect’s revision phase they’re having things about the business model, defining business capability, et cetera. There’s new artifacts being added to the vision phase and so it’s basically pulling forward some of the discussions of the problems of the business from phase B into phase A which makes sense.
The third thing that I’ll talk about is if you look at the definitions section for 9.1, there’s already lots and lots of pages devoted to terms. Well 9.2 has added a whole bunch of definitions and so now having a standard set of terms is one of those foundational concepts of the TOGAF standard because having a common language allows us to talk about enterprise architecture and when I say, you know talking about the enterprise you’ll know that the definition of the word enterprise is because that’s defined in the standard. So now there are more definitions that are being standardized. Part of this is because the ISO, the international standards organizations are coming up with architecture documents and they’re standardizing terms in there as well and so basically it’s aligning the TOGAF standard with the ISO 42010 standard for 2011.
And the fourth thing that I’m going to point out to you is the content meta model. If you’ll recall the TOGAF standard has defined … There’s a diagram which I won’t show you right now, but the diagram that defines the content meta model how all the documents, the processes and things relate to each other within the architecture repository, so now because we’re adding new artifacts into phase A and new artifacts into phase B, splitting up things that are treated as one element within TOGAF 9.1, then there’s a basically some additional changes to the content meta model. New entities on the diagram, revisions of existing entities, and new relationships between those entities and for instance they pulled out location into what’s called a global entity and as we get into the course for TOGAF we’ll talk about content meta model.
So to be honest, looking over these changes majority of the document, of the 500 remaining pages have not changed. A lot of the chapters have no updates or just some reorganization of the content. I think what the open group is doing is setting itself up to be able to make more substantial changes in the future. So the TOGAF 9.2 standard can be treated like a true minor release of TOGAF, cleaning some things up. Again the big changes that I’ve outlined in this video in terms of content meta model, in terms of phase A and phase B, et cetera, definitions, those are basically some things that have been lingering for a while that have needed to change, but as we get into 2019, 2020, 2021 we should expect that there be other changes to TOGAF that are more substantial to address some of the changes of the businesses going into this last seven eight years a lot of businesses have changed, so expect the standard to change more frequently.
To summarize this whole video. TL-DR basically they’ve cleaned some things up, fixed some bugs, fixed errors, removed unnecessary content, and they’re basically just setting themselves up for some easier things in the future for making changes of this standard. So this is the first few steps for updating the standard.