Datasets from Fifteen Years of Automated Requirements Traceability Research: Current State, Characteristics, and Quality

Zogaan, Waleed; Sharma, Palak; Mirahkorli, Mehdi; Arnaoudova, Venera

doi:10.1109/re.2017.80

Cited by 15 publications

(7 citation statements)

References 85 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…This finding is consistent with that only 39% of companies used recognized requirements management tools [40]. Consequently, there is a lack of datasets; our findings are consistent with previous work of Zogaan et al [33]. However, many state-of-the-art studies on modeling and assessment still lack more tools than knowledge-oriented models.…”

Section: ) Requirements Qualitysupporting

confidence: 92%

“…One major issue is the lack of open-source tools and benchmark datasets, as shown in Appendix B and consistent with Zogaan et al [61]. The research community should increase efforts to develop more tools and share more datasets.…”

Section: ) Lack Of Tools and Datasetsmentioning

confidence: 62%

“…The current work builds upon previous work of Besrour et al [32], which identifies critical challenges in Software Engineering (1995-2016); Moketar et al [27], which shows trends in tools of requirements validation (2007)(2008)(2009)(2010)(2011)(2012)(2013)(2014)(2015)(2016); and Zogaan et al [33], which discusses datasets of software requirements. Hence, the search strings for screening studies were limited for studies from January 2016 to December 2020.…”

Section: ) Search Protocolmentioning

confidence: 65%

See 2 more Smart Citations

Challenges of Software Requirements Quality Assurance and Validation: A Systematic Literature Review

Atoum¹,

Baklizi

Alsmadi

et al. 2021

IEEE Access

View full text Add to dashboard Cite

show abstract

Section: ) Requirements Qualitysupporting

confidence: 92%

Section: ) Lack Of Tools and Datasetsmentioning

confidence: 62%

Section: ) Search Protocolmentioning

confidence: 65%

See 1 more Smart Citation

Challenges of Software Requirements Quality Assurance and Validation: A Systematic Literature Review

Atoum¹,

Baklizi

Alsmadi

et al. 2021

IEEE Access

View full text Add to dashboard Cite

show abstract

“…In the field of Requirements Engineering, Zogaan et al (2017) conducted a systematic literature review on 73 data sets used for software traceability over a fifteen-year period, between 2000-2016. Using both manual and automated methods they selected studies that have used data sets, case studies, or empirical data, to develop, validate, train, or test traceability techniques.…”

Section: Related Workmentioning

confidence: 99%

Standing on shoulders or feet? An extended study on the usage of the MSR data papers

et al. 2020

View full text Add to dashboard Cite

The establishment of the Mining Software Repositories (MSR) data showcase conference track has encouraged researchers to provide data sets as a basis for further empirical studies. Objective: Examine the usage of data papers published in the MSR proceedings in terms of use frequency, users, and use purpose. Method: Data track papers were collected from the MSR data showcase track and through the manual inspection of older MSR proceedings. The use of data papers was established through manual citation searching followed by reading the citing studies and dividing them into strong and weak citations. Contrary to weak, strong citations truly use the data set of a data paper. Data papers were then manually clustered based on their content, whereas their strong citations were classified by hand according to the knowledge areas of the Guide to the Software Engineering Body of Knowledge. A survey study on 108 authors and users of data papers provided further insights regarding motivation and effort in data paper production, encouraging and discouraging factors in data set use, and future desired direction regarding data papers. Results: We found that 65% of the data papers have been used in other studies, with a longtail distribution in the number of strong citations. Weak citations to data papers usually refer to them as an example. MSR data papers are cited in total less than other MSR papers. A considerable number of the strong citations stem from the teams that authored the data papers. Publications providing Version Control System (VCS) primary and derived data are the most frequent data papers and the most often strongly cited ones. Enhanced developer data papers are the least common ones, and the second least frequently strongly cited. Data paper authors tend to gather data in the context of other research. Users of data sets appreciate high data quality and are discouraged by lack of replicability of data set construction. Data related to machine learning or derived from the manufacturing sector are two suggestions of the respondents for future data papers. Conclusions: Data papers have provided the foundation for a significant number of studies,

show abstract

“…Zogaan et al [113] summarize possible threats to validity for datasets used for traceability studies, covering different aspects of internal validity, external validity, and reliability [105]:…”

Section: Threats To Validitymentioning

confidence: 99%

Requirements document relations

2022

View full text Add to dashboard Cite

Relations between requirements are part of nearly every requirements engineering approach. Yet, relations of views, such as requirements documents, are scarcely considered. This is remarkable as requirements documents and their structure are a key factor in requirements reuse, which is still challenging. Explicit formalized relations between documents can help to ensure consistency, improve completeness, and facilitate review activities in general. For example, this is relevant in space engineering, where many challenges related to complex document dependencies occur: 1. Several contractors contribute to a project. 2. Requirements from standards have to be applied in several projects. 3. Requirements from previous phases have to be reused. We exploit the concept of “layered traceability”, explicitly considering documents as views on sets of individual requirements and specific traceability relations on and between all of these representation layers. Different types of relations and their dependencies are investigated with a special focus on requirement reuse through standards and formalized in an Object-Role Modelling (ORM) conceptual model. Automated analyses of requirement graphs based on this model are able to reveal document inconsistencies. We show examples of such queries in Neo4J/Cypher for the EagleEye case study. This work aims to be a step toward a better support to handle highly complex requirement document dependencies in large projects with a special focus on requirements reuse and to enable automated quality checks on dependent documents to facilitate requirements reviews.

show abstract

Datasets from Fifteen Years of Automated Requirements Traceability Research: Current State, Characteristics, and Quality

Cited by 15 publications

References 85 publications

Challenges of Software Requirements Quality Assurance and Validation: A Systematic Literature Review

Challenges of Software Requirements Quality Assurance and Validation: A Systematic Literature Review

Standing on shoulders or feet? An extended study on the usage of the MSR data papers

Requirements document relations

Contact Info

Product

Resources

About