The pace of technological change is leaving some businesses unable to compete. This blog covers how Application Architecture lays the foundation for agility, scalability and reliability in an organization's application framework.
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.
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.
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.
This blog covers how in the rapidly evolving digital market a Solution Architect builds a solution to face new challenges faced by your organization.
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.
As technology advances the pressure increases drastically on business infrastructure. This blog covers how Infrastructure Architecture is structured approach to help your organization run efficiently in the digital landscape.
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 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: