Telemetry System Manager Automatic Program Synthesis, 10-R8532
Inclusive Dates: 01/14/15 – 05/14/15
Background — The current telemetry component provider landscape is diverse in approach and capability, and this landscape continues to evolve as new test articles require new components, which leads to new system management requirements and complexities, especially in the area of configuration. To combat this evolving landscape, the integrated network enhanced telemetry (iNET) program has defined an extensible markup language (XML) grammar that defines how telemetry devices are to configure themselves, the metadata description language (MDL). This vendor-independent grammar is being increasingly adopted across the board by the telemetry industry. As such, a general method for creating MDL while considering the constraints (or capabilities) of individual devices is needed. The only viable approach to this problem is for the vendors to supply the new or updated constraints along with any new or updated devices. However, there are various classes of users, or layers of users, that require the ability to add further constraints on top of the vendor constraints.
Approach — Standardized XML technologies were used to develop an experimental framework that automatically generated XForms, or user interface elements, directly from an XML schema, while also constraining the relevant fields. The generated user interface was then capable of providing immediate feedback, in the form of error messages describing the failed constraint(s), as the user input configuration data. The supplied constraints were written using XPath expressions, providing interoperability and straightforward conversion to other XML-based languages. Once the XForms were created, templates that contained basic data and partial frameworks for devices were used as initial instance data to feed into the interface. This allowed for defined specialization of the interfaces, as the initializing data combined with the constraints meant that portions of the user-editable data could be intelligently completed without user input. After the XForms were filled out, populated XML fragments containing all the information were stored in a database. Then, using marshalling techniques to combine all necessary devices/elements of the desired output, a final XML output file was produced. This approach resulted in an XML file that described a valid device configuration, which was used to successfully configure the target device.