Microservices Expo Authors: Pat Romanski, AppDynamics Blog, Liz McMillan, Elizabeth White, Stackify Blog

Related Topics: Microservices Expo

Microservices Expo: Article

So Many Frameworks...So Little Time: What's an Architect to Do?

The relationships between The Open Group Architecture Framework and the U.S. Department of Defense Architecture Framework

Numerous architecture framework standards have been developed and have matured over the past decade. Some of these standards overlap in their focus areas, and others address completely different aspects of the architecting process. In this latter case, a natural synergy can sometimes be identified and leveraged between frameworks.

An industry working group was formed to analyze and document the relationships between The Open Group Architecture Framework and the U.S. Department of Defense Architecture Framework, identifying complementary areas between these two standards. This article is a brief summary of that initiative's detailed 50-page white paper, "The Open Group Architecture Framework and the U.S. Department of Defense Architecture Framework."

The Open Group Architecture Framework (TOGAF) is primarily focused on architecting methodology - i.e, the "how to" aspect of architecture without prescribing description constructs to document the architecture. The U.S. Department of Defense Architecture Framework (DoDAF) is focused on architecture description via a set of views without specifying any methodology. The complementary aspects of these two frameworks lead to the question: "Can architects benefit from leveraging both TOGAF and DoDAF together?" Two years ago, this is what a working group that included representatives from MITRE, Raytheon, and Architecting-the-Enterprise - supported by members of The Open Group Architecture Forum - set out to study. Core members of the group included individuals from the official DoDAF and TOGAF standards working groups. The baseline versions of the documents used were TOGAF Version 8.1 and DoDAF Version 1.0. Upcoming revisions of both these standards will heighten their support of architecting service-oriented systems, and both are valuable enablers to architects and architecture teams.

Below are some of the group's key findings, as well as insights into how architects can use these frameworks to align their business objectives better with IT infrastructure and systems.

Architecture Methodology: The Open Group Architecture Framework
The Open Group first developed the TOGAF Architecture Development Method (ADM) in 1995, baselining it from the Technical Architecture Framework for Information Management (TAFIM), a series of architecture guidance documents provided to them by the U.S. Department of Defense. The DOD spent millions of dollars and several years evolving its TAFIM before turning it over to the Open Group for its ongoing maturation and dissemination across government and industry. TAFIM was subsequently retired.

The ADM is a prescriptive, step-by-step instruction guide for "how to" architect. It's presented in a series of phases that guide the architect or architecture team through the architecting lifecycle of system development. The first seven releases of TOGAF ADM (1995-2001) were focused on providing technical architecting guidance. The 2002 release of TOGAF 8.0 extended this earlier technical focus into four areas: business, data, applications, and technology architectures. This "collection" of architectures is commonly known as enterprise architecture - the interrelation and integration of business and technology. This same business and technology interrelation and integration are at the heart of service-oriented architecture design and implementation.

Architecture Description: U.S. Department of Defense Architecture Framework (DoDAF)
The primary focus of the DoDAF is architecture description - it prescribes a specific set of models that illustrate the architecture of concern. The framework defines 26 products (see Table 1) that reflect three different architectural viewpoints: operational, systems, and technical standards. DoDAF was developed to support interoperability between systems whose architectures are described with this framework. It's easier to determine how to integrate systems when they are modeled in a "common language" so that system interfaces, data formats and exchanges, implemented standards, etc. can be analyzed with the operational and system behaviors and structure.

DoDAF has formed the basis for several other frameworks such the U.K.'s Ministry of Defense Architecture Framework (MODAF) and the soon-to-be-published Standardization Agreement (STANAG) NATO Architecture Framework. DoDAF is comprised of two volumes: "Definitions & Guidelines" and "Product Descriptions."

A supplemental DoDAF Deskbook was also published to provide guidance to DoDAF users. This Deskbook consolidates supporting information such as white papers, case studies, discussion on the Core Architecture Data Model (CADM), architecture tools, Universal Reference Resources (URRs), and the Federal Enterprise Architecture (FEA) reference models.

Results Summary
The TOGAF/DoDAF working group validated its original hypothesis that there is synergy across a number of areas between these two frameworks, where DoDAF views can be used throughout the steps of the TOGAF ADM phases to develop a model of the overall architecture. The model can be used to document architectural decisions made following the TOGAF architecture methodology and through ongoing iteration and evolution of all architecture artifacts across the system development lifecycle. The general relationships between the DoDAF views and TOGAF phases are as follows:

  • DoDAF's All Views primarily aligns with TOGAF Preliminary Phase and Phase A: Architecture Vision.
  • DoDAF's Operational View primarily aligns with TOGAF Phase B: Business Architecture and Phase C: Information Systems Architecture activities.
  • DoDAF's Systems View primarily aligns with TOGAF Phase C: Information Systems Architecture, Phase D: Technology Architecture, Phase F: Migration Planning, and Phase E: Opportunities and Solutions.
  • DoDAF's Technical Standards View primarily aligns with TOGAF Phase D: Technology Architecture, Technical Reference Model, and Phase E: Opportunities and Solutions.
Table 2 overviews the primary relationships identified through analysis of these two leading architecture frameworks. Specific tailoring guidelines to adapt the TOGAF ADM methodology steps for DoDAF model outputs are documented in the detailed white paper of this analysis effort.

Relevance of the Findings
While the TOGAF/DoDAF working group initially set out simply to compare the two frameworks, its efforts recognized that the frameworks were complimentary. What this means for architects today is that they can immediately use the TOGAF ADM to build DoDAF architectures, and, in doing so, leverage a more robust, comprehensive, and complete enterprise architecture development method designed with business alignment in mind.

The working group also observed that both frameworks are currently dealing with potential gaps such as support for service orientation. The organizations that maintain these different frameworks would benefit should they come together to harmonize their efforts and work on evolving their respective frameworks to deal with the gaps such as security viewpoints, Service Oriented Architectures, and net centricity. For the architect, this ultimately means being better equipped to practice within a much broader space, which is a significant advantage in today's competitive environment.

Each complex architecting endeavor requires several key elements to be successful: repeatable methodology, standardized output models, formal validation, governance, collaboration guidelines, configuration management, tools, and patterns. The architect can address many of these needs through the application of The Open Group's Architecture Development Method as a disciplined process in developing the Department of Defense Architecture Framework set of views to model the architecture.

More Stories By Fatma Dandashi

Dr. Fatma Dandashi leads an Object Management Group (OMG) effort to define a UML profile for the DOD Architecture Framework. Prior to this activity she supported the development of Air Force Enterprise Architecture for SAF/XC. Dr. Dandashi was task lead on the MITRE development team responsible for DoD Architecture Framework Version 1.0 (Volumes I and II), and currently serves on the working group developing DoDAF Version 2.0.

Dr. Dandashi holds a PhD in information technology from George Mason University, ann MS in computer science from the University of Louisiana (Lafayette), and a BA in computers/business administration from the Lebanese American University.

More Stories By Terence Blevins

Terence Blevins is branch chief and lead architect, Air Force Operational Support Enterprise Architecture, at Mitre. He has been involved with the architecture discipline since the '80s when he was at the NCR Corporation as director of strategic architecture. He has been involved with evolving this discipline since 1996 when he first was introduced to The Open Group's Architecture Forum. Terence was co-chair of the Architecture Forum and frequent contributor of content to TOGAF including the Business Scenario Method.

He holds undergraduate and Masters degrees in Mathematics from Youngstown State University. He is TOGAF 8 certified.

More Stories By Rolf Siegers

Rolf Siegers is Raytheon’s corporate director of architecture & systems integration and an Engineering Fellow. He also sits on Raytheon’s corporate Architecture Review Board (ARB), leading and supporting a variety of architecture-related initiatives.

Rolf’s program experience includes leading several multi-discipline software architecture teams for large-scale, software-intensive national and international systems since 1997. He is a certified TOGAF-8 architect (The Open Group), ATAMÒ Evaluator (SEI), and Software Architecture Professional (SEI). Rolf holds bachelor degrees in Computer Science and Mathematics from Huntingdon College and is a member of IEEE and INCOSE.

More Stories By Judith Jones

Judith Jones has served as an advisor to Brussels, CCTA and industry organizations on enterprise architecture and IS/IT architecture and frameworks, eGovernment, practitioner of TOGAF, and Prince 2. Her background experience includes 10 years as an independent consultant and 20+ years as a business manager with ICL, now Fujitsu Services.

Judith is an extremely active member of The Open Group and has worked with their Architecture Forum to establish enterprise architecture development processes and strategies suitable for global government and private sector usage. She currently leads the TOGAF 9 development effort.

Comments (0)

Share your thoughts on this story.

Add your comment
You must be signed in to add a comment. Sign-in | Register

In accordance with our Comment Policy, we encourage comments that are on topic, relevant and to-the-point. We will remove comments that include profanity, personal attacks, racial slurs, threats of violence, or other inappropriate material that violates our Terms and Conditions, and will block users who make repeated violations. We ask all readers to expect diversity of opinion and to treat one another with dignity and respect.

Microservices Articles
Skeuomorphism usually means retaining existing design cues in something new that doesn’t actually need them. However, the concept of skeuomorphism can be thought of as relating more broadly to applying existing patterns to new technologies that, in fact, cry out for new approaches. In his session at DevOps Summit, Gordon Haff, Senior Cloud Strategy Marketing and Evangelism Manager at Red Hat, discussed why containers should be paired with new architectural practices such as microservices rathe...
DevOps is under attack because developers don’t want to mess with infrastructure. They will happily own their code into production, but want to use platforms instead of raw automation. That’s changing the landscape that we understand as DevOps with both architecture concepts (CloudNative) and process redefinition (SRE). Rob Hirschfeld’s recent work in Kubernetes operations has led to the conclusion that containers and related platforms have changed the way we should be thinking about DevOps and...
With the rise of Docker, Kubernetes, and other container technologies, the growth of microservices has skyrocketed among dev teams looking to innovate on a faster release cycle. This has enabled teams to finally realize their DevOps goals to ship and iterate quickly in a continuous delivery model. Why containers are growing in popularity is no surprise — they’re extremely easy to spin up or down, but come with an unforeseen issue. However, without the right foresight, DevOps and IT teams may lo...
"There is a huge interest in Kubernetes. People are now starting to use Kubernetes and implement it," stated Sebastian Scheele, co-founder of Loodse, in this SYS-CON.tv interview at DevOps at 19th Cloud Expo, held November 1-3, 2016, at the Santa Clara Convention Center in Santa Clara, CA.
In his session at 20th Cloud Expo, Mike Johnston, an infrastructure engineer at Supergiant.io, will discuss how to use Kubernetes to setup a SaaS infrastructure for your business. Mike Johnston is an infrastructure engineer at Supergiant.io with over 12 years of experience designing, deploying, and maintaining server and workstation infrastructure at all scales. He has experience with brick and mortar data centers as well as cloud providers like Digital Ocean, Amazon Web Services, and Rackspace....
Today most companies are adopting or evaluating container technology - Docker in particular - to speed up application deployment, drive down cost, ease management and make application delivery more flexible overall. As with most new architectures, this dream takes significant work to become a reality. Even when you do get your application componentized enough and packaged properly, there are still challenges for DevOps teams to making the shift to continuous delivery and achieving that reducti...
Modern software design has fundamentally changed how we manage applications, causing many to turn to containers as the new virtual machine for resource management. As container adoption grows beyond stateless applications to stateful workloads, the need for persistent storage is foundational - something customers routinely cite as a top pain point. In his session at @DevOpsSummit at 21st Cloud Expo, Bill Borsari, Head of Systems Engineering at Datera, explored how organizations can reap the bene...
Is advanced scheduling in Kubernetes achievable?Yes, however, how do you properly accommodate every real-life scenario that a Kubernetes user might encounter? How do you leverage advanced scheduling techniques to shape and describe each scenario in easy-to-use rules and configurations? In his session at @DevOpsSummit at 21st Cloud Expo, Oleg Chunikhin, CTO at Kublr, answered these questions and demonstrated techniques for implementing advanced scheduling. For example, using spot instances and co...
Docker is sweeping across startups and enterprises alike, changing the way we build and ship applications. It's the most prominent and widely known software container platform, and it's particularly useful for eliminating common challenges when collaborating on code (like the "it works on my machine" phenomenon that most devs know all too well). With Docker, you can run and manage apps side-by-side - in isolated containers - resulting in better compute density. It's something that many developer...
In his general session at 19th Cloud Expo, Manish Dixit, VP of Product and Engineering at Dice, discussed how Dice leverages data insights and tools to help both tech professionals and recruiters better understand how skills relate to each other and which skills are in high demand using interactive visualizations and salary indicator tools to maximize earning potential. Manish Dixit is VP of Product and Engineering at Dice. As the leader of the Product, Engineering and Data Sciences team at D...