MilSOFT DDS is an implementation of Object Management Group’s (OMG) Data Distribution Service (DDS) specification, which is a data-centric publish-subscribe middleware with a rich set of Quality of Service (QoS) attributes.

MilSOFT DDS also supports OMG’s Real-Time Publish-Subscribe (RTPS) interoperability protocol. RTPS protocol is designed to enable interoperability between DDS implementations from different vendors. MilSOFT DDS is tested to be interoperable with other commercialy available DDS implementations which support RTPS.

MilSOFT DDS middleware supports “Minimum Profile” as defined in OMG DDS specification. “Persistence Profile” and “Content Subscription Profile” are also supported. “Persistence Profile” enables the middleware to resend data to applications which are crashed and then re-started. “Content Subscription Profile” enables the users to filter the data they receive with some SQL-like queries.

MilSOFT DDS basically provides the following features:

MilSOFT has used her own DDS implementation in the development of Combat Management System, Multi-Link Data Processor and Unmanned Air Vehicle Image Exploitation programs and it’s also planned to be used in future applications. For unclassified information on these systems and MilSOFT DDS’ role in them, please download the following documents:

DDS Modeler is the utility provided for software developers. Developers can model their MilSOFT DDS applications with DDS Modeler and then it generates source code needed to interface with DDS middleware which prevents the users from dealing with specifics of the middleware.

DDS Spy is used to monitor the participants in the system and the data that they publish or subscribe. The publish-subscribe architecture of DDS middleware enables DDS Spy tool to be started at any time when the system is operational. Users may monitor the DDS entities, their Quality of Service attributes and the data that are published in the system.

DDS Tester provides very flexible mechanisms to test systems that utilize the MilSOFT DDS middleware. Test engineers can define test suites which contains input data and the expected results data. Input data consists of data that will be published as DDS topics and their relative timestamps according to start of execution of the test suite. DDS tester will automatically subscribe to topics for the expected results data and at the end of the execution, the expected results are compared with the actual results obtained from the system.