The Dynamics Design is very similar to the Statics Design as can be seen in the XRadar architecture . In the following sections, the design of the dynamics processes will be described in turn. References to the statics processes will be used where applicable.
The statics merging process takes the normalized xml from statics and merges each into a common xml. The same stylesheet - merge-normalized-report-to-dynamics-master.xsl - is used for all the merges. In principle the output has the same structure as the normalized xml, except that for each metric there is a "value" element for each version of the system. The simplest way to understand this is to take a look at the output structure from the testproject.
The dynamics post-processing process adds adds some extra info to the xml so that everything is ready for the final step: The report itself.
The dynamics graphing process is very similar to the statics process except one major detail - all graphs are produced directly from within the report structure. Otherwise the strucure is similar in that there is one style-sheet as input dynamics-report-master-frames.xsl and that this stylesheet is responsible for delegating all creation of the report pages. One very convenient part of the statics design is that system, module, and package all use the same templates for reports in each ares.
My experience with development in dynamics is that it is very quick and fun to add new reports. For every change I have also refactored a lot so the design has steadily become more simple. I believe that if there was a xslt analysis version of the XRadar, the dynamics module would get far better ratings than the statics module!