Tailoring the TOGAF Architecture Development Method

The Open Group Architecture Framework TOGAF® is an industry-standard and foundational framework that can be applied to develop any kind of architecture and Enterprise Architecture practices in any context.  It is freely available for any organization wishing to develop an Enterprise Architecture for internal use.

As a generic architecture framework, TOGAF® requires adaption for specific contexts. According to the TOGAF® specification v9.2, it is "in all cases expected that the architect will adapt and build on the TOGAF® framework to define a tailored method" quote from TOGAF® specification v9.2.). The SAP EA Methodology leverages and tailors TOGAF® to provide a refined methodology for most use cases along the entire software lifecycle.

SAP product engineering, SAP Customer Advisory, SAP Service Delivery, and key SAP customers from various industries closely collaborated to the following tasks:

• Refine and detail concepts, artifacts, techniques, and principles
• Prepare and reduce tailoring efforts for typical architecture needs

The SAP EA Methodology is based on The Open Group Architecture Framework and is designed to reduce tailoring efforts for a broad range of architecture activities.

Additionally, the SAP Enterprise Architecture Framework also includes SAP Reference Architecture Content - provided by SAP experts - such as tooling, practice recommendations, and professional services. These enable the following

• They allow SAP, SAP partners, and customers a jump start in the architecture engagements, thereby reducing and minimizing tailoring and preliminary efforts and  
• They provide concrete guidance in all phases to ensure a coherent architecture engagement.

The provisioning of SAP portfolio-agnostic Reference Business Architecture content and SAP or Partner Reference Solution Architectures supports rapid initiation of many architecture projects. The Reference Architecture content can help to overcome typical difficulties when starting architecture activities from scratch.

The SAP reference solution architecture provides valuable information on possible integration, APIs, middleware content, and master data distribution between SAP and Non-SAP solution components as partners of third-party components. System Integrators will find valuable insights in combining solutions, software, or services from different providers.

Meanwhile, reference architecture content is the only valuable input that needs to be adjusted to the needs and goals of concrete architecture activities.

Tooling, practice recommendations, and service offerings provide intense help and support when establishing Enterprise Architecture practices, Enterprise Architecture capabilities, or specific architecture projects.

Summarize how the tailored SAP EA Framework builds upon the generic TOGAF standard to provide a more precise, practical, and effective approach to enterprise architecture within the SAP environment.

The Open Group Architecture Framework (TOGAF) is a framework for enterprise architecture that provides an approach for designing, planning, implementing, and governing an enterprise information technology architecture. TOGAF is a high-level approach to design. It is typically modeled at four levels: Business, Application, Data, and Technology. It relies heavily on modularization, standardization, and already existing, proven technologies and products.

TOGAF was developed starting 1995 by The Open Group, based on DoD's TAFIM. As of 2016, The Open Group claims that TOGAF is employed by 80% of Global 50 companies and 60% of Fortune 500 companies.

Members of the Open Group Standard are, for example, Shell, Boeing, Apple Inc., Honeywell International Inc., and many more.

The ADM is iterative, over the whole process, between phases, and within phases (see the TOGAF Standard - ADM Techniques)For each iteration of the ADM, a fresh decision must be taken as to provide the following:

• The breadth of coverage of the enterprise to be defined
• The level of detail to be defined
• The extent of the time period aimed at, including the number and extent of any intermediate time periods
• The architectural assets to be leveraged, including:
  • Assets created in previous iterations of the ADM cycle within the enterprise
  • Assets available elsewhere in the industry (other frameworks, systems models, vertical industry models, and so on)
• These decisions should be based on a practical assessment of resource and competence availability, and the value that can realistically be expected to accrue to the enterprise from the chosen scope of the architecture work
• As a generic method, the ADM is intended to be used by enterprises in a wide variety of different geographies and applied in different vertical sectors/industry types

Architecture Vision describes and defines the following:

• It describes the broader context in which architecture work needs to take place
• It defines the solution context and solution concept while taking constraints and assumptions into account
• It includes the following:
  • Statement of architecture work
  • Project setup and initiation of the Architecture Development Cycle
  • Organizational capability assessment

Business Architecture describes and defines the following:

• It describes how business works
• It aligns organization's operating model, strategies, and objectives with IT
• It includes the following:
  • Objectives and goals
  • Business capabilities / business processes carried out by the enterprise
  • Major organizational structures

Information Systems - Application Architecture include the following:

• Application and service-centric view of an organization
• Portfolio management: inventory of key application services that support business services
• It includes the following:
  • Descriptions services that support the business processes
  • Descriptions of the interaction / interdependencies (interfaces) of the organization's application systems

Information Systems - Data Architecture include the following:

• Describes what the organization needs to know to run its business processes and operations
• Describes how data is bound into the workflow
• Includes:
  • Standard data models
  • Data management policies
  • Descriptions of the patterns of information production and consumption in the organization

Technology Architecture enables the following:

• It lays out the hardware and software supporting the org
• It provides a logical, vendor-independent description of infrastructure/system components necessary to support the application and data domains
• It includes the following:
  • Operating systems
  • Network connectivity components

Opportunities and Solutions define and identify the following:

• They define a holistic roadmap indicating the transition to the target architecture over a period of time (3-5 years)
• They identify the required programs and projects, including dependencies
• It includes the following:
  • Architecture Roadmap definition and alignment with key stakeholders
  • Creation of a work break down structure for planned projects