VERSION 15 Primitives – Lexicon IPR 6 August 2008

Slides:



Advertisements
Similar presentations
DoDAF V2.0 Community Update Overview
Advertisements

OASIS Reference Model for Service Oriented Architecture 1.0
Security Extensions to the DOD Architecture Framework Kevin Richardson Information Assurance Lab Auburn University Computer Science and Software Engineering.
9/6/2001Database Management – Fall 2000 – R. Larson Information Systems Planning and the Database Design Process University of California, Berkeley School.
1 IS 4420 Database Fundamentals Chapter 2: Database Development Process Leon Chen.
Creating Architectural Descriptions. Outline Standardizing architectural descriptions: The IEEE has published, “Recommended Practice for Architectural.
The Software Product Life Cycle. Views of the Software Product Life Cycle  Management  Software engineering  Engineering design  Architectural design.
DCMO - CIO Architecture Federation Pilot Larry Singer 5 January, 2012.
OMG UML Profile for the DoD and MoD Architecture Frameworks (UPDM) Dwayne Hardy American Systems Jan 30, 2007.
Introduction to Software Quality Assurance (SQA)
Slide 1 Wolfram Höpken RMSIG Reference Model Special Interest Group Second RMSIG Workshop Methodology and Process Wolfram Höpken.
Chapter 7 Applying UML and Patterns Craig Larman
Information Systems Engineering. Lecture Outline Information Systems Architecture Information System Architecture components Information Engineering Phases.
Notes of Rational Related cyt. 2 Outline 3 Capturing business requirements using use cases Practical principles  Find the right boundaries for your.
12 August 2010 DoDAF Development Team
 CMMI  REQUIREMENT DEVELOPMENT  SPECIFIC AND GENERIC GOALS  SG1: Develop CUSTOMER Requirement  SG2: Develop Product Requirement  SG3: Analyze.
1 CASE Computer Aided Software Engineering. 2 What is CASE ? A good workshop for any craftsperson has three primary characteristics 1.A collection of.
DoD CIO Architecture and Interoperability Directorate December 2013
DoDAF Data Meta Model (DM2) Overview
Elaboration popo.
Business System Development
DoDAF 2 Was Designed to Support DoD’s 6 Core Processes
Software Configuration Management
Walkthrough DoDAF 2.0 Meta Model (DM2) TBD 20 March 2009 VERSION 15
Agenda Federated Enterprise Architecture Vision
DoDAF and Joint HSI WG (Human View) Dialog Kick-Off
Unified Architecture Framework NATO Architecture CaT Introduction
Official Current Version of DoDAF
VERSION 15 DARS User’s Group / DoDAF Vendor’s Day 11 February 2009
GEA CoP DRM Briefing for July 13 Meeting with Andy Hoskinson
IC Conceptual Data Model (CDM)
DoDAF Version 2.03 Update 05 Jan 2012 DoDAF Team 1 1.
Introduction to MODEM Building a Semantic Foundation for EA: Reengineering the MODAF™ Meta-Model Based on the IDEAS Foundation Model Lt Col Mikael Hagenbo,
DATA VERTICAL Technical Exchange
VERSION 15 DoDAF Vendor’s Day Session 22 July 2008
US Kickoff brief to Frameworks Convergence Meeting
Architecture Tool Vendor’s Day
Workshop for ACT – IAC, EA-SIG Mr. David McDaniel (ctr) 20 July 2012
Agenda All-Monday 15 Sep 0800 Welcome - Opening remarks
Overview and Role in DoD Governance
Developing Information Systems
Introduction DoDAF 2.0 Meta Model (DM2) TBS dd mon 2009 VERSION 15
Active Data Management in Space 20m DG
Introduction DoDAF 2.0 Meta Model (DM2) TBS dd mon 2009 VERSION 15
CV-1: Vision The overall vision for transformational endeavors, which provides a strategic context for the capabilities described and a high-level scope.
د. حنان الداقيز خريف /28/2016 Software Quality Assurance ضمان جودة البرمجيات ITSE421 5 – The components of the SQA.
VERSION 15 9/12/ :44 International Defence Enterprise Architecture Specification (IDEAS) and DoDAF 2.0 Data Model OMG Systems Engineering Domain.
Architect’s Walkthrough (Logical Data Model)
BSA 376 Competitive Success/snaptutorial.com
BSA 376 Education for Service/snaptutorial.com
BSA 376 Teaching Effectively-- snaptutorial.com
DoDAF Data Meta Model (DM2) Overview
DoDAF 2.x Meta Model (DM2) Conceptual Level
VERSION 15 UCORE Conference 23 Sep 2009
DM2 D O A F M E T L Conceptual Data Model (CDM)
AWG 17 April 2012 Candidate Topics
IDEAS Core Model Concept
DM2 D O A F M E T L Conceptual Data Model (CDM)
Manager’s Overview DoDAF 2.0 Meta Model (DM2) TBS dd mon 2009
“New” things Discussed in London
Systems Architecture & Design Lecture 3 Architecture Frameworks
Requirements Document
Architecture & Interoperability Directorate
CORE Name: CORE® Description:
What is the DM2? DoDAF Vocabulary Discovery Categories D O A F M E T L
US Kickoff brief to Frameworks Convergence Meeting
Software Development Process Using UML Recap
Architect’s Walkthrough (Logical Data Model)
International Defense Enterprise Architecture Specification (IDEAS)
Presentation transcript:

VERSION 15 Primitives – Lexicon IPR 6 August 2008 1/14/2018 07:27 DoDAF 2.0 Data Model (DM2) Overview Primitives – Lexicon IPR 6 August 2008

Briefing Outline DM2 and DoDAF Top-Level Diagram Development and Life-Cycle Methodology Data Groups Overviews

DoDAF Meta Model (DM2) Purposes: The vocabulary for description and discourse about DoDAF models (formerly “products”) and core process usage The basis for generation of the “physical” exchange specification for exchange of data between architecture tools and databases. Form: VOLUME I, DoDAF Conceptual Data Model (CDM) Core concepts, definitions (with examples, sources, aliases) Relationships (with some typing) VOLUME II, DoDAF Logical Data Model (LDM) The DoDAF Logical Data Model (LDM) is the Conceptual Data Model described in Volume I with attributes, specializations, and association reifications added VOLUME III, DoDAF Physical Exchange Model (PES) Physical Data Exchange Model is the Logical Data Model with general data types specified and implementation attributes (e.g., source, date) added and then generated as a set of XSD’s, one schema per product/view type described in Volume II.

Volume II Organization PRE-DECISIONAL WORKING DRAFT Volume II Organization Vol II Perspectives Metamodel Data Groups Views  Metamodel Data Groups Capability Services Project Goals Rules Measures Location Doctrine Training / Skill / Education Performer Object Exchange / Flow Information & Data x.y.1 Data Diagram and definitions from DM2 Discussion x.y.2 Method x.y.3 Usage in Core Processes x.y.4 Presentation PRE-DECISIONAL WORKING DRAFT

Data Groups PRE-DECISIONAL WORKING DRAFT PRE-DECISIONAL WORKING DRAFT The “groups” are clusters of semantically related concepts Performer. Things that perform activities such as service performers, systems, personnel, and organizations. Object Exchange / Flow. The interaction between performers that is both temporal and results in the flow or exchange of objects such as information, data, materiel, and even other performers. Information and Data. Representations (descriptions) of things of interest and necessary for the conduct of activities. Doctrine. (TBS in Spiral 4). Training / Skill / Education. (TBS in Spiral 4) Capability. Models the need to perform a set of activities under certain conditions and standards to achieve desired effects and the way in which those needs are satisfied (or satisfiable.) Services. Business and software services, what they do for what effects, by what measures and rules, how they are described for discovery and use, and how and where they can be accomplished. Project. All forms of planned activities that are responsive to visions, goals, and objectives that aim to change the state of some situation. Goals. How goals, visions, objectives, and effects relate and bear on architectures. Rules. How rules, standards, agreements, constraints, and related and are relevant to architectures. Measures. All form of measures (metrics) applicable to architectures including needs satisfaction, performance, interoperability, organizational, and resources. Location. All forms of locations including points, lines, areas, volumes, regions, installations, facilities, and addresses including electronic addresses (e.g., URL’s) and physical (e.g., postal.) PRE-DECISIONAL WORKING DRAFT

PRE-DECISIONAL WORKING DRAFT Data Groups Relate to DoDAF Perspectives, Views, Core Processes, and Models (formerly Products) Notional Draft Will be in Section 3 of DoDAF Vol II PRE-DECISIONAL WORKING DRAFT

The Elements of the Data Groups Map to DoDAF Models PRE-DECISIONAL WORKING DRAFT The Elements of the Data Groups Map to DoDAF Models Notional Draft Three mappings: Concepts (Classes) Associations Class attributes In Section 4 of DoDAF Vol II PRE-DECISIONAL WORKING DRAFT

Top-Level Overviews

Capabilities PRE-DECISIONAL WORKING DRAFT Goals Rules Measures Ontologic Foundation (IDEAS) Locations Performers Personnel Materiel Flows Information & Data Temporal Services Descriptions Ports & Channels Service Functions QoS Metrics Service Policies Service Contracts Service System Organization Points / Areas / Volumes Regions Real Property Facilities Addresses Visions Objectives Effects Goals Capabilities Realization - implementation Projects Activities Metrics Conditions Performance Needs Satisfaction Organizational Maintainability Adaptability Parts, types, temporal parts, states, overlaps Environmental Socio-political Military Rules Guidance Agreements Constraints Standards IA/Security Functions Processes Tasks Cost / Schedule / Metrics Organizations / Performers Measures PRE-DECISIONAL WORKING DRAFT

Overall Map of DoDAF Metamodel

Modeling Methodology

Top-Down / Bottom-Up Development DoDAF 2.0: Conceptual Data Model (Vol I) Logical Data Model (Vol II) Physical Exchange Model (Vol III) Existing / Emerging Schema, Models, and Databases Data Model Development COI1 COIn COI Coordination PPBE Process Information Requirements JCIDS Process Information Requirements Ops Planning Process Information Requirements SE Process Information Requirements DoD Core Process Information Requirements Collection UCORE DAS Process Information Requirements CPfm Process Information Requirements

Sources Models CADM 1.5 IDEAS UPDM BMM Hay/Zachman ASM CRIS Conceptual CADM in DoDAF 1.0 / prototype CADM 2.0 M3 NAF Meta Model DoI Meta Model JC3IEDM GML UCORE 1.1 GEIA 927 AP233 SUMO and ISO 15926 (via IDEAS) FEA Reference Models JFCOM JACAE Definitions IEEE ISO W3C OMG EIA DODD & DODI JCS Pubs, especially CJCSI's Models in the Source_Candidates_071115.ppt DoDAF Other frameworks: Zachman, MODAF, TOGAF, NAF, ... FEA BMM Wordnet Wikipedia English dictionaries DoDAF Glossary On the left are the model sources we considered to date; on the right, additional sources for definitions. Note that as a result of the Ops Planning workshop at JFCOM last week, we now can add JACAE as source. That metadata is being parsed into the spreadsheet this week. Note also, that we considered sereral non-AF sources, e.g., JCS Pub 1-02, the DoD Dictionary of Military Terms, and English dictionaries.

Modeling Principles Model Core Process (PPBE, DAS, JCIDS, CPM, SE, Ops) business objects Terms enter model through thorough semantic research: Assignment to a researcher Collection of authoritative definitions, documenting source Assessment of redundant (alias) or composite terms Formulation / selection of definition based on authoritative definitions Examples Outbrief to team Recording of research and decision rationale No need to distinguish / label concepts that differ only in level of aggregation – e.g., subfunction – function. Whole-part relationship covers the need without different names for different types of wholes and parts. When a user has need to label, the naming pattern accommodates. Typed Relationships, e.g., using IDEAS No commitment to an implementation type. Support RDBMS, XSD, Java, etc. from core model Goal is a core that can be extended by user communities, not to try to cover all user detail. Extenders should be careful to not create redundant representations. Model will enter a CM process

Definitions and Aliases Record PRE-DECISIONAL WORKING DRAFT Definitions and Aliases Record PRE-DECISIONAL WORKING DRAFT

Definitions and Aliases Record PRE-DECISIONAL WORKING DRAFT Definitions and Aliases Record PRE-DECISIONAL WORKING DRAFT

Definitions and Aliases Record PRE-DECISIONAL WORKING DRAFT Definitions and Aliases Record PRE-DECISIONAL WORKING DRAFT

Definitions and Aliases Record PRE-DECISIONAL WORKING DRAFT Definitions and Aliases Record PRE-DECISIONAL WORKING DRAFT

Model Walkthru

Foundation Ontology http://en.wikipedia.org/wiki/IDEAS_Group All the DoDAF 2 domain concepts are founded on a mathematically-based foundation “Individuals” that have 4D extent “Types” – basically sets of Things “Tuples” – ordered relationships between Things Rigorously worked-out common patterns are reused Saved a lot of repetitive work – “ontologic free lunch” Result is higher quality and consistent throughout http://en.wikipedia.org/wiki/IDEAS_Group

Big-Four Reuse Patterns PRE-DECISIONAL WORKING DRAFT Big-Four Reuse Patterns Super/Sub Type, e.g., F-15 is type of Fighter Whole Part, e.g., AEGIS radar is part-of the AEGIS ship Interface Type, e.g., Asset data collection activities produce data for audit reporting Temporal Type, e.g., The collection task takes place before the posting and exploitation tasks PRE-DECISIONAL WORKING DRAFT

IDEAS Foundation Linkage to DoDAF Domain

Doctrine Training / Skill / Education TBD

Backups