extensible modeling and simulation framework extensible 3d graphics (x3d)
DESCRIPTION
Joint Synthetic Battlespace (JSB) Technical Exchange Hanscomb AFB, 12 November 2003. Extensible Modeling and Simulation Framework Extensible 3D Graphics (X3D). Don Brutzman MOVES Institute, Naval Postgraduate School Andreas Tolk VMASC, Old Dominion University (ODU). - PowerPoint PPT PresentationTRANSCRIPT
Extensible Modeling and Simulation
Framework Extensible 3D Graphics (X3D)
Don BrutzmanMOVES Institute, Naval Postgraduate School
Andreas TolkVMASC, Old Dominion University (ODU)
Joint Synthetic Battlespace (JSB) Technical Exchange Hanscomb AFB, 12 November 2003
Recommendations for a Framework ensuringInteroperability, Reusability, & Composability
12 November 2003XMSF/X3D Overview, JSB Technical Briefings 3
A Framework for Interoperability, Reusability, and Composability
Without the necessary management processes, technical solutions are point solutions in time only valid until the next change (update, upgrade, etc.)
Alignment of Management is necessary
To Enable meaningful interoperability on the simulation system level, composable models on the conceptual level are necessary
Common Conceptual Modeling is necessary
12 November 2003XMSF/X3D Overview, JSB Technical Briefings 4
Recommended Solution for JSB
Three columns of JSB
1. An overarching Engineering Approach applicable to existing and future simulation components including migration concepts;
2. Establishing a Resource Repository comprising these Components and the necessary Meta-Models;
3. Alignment of the Management Processes
12 November 2003XMSF/X3D Overview, JSB Technical Briefings 5
JSB Column 1 – A Common Engineering Approach
Requirements for the Integration Framework Support Future Emerging Simulation Needs Applicable for Future Components Migration for Legacy Components Supporting Integration of Real World Components (C4ISR, Platforms, Sensors, etc.)
The JSB Integration Framework must be a conceptually stable solution independent from technical implementations, but commercially supported
12 November 2003XMSF/X3D Overview, JSB Technical Briefings 6
The MDA embraces technical implementations and standards, such asweb services, XML, EJB, SOAP, CORBA, etc.
JSB Column 1 – A Common Engineering Approach
Recommended Backbone – Application of the Model Driven Architecture (MDA) of the Object Management Group (OMG)
Implementation independent Modeling based on the Unified Modeling Language (UML)
Implementation independent Data and Object Modeling based on the Common Warehouse Meta-Model (CWM)
Implementation independent Repository Description based on the Meta-Object Facility (MOF)
12 November 2003XMSF/X3D Overview, JSB Technical Briefings 7
The MDA connects conceptual and implementation level of the components => Bridging Management and Implementation
JSB Column 1 – A Common Engineering Approach
The model hierarchy of the Model Driven Architecture (MDA)
Platform Independent Model (PIM); conceptual model resulting from requirement analysis (“What to model”)
Platform Specific Model (PSM); implementation oriented version (“How to implement”)
Code/Implemented Component
PIM
PSM
Code
12 November 2003XMSF/X3D Overview, JSB Technical Briefings 8
JSB Column 2 –Resource Repository
Level of Interoperability
Description Examples
Technical Level Connectivity established to exchange bits and bytes
Physical Connections, Network Layers
Syntactical Level Data can be exchanged in standardized formats
HLA OMT, CORBA IDL, DIS PDU, XML, WSDL
Semantic Level Data in its contexts can be exchanged (unambiguous understanding of data)
Reference Data Models (C2IEDM)
Pragmatic Level Information, I.e., data and its use in the component, can be exchanged
Reference Models in UML XMI, or MOF
Conceptual Level Common view of the world, system-of-systems wide conceptual model
Common Conceptual Models (in UML, XMI, or MOF)
12 November 2003XMSF/X3D Overview, JSB Technical Briefings 9
JSB Column 2 –Resource Repository
The Resource Repository must comprise not only the component, but also the meta-data describing the component on the various levels of interoperability
Recommendation: Use the MDA as the Framework for the JSB Repository
Component as Code (executable)
Include PSM (“White Box” of implementation without having to enforce open source)
Include PIM (Contribution to the Common Conceptual Model)
Gradual Development of a common conceptual view of the mission space of JSB
12 November 2003XMSF/X3D Overview, JSB Technical Briefings 10
JSB Column 3 –Aligning Management Processes
Common Data Engineering as the first Step: Data Administration – Managing Information Exchange needs,
I.e., which data are where in which format
WSDL and UDDI support Data Administration Data Management – Managing of unambiguous interpretation,
I.e., which data mean what
C2IEDM/Generic Hub support Data Management Data Alignment – Managing of mapping of data sources to data
targets, I.e., is all necessary data available
XML enables efficient Data Alignment Data Transformation – Technical mapping of source data format
to target data format
XSLT enables Data Transformation
12 November 2003XMSF/X3D Overview, JSB Technical Briefings 11
JSB Column 3 –Aligning Management Processes
Each project must be embedded into the overarchingJSB processes
Each project reuses JSB components (mandatory) Each project contributes to the JSB components
(at least on the conceptual level by adding with itsPIM to the Common Conceptual View of the JSB Mission Space)
All projects are orchestrated by an OverarchingIntegrated Product Development Team
JSB orchestrates the heterogeneous implementations by aligning conceptual contributions to enable homogeneous training and support to operations
12 November 2003XMSF/X3D Overview, JSB Technical Briefings 12
Initial Recommendations
What is necessary to enable a fast JSB start avoiding running into dead ends?
1. Use open standards in an orchestrated way2. Establish an independent advisory board3. Document management processes for evaluation and
deriving of a guide4. XML Namespace Management as a requirement for
common data engineering5. Start to develop PIM for the Common Conceptual
View of the JSB Mission Space6. Participate actively in open standard communities
efforts for JSB (OGC, OMG, SISO, W3C, Web3D)
12 November 2003XMSF/X3D Overview, JSB Technical Briefings 13
Contact NPS
Don Brutzman
[email protected]://web.nps.navy.mil/~brutzman
Code UW/Br, Naval Postgraduate SchoolMonterey California 93943-5000 USA
1.831.656.2149 voice1.831.656.3679 fax
12 November 2003XMSF/X3D Overview, JSB Technical Briefings 14
Contact ODU
Andreas Tolk
[email protected]://myprofile.cos.com/atolk
Virginia Modeling Analysis & Simulation CenterOld Dominion University
Norfolk, VA 235291.757.686.6203 (voice)1.757.686.6214 (fax)
12 November 2003XMSF/X3D Overview, JSB Technical Briefings 15
Contacts XMSF
http://www.MovesInstitute.org/xmsf
Don Brutzman [email protected] 831.656.2149Michael Zyda [email protected] 831.656.2305Don McGregor [email protected] 831.656.4090Andrzej Kapolka [email protected] 831.656.2253
Mark Pullen [email protected] 703.993.1538
Katherine Morse [email protected] 858.826.6728David Drake [email protected] 858.826.2278Ryan Brunton [email protected]
Andreas Tolk [email protected] 757.686.6203Bowen Loftin [email protected] 757.686.6200