There is nothing magical to the XRadar framework - it is based on best practices within xml processing. You have a set of XSL stylesheets with specific tasks that you run consecutively. Input and output are both XML documents.
The XRadar framework currently runs through a build file in Apache Ant as a batch process, but there is no reason why it cannot be initiated and controlled by any other means that offer the needed supporting functionality. We also have maven-plugin so that you can run the process on a cluster of maven-projects.
When you run Statics, you initiate an XSL pipeline where each metric source is integrated by a specific merge style sheet. Relevant data from each merge is added to the total xml report. In a way you produce an extendable xml metric database of the system. The final XML report is post processed and then sent to the relevant report framework. For the XRadar Statics report, that report framework is to a set of XSL style sheets that produces the final HTML/SVG report. See the figure below for a rough figure of framework running XRadar Statics.
See Statics Design for further detials on the statics design and specifics on the various elements.
The XRadar architecture for Dynamics is very similar as for Statics. A pipeline is initiated, but here each source to be merged is a final Radar Statics XML report. Each is merged sequentially through a pipeline producing a common historical XML database of the system. This XML is then sent to the XRadar Dynamics report framework that produces the final HTML/SVG report. See the figure below for graphical representation of the pipeline.
See Dynamics Design for further detials on the dynamics design and specifics on the various elements.