Design ldeas 1 Design Ideas ervices support wide-area routing and playback ming metaphors+ XMl tagsets/registries all Language and object-syste -level time ab ing languages and AP bdet anguage bindings Infrastructur da Wire protocols bly defined using XML Run-time extensibity. portability, interoper/ability for bility from Schema Business Model 1 Business Model 2 Roval fee. us able wuthout ahy fee rell Commercial models in partnership with open-source important to ha Int Offer nning ski for a fee and give up ngt a Proprietary softwar Long-term stable business intrastructure. they can use any license they like of this and se r - Someone needs to put together the simulations Even t al the parts 中 中四 Success of the overall endeavor is key to business success DoD Business Model Open Issues Commercial tech is crucial We can't do it alone Special technology requirements harmful anslate into alw g too much for unique, Nothing succeeds like sucdess ndards and industrly best practices makes best sense for industry partners aton. or 3 upporting inherent 66 19-20 August 2002 31 Design Ideas 1 Object-oriented programs + validatable structured data n Repeatable programming metaphors + XML tagsets/registries Language and object-system independent n e.g. CORBA/IDL, SOAP, RMI/RPC, others Design patterns unambiguously define language bindings n Map representations, component models from root XML schemas to programming languages and API bindings of interest Wire protocols unambiguously, flexibly defined using XML n Run-time extensibility, portability, interoperability for streams n Packet description language -or- direct mappability from Schema 19-20 August 2002 32 Design Ideas 2 Time services support wide-area routing and playback n Participating computer clocks all set correctly(!) via NTP or GPS n RTP for all stream headers n SMIL for stream synchronization n Higher-level time abstractions communicable by system n What about supercomputer batch-mode asynchronous? Infrastructure represented as objects in system n Enable object and service discovery at runtime n Ability to monitor, test, improve systems at local and global scale 19-20 August 2002 33 Business Model 1 Minimal architecture is open source implementation n Royalty free, usable without any fee restrictions whatsoever Important to have two or more interoperable implementations n Commercial implementations profitably augment open source Long-term stable infrastructure enables sustainable business models n Flexible architecture broadens market: not “just” military simulation, also full World Wide Web via open/secure Internets n Web-enabled architecture allows more sponsors to participate, which allows simulations, models, and applications to survive despite intermittent funding profiles n Transferable career-building skills and reusable experience for programmers and managers 19-20 August 2002 34 Business Model 2 Commercial models in partnership with open-source n Support w Offer programming skill for a fee and give up rights to the source if it is infrastructure related. n Proprietary software w A vendor may write a simulator that runs on top of the free infrastructure. They can use any license they like on this and sell it as they see fit. n Consulting w Someone needs to put together the simulations. Even if all the parts are free, this is a salable service. n Maintenance w Numerous success stories exist. Success of the overall endeavor is key to business success. 19-20 August 2002 35 DoD Business Model Commercial technology is crucial nWe can’t do it alone Special technology requirements harmful n Translate into always spending too much for unique, outdated technology Nothing succeeds like success n Slipstreaming standards and industry “best practices” makes best sense for industry partners too 19-20 August 2002 36 Open Issues Source code control n Interoperability test suite and certification shows conformance n Source forking no longer divisive issue, let many flowers bloom n “Actual results” validation through use with tactical systems Architecture n What are good driving exemplar applications? wReality pulls teams through the big design space wMust show significant “value add” to current practices plus current excitement n Can we extend some existing systems (e.g. HLA/RTI capable), show interoperability with legacy systems via good examples? we.g. NSS, OneSAF, ITEM n Multiple inheritance – no; multiple interfaces – yes n Do we need a specified method for distributed synchronization, or is open architecture supporting different models sufficient?