1 / 15

Extensible Modeling and Simulation Framework Extensible 3D Graphics (X3D)

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).

hamlin
Télécharger la présentation

Extensible Modeling and Simulation Framework Extensible 3D Graphics (X3D)

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. 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)

  2. Recommendations for a Framework ensuringInteroperability, Reusability, & Composability

  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 XMSF/X3D Overview, JSB Technical Briefings

  4. Recommended Solution for JSB • Three columns of JSB • An overarching Engineering Approach applicable to existing and future simulation components including migration concepts; • Establishing a Resource Repository comprising these Components and the necessary Meta-Models; • Alignment of the Management Processes XMSF/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 XMSF/X3D Overview, JSB Technical Briefings

  6. 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) The MDA embraces technical implementations and standards, such asweb services, XML, EJB, SOAP, CORBA, etc. XMSF/X3D Overview, JSB Technical Briefings

  7. 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 The MDA connects conceptual and implementation level of the components => Bridging Management and Implementation XMSF/X3D Overview, JSB Technical Briefings

  8. JSB Column 2 –Resource Repository XMSF/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 XMSF/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 XMSF/X3D Overview, JSB Technical Briefings

  11. JSB Column 3 –Aligning Management Processes • Each project must be embedded into the overarching JSB processes • Each project reuses JSB components (mandatory) • Each project contributes to the JSB components (at least on the conceptual level by adding with its PIM to the Common Conceptual View of the JSB Mission Space) • All projects are orchestrated by an Overarching Integrated Product Development Team • JSB orchestrates the heterogeneous implementations by aligning conceptual contributions to enable homogeneous training and support to operations XMSF/X3D Overview, JSB Technical Briefings

  12. Initial Recommendations • What is necessary to enable a fast JSB start avoiding running into dead ends? • Use open standards in an orchestrated way • Establish an independent advisory board • Document management processes for evaluation and deriving of a guide • XML Namespace Management as a requirement for common data engineering • Start to develop PIM for the Common Conceptual View of the JSB Mission Space • Participate actively in open standard communities efforts for JSB (OGC, OMG, SISO, W3C, Web3D) XMSF/X3D Overview, JSB Technical Briefings

  13. Contact NPS • Don Brutzman • brutzman@nps.navy.mil • http://web.nps.navy.mil/~brutzman • Code UW/Br, Naval Postgraduate School • Monterey California 93943-5000 USA • 1.831.656.2149 voice • 1.831.656.3679 fax XMSF/X3D Overview, JSB Technical Briefings

  14. Contact ODU • Andreas Tolk • atolk@odu.edu • http://myprofile.cos.com/atolk • Virginia Modeling Analysis & Simulation Center • Old Dominion UniversityNorfolk, VA 23529 • 1.757.686.6203 (voice) • 1.757.686.6214 (fax) XMSF/X3D Overview, JSB Technical Briefings

  15. Contacts XMSF • http://www.MovesInstitute.org/xmsf • Don Brutzman brutzman@nps.navy.mil 831.656.2149 • Michael Zyda zyda@nps.navy.mil 831.656.2305 • Don McGregor mcgredo@nps.navy.mil 831.656.4090 • Andrzej Kapolka akapolk@nps.navy.mil 831.656.2253 • Mark Pullen mpullen@gmu.edu 703.993.1538 • Katherine Morse morsek@saic.com 858.826.6728 • David Drake drakedavid@saic.com 858.826.2278 • Ryan Brunton bruntonr@saic.com • Andreas Tolk atolk@odu.edu757.686.6203 • Bowen Loftin bloftin@odu.edu 757.686.6200 XMSF/X3D Overview, JSB Technical Briefings

More Related