Lesson 156 - Zachman Framework in 10 Minutes

Summary

In this 'Software Architecture Monday' lesson, Mark Richards introduces the Zachman Framework, an Enterprise architecture framework developed by John Zachman in 1992. Richards explains the framework's two-dimensional taxonomy of models, which are organized by perspectives (executive, business, architect, engineering, and technical) and interrogatives (what, how, where, who, when, and why). He discusses the utility of each model, emphasizing the 'why' model as particularly important for understanding business motivations and architecture decisions. The framework is praised for its comprehensive approach to modeling the enterprise, though it's noted as a taxonomy rather than a procedural guide.

Takeaways

• 😀 The Zachman Framework is an architecture framework developed by John Zachman in 1992, designed to provide a comprehensive structure for understanding enterprise information.
• 🎯 The framework consists of two dimensions: different perspectives (executive, business, architect, engineering, and technical) and a set of models that answer core questions (what, how, where, who, when, and why).
• 📚 The models within the framework are small and well-scoped, making it easier to focus on specific aspects of the enterprise architecture.
• 🔍 The 'what' model is particularly useful for inventorying entities, such as business entities, applications, databases, technologies, and infrastructure.
• 🛠️ The 'how' model describes processes, including business processes, system dependencies, build and release procedures, and infrastructure procurement.
• 🌐 The 'where' model addresses distribution networks and the physical locations of business operations, systems architecture, and team locations.
• 👤 The 'who' model focuses on organizational units, responsibilities, and security models, detailing who owns what and who is allowed to do what within systems.
• ⏰ The 'when' model deals with timing cycles, event schedules, system availability, and backup cycles.
• 💡 The 'why' model is crucial for understanding motivations, intentions, and justifications for architectural decisions, from strategic goals to technical infrastructure choices.
• 🔑 The Zachman Framework is not a process framework but serves as a taxonomy for modeling the enterprise, providing a structured way to capture and organize key information.

Q & A

What is the primary focus of the Zachman Framework?

The Zachman Framework is a taxonomy of models that focuses on organizing and structuring information about an enterprise's architecture from different perspectives and answering core questions about what, how, where, who, when, and why.

Who developed the Zachman Framework and when was it created?

The Zachman Framework was developed by John Zachman from IBM in 1992.

What are the two dimensions of the Zachman Framework?

The two dimensions of the Zachman Framework are different perspectives (executive, business, architect, engineering, and technical) and a list of models that answer core questions in the universe.

What is the initial challenge mentioned in the script regarding the Zachman Framework?

The initial challenge is knowing what goes into each model for each perspective because the framework consists of grids where various models are placed.

What does the 'What' model in the Zachman Framework represent?

The 'What' model represents an inventory of sets and entities, essentially lists of things that are important to the enterprise from different perspectives.

How does the 'How' model differ from the 'What' model in the Zachman Framework?

The 'How' model describes various processes, both technical and non-technical, and how they operate within the enterprise, whereas the 'What' model focuses on the inventory of entities.

What does the 'Where' model in the Zachman Framework cover?

The 'Where' model is about distribution networks and where things happen within the enterprise, including physical locations, logistics of business processes, and system distribution.

What aspects of the enterprise are included in the 'Who' model?

The 'Who' model includes actors and responsibilities for areas within the enterprise, such as organizational units, product owners, system owners, and infrastructure owners.

What is the purpose of the 'When' model in the Zachman Framework?

The 'When' model focuses on timing cycles and dependencies, including event cycles, processing schedules, system availability, and timing for backups.

Why is the 'Why' model considered the most important by the speaker?

The 'Why' model is considered the most important because it addresses the motivations, intentions, goals, strategies, and justifications behind architectural decisions and infrastructure choices.

How does the speaker suggest using the Zachman Framework in relation to TOGAF?

The speaker suggests adding Zachman's 'Why' model to the TOGAF ADM (Architecture Development Method) to enhance the understanding of motivations and justifications for architectural decisions.