1 / 13

DoDAF 2.0 Data Technical Working Group Understanding “Capability”

DoDAF 2.0 Data Technical Working Group Understanding “Capability”. Forrest Snyder, Army CIO/G-6 (MITRE). Outline. Problem Background Approach Analysis Results Next Steps. Problem. JCIDS (The Joint Capabilities Integration and Development System)

danielb
Télécharger la présentation

DoDAF 2.0 Data Technical Working Group Understanding “Capability”

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. DoDAF 2.0 Data Technical Working GroupUnderstanding “Capability” Forrest Snyder, Army CIO/G-6 (MITRE)

  2. Outline • Problem • Background • Approach • Analysis • Results • Next Steps

  3. Problem • JCIDS (The Joint Capabilities Integration and Development System) • Focused on delivering “capabilities” BUT • The definition of “Capability” continues to evolve • An ability to achieve an objective (DoD CADM) • The ability to execute a specified course of action (CJCSI 3170.01D, 12 March 2004) • The ability to achieve a desired effect under specified standards and conditions through combinations of means and ways to perform a set of tasks. (CJCSI 3170.01F, 1 May 2007) • “Capability” is a complex concept • Our Question: How do we model “capability” as data?

  4. Defining the Capability Space • Capability: The ability to execute a specified course of action (JCS Pub 1.02); the ability to achieve a desired effect under specified standards and conditions through combinations of means and ways to perform a set of tasks. (CJCSI 3170.01F, 1 May 2007) • Things in the Capability Space • “Ability” is power or capacity to do or act • “Course of Action” is any sequence of activities that an individual or unit may follow. (JCS Pub 1.02) • Effect” is the result, outcome, or consequence of an action. (JCS Pub 1.02) • “Standards” are specifications of allowed values for outputs, inputs or processes. • “Conditions” Those variables of an operational environment or situation in which a unit, system, or individual is expected to operate and may affect performance. (JCS Pub 1-02) • “Means” are resources through which results are brought about • “Ways” are processes and procedures • “Tasks” are actions, activities or undertakings that enable missions, activities or functions to be performed or accomplished. • “Objective” is a clearly defined, decisive, and attainable end toward which every operation is directed. (JCS Pub 1.02) Objectives are specific, time-targeted, measurable, and attainable targets (BMM)

  5. The Capability Space: final The Capability Space T Capability Means ability Performer Ways Effect Ways Result/Outcome/ Consequence Course of Action task standard Action goal Activity objective condition Function

  6. The Capability Concept Model: Final

  7. Capability Modeled as Data: not quite final Note: Need to add relationships showing that each performer may also be subject to conditions and required to meet certain standards. Need to consider incorporating the idea that each performer must have some capacity to perform its activities.

  8. Conclusions and Next Steps • Core concepts of Capability are the core concepts of Enterprise Architecture: • Means deal with • Processes and activities that realize one or more courses of action which are themselves descriptions of processes and activities • Performers • Constraints • Measures of Performance of a Performer to perform one or more Activities to certain Standards under certain conditions • Ends deal with Vision, goals, and objectives • Of the three, only objectives provide a definite time-focused target • Next Steps: Produce a Logical Data Model of the Capability Concepts as part of the EA Logical Data Model.

  9. Back-up

  10. References • Hay, David C., Data Model Patterns: A Metadata Map, Elsevier, 2006 • The Object Management Group (OMG), The Business Motivation Model (BMM) Specification, September 2007 • The Business Rules Group, The Business Motivation Model: Business Governance in a Volatile World, release 1.3, September 2007 • Berkem, Birol; “Running Business on the Basis of Your Goals and Directives”, www.goobiz.com, 2005-2007 • Berkem, Birol, “How to Align IT with the Changes Using UML, MDA and BMM on a Goal-Driven Service Oriented Architecture”, www.goobiz.com, 2005-2007

  11. External Reference: the Business Motivation Model • The Business Motivation Model (BMM) • Is a conceptual model of things that affect business motivation • A product of the Business Rules Group available at http://www.businessrulesgroup.org • A pending OMG Specification available at http://www.omg.org/docs/dtc/07-08-03.pdf • Depicts things important to Business Motivation (Zachman “Why” column) from the perspective of Business Process (Zachman “How” column) • A pattern for discussing “Motivation”, used by David Hay in Chapter 7 of Data Model Patterns, A Metadata Map (Elsevier, 2006) • Basis of a goal oriented architecture methodology (See http://www.goobiz.com) • Does not explicitly model “capability” BUT models things that go together make up a capability.

  12. The Business Motivation Model: Core Concepts

  13. Placeholder and Placeholder Connections in the Business Motivation Model

More Related