How to SuccessfullyImplement DoDAF2.0- DoDAF2.0 Overview

The First in a Series ofFive Featured Whitepapers

IntroductionThe DoDAF 2.0, released by the OSD-NII, DoD CIO in May of 2009 presents a

significant shift in the way in which DoD architectural descriptions are to be built,

analyzed and used. The guidance, descriptions, best practices and instructions

presented in DoDAF 2.0 are based on sound principles –such as data-centric

architecture, architecture development that is “fit-for-purpose”, models as “templates

for collecting data”, and presentation views vs. architecture models to name a few.

However, there is a sentiment in the community that, although there is little argument

over the fundamentals of DoDAF 2.0, the implementation of DoDAF 2.0 in reality has

been difficult and slow-going at best. Some point to the lack of tools on the market

that provide “true”, out-of-the-box support for DoDAF 2.0. Others point to the fact that

although the concepts in DoDAF 2.0 are sound in theory, they are difficult to implement

in practice without more tangible, “hands-on” guidance for how to carry out the

direction provided by DoDAF 2.0.

The purpose of this document is to introduce a DoDAF 2.0 implementation framework

that addresses four key areas critical to the successful implementation and effective

utilization of DoDAF 2.0. They are:

• UnderstandingandLeveragingtheDM2

• WorkingwiththeDoDAF2.0ViewpointsandModels

• Developing“Fit-for-Purpose”PresentationViews

• ConvertingDataandModelsfromDoDAF1.xtoDoDAF2.0

This is the first, in a series of whitepapers by Casewise, on how to successfully

implement DoDAF 2.0. The other whitepapers will focus on each of these four pillars in

greater detail and provide specific guidance in that particular area.

The pages ahead lay the groundwork for each of these four pillars and establish the key

concepts necessary for the successful implementation of DoDAF 2.0.

The purpose of this document is to outline the four key pillars towards a successful implementation and utilization of DoDAF 2.0.

Four additional whitepapers provide deeper insight into how to get the most out of these pillars:

• DM2Conformance• DoDAF2.0Viewpoints&Models

• Fit-For-PurposeViews• DoDAF1.xConversionto

DoDAF 2.0

UnderstandingandLeveragingtheDM2The overarching theme of DoDAF 2.0 is “data-centricity” – in other words, taking a

data-centric approach to the development and analysis of architecture. The DoDAF 2.0

metamodel (DM2), which establishes the “constrained language” of the DoDAF and the

underlying structure of the data, plays a critical role in understanding and implementing

DoDAF 2.0. As we prepare to implement DoDAF 2.0 and, as such, the DM2, we need

to understand both the components of the DM2 (i.e., what their purpose is and how

they are intended to be used) and the DM2 data groups, in context (i.e., what they

represent, how they are intended to be used, etc.).

The DM2 whitepaper addresses the Conceptual and Logical data model and the

Physical Exchange Specification. It will also detail some of the key data groups (aka

subject areas) defined in the DM2.

In addition, the DM2 was built upon a foundational ontology model called the

International Defense Enterprise Architecture Specification (IDEAS). It is important to

understand what aspects of that foundation are meaningful to the “typical” DoDAF

architect, and what value it provides as we develop our architectural descriptions. We

often refer to the DM2 as “flexible, yet rigorous.” But what does this actually mean? It is

important to get a deep understanding of this in very real terms, which means reviewing

the use of inheritance throughout the DM2 logical data model and the looking at the

“tupletypes” defined in the IDEAS foundation.

The DM2 whitepaper covers these topics as well, providing key insights into how

to make the DM2 work for you and become a powerful “tool” for describing

architectural perspectives.

DM2 Activity Data Group implemented in Corporate Modeler for DoDAF 2.0 (CMD2) by Casewise

DoDAF2.0ViewpointsandModelsFor years, people have associated the concept of architecture “views” or “products”

with DoDAF. Previous versions of DoDAF contained Operational Views, Systems Views,

Technical Views and All Views. These views were made up of “products” used to

describe various aspects of a given architectural description.

In DoDAF 2.0, the name “view” has been changed to “viewpoint”. More importantly,

there are new viewpoints, modified viewpoints and renamed viewpoints. Similarly,

“DoDAF products” are now referred to as models, defined as “templates for collecting

information”. Like the viewpoints, there are new models, modified models and

renamed models.

Probably the most common activity performed by DoDAF Architects is the development

of architecture models. As such, it is critically important for anyone implementing

DoDAF 2.0 to understand the new viewpoints and models, how they are intended

to be used, what data they are intended to collect and describe as well as how they

are interrelated. An important aspect of this is how they correlate to the objects and

associations in the DM2. Every object, line, relationship, etc. captured in a model should

be captured in the structure of the DM2.

Whitepaper three, in the five-part series, addresses the DoDAF 2.0 viewpoints and

models. It details what’s new in DoDAF 2.0 as well as what has changed. Additional

insights are shared into how the models correlate to the DM2 and how the flexibility

of the DM2 allows us to be more creative with the development of our models.

This whitepaper defines each of the model categories defined in the DoDAF 2.0

and introduces a concept called “DoDAF model patterns” – which can be used to

understand, interpret and extend the DoDAF model concept.

DoDAF 2.0 Viewpoints as implemented in CMD2

Fit-For-PurposePresentationViewsAnother foundational theme of DoDAF 2.0 is “Fit-for-Purpose”. Part of what this means

is that Architects are instructed to develop architectural descriptions that are “fit” for the

purpose of the architecture, or their customers’ or consumers’ purpose. In other words,

rather than blindly following the framework and building DoDAF models because the

framework says “thou shalt build an OV-4” (for example), architects should understand

the purpose and scope of any given architecture development effort and build only

those models necessary to capture the information required to support the purpose of

the architecture.

“Fit-for-Purpose” also refers to the views of information that are to be presented to the

information consumer (e.g., stakeholders, decision makers, etc.) based on the data in

the architecture repository. These “Presentation Views” have been categorized into five

types in the DoDAF 2.0 – Dashboards, Graphical Depictions, Reference Models, Fusion

Products, and Hybrid Products. Furthermore, DoDAF 2.0 makes a distinction between

“models” and “views”. However, the distinction doesn’t always seem to be clear in the

DoDAF documentation and is worthy of interpretation.

Our fourth whitepaper of the five-part series on DoDAF 2.0 dives deeper into this notion

of “Fit-for-Purpose”. It addresses what this means to the front-end of the architecture

development lifecycle, in terms of building the necessary viewpoints and models, as well

as to the back-end, which focuses more on the creation or generation of presentation

views in accordance with stakeholders needs and requirements.

Fit-for-Purpose example of a capability viewpoint model (CV-4)

ConversionfromDoDAF1.xtoDoDAF2.0The final “pillar” in the DoDAF 2.0 implementation

framework is the ability to transition to DoDAF 2.0 from

previous versions of DoDAF – be it DoDAF 1.0 or 1.5. More

specifically it’s about the ability to convert the data captured

in DoDAF 1.x to DoDAF 2.0, and subsequently the DM2. This

conversation requires both a conceptual discussion as well

as a mechanical discussion.

The conceptual discussion addresses the conversion of

some of the core DoDAF 1.x objects that have either been

changed, consolidated, distributed or eliminated in the DM2.

This list includes, but is not limited to, Node (both operational

and system), Operational Activities and Systems Functions,

Information Exchanges and System

Data Exchanges and Services. In each case, there are some

unique nuances in the conversion from DoDAF 1.x and

DoDAF 2.0. These are addressed in the final whitepaper in

the five-part series on DoDAF 2.0. In addition, this whitepaper touches on the mechanics

of how the Casewise solution, Corporate Modeler for DoDAF 2.0 (CMD2), supports and

automates the conversion from DoDAF 1.x to DoDAF 2.0, regardless of what tool you are

using for your legacy DoDAF architectures.

SummaryIn summary, DoDAF 2.0 is an architecture development framework built on a foundation

of principles – metamodel rigor, flexibility, data-centricity and “Fit-for-Purpose”. It has

been signed into law and is mandated for the future development of DoD architectural

descriptions.

Casewise is committed to those entities working towards successfully implementing

DoDAF 2.0. We have gone to great length to bring a full-functioning, true DoDAF 2.0

architecture development and analysis tool to the market. The next step is to provide

the Community with best practices and guidance on how to implement DoDAF 2.0 and

maximize the benefits of this framework. We believe our five-part whitepaper series will

begin to do that.

We hope you enjoy the whitepaper series and we look forward to hearing your thoughts!

SV-6OV-3

DoDAF 2.0 Diagrams

Core Architecture Data Model

All View

Operational View

Technical Standards ViewSystem

s/Serv

ices V

iew

CMD2

AboutCasewiseEstablished in 1989, Casewise provides software and consulting solutions to over 3,000

major global organizations for Business & Enterprise Architecture, Business Process Analysis

& Improvement, Business Process Management as well as Governance, Risk & Compliance

purposes.

In addition, Casewise’s dedicated North American Government Division focuses on the specific

needs of Defense & Civilian Agencies, State & Local Government and Systems Integrators.

Casewise solutions enable organizations to visualize, audit, report, improve and continually

maximize complex operating processes and technology infrastructures.

With a team of passionate experts, and with offices in the United States, United Kingdom,

France, Belgium and Germany – and a network of global resellers – Casewise provides thought

leadership and solutions enabling clients to achieve stronger strategic planning, better decision

making and improved business efficiencies.

AboutTheAuthorChris White, VP of Architecture Strategy and Implementation for

Casewise, is a recognized expert and thought leader in the field of

enterprise architecture. He has over 20 years of technical sales,

implementation and consulting experience, working extensively

with Federal Government clients including DoD and Civilian

Agencies, as well as Fortune 500 companies. He is a regular

speaker in the Federal EA community and highly sought after as a

consultant and advisor on EA planning, implementation,

and utilization.

www.casewise.com

GermanyCasewise GermanyFrankfurt Herriot’s,Herriotstrasse 160528 Frankfurt, GermanyT: +49 (0) 69 677 33 414

All Company and Product Logos, Trademarks and Trade Names are respectfully acknowledged as belonging to the rightful license holder.

© Casewise Limited 2010.

US - Government DivisionCasewise Systems, Inc.11654 Plaza America Dr.Suite 253Reston, Virginia20190T: +1 888-98-DODAF

USACasewise Systems Inc. 100 Century Parkway, Suite 150 Mount Laurel, New Jersey 08054, USAT: +1 856-380-1400

USACasewise Systems Inc. 777 Summer Street, Suite 303Stamford, Connecticut06901 USAT: +1 203-588-1967

UKCasewise Limited64 Clarendon Road, Watford Hertfordshire, WD17 1DA United KingdomT: +44 (0) 1923 830 300

France Casewise SARL 5 Rue Scribe,75009, Paris,FranceT: +33 (0) 1 70 95 00 05

Belgium Casewise Belgium Pegasuslaan 5,1831 Diegem Brussels, BelgiumT: +32 2 709 29 21