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!
TOGAF and ArchiMate come from the same stable as they are both EA standards managed and maintained by The Open Group.But to what extent do they overlap or complement each other? How can they be used in combination? And how can we overcome any limitations they might impose? Read this blog to find out!
TOGAF is largely about identifying and documenting architecture requirements... but what is an Architectural Requirement? Frequently we document requirements, not "architecture" requirements! In this blog I explain what we need to do to make requirements architectural.
Read this TOGAF Case Study by Enterprise Architecture expert Roger Evendern: Using TOGAF to Re-engineer Legacy Systems and Data
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.
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?
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.
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:
TOGAF makes a big point of the need for good stakeholder management, devoting the whole of Chapter 24 to the subject, while Step 2 in Phase A: Architecture Vision describes the process to Identify Stakeholders, Concerns, and Business Requirements.