HLA OMT Fundamentals Alessandro Specchia Carnegie Mellon University.

Slides:



Advertisements
Similar presentations
An Introduction to the HLA Part 1 Roger McFarlane School of Computer Science McGill University Montreal, CANADA.
Advertisements

The eXtensible Markup Language (XML) An Applied Tutorial Kevin Thomas.
TACOM Tank-automotive & Armaments COMmand UNCLASSIFIED 10 June 2003 Robert Kling Electronic Architecture Team Phone: (586)
High Level Architecture
High Level Architecture (HLA) Don McGregor Research Associate MOVES Institute
An Automata-based Approach to Testing Properties in Event Traces H. Hallal, S. Boroday, A. Ulrich, A. Petrenko Sophia Antipolis, France, May 2003.
An Agent-Based Approach to Inference Prevention in Distributed Database System Xue Ying Chen Department of Computer Science.
1 Software Testing and Quality Assurance Lecture 12 - The Testing Perspective (Chapter 2, A Practical Guide to Testing Object-Oriented Software)
A New Computing Paradigm. Overview of Web Services Over 66 percent of respondents to a 2001 InfoWorld magazine poll agreed that "Web services are likely.
NEW TIES year 2 review NEW TIES = New and Emergent World models Through Individual, Evolutionary and Social learning.
1 MPEG-21 : Goals and Achievements Ian Burnett, Rik Van de Walle, Keith Hill, Jan Bormans and Fernando Pereira IEEE Multimedia, October-November 2003.
David Harrison Senior Consultant, Popkin Software 22 April 2004
Protocols and the TCP/IP Suite Chapter 4. Multilayer communication. A series of layers, each built upon the one below it. The purpose of each layer is.
Future of MDR - ISO/IEC Metadata Registries (MDR) Larry Fitzwater, SC 32 WG 2 Convener Computer Scientist U.S. Environmental Protection Agency May.
BOM Template Specification Images SISO-STD DRAFT-V0.13.
Day 2 – Topic 1 (and 4) Dagstuhl Seminar April 2015.
Introduction to XML. XML - Connectivity is Key Need for customized page layout – e.g. filter to display only recent data Downloadable product comparisons.
Information Systems: Databases Define the role of general information systems Describe the elements of a database management system (DBMS) Describe the.
High Level Architecture Overview and Rules Thanks to: Dr. Judith Dahmann, and others from: Defense Modeling and Simulation Office phone: (703)
Data Distribution Dynamic Data Distribution. Outline Introductory Comments Dynamic (Value based) Data Distribution: HLA Data Distribution Management –Routing.
Odyssey A Reuse Environment based on Domain Models Prepared By: Mahmud Gabareen Eliad Cohen.
Requirements Specification for Lab3 COP4331 and EEL4884 OO Processes for Software Development © Dr. David A. Workman School of Computer Science University.
Rex E. Gantenbein PhD, Senior Member IEEE Center for Rural Health Research and Education University of Wyoming.
95-843: Service Oriented Architecture 1 Master of Information System Management Service Oriented Architecture Lecture 3: SOA Reference Model OASIS 2006.
SpaceWire Plug-and-Play: A Roadmap Peter Mendham, Albert Ferrer Florit, Steve Parkes Space Technology Centre, University of Dundee 1.
A Web-based Distributed Simulation System Christopher Taewan Ryu Computer Science Department California State University, Fullerton.
The High Level Architecture Introduction. Outline High Level Architecture (HLA): Background Rules Interface Specification –Overview –Class Based Subscription.
Parallel and Distributed Simulation Data Distribution I.
Sheet 1XML Technology in E-Commerce 2001Lecture 2 XML Technology in E-Commerce Lecture 2 Logical and Physical Structure, Validity, DTD, XML Schema.
CMPS 435 F08 These slides are designed to accompany Web Engineering: A Practitioner’s Approach (McGraw-Hill 2008) by Roger Pressman and David Lowe, copyright.
From FOMs to BOMs and Back Again Paul Gustavson Tram Chase Larry Root SimVentions, Incorporated Bowman Drive, Suite 502 Fredericksburg, VA
ESIP Vision: “Achieve a sustainable world” by Serving as facilitator and advisor for the Earth science information community Promoting efficient flow of.
Framework of a Simulation Based Shop Floor Controller Using HLA Pramod Vijayakumar Systems and Industrial Engineering University of Arizona.
Domain Classes – Part 1.  Analyze Requirements as per Use Case Model  Domain Model (Conceptual Class Diagram)  Interaction (Sequence) Diagrams  System.
Crisis Line/Safe House Case Management System Martin Zhao Mercer University.
© 2013, published by Flat World Knowledge Chapter 10 Understanding Software: A Primer for Managers 10-1.
Composition in Modeling Macromolecular Regulatory Networks Ranjit Randhawa September 9th 2007.
Introducing WI Proposal about Authorization Architecture and Policy Group Name: WG4 Source: Wei Zhou, Datang, Meeting Date: Agenda Item:
Distributed Data Analysis & Dissemination System (D-DADS ) Special Interest Group on Data Integration June 2000.
AIXM 5 UML Modelling Conventions. AIXM is GML AIXM is an XML exchange standard based on a subset of GML. Essentially: –AIXM Features are GML features.
Class diagrams Terézia Mézešová.
Slide 1 Service-centric Software Engineering. Slide 2 Objectives To explain the notion of a reusable service, based on web service standards, that provides.
Framework for the Specification and Standardization of Data Elements Part1 of ISO/IEC by Daniel W. Gillman, editor.
Data Distribution. Outline Fundamental concepts –Name space –Description expressions –Interest expressions Static Data Distribution: HLA Declaration Management.
GRID ANATOMY Advanced Computing Concepts – Dr. Emmanuel Pilli.
Parallel and Distributed Simulation Data Distribution II.
Diistributed Data Management DDM in HLA. Distributed Data Management HLA by default does one sort of interest management: functional. Your federate can.
OOD OO Design. OOD-2 OO Development Requirements Use case analysis OO Analysis –Models from the domain and application OO Design –Mapping of model.
1 SOA Seminar Seminar on Service Oriented Architecture SOA Reference Model OASIS 2006.
2013 Spring Simulation Interoperability Workshop 13S-SIW-004 Extended FOM Module Merging Capabilities Bjo ̈ rn Mo ̈ ller Andy Bowers Mikael Karlsson Björn.
IPDA Architecture Project International Planetary Data Alliance IPDA Architecture Project Report.
2003 Spring Simulation Interoperability Workshop 1 SISO SAC Report to IEEE CS SAB June 10, 2004 Long Beach, CA Katherine L. Morse, Ph.D., SAIC
Fall ‘99 Simulation Interoperability Workshop RTI Interoperability Study Group Final Report Michael D. Myjak, Chair.
1 IS 0020 Program Design and Software Tools Unified Modeling Language Lecture 13 April 13, 2005.
1 A Multi-Paradigm Approach to Describe Software Systems presented by Adel Smeda.
1 The XMSF Profile Overlay to the FEDEP Dr. Katherine L. Morse, SAIC Mr. Robert Lutz, JHU APL
An Introduction to FOM Modules
Katherine L. Morse, PhD JHU/APL 9 October 2015
Development of a Simulator for the HANARO Research Reactor (Communication Protocol) H.S. Jung.
Current Framework and Fundamental Concepts
Reuse of IEEE Content in Vendor Documentation
BOMs – Base Object Models
Distribution and components
High Level Architecture
Databases and Information Management
Service-centric Software Engineering
2. An overview of SDMX (What is SDMX? Part I)
Databases and Information Management
Data Visualizer for CommCare
Presentation transcript:

HLA OMT Fundamentals Alessandro Specchia Carnegie Mellon University

What is it ? HLA Object Model Template (OMT) a common format and syntax for recording the information in HLA Object Models

OMT Objective Facilitate interoperability among simulations and reuse of simulation components. How ? By providing a commonly understood mechanism for FOM development coordination By providing a common, standardized means of describing potential federation members By facilitating the design and application of common tool sets for development of HLA object models

FOM Federation Object Model (FOM) - specification of the exchange of public data among the participants in HLA federation The intent is to describe inter-federate exchange within the system.

SOM Simulation Object Model (SOM) - a specification the capabilities offered to federations by individual simulations. The intent is to describe the public interface of the federate in terms of an identified set of supported objects and interactions.

OMT Components I There are seven components : Object model identification: to associate important identifying information with the HLA object model. Object class structure table: to record the namespace of all simulation/federation object classes and to describe their class-subclass relationship. Interaction class structure table: to record the namespace of all simulation/federation interaction classes and to describe their class-subclass relationship.

OMT Components II Attribute table: to specify features of object attributes in a simulation/federation.* Parameter table: to specify features of interaction attributes in a simulation/federation.* Routing space table: to specify features of object attributes and interactions in a federation. FOM/SOM lexicon: to define all of the terms used in the tables. * The Attribute and Parameter table are associated with Object and Interaction class structure table respectively.

Warning In some cases, certain tables may be empty. However all HLA object models shall contain at least one object class or interaction class. Examples : Some federates might not be involved in interaction (such a Wright- Flyer viewer) => no interaction class structure (=> no parameter table) For SOMs, the routing space is always empty. If there is no Data Distribution Management (DDM), the routing space is also empty for FOMs.

Object model identification table

Object class structure table

Interaction class structure table

Attribute table

Parameter table

Routing space table

FOM/SOM lexicon

More Tables... There are more tables to included in the OMT for specifying users types: Enumerated datatype table Complex datatype table