Once the data is collected, it is time for analysis. Hackystat is not intended to replace or compete with statistical packages such as S or R, but rather to facilitate the transfer of empirical data about development products and processes into these environments that are designed specifically for empirical analysis.
In some cases, it is possible that existing Hackystat analyses are all that are required. For example, in the case of the example experiment TFDvTLD, no specialized exporting mechanisms would be required. Instead, the Experiment Administrator can simply use the Experiment Telemetry Chart command to generate the final values of DevTime and Coverage for each subject, then copy those values manually into the external analysis package.
In other cases, more sophisticated post-processing might be required, such as in the case of workflow analysis and inference. In this case, it can be useful to obtain the raw sensor data from the experiment in a form amenable to processing by an external tool. The Experiment Export command is designed to support such external analysis. This Admin command accepts only the name of an Experiment, and generates a zip file containing, in XML format, the contents of the sensor data associated with the users and Projects for this Experiment. Figure 11.10, “ Experiment Data Export Command ” illustrates this command and Figure 11.11, “ A Portion of Exported Experiment Data ” illustrates a portion of the XML data generated for our example experiment.
