The Special Role of M&S in Cross-COI Mediation Bernard P. Zeigler, Ph.D., Arizona Center for Integrative Modeling and Simulation and Joint Interoperability.

Slides:



Advertisements
Similar presentations
Dr. Leo Obrst MITRE Information Semantics Information Discovery & Understanding Command & Control Center February 6, 2014February 6, 2014February 6, 2014.
Advertisements

Status on the Mapping of Metadata Standards
CH-4 Ontologies, Querying and Data Integration. Introduction to RDF(S) RDF stands for Resource Description Framework. RDF is a standard for describing.
Ch:8 Design Concepts S.W Design should have following quality attribute: Functionality Usability Reliability Performance Supportability (extensibility,
Illustrating System Entity Structure For Building Simulation Bernard Zeigler RTSync Corp ACIMS C4I Center, GMU April 2011.
Shelley Powers, O’Reilly SNU IDB Lab. Hyewon Kim
Database Systems: Design, Implementation, and Management Tenth Edition
The Hard Real-Time Unified Modeling Language (HRT-UML) method provides a comprehensive solution to the modeling of Hard Real Time systems. HRT-UML incorporates.
Object-Oriented Analysis and Design
9/6/2001Database Management – Fall 2000 – R. Larson Information Systems Planning and the Database Design Process University of California, Berkeley School.
Modified from Sommerville’s originalsSoftware Engineering, 7th edition. Chapter 8 Slide 1 System models.
Article by: Farshad Hakimpour, Andreas Geppert Article Summary by Mark Vickers.
“DOK 322 DBMS” Y.T. Database Design Hacettepe University Department of Information Management DOK 322: Database Management Systems.
8/28/97Information Organization and Retrieval Files and Databases University of California, Berkeley School of Information Management and Systems SIMS.
Architectural Design Establishing the overall structure of a software system Objectives To introduce architectural design and to discuss its importance.
IBM User Technology March 2004 | Dynamic Navigation in DITA © 2004 IBM Corporation Dynamic Navigation in DITA Erik Hennum and Robert Anderson.
Domain-Specific Software Engineering Alex Adamec.
Introduction to UDDI From: OASIS, Introduction to UDDI: Important Features and Functional Concepts.
Vocabulary Services “Huuh - what is it good for…” (in WDTS anyway…) 4 th September 2009 Jonathan Yu CSIRO Land and Water.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 18 Slide 1 Software Reuse.
Methods For Web Page Design 6. Methods Why use one? What it covers –Possibly all stages Feasibility Analysis Design Implementation Testing –Maybe just.
 Copyright 2005 Digital Enterprise Research Institute. All rights reserved. Towards Translating between XML and WSML based on mappings between.
Chapter 7 Structuring System Process Requirements
Chapter 4 System Models A description of the various models that can be used to specify software systems.
INF 384 C, Spring 2009 Ontologies Knowledge representation to support computer reasoning.
Concepts and Terminology Introduction to Database.
Nancy Lawler U.S. Department of Defense ISO/IEC Part 2: Classification Schemes Metadata Registries — Part 2: Classification Schemes The revision.
Metadata and Geographical Information Systems Adrian Moss KINDS project, Manchester Metropolitan University, UK
MPEG-7 Interoperability Use Case. Motivation MPEG-7: set of standardized tools for describing multimedia content at different abstraction levels Implemented.
ISURF -An Interoperability Service Utility for Collaborative Supply Chain Planning across Multiple Domains Prof. Dr. Asuman Dogac METU-SRDC Turkey METU.
1 Ontology-based Semantic Annotatoin of Process Template for Reuse Yun Lin, Darijus Strasunskas Depart. Of Computer and Information Science Norwegian Univ.
Development Process and Testing Tools for Content Standards OASIS Symposium: The Meaning of Interoperability May 9, 2006 Simon Frechette, NIST.
updated CmpE 583 Fall 2008 Ontology Integration- 1 CmpE 583- Web Semantics: Theory and Practice ONTOLOGY INTEGRATION Atilla ELÇİ Computer.
Definition of a taxonomy “System for naming and organizing things into groups that share similar characteristics” Taxonomy Architectures Applications.
Chapter 7 System models.
Ocean Observatories Initiative Data Management (DM) Subsystem Overview Michael Meisinger September 29, 2009.
Sommerville 2004,Mejia-Alvarez 2009Software Engineering, 7th edition. Chapter 8 Slide 1 System models.
Illustrations and Answers for TDT4252 exam, June
Formalized Model Development & Test Generation: Key Role of Abstraction Bernard P. Zeigler Arizona Center for Integrative Modeling and Simulation (ACIMS)
Semantic Web - an introduction By Daniel Wu (danielwujr)
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 14 Slide 1 Object-oriented Design.
2007. Software Engineering Laboratory, School of Computer Science S E Web-Harvest Web-Harvest: Open Source Web Data Extraction tool 이재정 Software Engineering.
Semantic web course – Computer Engineering Department – Sharif Univ. of Technology – Fall Knowledge Representation Semantic Web - Fall 2005 Computer.
Object Oriented Multi-Database Systems An Overview of Chapters 4 and 5.
Some Thoughts on DDI4 and Qualitative Data Larry Hoyle revised 8/13/2015DDI4 for Qualitative, Hoyle 1.
Learners Support Publications Object Oriented Programming.
ReSeTrus Development of a digital library technology based on redundancy elimination and semantic elevation, with special emphasis on trust management.
CoOL: A Context Ontology Language to Enable Contextual Interoperability Thomas Strang, Claudia Linnhoff-Popien, and Korbinian Frank German Aerospace Centor.
M&S Services at the Crossroads of Service Oriented Architecture and the DoD Architectural Framework Bernard P. Zeigler, Ph.D., Arizona Center for Integrative.
Dictionary based interchanges for iSURF -An Interoperability Service Utility for Collaborative Supply Chain Planning across Multiple Domains David Webber.
Web Technologies for Bioinformatics Ken Baclawski.
Architecture View Models A model is a complete, simplified description of a system from a particular perspective or viewpoint. There is no single view.
The Structure of the User Interface Lecture # 8 1 Gabriel Spitz.
Winter 2011SEG Chapter 11 Chapter 1 (Part 1) Review from previous courses Subject 1: The Software Development Process.
Qualitative Data in DDI. What is “Qualitative Data” Text, mixed mode documents Images Video Physical Objects 10/5/2015Qualitative data in DDI - Hoyle.
1 Open Ontology Repository initiative - Planning Meeting - Thu Co-conveners: PeterYim, LeoObrst & MikeDean ref.:
CSCI 3428: Software Engineering Tami Meredith UML Unified Modeling Language.
Manufacturing Systems Integration Division Development Process and Testing Tools for Content Standards Simon Frechette National Institute of Standards.
1 Chapter 2 Database Environment Pearson Education © 2009.
Ontologies Reasoning Components Agents Simulations An Overview of Model-Driven Engineering and Architecture Jacques Robin.
Semantic Interoperability in GIS N. L. Sarda Suman Somavarapu.
Building Preservation Environments with Data Grid Technology Reagan W. Moore Presenter: Praveen Namburi.
Systems Architectures System Integration & Architecture.
Of 24 lecture 11: ontology – mediation, merging & aligning.
Chapter 9 Architectural Design. Why Architecture? The architecture is not the operational software. Rather, it is a representation that enables a software.
COP Introduction to Database Structures
Evolution of UML.
Software Engineering Development of procedures and systematic applications that are used on electronic machines. Software engineering incorporates various.
Database Design Hacettepe University
Systems Architecture & Design Lecture 3 Architecture Frameworks
Presentation transcript:

The Special Role of M&S in Cross-COI Mediation Bernard P. Zeigler, Ph.D., Arizona Center for Integrative Modeling and Simulation and Joint Interoperability Test Command Fort Huachuca, AZ

System Entity Structure The M&S COI has a special role to play in the area of mediation among metadata schemes developed by the various COIs Interoperability among the web services of COIs will require a more dynamic elements and associated simulation interpretations, typical of the M&S concerns Use System Entity Structure (SES) from Theory of Modeling and Simulation The SES is the basis for a methodology, and practical tool set that supports data engineering and modeling of application domains with hierarchical system characteristics It is being applied by the Joint Interoperability Test Command (JITC) to imagery metadata characterization for the some of the sensor products of the National Geospatial-Intelligence Agency (NGA).

SES Overview SES methodology and tool set –Java classes using Sun’s XML classes –develop well-structured, hierarchically composable data models –can be mapped to a variety of legacy formats. Due to its fairly simple axiomatic structure the SES lends itself to tool-supported structure analysis –tools to compute the common elements and substructures of a pair of SES representations. –not as powerful as a full-blown, logic-based ontology framework –it is sufficiently expressive for real application –sufficiently well structured to allow useful tool support.

System Entity Structure – Basic Concepts Entity – a thing in the real world, e.g book Variable – an attribute of an entity, e.g. title Aspect – decomposition, a way to break down an entity into parts or components (entities), e.g., front cover, back cover, pages Specialization – a classification, a way to classify an entity into special cases or subclasses, e.g., genre MultipleAspect – a decomposition into similar parts, e.g. pages Entities alternate with Aspects and Specializations Prunings generate family of pruned entity structures (PES)

Example: SES Representation of Book book contentDec chapters chapter chapterDec explanation theorem proof theorems example physicalDec pages page front cover back cover Aspect Entity MultiAspect genre bio- graphy fiction Specialization physicalDec pages page1 front cover back cover fiction_book page100 pruning

Generation of XML Schema

merge SES merged SES merge PES merged PES Synthesizing Large SESs and PESs From Components

Top Level SES Representation of NITF Core Information Mission Mission Image Aspect Image Aspect Images Image Identification Segment descriptionsGround referenceSensor Image Data Aspect

SES Breakdown of Identification Information Identification Identification Data Aspect Image Sequence Data Aspect Sequence ID ~ISID Original Image Data Image Sequence ~NRG ~NCG ~TRG ~TCG Date/Time Data Simultaneous Collection

Mission Mission Image Aspect Image Aspect Images Image Identification Segment descriptionsGround referenceSensor Image Data Aspect Identification Entity Merged Into Mission SES Identification Identification Data Aspect Image Sequence Data Aspect Sequence ID ~ISID Original Image Data Image Sequence ~NRG ~NCG ~TRG ~TCG Date/Time Data Simultaneous Collection

Advantages of Hierarchical Methodology for Managing Body of Standards Divide and Conquer - Complex standard is decomposed into smaller more manageable pieces Pieces can be developed and maintained individually as modifications are required Builds (merges) can be performed at any time to create current version of overall standard Some pieces can be stand-alone standards under the same or other authorities XML instances of component standards can be merged into larger XML instances of the overall standard.

Approach to Harmonization Multiple legacy metadata formats that partially overlap in their referents Attempt to find as much common core as possible Express common core in SES Expland SES with Specializations to capture non-core elements Re-derive original content of metadata by pruning from master SES

Tools for Harmonization Relational representation of SES Commonality measures Operations to increase commonality Thesaurus

Relational Representation of SES entities SES can be represented as a collection of relations such as entityHasAspect, aspectHasEntity, entityHasSpecialization, etc. as shown. SES’s can be compared on the basis of their relational representation. SES aspects multi aspects specializations attributes entity specialization attributemulti-aspect 0..n 1 aspect 0..n 11..n 0..n 1..n 0..n n

Finding common entities and SES’s entities common entities SES A SES B

Computing Commonality of SES’s equality of subSES below common entity ? SES A SES B subSES below common entity common entity common entity Commonality = fraction of shared entites fraction of shared sub-SES’s

Entity Removal May Increase Commonality House couch removeEntity (“LivingRoom”) House sofa House Living Room Living Room

Name Substitution may Increase Commonality House couch addRename(“sofa”,”couch”) replaceAll() House sofa House couch House couch

Maintaining Thesaurus of Equivalent Names thesaurus thesaurus.xml store in persistent form addRename(“sofa”,”couch”) replaceAll() House sofa House couch transfer pairs apply to SES set representatives for equivalence classes Representatives of equivalence classes are canonical names that will be used as defaults in application to SES’s, thereby providing a standard version of an SES. RepresentativeClass members sofacouch, sofa, divan,.. wallside, wall,… ……

Dynamic SES Need metadata that tracks processing as data is processed through stages Develop dynamic SES that can evolve through transformations Include forward and reverse links for traceability

Dynamic Process Example: Evolution of a Book Book (concept) Book (content description) Book (physical embodiment) Book (re-printings) Book (revisions)

Ex: Representing Versions In SES book contentDec chapters chapter chapterDec explanatory theorem proofexample theorems engineering version – remove all proofs from theorems mathematician’s version – remove all examples from theorems theorem example theorems theorem proof theorems chapterDec

Trajectories in Space of SESs Book SES Book SES’ transformation retain description of transformation to enable reverse traceability Space of SES’s edges labeled by transformations and ancestor links nodes are SES’s derived from precursors

Summary SES is rich enough to support approaches to harmonization and dynamic processing that will be involved in cross-COI mediation Representation as relations allow Java operation and measurement tools Supports alternative Mappings to XML to satisfy different applications

Bernard P. Zeigler ACIMS JITC jitc.fhu.disa.mil Contact: More information:

Joint Interoperability, Assured Security, Best Value, Customer Success Global Net-Centric Solutions -- The Warfighter's Edge