Do DAF and Joint HSI WG Human View

Do. DAF and Joint HSI WG (Human View) Dialog Kick-Off 25 August 2010 Do. DAF Development Team

Briefing Outline • How human performance, metrics, and interactions are modeled in Do. DAF Meta Model • Do. DAF views where this could show up • Example from UPDM 1. 0 • Configuration Management of Do. DAF for further refinement and evolution

A Human is a Performer Do. DAF-DM 2 Term Performer In architectures, we don’t ever model actual named persons, but, rather, their roles, e. g. , President, not George Washington Definition Any entity - human, automated, or any aggregation of human and/or automated - that performs an activity and provides a capability. Potentially Related Terms or Aliases Actor, Agent, Capability Configuration (MODAF)

Definitions of Other Terms in Diagrams Do. DAF-DM 2 Term Definition Potentially Related Terms or Aliases Activity Work, not specific to a single organization, weapon system or individual that transforms inputs (Resources) into outputs (Resources) or changes their state. Action, Process Operational Activity, Processes, Function, System Function, Operation, Task, Plan, Project activity. Performable. Under. Condition Represents that an activity was / is / can-be/ must-be conducted under certain conditions with a spatiotemporal overlap of the activity with the condition. activity. Performed. By. Performer An overlap between a Performer and an Activity that is non-specific as to whether: 1. the Activity is solely performed by the Performer 2. the Activity is performed by several Performers 3. the Performer performs only this Activity 4. the Performer performs other Activities Agreement A consent among parties regarding the terms and conditions of activities that said parties participate in. Condition The state of an environment or situation in which a Performer performs or is disposed to perform. Individual. Performer A specific thing that can perform an action Individual. Person. Role Person roles defined by the role or roles they share that are relevant to an architecture. Includes assigned materiel. Location. Type The powertype of Location Materiel Equipment, apparatus or supplies that are of interest, without distinction as to its application for administrative or combat purposes.

Definitions of Other Terms in Diagrams Do. DAF-DM 2 Term Definition Potentially Related Terms or Aliases materiel. Part. Of. Performer A whole-part association between a Performer (whole) and the Materiel parts of the Performer. (A Performer can have Personnel Type, System, Service, and Organizational components. ) Measure The magnitude of some attribute of an individual. A Skill that can be measured numerically Measureable. Skill measureable. Skill. Of. Person. Role. Type skill. Part. Of. Person. Role. Type is a member of Measure measure. Of. Type. Activity A measure. Of. Type that relates an Activity to a Measure measure. Of. Type. Condition is a member of Measure measure. Of. Type. Resource. Type is a member of Measure Organization A specific real-world assemblage of people and other resources organized for an on-going purpose. Department, Agency, Enterprise Organization. Type A type of Organization Performer Any entity - human, automated, or any aggregation of human and/or automated - that performs an activity and provides a capability. Actor, Agent, Capability Configuration (MODAF) Person. Role. Type A category of person roles defined by the role or roles they share that are relevant to an architecture. Includes assigned materiel. Role person. Role. Type. Part. Of. Performer A whole. Part between a Person. Role. Type and a Performer in which it performs

Definitions of Other Terms in Diagrams Do. DAF-DM 2 Term Resource resource. In. Location. Type Definition Data, Information, Performers, Materiel, or Personnel Types that are produced or consumed. The relationship that describes the location of a performer or type of performer Potentially Related Terms or Aliases Rule A principle or condition that governs behavior; a prescribed guide for conduct or action rule. Constrains. Activity An overlap between a Rule and the Activities it allows 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. Skill The ability, coming from one's knowledge, practice, aptitude, etc. , to do something well. Training, Knowledge, Ability System A functionally, physically, and/or behaviorally related group of regularly interacting or interdependent elements.

Performers Perform Activities that Flow Resources

Metrics are Ubiquitous in Do. DAF 2

The Ontologic Foundation is Key to Do. DAF 2’s Modeling • • Four dimensionalist -- xyzt Extensional -- physical existence is the criterion for identity Signs and representations are separated from referents Mathematics: – Type theory ~ Set theory – Mereology (wholes and parts) – 4 D Mereotopology (spatio-temporal relations) • http: //www. ideasgroup. org

Design Reification and Requirements Traceability describes Thing describes Pedigree (requirements) Architectural Description Pedigree (requirements) Architectural Description Rules Rules constrain constrain Strategic time Executive Architect Engineer Technician Worker Op Rqmt TLR SLR A-Spec B-Spec C-Specs CBA ICD Ao. A Perf Spec CDD CPD IOC

Many Views Can Render this Data AV-1 Overview and Summary Information o AV-2 Integrated Dictionary o OV-1: High Level Operational Concept Graphic OV-2: Operational Connectivity Description o OV-3: Operational Resource Flow Matrix OV-4: Organizational Relationships Chart n=necessary o=optional o Svc. V-3 b Services-Services Matrix o Svc. V-4 Services Functionality Description o Svc. V-5 Operational Activity to Services Traceability Matrix o Svc. V-6 Services Data Exchange Matrix o OV-5 a: Activity Decomposition Tree Svc. V-7 Services Performance Parameters Matrix n OV-5 b: Activity Model o Svc. V-8 Services Evolution Description o OV-6 a: Operational Rules Model o Svc. V-9 Services Technology and Skills Forecast o OV-6 b: State Transition Description o Svc. V-10 a Services Rules Model o OV-6 c: Event-Trace Description o Svc. V-10 b Services State Transition Description o SV-1 Systems Interface Description o Svc. V-10 c Services Event-Trace Description o SV-2 Systems Communications Description o Standards View-1 Standards Profile o SV-3 Systems-Systems Matrix o Standards View-2 Standards Forecast o SV-4 Systems Functionality Description o PV-1: Project Portfolio Relationships o SV-5 a Operational Activity to Systems Function Traceability Matrix PV-2: Project Timelines n SV-5 b Operational Activity to Systems Traceability Matrix Person. Role. Type A category of person roles defined by the role or roles they share that are relevant to an architecture. Includes assigned materiel. Svc. V-3 a Systems-Services Matrix PV-3: Project to Capability Mapping n CV-1: Vision SV-6 Systems Data Exchange Matrix o CV-2: Capability Taxonomy o SV-7 Systems Performance Parameters Matrix n CV-3: Capability Phasing o SV-8 Systems Evolution Description o CV-4: Capability Dependencies o SV-9 Systems Technology and Skills Forecast o CV-5: Capability to Organizational Development Mapping o SV-10 a Systems Rules Model o CV-6: Capability to Operational Activities Mapping o SV-10 b Systems State Transition Description o CV-7: Capability to Services Mapping o SV-10 c Systems Event-Trace Description o DIV-1: Conceptual Data Model Svc. V-1 Services Interface Description o DIV-2: Logical Data Model Svc. V-2 Services Communications Description o DIV-3: Physical Data Model

Version Control • Initial baseline Do. DAF 2. 0 released May 2009 • 2. 01 released Feb 2010 – 2. 01 Version Description Document (VDD) describes changes made in response to Action Items • 2. 02 to be released 26 Aug 2010 – 2. 02 VDD – New baseline published on public and DKO Do. DAF and Do. D EA COI namespace in Do. D Meta Data Registry • 2. 03 planned for Fed 2011 – Do. DAF-DM 2 Action Item tracker identifies planned items – New and other currently deferred AI’s will be prioritized by Do. DAF-DM 2 Working Group with Federated Architecture Council (FAC) oversight 2. 01 2. 02 May 2009 Feb 2010 Aug 2010 2. 03 Feb 2011

Relevant Governance Process Documents • Architecture Standards Review Group CONOPS – Roles, Responsibilities, and Processes – ASRG -- FOGO / SES level – Federated Architecture Council – 06 level • Do. DAF and DM 2 CM Plan – Configuration Identification – Organizational Roles, Responsibilities, and Interactions – CM Processes and Procedures – CM Business Rules – Do. DAF & DM 2 WG EA COI • COI POA&M • COI Data Management Working Group – Meets Quarterly, 1 st meeting was 2 July 2010 • COI Metrics

DISA Marine Corps Army Do. N AF NSA FAC is Small Formal Voting Body WG is Large Collaborative * Some C/S/A have multiple members Do. D CIO Framework Groups • OMG / INCOSE / NDIA • MODAF / NAF / TOGAF • FEA / FSAM Core Process Stakeholders • CJCSI revs • AT&L So. SE & Acq Reform • Combatant Command architectures • CPM Governance • PA&E • Do. DAF-DM 2 Configuration Status Accounting Report (CSAR) • Do. DAF-DM 2 Baseline Status • Do. DAF-DM 2 WG Activity Summaries • COI Metrics and Progress Report DNI CIO AT&L P&R USD(I) DCMO JCS J 6 STRATCOM Do. DAF-DM 2 Change Requests • COI Guidance • Do. DAF-DM 2 Action Item Prioritization • Do. DAF-DM 2 Baseline Direction • JFCOM FAC – Voting – 23* votes Framework & Ontology Groups • OMG / INCOSE / NDIA • IDEAS / NAF • UCORE • Enterprise Vocabularies Do. DAF-DM WG – Collaborative – Agreed-upon business rules enable analysis of different opinions Vendors • EA/ITA Tool • M&S • Data Analysis • Repository • Data Integration Data Exchange • Pilots • Early Adopters • Federation COI Coordination Groups • Do. D MDR WG • Do. D COI Forum To join, go to www. silverbulletinc. com/Do. DAF-DM 2 • 230+ members • Meets weekly

2. 00 2. 01 2. 02 2. 03 Overview 2. 00 – 12 DM 2 data groups • 52 Models 2. 02 70 Action Items • DM 2 CDM, LDM, PES 2. 01 29 Action Items • IDEAS v 1. 0 alignment • Measures • Representation, Names, Descriptions • Structured Service Description • Reification • Structured Desired Effect • Properties and Measures generalized and better aligned with IDEAS and JFCOM JMT needs • Reification diagram to explain requirements, design levels, and traceability for SE community • Consolidate Activity, Goal, diagrams • Simplified complex tuples (triples, tuples as places) • Redundant associations • Re-organized type orders, e. g. , for information and data • Added more structure to Agreement • Made higher-order typing consistent • Some XSD cleanup from pilot feedback 2. 03 (in-planning) 25 AI’s currently queued 85 new AI’s to review • State machine diagram • Temporal Flow diagram • Do. DAF Models revised to match DM 2 terminology better • Core process required datasets • More structure to Rules and Agreement • Services reification and joint action • Ontologic structure for Command Relationships • Basis for authority • Vision vs. Desired Effect • IDEAS Set Theory Unions (for mappings)

Questions?