Datasets:
File size: 1,702 Bytes
e2b6f23 f4f2893 7d7d323 f4f2893 7d7d323 f4f2893 7d7d323 f4f2893 7d7d323 9fbd1b6 7d7d323 9fbd1b6 caa5f57 f4f2893 9fbd1b6 7d7d323 |
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 |
---
configs:
- config_name: artifacts
data_files: artifacts.csv
- config_name: traces
data_files: traces.csv
- config_name: matrices
data_files: matrices.csv
- config_name: train
data_files: train.csv
language:
- en
license: mit
pretty_name: Event Based Traceability
task_categories:
- sentence-similarity
- text-classification
tags:
- software traceability
size_categories:
- n<1K
---
# Overview
The following dataset contains the software artifacts used to evaluate the accuracy of traceability algorithms. It contains requirements, test cases, and source code with links established between requirements to code and requirements to test cases.
[Source Files](http://sarec.nd.edu/coest/datasets.html)
# Format
The following files contains three datasets:
- artifacts: Contains all software artifacts including their ID and content.
- traces: Contains list of positive trace links established in the project.
- matrices: Details the artifacts types containing traces (e.g. requirements -> test cases)
- train: Contains a dataset ready for training with each row containing source and target artifact content alongside the label between the artifacts.
### Citation Information
```
@ARTICLE{1232285,
author={Cleland-Huang, J. and Chang, C.K. and Christensen, M.},
journal={IEEE Transactions on Software Engineering},
title={Event-based traceability for managing evolutionary change},
year={2003},
volume={29},
number={9},
pages={796-810},
keywords={Software maintenance;Software systems;Maintenance engineering;Control systems;Computer science;Computer Society;Project management;Software testing;System testing;Software engineering},
doi={10.1109/TSE.2003.1232285}}
``` |