Quite frequently I get asked about the scope of Enterprise Architecture. Sometimes the question is a simple one: what is included in a typical EA initiative? But sometimes there’s a bit more to the question, with an implied: why is that included in EA? This question came up a couple of times this week, so it seemed a good time to go over some of the key points in this blog, and explain what TOGAF has to say about scope.
Each profession has a unique way of doing things. It’s what separates one discipline from another. A psychologist or a physician will think differently about their subject. So what does this mean if you are studying TOGAF?
TOGAF describes three types of architecture role. Two of these types - Enterprise and Solution - are often used in the job title for architects, but it is rare to find someone called a Segment Architect. If you are confused about this missing role... read on, and all will be revealed.
The elements of TOGAF cover the entire lifecycle for Enterprise Architecture (EA), right from setting up EA as an idea within an organization, to creating and maintaining established Enterprise Architectures.
TOGAF is described as an Open Group Standard. But what do we mean by a “standard”, and what happens when there is more than one competing standard?
Without a strong architectural voice at the governance table, the EA contribution and value will always be compromised. Unless you have effective EA governance, then you will suffer the following outcomes:
Both TOGAF and ArchiMate have been developed by The Open Group. TOGAF describes the process of developing an enterprise architecture and ArchiMate is a modeling language which compliments TOGAF. This blog outlines the difference between these standards.
Is there a future for TOGAF? Whether you are a large organization deciding to invest heavily in the use of TOGAF - or an individual thinking about getting trained and certified in TOGAF - you will want to know that TOGAF is not just a passing fad!
Each profession has its unique way of doing things, and that when applying TOGAF the key thing is to “think” like an architect! The first step is to think holistically, and to do this you need to take into account the views and viewpoints of all stakeholders. But what other steps can you take to think as an architect?
A lingua franca is the language, adopted as common, between speakers whose native languages are different but how useful is TOGAF as an Esperanto go-between language for enterprise architects from different backgrounds?