Software architecture and design for facilitating prototyping in distributed virtual environments

Abstract

The invention is a data-handling architecture that exploits the technical advantages offered by object-oriented techniques, classes, data containers, component software, object frameworks, containerization, design patterns, and a central runtime data repository. The architecture is based on the Common Object DataBase (CODB), frameworks, components, objects, information streams, and containers. The software exploits the Extensible Markup Language (XML), employs software gauges, and uses intelligent agents to aid in assembly, diagnosis, evaluation, composition, and re-configuration of a DATE-based application. The architecture of the present invention is defined by highly-modular components where interdependencies are well-defined and minimized. Components define the major aspects of the inventive architecture, objects are used to flesh out the specification, design, and implementation of the components. The invention's architecture can support the dynamic loading of any of the components or major objects in any component required without re-linking or recompiling software. Within the architecture, data is transmitted between components only along information streams within containers using the Extensible Markup Language (XML).

1. A data-handling, software architecture enabling new components and software objects to be added and interchanged without forcing the modification of or otherwise disturbing existing software comprising:
 information streams for receiving and transmitting data;  
 state-changing computer model components for receiving, processing and transmitting incoming data from said information streams;  
 unvarying, during execution, software object containers including data structure and software methods for managing data and wherein source of incoming data determines container selection and wherein only one container selection is available for each of said components;  
 a first framework at a highest level of said data-handling software architecture providing minimal coupling of said components and data routing and data management services including efficient data transport between said components and between said components and a virtual environment coupled to a network via a World State Manager;  
 a second framework supporting said state-changing computer model components by providing a set of services required for specific component applications and decoupling individual components from each other and said architecture;  
 intelligent computer services within said second framework comprising: 
 a physical representation component;  
 a cognitive representation component;  
 a skills component;  
 a physical state information interface;  
 a sensor interface, and  
 a knowledge database;  
 
 said first and second framework invisible in the interior operation of any component of said state-changing computer model components; and  
 a Common Object Database functioning as a central data repository and information router between all of said state-changing computer model components and wherein data moves between said state-changing computer model components, responsive to information from said intelligent computing services, after passing through said Common Object Database through said software object containers along said information streams.  
 
   
   
     2. The data-handling software architecture of  claim 1  wherein said state-changing computer model components comprise a computer model of a defense vehicle. 
   
   
     3. The data handling software architecture of  claim 1  wherein said state-changing computer model components further comprise an intelligence actor in said component. 
   
   
     4. The data-handling software architecture of  claim 1  wherein said Common Object Database comprises:
 intelligence agents used to check accuracy of connections in an information stream; and  
 software gauges selected by said Common Object Database providing data about transmitted information and component fit.  
 
   
   
     5. The data-handling software architecture of  claim 1  wherein said Common Object Database comprises:
 means for receiving inbound information for all servicing data streams;  
 means for determining data recipients; and  
 means for storing information until requested.  
 
   
   
     6. The data-handling software architecture of  claim 1  wherein said unvarying, during execution, software object containers further comprise:
 hierarchically nested pallets comprising a major category of information or data in a container; and  
 slots within said pallets wherein all information related to a specific component is placed into only one slot within a container.  
 
   
   
     7. The data-handling software architecture of  claim 1  wherein said first framework further comprises:
 means for coordinate conversion; and  
 means for data filtering.  
 
   
   
     8. The data-handling software architecture of  claim 1  wherein said first framework further comprises:
 means for holding together major system components; and  
 a skeleton upon which to assemble computer-generated actors to assemble host sensor models.  
 
   
   
     9. The data-handling software architecture of  claim 1  wherein said first and second frameworks further comprise
 means to support component migration;  
 component information logging in Extensible Markup Language;  
 means for data management;  
 means for initialization;  
 means for shut down;  
 means for GPS satellite based position computation; and  
 means for entity tracking.  
 
   
   
     10. The data-handling software architecture of  claim 1  wherein said knowledge database further comprises:
 an environment database; and  
 a mission, tactics and strategy database.  
 
   
   
     11. A data-handling software design enabling adding and interchanging of new components and objects without disturbing existing software comprising the steps of:
 receiving and transmitting data using information streams;  
 receiving, processing and transmitting incoming data from said information streams using state-changing computer model components;  
 managing data using unvarying, during execution, software object containers wherein source of incoming data determines container selection and wherein only one container selection is available for each of said components;  
 data routing with minimal coupling of said components and data managing services using a first framework at the highest level of said data-handling software design including efficient data transport between said components and a virtual environment and a network coupling environment;  
 supporting said state-changing computer model components using a second framework by providing a set of services required for specific component applications and decoupling individual components from each other and said architecture;  
 providing intelligent computing services within said second framework comprising the steps of: 
 physical representation computing;  
 cognitive computing;  
 skills computing;  
 interfacing based on physical state information;  
 sensor interfacing, and  
 providing a knowledge database;  
 
 said data routing and supporting steps invisible in the interior operation of any component of said state-changing computer model components; and  
 providing a Common Object Database functioning as a central data repository and information router between all components and wherein data moves between said state-changing computer model components, responding to said intelligent computing services, after passing through said Common Object Database through said software object containers along said information streams.  
 
   
   
     12. The data-handling software design of  claim 11  wherein said receiving, processing and transmitting step further comprises the step of receiving, processing and transmitting incoming defense vehicle data from said information streams using state-changing defense vehicle computer model components. 
   
   
     13. The data handling software design of  claim 11  wherein said receiving, processing and transmitting step further comprises the step of receiving, processing and transmitting incoming defense vehicle data from said information streams using state-changing defense vehicle computer model components containing an intelligence actor. 
   
   
     14. The data-handling software design of  claim 11  wherein said step of providing a Common Object Database further comprises the steps of:
 determining accuracy of connections in an information stream using intelligence agents; and  
 providing data about transmitted information and component fit using software gauges selected by said Common Object Database.  
 
   
   
     15. The data-handling software design of  claim 11  wherein said step of providing a Common Object Database comprises the additional steps of:
 receiving inbound information for all servicing data streams;  
 determining data recipients; and  
 storing information until requested.  
 
   
   
     16. The data-handling software design of  claim 11  wherein said step of managing data using unvarying, during execution, software object containers wherein source of incoming data determines container selection and wherein only one container selection is available for each of said components further comprises the steps of:
 providing hierarchically nested pallets comprising a major category of information or data in a container; and  
 providing slots within said pallets wherein all information related to a specific component is placed into only one slot within a container.  
 
   
   
     17. The data-handling software design of  claim 11  wherein said data routing step further comprises the steps of:
 providing coordinate conversion; and  
 filtering data.  
 
   
   
     18. The data-handling software design of  claim 11  wherein said data routing step further comprises the steps of:
 holding together major system components; and  
 providing a skeleton upon which to assemble computer-generated actors to assemble host sensor models.  
 
   
   
     19. The data-handling software design of  claim 11  wherein said data routing step and said supporting step further comprise the steps of:
 supporting component migration;  
 providing component information logging in Extensible Markup Language;  
 managing data;  
 initializing;  
 shutting down;  
 computating GPS satellite position; and  
 tracking components.  
 
   
   
     20. The data-handling software design of  claim 11  wherein said step of providing a knowledge database further comprises the steps of:
 providing an environment database; and  
 providing a mission, tactics and strategy database.