From FOMs to BOMs and Back Again Paul Gustavson Tram Chase Larry Root SimVentions, Incorporated 11905 Bowman Drive, Suite 502 Fredericksburg, VA 22408.

Slides:



Advertisements
Similar presentations
1 OOR in the Classroom An Experience Report Ken Baclawski Northeastern University.
Advertisements

Integration of MBSE and Virtual Engineering for Detailed Design
1 Aspects of IEEE P1471 Viewpoints in Unified Modeling Language (UML) Manzur Ashraf, BRAC University Humayra Binte Ali, Dhaka University Md.Mahfuz Ashraf,
>> How to Ensure Fair Fight in LVC Simulation: Architectural and Procedural Approaches Robert Siegfried, Johannes Lüthi, Günter Herrmann, Matthias Hahn.
Ch:8 Design Concepts S.W Design should have following quality attribute: Functionality Usability Reliability Performance Supportability (extensibility,
Component Oriented Programming 1 Chapter 2 Theory of Components.
NATO UNCLASSIFIED NIAG/SG-76: C2 Interoperability Slide 1HWP May 03 Battlespace Objects Hans Polzer 19 May 2003.
Documenting a Software Architecture By Eng. Mohanned M. Dawoud.
Technology to the Warfighter Quicker SBIR Phase II IPR - 1/26/06 Paul Gustavson (Principle Investigator) Ben Sisson (Principle Engineer) Karl Crosson (BAF.
Adding Aggregate Services to the Mix: An SOA Implementation Use Case Ben Sisson Paul Gustavson Karl Crosson SimVentions, Incorporated Bowman Drive,
Brief developed by Paul Gustavson (SimVentions) – 1 Base Object Model (BOM) Overview Summer 2008.
Department of Computing
©Ian Sommerville 2006Software Engineering, 8th edition. Chapter 8 Slide 1 System models.
Irwin/McGraw-Hill Copyright © 2004 The McGraw-Hill Companies. All Rights reserved Whitten Bentley DittmanSYSTEMS ANALYSIS AND DESIGN METHODS6th Edition.
Site Skin Structure Services Space plan Stuff Software Architecture and Software Architecture Patterns (1)
Unified Modeling (Part I) Overview of UML & Modeling
Modified from Sommerville’s originalsSoftware Engineering, 7th edition. Chapter 8 Slide 1 System models.
SE-565 Software System Requirements More UML Diagrams.
IRS XML Standards & Tax Return Data Strategy For External Discussion June 30, 2010.
SCORM By: Akshay Kumar. SCORM 2 What we want? What is SCORM? What is SCORM? Connection with e-learning Connection with e-learning Application of XML Technology.
BOM Template Specification Images SISO-STD DRAFT-V0.13.
Technology to the Warfighter Quicker SBIR Phase II Discussion / Demo 6/29/06 Paul Gustavson (Principle Investigator) Ben Sisson (BASS Engineer) Tram Chase.
Chapter 4 System Models A description of the various models that can be used to specify software systems.
THE GITB TESTING FRAMEWORK Jacques Durand, Fujitsu America | December 1, 2011 GITB |
An Introduction to Software Architecture
XMSF Early Adopters’ Workshop 2/7/2003 composable, reusable model components Paul Gustavson SimVentions, Inc. (540)
1 Technologies for distributed systems Andrew Jones School of Computer Science Cardiff University.
High Level Architecture Overview and Rules Thanks to: Dr. Judith Dahmann, and others from: Defense Modeling and Simulation Office phone: (703)
Programming in Java Unit 3. Learning outcome:  LO2:Be able to design Java solutions  LO3:Be able to implement Java solutions Assessment criteria: 
Odyssey A Reuse Environment based on Domain Models Prepared By: Mahmud Gabareen Eliad Cohen.
Technology to the Warfighter Quicker SBIR Phase II IPR - 5/10/06 Paul Gustavson (Principle Investigator) Ben Sisson (Principle Engineer) Karl Crosson (BAF.
Chapter 7 System models.
Ocean Observatories Initiative Data Management (DM) Subsystem Overview Michael Meisinger September 29, 2009.
Pertemuan 19 PEMODELAN SISTEM Matakuliah: D0174/ Pemodelan Sistem dan Simulasi Tahun: Tahun 2009.
The High Level Architecture Introduction. Outline High Level Architecture (HLA): Background Rules Interface Specification –Overview –Class Based Subscription.
Sommerville 2004,Mejia-Alvarez 2009Software Engineering, 7th edition. Chapter 8 Slide 1 System models.
XASTRO-2 Overview Presentation CCSDS SAWG Athens Meeting 12 th April 2005.
1 SBIR Phase II Final Report 10/18/06 Paul Gustavson (Principle Investigator) Ben Sisson (BASS Engineer) Tram Chase (BOMworks Engineer) SimVentions, Inc.
Chapter 10 Analysis and Design Discipline. 2 Purpose The purpose is to translate the requirements into a specification that describes how to implement.
GRASP: Designing Objects with Responsibilities
Tram Chase Real-Time Platform Reference (RPR) Base Object Model (BOM) Composability Standard for Enabling Interoperability A B C.
ECE450 - Software Engineering II1 ECE450 – Software Engineering II Today: Introduction to Software Architecture.
Domain Classes – Part 1.  Analyze Requirements as per Use Case Model  Domain Model (Conceptual Class Diagram)  Interaction (Sequence) Diagrams  System.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 8 Slide 1 System models.
Architecture View Models A model is a complete, simplified description of a system from a particular perspective or viewpoint. There is no single view.
Software Engineering Chapter: Computer Aided Software Engineering 1 Chapter : Computer Aided Software Engineering.
Week 04 Object Oriented Analysis and Designing. What is a model? A model is quicker and easier to build A model can be used in simulations, to learn more.
Providing web services to mobile users: The architecture design of an m-service portal Minder Chen - Dongsong Zhang - Lina Zhou Presented by: Juan M. Cubillos.
OOD OO Design. OOD-2 OO Development Requirements Use case analysis OO Analysis –Models from the domain and application OO Design –Mapping of model.
Generalizable Element Namespace Model Element name visibility isSpecification Classifier isRoot Constraint Body Coming up: Unified Modeling Language Introduction.
Object-Oriented Software Engineering Practical Software Development using UML and Java Modelling with Classes.
Object Oriented Analysis and Design Introduction to Rational Rose.
From Use Cases to Implementation 1. Structural and Behavioral Aspects of Collaborations  Two aspects of Collaborations Structural – specifies the static.
HLA OMT Fundamentals Alessandro Specchia Carnegie Mellon University.
Generalizable Element Namespace Model Element name visibility isSpecification Classifier isRoot Constraint Body Introduction to the Unified Modeling Language.
2013 Spring Simulation Interoperability Workshop 13S-SIW-004 Extended FOM Module Merging Capabilities Bjo ̈ rn Mo ̈ ller Andy Bowers Mikael Karlsson Björn.
2013 Spring SIW Software Model Reuse Interface LSA Presentation Presented by Martin Tapp.
From Use Cases to Implementation 1. Mapping Requirements Directly to Design and Code  For many, if not most, of our requirements it is relatively easy.
Simulation in Operational Research form Fine Details to System Analysis.
1 The XMSF Profile Overlay to the FEDEP Dr. Katherine L. Morse, SAIC Mr. Robert Lutz, JHU APL
An Introduction to FOM Modules
Systems Analysis and Design With UML 2
BOMs – Base Object Models
Software Architecture & Design Pattern
Software Architecture and
Introduction to the Unified Modeling Language
SYS466 Domain Classes – Part 1.
An Introduction to Software Architecture
Sample Test Questions Please identify the use cases of the system that cover all the behaviors described in the system specification. Please identify.
PASSI (Process for Agent Societies Specification and Implementation)
Presentation transcript:

From FOMs to BOMs and Back Again Paul Gustavson Tram Chase Larry Root SimVentions, Incorporated Bowman Drive, Suite 502 Fredericksburg, VA

Topics Covered Background Composability & BOMs Breaking up a FOM Creating BOMs BOM Assemblies Exporting a FOM Summary

Background HLA RTI FOM DIS Computability Interoperability

Interoperability & HLA Is this how it feels trying to make interoperability work?

void buttonClicked() { x = 5; } DLL void buttonClicked() { x = 5; beep(); } DLL Composability OK Software Development Example Component OK “the capability to select and assemble simulation components in various combinations into simulation systems to satisfy specific user requirements.” - Dr. M. Petty

What is a BOM? A piece part of a conceptual model, simulation object model, or federation object model, which can be used as a building block in the development and/or extension of a simulation or federation. BOMs can be used to document the interface for one or more of the following piece part elements: –Object classes –Interaction classes –Patterns of interplay –State machines –Events Used as a building block for composing HLA object models, federate capabilities, or federation agreements. Provides developers and users a modular approach –for defining and adding new capabilities to a federate or federation, –for quickly composing object models such as HLA FOMs and SOMs through BOM Assemblies. BOMs Conceptual Models Libraries Tools Patterns FEDEP Enablers Composability

Model Identification (Metadata) Notes Lexicon (definitions) Object Model Definition HLA Object Classes HLA Object Class Attributes HLA Object Classes HLA Interaction Classes HLA Interaction Class Parameters HLA Interaction Classes HLA Data Types Conceptual Model Pattern Of Interplay State Machine Entity Type Event Type Model Mapping Entity Type Mapping Event Type Mapping Essential metadata needed so that the BOM can be described, discovered and properly reused XML based standard for capturing model metadata, aspects of the conceptual model, an object model which can perform the behavior of the conceptual model, and the mapping between that conceptual model and object model. What is a BOM really? Conceptual entities and the events which occur among those entities as well as the states attainable by those entities. Mapping of conceptual entities and events to object model object and interaction classes. Object classes, interaction classes, and datatypes used to perform the behavior described in the conceptual model. Notes and definitions supporting any of the above mentioned elements.

Breaking up a FOM Model Identification (Metadata) Notes Lexicon (definitions) HLA Object Classes HLA Object Class Attributes HLA Object Classes HLA Interaction Classes HLA Interaction Class Parameters HLA Interaction Classes HLA Data Types HLA Dimensions HLA Time HLA Tags HLA Synchronizations HLA Transportations HLA Switches Model Identification (Metadata) Notes Lexicon (definitions) Object Model Definition HLA Object Classes HLA Object Class Attributes HLA Object Classes HLA Interaction Classes HLA Interaction Class Parameters HLA Interaction Classes HLA Data Types Conceptual Model Pattern Of Interplay State Machine Entity Type Event Type Model Mapping Entity Type Mapping Event Type Mapping FOM BOM

Objects & Behavior Object BOM Behavior BOM Object Model Definition Notes Lexicon (definitions) Object Model Definition HLA Object Classes HLA Object Class Attributes HLA Object Classes HLA Interaction Classes HLA Interaction Class Parameters HLA Interaction Classes HLA Data Types Model Identification (Metadata) Model Mapping Entity Type Mapping Event Type Mapping Conceptual Model Pattern Of Interplay State Machine Entity Type Event Type Notes Lexicon (definitions) HLA Data Types

Object Representations Entity Objects Signal Objects Environment Objects Minefield Objects

Object Representations BOMworks Demo

Behavior Representations

Firing Entity Weapon Fire Interaction Target Entity WeaponFire MunitionDetonation DamageStateUpdate Pattern of Interplay - Sequence of activities (actions) related to one or more conceptual entities Fire MunitionFlight Ready UnderFire ImpactDetonation Conceptual Entities Events States

Behavior Representations BOMworks Demo

RPR BOM Decomposition RPR FOM 2.0 DIS 1278 GRIM Repair Resupply Entity Creation Entity Reconst’n Entity Removal Action Request Post Comment Post Event Behavior Rep Object Rep EntityObjects EnvObjects MinefieldObjects SignalObjects Weapons Fire Collision Entity State Update Minefield Synthetic Enviro SIMAN Logistics RadioComms “The use of interaction classes involves a detailed understanding of the state transitions and timing between events.” - RPR FOM GRIM

Federate BOM Coupling BOM Assembly BOM 1 Pattern of Interplay BOM 2 Pattern of Interplay BOM n Pattern of Interplay Interface Assembly Composition Sim / System A Representation Federation Federate B Federate X Federate A Aggregation Model #1 Model #2 Model #3 Model #n - or - Weapons Fire Realtime Platform Warfare Representation Resupply Repair How BOMs are Used? These BOMs represent the relationship of activities among conceptual entities (FOM level),

BOM Assemblies Model Identification (Metadata) Notes Lexicon (definitions) Object Model Definition HLA Object Classes HLA Attributes HLA Object Classes HLA Data Types EntityObjects BOM WeaponsFire BOM Model Identification (Metadata) Notes Lexicon (definitions) Object Model Definition HLA Interaction Classes HLA Parameters HLA Interaction Classes HLA Data Types Conceptual Model Pattern Of Interplay State Machine Entity Type Event Type Model Mapping Entity Type Mapping Event Type Mapping Repair BOM Model Identification (Metadata) Notes Lexicon (definitions) Object Model Definition HLA Interaction Classes HLA Parameters HLA Interaction Classes HLA Data Types Conceptual Model Pattern Of Interplay State Machine Entity Type Event Type Model Mapping Entity Type Mapping Event Type Mapping Model Identification (Metadata) Conceptual Model Pattern Of Interplay State Machine Entity Type Event Type BOM Assembly Notes Lexicon (definitions) A composition of BOMs that can result in a Federation Object Model (FOM), Simulation Object Model (SOM), or pattern which encompasses a larger scope.

BOM Assemblies Model Identification (Metadata) Conceptual Model Pattern Of Interplay State Machine Entity Type Event Type BOM Assembly Notes Lexicon (definitions) BOM Assembly Atomization Model Identification (Metadata) Notes Lexicon (definitions) Object Model Definition HLA Object Classes HLA Attributes HLA Object Classes HLA Data Types EntityObjects BOM Repair BOM Model Identification (Metadata) Notes Lexicon (definitions) Object Model Definition HLA Interaction Classes HLA Parameters HLA Interaction Classes HLA Data Types Conceptual Model Pattern Of Interplay State Machine Entity Type Event Type Model Mapping Entity Type Mapping Event Type Mapping Model Mapping Entity Type Mapping Event Type Mapping Object Model Definition HLA Interaction Classes HLA Parameters HLA Interaction Classes HLA Data Types HLA Object Classes HLA Attributes HLA Object Classes HLA Data Types WeaponsFire BOM Model Identification (Metadata) Notes Lexicon (definitions) Object Model Definition HLA Interaction Classes HLA Parameters HLA Interaction Classes HLA Data Types Conceptual Model Pattern Of Interplay State Machine Entity Type Event Type Model Mapping Entity Type Mapping Event Type Mapping HLA Interaction Classes HLA Parameters HLA Interaction Classes HLA Data Types Entity Type Mapping Event Type Mapping BOMworks Demo

BOM Assembly Atomization BOMworks Demo

Exporting a FOM Model Identification (Metadata) Notes Lexicon (definitions) Object Model Definition HLA Object Classes HLA Object Class Attributes HLA Object Classes HLA Interaction Classes HLA Interaction Class Parameters HLA Interaction Classes HLA Data Types Conceptual Model Pattern Of Interplay State Machine Entity Type Event Type Model Mapping Entity Type Mapping Event Type Mapping XSLT/ Method of choice BOM Assembly Model Identification (Metadata) Notes Lexicon (definitions) HLA Object Classes HLA Object Class Attributes HLA Object Classes HLA Interaction Classes HLA Interaction Class Parameters HLA Interaction Classes HLA Data Types HLA Dimensions HLA Time HLA Tags HLA Synchronizations HLA Transportations HLA Switches FOM

Exporting a FOM BOMworks Demo

Summary Benefits of breaking up FOMs into BOMs: –supports composability by allowing BOMs to be used as building blocks for simulations and federations –facilitates manageability of FOMs –provides extensibility of FOMs through the application and integration of new BOMs –provides the ability to capture additional model information such as patterns or interplay and states

Questions Paul Gustavson - Tram Chase – Larry Root –