SSTC-2012 BenKBovée 2933a_Backup Slides 26-Apr 1130-1300 Track1


Published on

Published in: Technology
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

SSTC-2012 BenKBovée 2933a_Backup Slides 26-Apr 1130-1300 Track1

  1. 1. UNCLASSIFIEDImproved Mapping and Modelingof Defense Domain Architectures Backup slides Benton “Ben” K Bovée Senior Enterprise Architect Principal, Patterndigm 26 Apr 2012, 11:15-12:00
  2. 2. UNCLASSIFIED DM2 on IDEF0 Reference: [SBVR, Bovée 2006].Slide 2
  3. 3. UNCLASSIFIED DoDAF infancy: BEA ver. 3.0 Business Operational FEA Business Ref. Capability Node Model (BRM) OV-5a, -5b BPM Process Operational (IDEF0 ICOM-Cs) (BPMN) Activity OSD OV-6c; and DoDAF OV-6b. FEA Data Ref. Model (DRM) Interface Diagram System (SV-1) Function (SV-4) FEA Cmpt. Svc. Ref. Model (SRM) Systems 2..2 System Interface Entity System Capabilities “aligned” by relating each to an enumeration value: •Application Systems Enterprise •Collaboration Data Exchange Sub-Service •Discovery •Enterprise Service Mgt. •HRM •Info Assurance & INFOSEC Standard Technical Service •Info Transfer •Logistics (StdV-1, -2) (or Function) •Messaging Technology FEA Technical Ref. Service Area Model (TRM)Slide 3
  4. 4. UNCLASSIFIED CDM of DoDAF ver. 2.0 Concepts (NOT all)Slide 4
  5. 5. UNCLASSIFIED DoDAF 2.0 Concepts & Views: Summary & Issues Reference: [DoD 2009, Pp. 5, 14, 220, C-2].Slide 5
  6. 6. UNCLASSIFIED DoDAF View IDs & Counts: Today & Imminent Viewpoint 1 2 3 4 5 6 7 8 9 10 Count All (AV) X X 2 Data & Info (DIV) X X X 3 Capability (CV) X X X X X X X 7 Operational (OV) X X X X a, b a, b, c 9 Project(PV) X X X 3 Service (SvcV) X X a, b X X X X X X a, b, c 13 Standard (StdV) X X 2 System (SV) 1(a, b, c, d, e) X X X a, b X X X X a, b, c 13 (16) Count 8 (13) 8 7 4 6 6 3 2 2 6 52 (55)Slide 6
  7. 7. UNCLASSIFIED Imminent New System Views • SV-1a Interface Description. Shows interfaces (Resource Flows) between Systems, Services, and/or Person Types • SV-1b Performer Configuration Diagram. Interface Description plus composition (whole-parts) of Resources involved. If Locations are involved in the configuration, relationships to Resources. • SV-1c Functional Allocation. Activities (System Functions) performed by Systems, Services, and Person Types. • SV-1d Organizational Resources. Shows Resources that are part of (whole-part) Organizations. • SV-1e Organizational Dependencies. Shows Organizations whose Activities are reified by System Functions (Activities) performed by Performer Configurations. All Views should show traceability to higher-order reifications, other views that constitute requirements, and/or other non-view requirements. [ASD 2012] My note: NOT sure how SV-1d would differ from relations represent-able via OV-4. Reference: [ASD 2012].Slide 7
  8. 8. UNCLASSIFIED DM2 Domain Class Hierarchy (1 of 2) Reference: [DoD 2009, p.33].Slide 8
  9. 9. UNCLASSIFIED DM2 Domain Class Hierarchy (2 of 2) Reference: [M3, Bovée].Slide 9
  10. 10. UNCLASSIFIED Overspecialization Kills: Natural Evidence Simple design is most commonly transcendental. All Ammonite arthropods are extinct, only a few Ceriatite varieties still exist, and no decline in Goniatites has been observed. Reference: [Tonmo].Slide 10
  11. 11. UNCLASSIFIED Ontological Conceptual Meta-Model (ALL)Slide 11
  12. 12. UNCLASSIFIED Ontological Physical Meta-Model (PM2): Top ½Slide 12
  13. 13. UNCLASSIFIED Ontological PM2: Bottom ½Slide 13
  14. 14. UNCLASSIFIED Ontological PM2 (Bottom ½): Relation Meta-TypesSlide 14
  15. 15. UNCLASSIFIED How to Map Information sets? Very Laboriously! • Correlate Terms  Complete matches—Equivalence—ideal; usually a low %  Partial matches common  Names match, definition Semantics differ  Names differ, definition Semantics match or similar  Names & Semantics match, Relations to other terms differ • Correlate Taxonomies?  Mappings require selection of one (1) base set  Forces “baking” mappings in to an information set (!) • Correlate Ontologies? – Possible only if Relation temporal Semantics match • Mapping is imprecise (i.e., Earned Value?)Slide 15
  16. 16. UNCLASSIFIED ASA(ALT) Mappings to BEA: 1st LevelSlide 16
  17. 17. UNCLASSIFIED ASA(ALT) Mappings to BEA: A3 2nd Level, with DA ACQ Activities ghostedSlide 17
  18. 18. UNCLASSIFIED ASA(ALT) Mappings to BEA: A3 2nd Level, with DA SALE LOG Activities ghostedSlide 18
  19. 19. UNCLASSIFIED The Bovée EA Unifying TaxonomY (BEAUTY) An alternative for taxonomies: Map all to the BEAUTYSlide 19
  20. 20. UNCLASSIFIED Base Object- Ref. Model Subject - ViewpointSlide 20
  21. 21. UNCLASSIFIED References [ASD 2012] DoDAF 2012 Plenary SV-1 Content Guidance for Template and Descriptions slide 18, ASD(NII)/DoD CIO, 5 Jan 2012. [Bovée 2000] Modeling & Engineering Systems with Objects: Visualizing Computer Software Throughout a Development Life Cycle, Presented Training Day 1 of 5, slide 5, 30 Oct 2000. [Bovée 2006] Proposed New and Modified Semantics of Business Vocabulary and Rules Core Concepts and Relations, Object Management Group (OMG), 20 Nov 2006. [DoD 2009] The Department of Defense Architecture Framework (DoDAF) version 2.0, Pp. 5, 14, 33, 220, C-2, 28 May 2009. [M3] MoDAF Meta-Model, accessed 25 Apr 2012. [OMB FEA] E-Gov FEA FEA Reference Model Mapping Quick Guide (FY10 Budget Preparation), Aug 2008 ; FEA Consolidated Reference Model Document version 2.3, Oct 2007; The Data Reference Model version 2.0, 17 Nov 2005. [OMG BPMN] Business Process Model and Notation version 2.0, OMG, 3 Jan 2011. [SBVR] Semantics of Business Vocabulary and Business Rules version 1.0, OMG, 2 Jan 2008. [Tonmo], accessed 24 Apr 2012.Slide 21
  22. 22. UNCLASSIFIED Questions? To contact the author with ideas  E-mail:  P-mail: PO Box 1531, FAIRFAX VA US 22038-1531.Slide 22
  23. 23. UNCLASSIFIEDACQ Acquisition—in ASA(ALT) AbbreviationsINFOSEC Information SecurityAILA Army Integrated LOG Architecture INTEL Intelligence—in NIIASA(ALT) Asst. Sec.’y of Army for ACQ, LOG & Technology LOG Logistics—in AILA, ASA(ALT)ASD Assistant Secretary of Defense, U.S. MoDAF Ministry of Defence Architecture Framework, UKAnly Analytical M3 MoDAF Meta-ModelBEAUTY Bovée EA Unifying TaxonomY Mfg. Manufacturing—in ICAMBPM Business Process Model NII National INTEL Information—in ASD(NII)BPMN Business Process Model and Notation, OMG NIST National Institutes of Stds. & TechnologyBRM Business RM, FEA OMB Office of Management & Budget, U.S.CADM Core Architecture Data Model OMG Object Management Group™CAP Capability OSD Office of the Secretary of Defense, U.S.CDM Conceptual Data Model Opl OperationalCmpt. Component—in SRM PM2 Physical Meta-ModelCmptr. Computer—in ICAM RM Ref. ModelDA Department of Army, U.S. Ref. Reference—in RMDM2 DoDAF Meta-Model SALE Single Army LOG EnterpriseDoD Department of Defense, U.S. SBVR Semantics of Business Vocabulary and Rules, OMGDoDAF DoD Architecture Framework SRM Svc. Cmpt. RM, FEADRM Data RM, FEA SW SoftwareEA Enterprise Architecture Std. Standard—in NISTFEA Federal EA, OMB Svc. Service—in SRMFIPS Fed. Information Processing Std.—in IDEF0 Sys SystemFY Fiscal Year TRM Technical RM, FEAICAM Integrated Cmptr.-Aided Mfg.—in ICOM(C) Tech TechnologicalICOM(C) Input, Control, Output, Mechanism (Call) UK United KingdomIDEF ICAM Definition U.S. United StatesIDEF0 IDEF for Function Modeling, NIST FIPSSlide 23