How can you use a solution architecture framework like TOGAF or Zachman?

Zachman and TOGAF are not Solution Architecture Frameworks. They are Enterprise Architecture Frameworks. They are best used for transformation efforts. These are very powerful frameworks and very useful in understanding large transformations in a well defined manner. For example, Zachman framework introduced the best practices around What, Why, How, When & Where while TOGAF introduced well-defined architecture domains like Business, Data, Application & Infrastructure and how to iterate thru the inter-dependent changes. Solution Architectures are next level of the abstraction are best defined using functional & non-functional requirements that fit into one of the architecture patterns like web, microservices or packaged solutions.

Embracing solution architecture frameworks, such as TOGAF or Zachman, is akin to wielding a master craftsman's toolkit. These frameworks are not rigid structures but dynamic canvases that empower architects to paint with strategic precision. Think of them as navigational stars guiding you through the cosmic complexity of design. As an architect, I've found these frameworks to be not just methodologies but collaborative symphonies orchestrating alignment. They're not shackles but wings, elevating your designs to strategic heights. So, let TOGAF or Zachman be your artistic accomplices, transforming the blueprint of ideas into the architectural marvels of tomorrow, where every stroke echoes the harmony of a well-structured masterpiece.

Zachman Framework helps and makes it easy to sell perspective of ‘who needs where’ in the process to make a successful solution. It’s a simplified approach that can be well perceived by businesses to understand complexity involved in technology agnostic way .

Solution Architecture framework provides a starting point and brings all stakeholders to think at organizational level. With an increase in cloud adoption, these frameworks also need to evolve and adapt as well to provide the business outcome.

In today's modern Enterprise's landscape, it could seem at least for some dept/teams in an org., that TOGAF & Zachman aren’t that relevant anymore. While it’s true that the ivory tower mindset doesn’t propel any structural grouping, leave alone EA practice, for the modern EA practitioner, the key mantra is all about identifying opportunities & being perseverant at the mastering “art of the possible”. Keep focus on bringing in the best & applicable deliverables from these frameworks making sure solution architecture for greenfield or brownfield settings are adhering to the Enterprise API, Integration, data & security strategies (to name a few) & not considering them as an afterthought, supports developing robust enterprise sol. & platforms.

Both are structured approaches used to guide the process of planning, designing, implementing, and governing enterprise information technology architectures. TOGAF is widely recognized for its comprehensive approach to the development of enterprise architectures. It provides a detailed method and a set of supporting tools for developing an enterprise architecture, which is designed to meet the business needs of an organization. The Zachman Framework, on the other hand, is more focused on providing a taxonomy through which it can view and categorize the artifacts developed in enterprise architecture. Both frameworks aim to create a clear structure for understanding and managing the complexity of IT systems in relation to business goals.

Frameworks like TOGAF provide a structure to the solutioning efforts enabling us to define & design an architecture that is scalable & resilient. TOGAF ADM guides us through the various stages of designing & implementing our architecture and at the same time providing us the flexibility to choose the required steps as needed for our solution allowing us to adopt the framework in Agile development efforts.

The Solution Architecture frameworks(TOGAF or Zachman) serves as an initial foundation, fostering organizational-level thinking. Cloud, devops and microservices adoption continues to rise, TOGAF/Zachman/Gartner frameworks must evolve and adapt to ensure they return the business values as required. They are keep on simplying the design and development of ADM projects.

Solution architecture frameworks are like a toolkit for building a house. Just as a toolkit contains various tools for different tasks (hammers for nailing, saws for cutting, measuring tapes for precision), these frameworks provide a range of methodologies, models, and artifacts for tackling the complexities of solution design. They help architects to construct solutions that are sturdy, functional, and aesthetically pleasing, while ensuring all the pieces fit together seamlessly.

Solution Architecture Frameworks: Solution architecture frameworks provide a structured approach to developing and implementing solution architectures. They offer a set of principles, processes, and best practices to guide architects in designing solutions that align with business objectives and meet stakeholder requirements.

TOGAF provides a best practice framework for adding value, and enables the organization to build workable and economic solutions which address their business issues and needs. Using the TOGAF Standard results in Enterprise Architecture that is consistent, reflects the needs of stakeholders, employs best practice, and gives due consideration both to current requirements and the perceived future needs of the business. It also plays an important role in standardizing and de-risks the architecture development process. Latest version of TOGAF is 10. TOGAF10 includes series guide which provide the practical guidance in the application of the TOGAF Standard.

TOGAF is a widely adopted enterprise architecture framework. It provides a comprehensive approach to designing, planning, implementing, and governing enterprise information architectures. TOGAF consists of various components, including a methodology, a set of framework artifacts, and a content metamodel.

TOGAF framework guides us right from defining the business objectives through to data, application & technology architectures at the same time providing various reference models,  principles & templates that can be immediately adopted in our solutioning efforts. It also ensures that effective risk management & governance models are in place to ensure successful implementation of the solution and the ongoing change management process.

TOGAF is capable of supporting all 4 subsets of over all enterprise architecture - Business, Application, Data & Technology. Most importantly its ADM cycles can be tailored to fit any organizational needs. It emphasizes business goals as architecture drivers and provides a repository of best practices for reference.

TOGAF is also generic and should be adjusted to the specific needs of enterprise is adopted in. The activities related to the adjustment should occur in the first phase of ADM, called Preliminary. The critical factor to successfully implementing TOGAF is choosing its elements wisely. There is not that many organisations that can and should follow full TOGAF guidelines.

Contrary to the popular belief, TOGAF is not a "solution architecture" framework and it's mostly not even about architecture per se, it's about processes that help establish and govern technological development of an enterprise, streamline proper artefacts and actors of said processes and emphasize values and outcomes. TL/DR: things like TOGAF (let's be honest, nobody uses Zachman in 2023) are mostly "meta-methodologies" that help companies building architecture and technology governance methodologies tailored to their particular needs or peculiarities of their internal organization and structure.

TOGAF is a proven framework to develop enterprise architectures. It provides a detailed and structured approach to enterprise architecture, including methodologies, tools, and best practices helping organisations to map their Tech strategy to business goals. TOGAF is the most used and reliable architecture standard in the industry and leveraged by several leading organisations. TOGAF’s architecture development methods(ADMs) has 8 phases including a preliminary phase. TOGAF is based on 4 Pillars, in short BDAT. B - Business Architecture D - Data architecture A - Application Architecture T - Technical Architecture

TOGAF provides a standardized approach to enterprise architecture, ensuring consistency across projects and organisations. It helps align IT strategies with business objectives, ensuring that investment support overall business goal. TOGAF covers all aspects of enterprise architecture, from planning and design to implementation. It’s uses simple terminologies enabling professionals from different unit to understand and communicate. It incorporates best practices and patterns, which can be adapted to specific needs.

TOGAF, or The Open Group Architecture Framework, is a widely used enterprise architecture methodology and framework. It provides a structured approach for designing, planning, implementing, and governing enterprise IT architecture. TOGAF helps organizations streamline their processes, reduce complexity, and align business goals with IT strategies. It consists of a comprehensive set of tools and resources for effective architectural development.

Zachman Framework is an ontology-based approach to enterprise architecture. It provides a matrix-based framework that helps organizations organize, document, and analyze the various facets of complex systems. The framework consists of six columns representing different perspectives (What, How, Where, Who, When, and Why) and rows representing stakeholders at different levels of detail.

TOGAF provides guardrails that guides the solution architecture. If used carefully and tweak to the organisational requirements, the ADM phases starting from Preliminary phase to Architecture Change Management can be adopted at a conceptual level and then it’s up to the Solutions Architect how to steer in between the guardrails that suits the size and appetite to follow architecture framework of the organisation.

TOGAF is basic building framework for ADM projects. To use TOGAF in your projects solution architecture: - Start by understanding the organization's business goals and IT needs. - Utilize TOGAF's methodology and framework to create a structured solution architecture. - Develop architectural artifacts and models that align technology solutions with business requirements. - Continuously use TOGAF to guide design, implementation, and governance to ensure the solution remains aligned with evolving business needs.

TOGAF can be used for solution architecture by following its Architecture Development Method (ADM). The ADM guides architects through a step-by-step process, from defining the scope and objectives of the architecture to creating architecture views, conducting gap analysis, and defining implementation plans.

TOGAF provides tools that should be considered in every phase of the ADM cycle. The devices are explained in a Part of the TOGAF Standard called ADM Techniques.

TOGAF should not be used for solution architecture, but instead is should be embraced as guidelines or best practices for creating and governing appropriate processes within a company; that includes not only solution architecture, but all architecture disciplines (business, technology, infrastructure, infosec, etc). Solution architecture is almost orthogonal to TOGAF, because while the former is more about end-to-end value delivery, the latter is about understanding particular disciplines of architecture and making them all work together.

TOGAF es un marco de trabajo para Arquitectura Empresarial muy completo y a ratos complejo, por lo que para utilizarlo en arquitectura de soluciones se deben seleccionar muy bien las herramientas y métodos de este marco. Lo fundamental es seguir el método de desarrollo de arquitectura (ADM) de una forma simplificada. Se pueden seleccionar una o dos vistas propuestas por TOGAF en cada fase (negocios, datos, software e infraestructura), apoyándose en el Metamodelo para diagramar. En la fase de negocio es muy útil utilizar la herramienta de "escenarios de negocios" y a partir de esa información desarrollar el resto de vistas de arquitectura.

Using TOGAF for solution architecture is like following a travel itinerary. Just as an itinerary outlines the different stops, activities, and accommodations for each day of your trip, TOGAF's Architecture Development Method (ADM) prescribes a series of phases (preliminary, architecture vision, business architecture, etc.) with specific steps, inputs, and outputs. By adhering to this itinerary, architects can ensure they cover all the essential aspects of the solution and deliver value at each stage of the journey.

Zachman for solution architecture involves filling matrix cells for scope and detail. Planner defines scope, owners set requirements, designers plan logic, builders implement, and users ensure operations. For example, a Manufacturing company developing a new product can use cells such as Planner, Owner, Designer, User and Builder perspective cells to come up with scope, requirements, plan, implementation and operations respectively. By filling in the Zachman cells at each perspective, the company creates a comprehensive architecture that guides the development of the new product, ensuring alignment with business goals and a structured approach.

Zachman Framework can be used for solution architecture by applying its matrix structure to analyze and document the different aspects of a solution. Each cell in the matrix represents a specific viewpoint, such as business objectives, system specifications, or technology infrastructure. Architects can use this framework to ensure that all relevant aspects of a solution are considered and addressed.

The important aspect here is the knowledge. The proper use of TOGAF or Zachman can bring much value to the organisation; however, misuse can lead to increased costs and wrong results. Tools or Frameworks won't deliver value by themselves. It must be delivered by experienced Architects who are conscious of their actions.

Before adopting a solution architecture framework, it's essential to assess whether it's the right fit for your organization. While it offers many benefits, it also requires commitment, training, and potentially cultural shifts within the organization. Some organizations might find it too prescriptive or complex, while others will appreciate its comprehensive nature. It's always a good idea to evaluate the specific needs and context of your organization before committing to any enterprise architecture framework.

As organizations grow, they find difficulty in responding to changes. Primarily this is due to a lack of understanding of the complex structure and components in different areas of the organization. Enterprise Architecture frameworks like TOGAF, ZACHMAN are great tool to build alignment between Business and IT at Enterprise Level by - bringing Standardization across Processes and Applications and Tech Stack - Reduce waste efforts and simplify learning curve by enabling reusable capabilities - Building Strong compliance Framework - Optimise Cost by consolidating processes. Also it consolidates partner/Vendors requirements

All SA frameworks are generic and in part - theoretical. Making a particular methodology or framework work for your company (or even choosing one that suits in the first place) is difficult because it requires these key things: 1) an experienced methodologist [role] who not only understands pros and cons of these frameworks, but also existing processes within the company; 2) sponsorship from top-management who are sold on the necessary change or transformation; 3) experienced process team that is competent not only to define and model the methodology, but is empowered to drive necessary changes in the enterprise; 4) internal maturity of the company and its employees who must clearly see the need and outcomes of adopting a framework.

TOGAF isn't strictly a solution architecture framework. While it can be helpful in the process, it isn't specifically designed for that purpose, here's why: 1. Enterprise Architecture: TOGAF's primary focus is on establishing and governing the overall technology landscape of an enterprise. It provides a framework for aligning the strategic business objectives with the right technology investments and ensures consistency. 2. It emphasises creating processes & best practices for building, managing & governing architecture within an organisation. 3. Abstraction & Flexibility: TOGAF operates at a higher level of abstraction compared to solution architecture, defining guidelines and processes.

Adopting an SA framework (or any technology governance methodology in general) must happen top-to-bottom. Senior management must clearly understand why is it needed for them, what value it brings to them and what are the costs and implications of making the change. At the same time, the delivery teams and key IT decision-makers should be brought on board and sold on the SA framework, otherwise they will actively resist the change, viewing it as yet-another-attempt to tell them how to do their job.

Using a solution architecture framework is like learning a new language. It takes time, practice, and immersion to become fluent and reap the full benefits. Don't expect to master TOGAF or Zachman overnight, but commit to a continuous learning and improvement journey. Seek mentors, join communities of practice, and share your experiences with others. Remember that these frameworks are not silver bullets but powerful tools that can help you communicate, collaborate, and innovate more effectively in your solution architecture endeavors.

I am not convinced TOGAF can be called a Solution Architecture Framework. Is much wider and rather should be considered an Enterprise Architecture Methodology. Indeed it can be narrowed down to the scope of a Solution - but not sure of its primary goal. TOGAF is used to cover the scope across multiple Value Streams within an organisation.

It is very critical that the buy-in from everyone right from the top is aligned towards the benefits that implementing such frameworks bring to the organization in the long run, to ensure success of its adoption. This requires to have an evangelist dedicated in driving its adoption within the organization, without which it is bound to fizzle out & fail.