Implementing Traceability Repositories as Graph Databases for Software Quality Improvement: Datasets used to test our methodology that is presented in the paper 10.1109/QRS.2018.00040

The first dataset is the Event Based Traceability for Managing Evolutionary Change (EBT), it is a public dataset provided by CoEST, the original artifacts and trace links are represented in XML and text format. From the EBT dataset, we selected the 41 requirements and 25 test case artifacts, in addition to the answer set of 51 trace links which relates the requirements with the test case. Artifacts and trace links are prepared in XML format. The data set contains XML for each artifact such as RQ.xml, EBTrelations.xml is the answer set file, TradModel.xml which describes the defined model and TradTraceabilityRule.xml that includes the rules applied for trace link types.

The second dataset AgileOERP is collected from commercial management tool to customize an open source ERP applying agile methodology. It contains 350 user stories (US), 1323 tasks (TS) and 198 developer test (DT) artifacts, in addition to answer set of trace links that manually generated by developers which relates the user story artifact with task (1304) artifact, as such relates the task artifact with developer test artifact (65). Artifacts and trace links are prepared in XML format. The data set contains XML for each artifact such as US.xml, ERPrelations.xml is the answer set file, AgileModel.xml which describes the defined model and AgileTraceabilityRule,xml that includes all rules applied for trace links  type

The original dataset of the last dataset is the Aqualush irrigation system which is used as a case study in “C. Fox, Introduction to Software Engineering Design: Processes, Principles and Patterns with UML2. Addison-Wesley, 2006”. The trace links are generated and provided in “E. Ben Charrada, D. Caspar, C. Jeanneret, and M. Glinz, towards a benchmark for traceability, in Joint EVOL and IWPSE 2011, pp. 21-30”, in HTML format. For our work, we selected the software requirements specification (396 SRS), user level requirements (48 ULR), use case (74 UC), detailed design (85 DD) and software architecture(15 SArch) artifacts in addition to the answer set of trace links that relate the SRS with other artifacts(4038) and thus relates the DD artifact with other artifacts (1719) . Artifacts and trace links are prepared in XML. The data set contains XML for each artifact such as SRS.xml, AqualushRelations.xml is the answer set file, TradModel.xml which describes the defined model and TradTraceabilityRule.xml that includes the rules applied for trace link types.