Skip to Content
Author's profile photo Sri Rajagopalan

TOGAF and SAP EAF Relationship – Part 2

Executive Summary

In the TOGAF and SAP EAF Relationship – Part 1, I had discussed about the drivers for launching SAP EAF and how it was built from TOGAF 8.1.  This blog goes in to a bit more details of how EAF can complement TOGAF and fill the gaps for customers who have standardized on TOGAF.

For SAP customers who have a fairly significant SAP footprint (more than 50% of their core operations run on SAP software) and have standardized on TOGAF 8.1 or 9.0, SAP EAF can still add tremendous value guiding the development of their Enterprise Architecture.  The key areas where they can leverage SAP EAF are described below.

Enterprise Architecture – Process and Methods

TOGAF 8.1 Architecture Development Method (ADM) is fairly comprehensive and provides a narrative of each architecture phase, describing the phase in terms of objectives, approach, inputs, steps and outputs. But it does not provide guidelines on how to go about performing the steps and create the necessary outputs. This can make TOGAF an abstract template for architects who are not seasoned TOGAF practitioners. So customers can refer to SAP EAF and leverage the following extensions to conduct each phase within ADM.

More Guidance on ADM – EAF contains more precise definitions of the concepts, specific tasks and terminology.  Plus for each phase, EAF offers clear and specific narratives, provides worksheets clearly describing the outputs and a number of accelerators that customers can leverage to conduct each ADM phase.  The combination of worksheets, narratives and accelerators can add clarity for customers to create the required work products during each phase of ADM.

Process Flexibility – “Not all Enterprise Architectures are equal”.  It is seldom that customers go through the rigors of creating both “as-is” and “to-be” architecture analysis.  On many occasions, customers only want to focus on “to-be” architecture as they don’t see limited value in rehashing through current architecture as they acknowledge that it is not optimal and would rather spend time and resources focusing on target architecture.  To support these differing needs, EAF introduces the notion of “architecture style” providing the process flexibility for customers that identifies “core” versus “light” activity and which iteration (“as-is” first or “to-be” first) needs to be performed in an efficient manner.

Note – Both these extensions were subsequently included in TOGAF 9.0 content.

SAP EAF Meta Model

TOGAF 8.1 did not contain a Meta Model while SAP EAF introduced this explicitly. Subsequently, the SAP EAF Meta model was included in TOGAF 9.0 mostly “as-is” with minor modifications. Nevertheless, the Meta model in EAF enables a clear understanding of enterprise architecture in its entirety. The Meta model clearly classifies the enterprise into contextual and architectural elements and defines the EA concepts into structured and semantically defined entities.  The Meta model depicts clear relationships between those entities and shows the linkages between business architecture and the rest of the architecture domains.  The entity relationships depicted in the Meta model can serve as a good schema for any EA modeling tool and can be leveraged effectively to clearly define one of the main EA artifacts called “matrices”. 

EAF Artifacts

TOGAF 8.1 provided a list of example architectural views, but does not define mandatory criteria for compliance.  Also it neither describes the majority of views nor specifies the content or their presentation. SAP EAF clearly organizes the artifacts namely Catalogs, Matrices and Views (Views are known as Diagrams in TOGAF 9.0) by the individual phase of ADM and provides more specific descriptions of those artifacts.  The artifacts are clearly integrated into the SAP EAF Process and Meta model. Customers can leverage the detailed guidance and examples in SAP EAF to develop these artifacts.

SAP Specific Mappings

This is by far where SAP EAF offers distinct content level guidance to customers who already have made or planning on making a significant investment in SAP Products and Services. The mapping to SAP content can accelerate customer’s efforts to develop their Enterprise Architecture. EAF contains references and mappings to SAP business, application and technical content that can serve as reference and/or reusable models and patterns either directly or as a template. Also SAP EAF contains direct mapping of each EAF Meta model entity to SAP specific entity providing clarity and guidance. 

Conclusion

In conclusion, SAP EAF can offer certain distinct advantages, can complement TOGAF 8.1/9.0 and accelerate SAP customer’s effort to develop their Enterprise Architecture. In addition, SAP Business Transformation Services Group offers a set of professional services that can be delivered by SAP experts to turn customer’s EA vision into a reality.

Assigned Tags

      Be the first to leave a comment
      You must be Logged on to comment or reply to a post.