Datasets.htm

---
layout: default
---

<p><font face="Verdana" size="3"><strong><font size="4" color="#006699">DESSERT 
          DATASETS</font></strong></font><font face="Verdana" size="1"><br>
          <br>

	  <!-- OSPL Dataset-->
          <font face="Verdana" size="1"><font size="3"><b>ATC Middleware Direct Monitoring Dataset</b></font><font size="2"><br>
	  ATC Middleware Direct Monitoring Dataset is a collection of data obtained during an experimental analysis of different direct monitoring techniques.<br>
	  The analysis based on a fault-injection campaign on a real-world air traffic control (ATC) middleware system conducted by SAFE tool.
	  The transport layer of the considered middleware implements three direct monitoring techniques, i.e., event logging, assertion checking, and <a href="http://ieeexplore.ieee.org/xpl/articleDetails.jsp?tp=&arnumber=6320555&queryText%3Drule-based+logging">rule-based logging</a> supported by LogBus.
	  We injected 12,733 software faults, which types extend the Orthogonal Defect Classification (ODC) for practical injection purposes, into the middleware transport layer source code.
	  For each injected faults, we collected the error messages generated by the considered techniques at middleware level, but also the event logs produced by the operating system (Red Hat 5 El) and 
	  the legacy ATC applications running on the top of the target middleware.
	  In summary, collected data include:
	  <ul>
	  <li>error messages generated by middleware: <ul> <li>error entries of the event logs (MwLog)</li><li>assertions (MwAss);</li><li>eror entries oh the rule-based logs (MwR-BLog);</li></ul></li>
	  <li>error entries of the operating system event logs (OsLog);</li>
	  <li>error entries of the application event logs (AppLog).</li>
	  </ul>

	  The dataset contains a folder for each technique mentioned above. Each folder contains 12,733 files, a file for each experiment (i.e., faults injected in the middleware).
	  Each file contains the error messages generated by a technique when we inject a fault in the middleware transport layer source code. The name of the file indicates the source code file where the 
          fault is injected and the type of the injected fault. The dataset also include a file that indicates the outcome of each experiment, i.e., if the injected fault led to a 
          failure in the middleware or not. For the experiments where a failure occurred in the system, the file indicates the type of the occurred failure as outcome of the experiment, i.e., <a href="http://dx.doi.org/10.1109/TDSC.2004.2">CRASH, SILENT or ERRATIC</a>.<br><br>
          <a href="/Datasets/MWdirectMonitoring.zip">Click here to download the dataset</a></font></font><font size="2"><br>
          <br>
          Please, cite our <a href="http://ieeexplore.ieee.org/xpl/articleDetails.jsp?arnumber=7493640">Transactions on Reliability paper</a> if you use the dataset in your research.
          <br>
	  For more information about the dataset and its generation, contact us at:<br>
	  <ul>
	  <li><i>macinque at unina.it</i>
	  <li><i>raffaele.dellacorte2 at unina.it</i></li></ul></font>
	  <br>
	  <!-- AMG Dataset-->
          <font face="Verdana" size="1"><font size="3"><b>ATC Arrival Manager Direct Monitoring Dataset</b></font><font size="2"><br>
	  Arrival Manager Direct Monitoring Dataset is a collection of data obtained during an experimental analysis of different direct monitoring techniques.<br>
	  The analysis based on a fault-injection campaign on a real-world Arrival Manager system conducted by SAFE tool.
	  The target system implements three direct monitoring techniques, i.e., event logging, assertion checking, and <a href="http://ieeexplore.ieee.org/xpl/articleDetails.jsp?tp=&arnumber=6320555&queryText%3Drule-based+logging">rule-based logging</a> supported by LogBus.
	  We injected 6,597 software faults, which types extend the Orthogonal Defect Classification (ODC) for practical injection purposes, into the arrival manager source code.
	  For each injected faults, we collected the error messages generated by the considered techniques.
	  In summary, collected data include:
	  <ul>
	  <li>error entries of the event logs (AmLog);</li>
	  <li>assertions (AmAss);</li>
	  <li>error entries of the rule-based logs (AmR-BLog).</li>
	  </ul>

	  The dataset contains a folder for each technique mentioned above. Each folder contains 6,597 files, a file for each experiment (i.e., faults injected in the arrival manager).
	  Each file contains the error messages generated by a technique when we inject a fault in the arrival manager source code. The name of the file indicates the source code file where the fault is 
          injected and the type of the injected fault. The dataset also include a file that indicates the outcome of each experiment, i.e., if the injected fault led to a 
          failure in the arrival manager or not. For the experiments where a failure occurred in the system, the file indicates the type of the occurred failure as outcome of the experiment, i.e., <a href="http://dx.doi.org/10.1109/TDSC.2004.2">CRASH, SILENT or ERRATIC</a>.<br><br>
          <a href="/Datasets/AMdirectMonitoring.zip">Click here to download the dataset</a></font></font><font size="2"><br>
          <br>
	  Please, cite our <a href="http://ieeexplore.ieee.org/xpl/articleDetails.jsp?arnumber=7493640">Transactions on Reliability paper</a> if you use the dataset in your research.
          <br>
	  For more information about the dataset and its generation, contact us at:<br>
	  <ul>
	  <li><i>macinque at unina.it</i>
	  <li><i>raffaele.dellacorte2 at unina.it</i></li></ul></font>