1. DoDAF Plan and Style Guide
OPS
DAS SE
CPM
JCIDS
PPBE
DoDAF Plan and Style Guide
1 August 2011
Overview for DoDAF TECHEDIT Team 1 1

2. Topics Introduction Organization DoDAF TechEdit POA&M Approach
Style Guide
5 minute drill
Closing

3. Introduction Mission – Achieve Communications The Difference between
“Decrease Mission Effectiveness” and “Kill”.
lan·guage/ˈlaNGgwij/Noun1. The method of human communication, either spoken or written, consisting of the use of words in a structured and conventional way.
2. Any nonverbal method of expression or communication: "a language of gesture and facial expression".
Language Arts
Reading, by definition, is the ability and knowledge of a language that allows comprehension by grasping the meaning of written or printed characters, words, or sentences. Reading involves a wide variety of print and nonprint texts that help a reader gain an understanding of what is being read. Reading of texts that are often included in educational curriculum include fiction, nonfiction, classic, and also contemporary works.
Composition
Composition is defined as the combination of distinct parts or elements to form a whole and the manner in which these elements are combined or related. The following are examples of Composition in Language Arts:
The art or act of composing a literary work
The structure or organization of literature
A short essay, especially one written as an academic exercise (an essay is a short literary composition on a particular theme or subject, usually in prose and generally analytic, speculative, or interpretative). There are many types of short essays, including, but not limited to:
1.Five-paragraph essay
2.Argumentative essay
3.Cause and effect essay
4.Comparative essay.
Compositions may also include:
Narrative Essays
Expository Essays
Persuasive Essays
Technical Writing

4. Organization Team Team Lead Term and Syntax Continuity Ralph Wallace
Writers
Walt Kulakowski
TBD
Reviewers
SV/STDV
Tom Murphy
Mike Rice
SvcCs
Dave Ellis
DIVs
Greg Schaeffer
Charles Thornburg
Team
Term and Syntax Continuity
Jeffery Welch
Alexander Bocast
Advisors
Dave McDaniel
Shelton Lee

5. Current Effort Status 52 Models (aka Views) Work Completed/In Process
CRs
Comments addressed; Unassigned (To Be Completed)
Entire Document, OV-2, OV-5b, OV-6c, SV-1, SV-4(a/b), DIV-4
CR 316
DM2 Diagrams (Approximately 50%)
CR 579
Title and One Line Descriptions (24 out of 52)

6. Mission Milestone 28 August 2011
Primary - Models Required for Information Support Plans (ISPs)
Secondary - Remaining OVs, SVs
Tertiary - CVs, DIVs, SvcCs, PVs

7. Primary Goal

8. Plan of Action and Milestones
End of Week (5 Aug)
Remaining one line descriptions revised and compiled for reviewers comments
End of Week (12 Aug)
First draft of narratives completed; Reviewer Comments returned on one line descriptions
End of Week (19 Aug)
Final one line descriptions completed; Reviewers comments provided on narratives
End of Week (26 Aug)
Final narratives for models associated with ISPs completed.

9. Mission – Achieve Communications
Style
Definition: The way in which something is spoken, written, or performed.
Technical Writing
Definition: Written communications done on the job, especially in fields with specialized vocabularies, such as science, engineering, technology, and the health sciences.
Purpose: Achieving something within an organization
Your knowledge of topic: Usually greater than that of the reader.
Audience: Often several people, with differing technical backgrounds.
Criteria for Evaluation: Clear and simple organization of ideas, in a format that meets the needs of busy readers.
Statistical and graphic support: Frequently used to explain existing conditions and to present alternative courses of action.
Audience
Who is the audience for what we are producing?
Primary - DoD Enterprise Architects and Systems Engineers
Secondary – DoD Chief Engineers and Acquisition Professionals
Tertiary – Any suggestions?

10. Your Knowledge and Experience
1.1 Purpose This document defines the content requirements and provides stylistic guidance for Operational Architecture (OA) products developed under the auspices of the OA Branch of the Marine Corps Combat Development Command (MCCDC). In addition to directive guidance, this guide provides recommended practices. This guide is intended to ensure that OA Branch Products satisfy three criteria: 1. Consistent development of high quality products in accordance with the Department of Defense Architecture Framework (DoDAF) direction and intent. 2. Development, validation, and verification of OA Products in a repeatable manner, achieving process improvement and efficiency. 3. Provide utility in support of external processes and analyses including the Planning, Programming, Budgeting, and Execution (PPBE) process; the Joint Capability Integration and Development System (JCIDS); the Defense Acquisition System, and other related processes and analyses as requested.
Source: USMC Operational Architecture Process and Style Guide (DRAFT) Version 0.5; Dated 03 April Author: Major Walter Kulakowski

11. Your Knowledge and Experience
6.0 OA Stylistic Guidance and Product Specification 6.1 Stylistic Guidance Purpose The need for standardization of OA Branch products is derived from: 1. DoDAF's intent to ensure that architecture descriptions can be compared and related, and 2. The OA Branch, MCCDC, approach to develop a comprehensive OA for the Marine Corps by drawing from OA products developed in support of JClDS and Acquisition efforts. When considered in conjunction, these two factors drive the OA Branch to establish stylistic guidance. The purpose of this guidance is to formulate a standardization of OA products in order to: lncrease the interoperability between OA products lncrease the reusability of the architecture data lncrease efficiency in validation of OA products lncrease efficiency in verification of OA products.
Source: USMC Operational Architecture Process and Style Guide (DRAFT) Version 0.5; Dated 03 April Author: Major Walter Kulakowski

12. Your Knowledge and Experience
SV-6
The SV-6 includes at least two rows for each systems pair (bidirectional) interface identifiers for each comm infrastructure equipment shown on the SV-2.
The 10 columns of required OV-3 information present and consistent (Needline #, Content, Accuracy, Transaction Type, Triggering Event, Criticality, Periodicity, Timeliness, Classification, and Classification Caveat).
Entries (e.g., timeliness) taken from the MCASE/MCEIR pick-lists.
The interfaces broken out are separate sections for Joint critical and Marine Corps interest.
Ensure data standards called out in the SV-6 are included in the TV-1, TV-1A, TV-2, or explained in the TV rationale.
Supporting text contains detailed, understandable language and answers any issues the view might raise.
Source: MCEIR SV Development Guide Version 1.1; Dated April 2007

13. DoDAF Model Specification and DM2 CM are intertwined
Model (view) specifications
Operational
Capabilities
Services
Systems
Data and Information
Standards
Projects
DM2
Conceptual Data Model
Logical Data Model
Physical Exchange Specification
The 52 DoDAF models and the DM2 are related via a matrix*
* SPAWAR requested a DM2 sub-diagram per DoDAF model years ago and that now underway. (CR # 316)

14. Conceptual Level of DM2 Activity Capability Resource Performer
anything can have Measures
Condition
Guidance
is-performable-under
Rule
Activity
Capability
Standard
Agreement
constrains
requires-ability-to-perform
has
consumes-and-produces
is-performed-by
is-realized-by
Project
achieves-desired-effect (a state of a resource)
is-the-goal-of
Resource
describes-something
Information
Not shown but implied by the IDEAS Foundation:
Everything is 4-D and so has temporal parts, i.e., states
Everything has parts
Everything has subtypes
Activity: Work, not specific to a single organization, weapon system or individual that transforms inputs (Resources) into outputs (Resources) or changes their state.
Resource: Data, Information, Performers, Materiel, or Personnel Types that are produced or consumed.
Materiel: Equipment, apparatus or supplies that are of interest, without distinction as to its application for administrative or combat purposes.
Information: The state of a something of interest that is materialized -- in any medium or form -- and communicated or received.
Data: Representation of information in a formalized manner suitable for communication, interpretation, or processing by humans or by automatic means. Examples could be whole models, packages, entities, attributes, classes, domain values, enumeration values, records, tables, rows, columns, and fields.
Performer: Any entity - human, automated, or any aggregation of human and/or automated - that performs an activity and provides a capability.
Organization: A specific real-world assemblage of people and other resources organized for an on-going purpose.
System: A functionally, physically, and/or behaviorally related group of regularly interacting or interdependent elements.
Person Role: A category of persons defined by the role or roles they share that are relevant to an architecture.
Service: A mechanism to enable access to a set of one or more capabilities, where the access is provided using a prescribed interface and is exercised consistent with constraints and policies as specified by the service description. The mechanism is a Performer. The capabilities accessed are Resources -- Information, Data, Materiel, Performers, and Geo-political Extents.
Capability: The ability to achieve a Desired Effect under specified (performance) standards and conditions through combinations of ways and means (activities and resources) to perform a set of activities.
Condition: The state of an environment or situation in which a Performer performs.
Desired Effect: A desired state of a Resource.
Measure: The magnitude of some attribute of an individual.
Location: A point or extent in space that may be referred to physically or logically.
Guidance: An authoritative statement intended to lead or steer the execution of actions.
Rule: A principle or condition that governs behavior; a prescribed guide for conduct or action.
Agreement: A consent among parties regarding the terms and conditions of activities that said parties participate in.
Standard: A formal agreement documenting generally accepted specifications or criteria for products, processes, procedures, policies, systems, and/or personnel.
Project: A temporary endeavor undertaken to create Resources or Desired Effects.
Geopolitical Extent A geospatial extent whose boundaries are by declaration or agreement by political parties.
Materiel
Performer
Data
System
Organization
is-at
Location
GeoPolitical
Service
PersonRole
is-part-of

15. “Writing Rules”

16. Definition Example Category Capability Technical Term
Proposed Definition
Capability: (n) 1. The ability to execute a specified course of action. (JP 1-02) 2. The ability to achieve a desired effect under specified standards and conditions through combinations of means and ways to perform a set of tasks. (JCIDS)
Potentially Related Terms or Aliases
Source/Current Definition (source) definition
(JCIDS): The ability to achieve a desired effect under specified standards and conditions through combinations of means and ways to perform a set of tasks. (DoDAF/CADM): An ability to achieve an objective. (DDDS Counter (333/1)(A)) (JC3IEDM): The potential ability to do work, perform a function or mission, achieve an objective, or provide a service. (NAF): The ability of one or more resources to deliver a specified type of effect or a specified course of action. (GEN TERM) (NAF): A high level specification of the enterprise's ability. (MM) (JCS 1-02): The ability to execute a specified course of action. (A capability may or may not be accompanied by an intention.) (Webster's): 1. The quality of being capable; ability. 2. A talent or ability that has potential for development or use. 3. The capacity to be used, treated, or developed for a specific purpose.
Examples
"The soldier shall be able to load and fire his individual weapon." (JP 1-02) "The soldier shall be able to load and fire his individual weapon from (positions) on a trainfire range, in (weather) to achieve a minimum score of "Marksman" on the Army Marksman criteria
Definition Rationale
Authority: "The Secretary of Defense, by DOD Directive , 23 August 1989, Standardization of Military and Associated Terminology, has directed the use of JP 1-02 throughout the Department of Defense to ensure standardization of military and associated terminology.

17. DoDAF-DM2 Version Process
DRAFT

18. Rationale For Team Effort
Description
USMC MCSC CD&I
316
DM2 Diagram per Model
579
 Inconsistent Model Descriptions
535
SV-1 Inconsistencies
SSC-LANT comments
Undefined Terms

19. As Is – To Be Today Name One Sentence Description Short Description
Detailed Description
Tomorrow
Name
One Sentence Description
Detailed Narrative Description (1 page max)
Meta Model
Two diagrams maximum
One core (must have) and one extension (optional)
One page
Provided by another team member
Result Associations (one quarter page)

20. Elements of a DoDAF Description
Example
Elements of a DoDAF Description
Name
Definition
Comment
Title
The Alpha-Numeric DoDAF Model Designation (e.g. OV-5b) and the short describing phrase (e.g. Activity Resource Flows)
Establishes the minimal description
One Line Description
The extension of the short describing phrase (e.g. The organizational activities and resource flows between them.)
Establishes the broader descriptive expression; Shall be a complete sentence written in active tense; no more than two sentences. No use of other than DM2 defined terms
Detailed Description
The extension of the one line description
Establishes descriptors to refine the term within the class by use. ½ to 1 page in length.
Boundaries
The boundaries identified constraining the model within the scope of its objective.
To further clarify the description; not required. This is any boundary (e.g. temporal, geographic, technical)
Meta-Model
The DM2 specific meta-model which depicts the above.
Result Associations
The associations between the result of the modeling activity with any other activities or documents within the federal space.

21. Meta Model
Core Data Elements of OV-5b
Optional Elements

22. Document Associations
describes
describes
Same pattern applies to a an evolutionary acquisition spiral, just repeated iteratively
describes
describes
describes
Thing
Pedigree
(traceability)
Pedigree
(traceability)
Rules
constrain
Architectural Description
Pedigree
(traceability)
Rules
constrain
Architectural Description
Pedigree
(traceability)
Rules
constrain
Architectural Description
Architectural Description
Pedigree
(traceability)
Rules
constrain
Architectural Description
Rules
constrain
A&D
Successive refinement of the Architectural description. For any phase, it is traceable to the prior (pedigree). The prior phase becomes the rules that constrain the activities of the next performer – adherence to requirements baseline.
They’re all aiming at the same future Thing, just describing it in more detail and in different ways as you go along.
Worker
Technician
Engineer
Architect
Executive
Architecture
Strategic
Acquisition MS A MS B MS C
Systems
Engineering Initiate/CBA ICD SRR SDR CDD PDR CDR TRR CPD CDR TRR IOC/FOC

23. 5 Minute Drill
OV-5a/b

24. Summary
Results of TECHEDIT Team’s work will go through WG review and ultimately Component-wide review
Team will have to follow business rules and DoDAF 2.0 emphasis changes
Efforts will end on 28 August 2011