Article

Code patterns for automatically validating requirements-to-code traces

Authors:

Alexander EgyedAuthors Info & Claims

ASE '12: Proceedings of the 27th IEEE/ACM International Conference on Automated Software Engineering

Pages 200 - 209

https://doi.org/10.1145/2351676.2351705

Published: 03 September 2012 Publication History

Abstract

Traces between requirements and code reveal where requirements are implemented. Such traces are essential for code understanding and change management. Unfortunately, traces are known to be error prone. This paper introduces a novel approach for validating requirements-to-code traces through calling relationships within the code. As input, the approach requires an executable system, the corresponding requirements, and the requirements-to-code traces that need validating. As output, the approach identifies likely incorrect or missing traces by investigating patterns of traces with calling relationships. The empirical evaluation of four case study systems covering 150 KLOC and 59 requirements demonstrates that the approach detects most errors with 85-95% precision and 82-96% recall and is able to handle traces of varying levels of correctness and completeness. The approach is fully automated, tool supported, and scalable.

References

[1]

N. Aizenbud-Reshef, B. T. Nolan, J. Rubin, and Y. Shaham-Gafni. Model traceability. IBM Systems Journal, 45(3):515–526, 2006.

Digital Library

[2]

G. Antoniol, G. Canfora, G. Casazza, A. De Lucia, and E. Merlo. Recovering traceability links between code and documentation. IEEE Transactions on Software Engineering, 28(10):970–983, Oct. 2002.

Digital Library

[3]

L. C. Briand, Y. Labiche, and T. Yue. Automated traceability analysis for UML model reﬁnements. Inf. Softw. Technol., 51(2):512–527, Feb. 2009.

Digital Library

[4]

K. Chen and V. Rajlich. Case study of feature location using dependence graph, after 10 years. In 18th IEEE International Conference on Program Comprehension, pages 1–3, Braga, Portugal, June 2010.

Digital Library

[5]

J. Cleland-Huang, B. Berenbach, S. Clark, R. Settimi, and E. Romanova. Best practices for automated traceability. Computer, vol. 40:27–35, 2007.

Digital Library

[6]

B. Dit, M. Revelle, M. Gethers, and D. Poshyvanyk. Feature location in source code: A taxonomy and survey. Journal of Software Maintenance and Evolution: Research and Practice (JSME), accepted for publication, 2011.

[7]

M. Eaddy, A. V. Aho, G. Antoniol, and Y. Guéhéneuc. CERBERUS: tracing requirements to source code using information retrieval, dynamic analysis, and program analysis. In 16th IEEE International Conference on Program Comprehension, pages 53–62, Amsterdam, The Netherlands, June 2008.

Digital Library

[8]

A. Egyed, F. Graf, and P. Grunbacher. Eﬀort and quality of recovering Requirements-to-Code traces: Two exploratory experiments. In 18th IEEE International Requirements Engineering Conference, pages 221–230, Sydney, Australia, Sept. 2010.

Digital Library

[9]

A. Ghabi and A. Egyed. Observations on the connectedness between requirements-to-code traces and calling relationships for trace validation. In 26th IEEE/ACM Internation Conference on Automated Software Engineering, 2011.

Digital Library

[10]

O. Gotel and C. Finkelstein. An analysis of the requirements traceability problem. In Proceedings of IEEE International Conference on Requirements Engineering, pages 94–101, Colorado Springs, CO, USA, Apr. 1994.

[11]

J. Hayes, A. Dekhtyar, and S. Sundaram. Advancing candidate link generation for requirements tracing: the study of methods. IEEE Transactions on Software Engineering, 32(1):4–19, Jan. 2006.

Digital Library

[12]

M. Jiang, M. Groble, S. Simmons, D. Edwards, and N. Wilde. Software feature understanding in an industrial setting. In 22nd IEEE ICSM, pages 66–67, Philadelphia, PA, USA, Sept. 2006.

Digital Library

[13]

W. Kong, J. Hayes, A. Dekhtyar, and J. Holden. How do we trace requirements? an initial study of analyst behavior in trace validation tasks. In Fourth International Workshop on Cooperative and Human Aspects of Software Engineering, May 2011.

Digital Library

[14]

A. Marcus and J. I. Maletic. Recovering documentation-to-source-code traceability links using latent semantic indexing. In Proceedings of the 25th ICSE, ICSE ’03, pages 125–135, Washington, DC, USA, 2003. IEEE Computer Society.

Digital Library

[15]

M. Marin, A. V. Deursen, and L. Moonen. Identifying crosscutting concerns using Fan-In analysis. ACM Transactions on Software Engineering and Methodology, 17(1):1–37, Dec. 2007.

Digital Library

[16]

C. McMillan, D. Poshyvanyk, and M. Revelle. Combining textual and structural analysis of software artifacts for traceability link recovery. In ICSE Workshop on Traceability in Emerging Forms of Software Engineering, pages 41–48, Vancouver, BC, Canada, May 2009.

Digital Library

[17]

P. Mäder and A. Egyed. Do software engineers beneﬁt from source code navigation with traceability? – an experiment in software change management. In 26th International Conference on Automated Software Engeering, Kansas, November 2011. IEEE/ACM.

Digital Library

[18]

R. E. K. S. Min Deng and B. H. C. Cheng. Retrieval by construction: A traceability technique to support veriﬁcation and validation of uml formalizations. International Journal of Software Engineering and Knowledge Engineering (IJSEKE), 15:837–872, 2005.

[19]

D. L. Parnas. Software aging. In Proceedings of the 16th international conference on Software engineering, ICSE ’94, pages 279–287, Los Alamitos, CA, USA, 1994. IEEE Computer Society Press.

Digital Library

[20]

D. Poshyvanyk and A. Marcus. Using traceability links to assess and maintain the quality of software documentation. In TEFSE’07, pages 27–30, 2007.

[21]

B. Ramesh, L. C. Stubbs, and M. Edwards. Lessons learned from implementing requirements traceability. Crosstalk – Journal of Defense Software Engineering, 8:11–15, 1995.

[22]

M. Robillard, W. Coelho, and G. Murphy. How eﬀective developers investigate source code: an exploratory study. IEEE Transactions on Software Engineering, 30(12):889–903, Dec. 2004.

Digital Library

[23]

M. P. Robillard and G. C. Murphy. Concern graphs: ﬁnding and describing concerns using structural program dependencies. In Proceedings of the 24th ICSE, page 406, Orlando, Florida, 2002.

Digital Library

[24]

P. Tonella. Using a concept lattice of decomposition slices for program understanding and impact analysis. IEEE Transactions on Software Engineering, 29(6):495–509, June 2003.

Digital Library

Cited By

Raţiu CMayr-Dorn CAssunção WEgyed A(2023)Taming Cross-Tool Traceability in the Wild2023 IEEE 31st International Requirements Engineering Conference (RE)10.1109/RE57278.2023.00031(233-243)Online publication date: Sep-2023
https://doi.org/10.1109/RE57278.2023.00031
Chang ZLi MWang QLi SWang J(2023)Cross-Domain Requirements Linking via Adversarial-based Domain Adaptation2023 IEEE/ACM 45th International Conference on Software Engineering (ICSE)10.1109/ICSE48619.2023.00138(1596-1608)Online publication date: May-2023
https://doi.org/10.1109/ICSE48619.2023.00138
Hammoudi MMayr-Dorn CMashkoor AEgyed A(2021)A Traceability Dataset for Open Source Systems2021 IEEE/ACM 18th International Conference on Mining Software Repositories (MSR)10.1109/MSR52588.2021.00073(555-559)Online publication date: May-2021
https://doi.org/10.1109/MSR52588.2021.00073
Show More Cited By

Index Terms

Code patterns for automatically validating requirements-to-code traces

Recommendations

Maintainability-Based Requirements Prioritization by Using Artifacts Traceability and Code Metrics
CSMR '13: Proceedings of the 2013 17th European Conference on Software Maintenance and Reengineering

Requirements 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 ...
Requirements Traceability for Object Oriented Systems by Partitioning Source Code
WCRE '11: Proceedings of the 2011 18th Working Conference on Reverse Engineering

Requirements trace ability ensures that source code is consistent with documentation and that all requirements have been implemented. During software evolution, features are added, removed, or modified, the code drifts away from its original ...
Interaction-based creation and maintenance of continuously usable trace links between requirements and source code
Abstract
Trace links between requirements and code are beneficial for many software engineering tasks such as maintenance, program comprehension, and re-engineering. If trace links are created and used continuously during a project, they need to have high ...

Comments

Information & Contributors

Information

Published In

cover image ACM Conferences

ASE '12: Proceedings of the 27th IEEE/ACM International Conference on Automated Software Engineering

September 2012

409 pages

ISBN:9781450312042

DOI:10.1145/2351676

General Chair:
Michael Goedicke,
Program Chairs:
Tim Menzies,
Motoshi Saeki

Copyright © 2012 ACM.

Permission to make digital or hard copies of all or part 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 components of this work owned by others than ACM must be honored. Abstracting with credit is permitted. To copy otherwise, or republish, to post on servers or to redistribute to lists, requires prior specific permission and/or a fee. Request permissions from [email protected]

Sponsors

SIGSOFT: ACM Special Interest Group on Software Engineering

In-Cooperation

SIGAI: ACM Special Interest Group on Artificial Intelligence
Universität Duisburg Essen: Universität Duisburg Essen
TCSE: IEEE Computer Society's Tech. Council on Software Engin.

Publisher

Association for Computing Machinery

New York, NY, United States

Publication History

Published: 03 September 2012

Permissions

Request permissions for this article.

Request Permissions

Check for updates

Author Tags

Qualifiers

Article

Conference

ASE'12

Sponsor:

SIGSOFT

ASE'12: IEEE/ACM International Conference on Automated Software Engineering

September 3 - 7, 2012

Essen, Germany

Acceptance Rates

Overall Acceptance Rate 82 of 337 submissions, 24%

Upcoming Conference

Contributors

Other Metrics

View Article Metrics

Bibliometrics & Citations

Bibliometrics

Article Metrics

19
Total Citations
View Citations
374
Total Downloads

Downloads (Last 12 months)4
Downloads (Last 6 weeks)0

Reflects downloads up to 15 Sep 2024

Other Metrics

View Author Metrics

Citations

Cited By

Raţiu CMayr-Dorn CAssunção WEgyed A(2023)Taming Cross-Tool Traceability in the Wild2023 IEEE 31st International Requirements Engineering Conference (RE)10.1109/RE57278.2023.00031(233-243)Online publication date: Sep-2023
https://doi.org/10.1109/RE57278.2023.00031
Chang ZLi MWang QLi SWang J(2023)Cross-Domain Requirements Linking via Adversarial-based Domain Adaptation2023 IEEE/ACM 45th International Conference on Software Engineering (ICSE)10.1109/ICSE48619.2023.00138(1596-1608)Online publication date: May-2023
https://doi.org/10.1109/ICSE48619.2023.00138
Hammoudi MMayr-Dorn CMashkoor AEgyed A(2021)A Traceability Dataset for Open Source Systems2021 IEEE/ACM 18th International Conference on Mining Software Repositories (MSR)10.1109/MSR52588.2021.00073(555-559)Online publication date: May-2021
https://doi.org/10.1109/MSR52588.2021.00073
Hammoudi MMayr-Dorn CMashkoor AEgyed A(2021)TraceRefiner: An Automated Technique for Refining Coarse-Grained Requirement-to-Class Traces2021 28th Asia-Pacific Software Engineering Conference (APSEC)10.1109/APSEC53868.2021.00009(12-21)Online publication date: Dec-2021
https://doi.org/10.1109/APSEC53868.2021.00009
Hübner PPaech B(2020)Interaction-based creation and maintenance of continuously usable trace links between requirements and source codeEmpirical Software Engineering10.1007/s10664-020-09831-w25:5(4350-4377)Online publication date: 1-Sep-2020
https://dl.acm.org/doi/10.1007/s10664-020-09831-w
TSUCHIYA RNISHIKAWA KWASHIZAKI HFUKAZAWA YSHINOHARA YOSHIMA KMIBE R(2019)Recovering Transitive Traceability Links among Various Software Artifacts for DevelopersIEICE Transactions on Information and Systems10.1587/transinf.2018EDP7331E102.D:9(1750-1760)Online publication date: 1-Sep-2019
https://doi.org/10.1587/transinf.2018EDP7331
Ashraf UMayr-Dorn CEgyed A(2019)Mining Cross-Task Artifact Dependencies from Developer Interactions2019 IEEE 26th International Conference on Software Analysis, Evolution and Reengineering (SANER)10.1109/SANER.2019.8667990(186-196)Online publication date: Feb-2019
https://doi.org/10.1109/SANER.2019.8667990
Mou LJin ZMou LJin Z(2018)TBCNN for Programs’ Abstract Syntax TreesTree-Based Convolutional Neural Networks10.1007/978-981-13-1870-2_4(41-57)Online publication date: 2-Oct-2018
https://doi.org/10.1007/978-981-13-1870-2_4
Kuang HNie JHu HRempel PLu JEgyed AMader P(2017)Analyzing closeness of code dependencies for improving IR-based Traceability Recovery2017 IEEE 24th International Conference on Software Analysis, Evolution and Reengineering (SANER)10.1109/SANER.2017.7884610(68-78)Online publication date: Feb-2017
https://doi.org/10.1109/SANER.2017.7884610
Zogaan WSharma PMirahkorli MArnaoudova V(2017)Datasets from Fifteen Years of Automated Requirements Traceability Research: Current State, Characteristics, and Quality2017 IEEE 25th International Requirements Engineering Conference (RE)10.1109/RE.2017.80(110-121)Online publication date: Sep-2017
https://doi.org/10.1109/RE.2017.80
Show More Cited By

View Options

Get Access

Login options

Check if you have access through your login credentials or your institution to get full access on this article.

Full Access

Get this Publication

View options

PDF

View or Download as a PDF file.

eReader

View online with eReader.

Media

Figures

Other

Tables

View Table of Contents