SST'19 - Software and Systems Traceability: Summary of the 10th International Workshop at the 41st International Conference on Software Engineering (ICSE), May 27, 2019
Pages 43 - 47
Abstract
Traceability is the ability to relate di erent artifacts during the development and operation of a system to each other. It enables program comprehension, change impact analysis, and facilitates the cooperation of engineers from di erent disciplines. The 10th International Workshop on Software and Systems Traceability (former International Workshop on Traceability in Emerging Forms of Software Engineering, TEFSE), explored the role and impact of traceability in modern software and systems development. The event brought together researchers and practitioners to examine the challenges of recovering, maintaining, and utilizing traceability for the myriad forms of software and systems engineering artifacts. SST'19 was a highly interactive working event focused on discussing the main problems related to software traceability in particular in the context of opportunities and challenges posed by the recent progress in Arti cial Intelligence techniques and proposing possible solutions for such problems.
References
[1]
[Alshakhouri et al. 2018] Mujtaba Alshakhouri, Jim Buchan, and Stephen G MacDonell. 2018. Synchronised visualisation of software process and product artefacts: Concept, design and prototype implementation. Information and Software Technology 98 (2018), 131{145.
[2]
[Alshakhouri et al. 2019] Mujtaba Alshakhouri, Jim Buchan, and Stephen G. MacDonell. 2019. Synchronised visualisation of software process and product artefacts: concept, design and prototype implementation. In SST@ICSE. IEEE / ACM, 2.
[3]
[Borg et al. 2014] Markus Borg, Per Runeson, and Anders Ardo. 2014. Recovering from a decade: a systematic mapping of information retrieval approaches to software traceability. Empirical Software Engineering (ESE) 19, 6 (2014), 1565{1616.
[4]
[Csuvik et al. 2019] Viktor Csuvik, Andr as Kicsi, and L aszl o Vid acs. 2019. Source code level word embeddings in aiding semantic test-to-code traceability. In SST@ICSE. IEEE / ACM, 29{36.
[5]
[Cuddeback et al. 2010] David Cuddeback, Alex Dekhtyar, and Jane Hayes. 2010. Automated requirements traceability: The study of human analysts. In 18th IEEE Int. Requirements Engineering Conf. (RE' 10). IEEE, 231{240.
[6]
[Farrar and Hayes 2019] David Farrar and Jane Hu man Hayes. 2019. A comparison of stemming techniques in tracing. In SST@ICSE. IEEE / ACM, 37{44.
[7]
[Gayer et al. 2016] Sebastian Gayer, Andrea Herrmann, Thorsten Keuler, Matthias Riebisch, and Pablo Oliveira Antonino. 2016. Lightweight traceability for the agile architect. Computer 49, 5 (2016), 64{71.
[8]
Ghaisas 2019] Smita Ghaisas. 2019. Traceability for a knowledge-driven software engineering. In SST@ICSE. IEEE / ACM, 1.
[9]
[Guo et al. 2017] Jin Guo, Jinghui Cheng, and Jane Cleland-Huang. 2017. Semantically enhanced software traceability using deep learning techniques. In Proceedings of the 39th International Conference on Software Engineering, ICSE 2017, Buenos Aires, Argentina, May 20--28, 2017. 3{14. https://doi.org/10.1109/ICSE.2017.9
[10]
[Hajri et al. 2018] Ines Hajri, Arda Goknil, Lionel C Briand, and Thierry Stephany. 2018. Change impact analysis for evolving con guration decisions in product line use case models. Journal of Systems and Software 139 (2018), 211{237.
[11]
[Hajri et al. 2019] Ines Hajri, Arda Goknil, Lionel C. Briand, and Thierry Stephany. 2019. Change impact analysis for evolving con guration decisions in product line use case models. In SST@ICSE. IEEE / ACM, 11.
[12]
[Khatwani et al. 2017] Charu Khatwani, Xiaoyu Jin, Nan Niu, Amy Kosho er, Linda Newman, and Juha Savolainen. 2017. Advancing viewpoint merging in requirements engineering: a theoretical replication and explanatory study. Requir. Eng. 22, 3 (2017), 317{338.
[13]
[Maro et al. 2018a] Salome Maro, Jan-Philipp Steghofer, and Miroslaw Staron. 2018a. Software traceability in the automotive domain: Challenges and solutions. Journal of Systems and Software 141 (2018), 85{110. https://doi.org/10.1016/j.jss.2018.03.060
[14]
[Maro et al. 2018b] Salome Maro, Jan-Philipp Steghofer, Jane Hu man Hayes, Jane Cleland-Huang, and Miroslaw Staron. 2018b. Vetting Automatically Generated Traceability Links: What Information is Useful to Human Analysts?. In RE'18. IEEE.
[15]
[Niu et al. 2013] Nan Niu, Anas Mahmoud, Zhangji Chen, and Gary Bradshaw. 2013. Departures from Optimality: Understanding Human Analyst's Information Foraging in Assisted Requirements Tracing. In 2013 Int. Conf. on Software Engineering (ICSE '13) (ICSE '13). IEEE, 572{581.
[16]
[Payne and Hayes 2019] Jared Payne and Jane Hu man Hayes. 2019. University of kentucky tracelab component similarity matrix voting merge. In SST@ICSE. IEEE / ACM, 17{20.
[17]
[Rahimi and Cleland-Huang 2018] Mona Rahimi and Jane Cleland-Huang. 2018. Evolving software trace links between requirements and source code. Empirical Software Engineering 23, 4 (2018), 2198{2231.
[18]
[Rahimi and Cleland-Huang 2019] Mona Rahimi and Jane Cleland-Huang. 2019. Evolving software trace links between requirements and source code. In SST@ICSE. IEEE / ACM, 12.
[19]
[Rath et al. 2018] Michael Rath, Jacob Rendall, Jin L. C. Guo, Jane Cleland-Huang, and Patrick Mader. 2018. Traceability in the wild: automatically augmenting incomplete trace links. In Proceedings of the 40th International Conference on Software Engineering, ICSE 2018, Gothenburg, Sweden, May 27 - June 03, 2018. 834{845. https://doi.org/10.1145/3180155.3180207
[20]
[Seiler et al. 2019] Marcus Seiler, Paul Hubner, and Barbara Paech. 2019. Comparing traceability through information retrieval, commits, interaction logs, and tags. In SST@ICSE. IEEE / ACM, 21{28.
[21]
[Tinnes et al. 2019] Christof Tinnes, Andreas Biesdorf, Uwe Hohenstein, and Florian Matthes. 2019. Ideas on improving software artifact reuse via traceability and self-awareness. In SST@ICSE. IEEE / ACM, 13{16.
[22]
[Vierhauser et al. 2019] Michael Vierhauser, Jane Cleland-Huang, Janet E. Burge, and Paul Grunbacher. 2019. The interplay of design and runtime traceability for non-functional requirements. In SST@ICSE. IEEE / ACM, 3{10.
[23]
[Wang et al. 2019] Wentao Wang, Nan Niu, Mounifah Alenazi, and Li Da Xu. 2019. In-Place Traceability for Automated Production Systems: A Survey of PLC and SysML Tools. IEEE Trans. Industrial Informatics 15, 6 (2019), 3155{3162.
[24]
[Wang et al. 2018] Wentao Wang, Nan Niu, Hui Liu, and Zhendong Niu. 2018. Enhancing Automated Requirements Traceability by Resolving Polysemy. In 26th IEEE International Requirements Engineering Conference, RE. 40{51.
[25]
[Wettel et al. 2011] R. Wettel, M. Lanza, and R. Robbes. 2011. Software systems as cities: a controlled experiment. In 33rd International Conference on Software Engineering (ICSE). 551{560. https://doi.org/10.1145/1985793.1985868
[26]
[Wohlrab et al. 2016] Rebekka Wohlrab, Jan-Philipp Steghofer, Eric Knauss, Salome Maro, and Anthony Anjorin. 2016. Collaborative Traceability Management: Challenges and Opportunities. In 24th IEEE International Requirements Engineering Conference, RE. 216{225.
Recommendations
Using scenarios to support traceability
TEFSE '05: Proceedings of the 3rd international workshop on Traceability in emerging forms of software engineeringSoftware traceability is a recognized challenge in software development that can be ameliorated with requirements management tools. Traceability information can be used in a number of different software engineering activities such as software change ...
Traceability im Usability-Engineering: Integration von Usability Engineering und Software Engineering mittels eines Traceability-Tools
MuC '19: Proceedings of Mensch und Computer 2019Usability-Aktivitäten in den Software Entwicklungsprozess zu in-tegrieren ist oftmals problematisch. Zeitliche Abläufe müssen ko-ordiniert, Kollegen müssen überzeugt und es muss an fehlende Arbeitsschritte erinnert werden. Traceability bietet eine ...
Maintainability-Based Requirements Prioritization by Using Artifacts Traceability and Code Metrics
CSMR '13: Proceedings of the 2013 17th European Conference on Software Maintenance and ReengineeringRequirements prioritization is a fundamental activity during software system maintenance. Prioritize requirements, in fact, means to determine the ordering in which requirements have to be considered in a given planning or maintenance activity. Most of ...
Comments
Information & Contributors
Information
Published In
July 2019
100 pages
ISSN:0163-5948
DOI:10.1145/3356773
- Editors:
- John Georgas,
- Dietmar Pfahl,
- Will Tracz
Copyright © 2019 Copyright is held by the owner/author(s).
Permission to make digital or hard copies of part or all of this work for personal or classroom use is granted without fee provided that copies are not made or distributed for profit or commercial advantage and that copies bear this notice and the full citation on the first page. Copyrights for third-party components of this work must be honored. For all other uses, contact the Owner/Author.
Publisher
Association for Computing Machinery
New York, NY, United States
Publication History
Published: 14 November 2019
Published in SIGSOFT Volume 44, Issue 3
Check for updates
Author Tags
Qualifiers
- Research-article
Contributors
Other Metrics
Bibliometrics & Citations
Bibliometrics
Article Metrics
- 0Total Citations
- 110Total Downloads
- Downloads (Last 12 months)4
- Downloads (Last 6 weeks)0
Reflects downloads up to 28 Jan 2025
Other Metrics
Citations
View Options
Login options
Check if you have access through your login credentials or your institution to get full access on this article.
Sign in