[go: up one dir, main page]
More Web Proxy on the site http://driver.im/ skip to main content
10.1145/1984642.1984648acmconferencesArticle/Chapter ViewAbstractPublication PagesicseConference Proceedingsconference-collections
research-article

How do we trace requirements: an initial study of analyst behavior in trace validation tasks

Published: 21 May 2011 Publication History

Abstract

Traceability recovery is a tedious, error-prone, person-power intensive task, even if aided by automated traceability tools. Human analysts must vet candidate traceability links retrieved by such tools and must often go looking for links that such tools fail to locate as they build a traceability matrix. This paper examines a research version of the traceability tool REquirements TRacing On target (RETRO) that logs analyst actions. We examine the user logs in order to understand how analysts work on traceability recovery tasks. Such information is a pre-requisite to understanding how to better design traceability tools to best utilize analyst time while developing a high quality final traceability matrix.

References

[1]
Antoniol, G., Canfora, G., Casazza, G., De Lucia, A. and Merlo, E. 2002. Recovering traceability links between code and documentation. Software Engineering, IEEE Transactions on. 28, 10 (2002), 970--983.
[2]
Cleland-Huang, J., Chang, C.K., Sethi, G., Javvaji, K., Hu, H. and Xia, J. 2002. Automating Speculative Queries through Event-Based Requirements Traceability. Requirements Engineering, IEEE International Conference on (Los Alamitos, CA, USA, 2002), 289.
[3]
Cuddeback, D. Automated Requirements Traceability: the Study of Human Analysts. Ph.D. Thesis, Cal Poly, CA., 2010.
[4]
Cuddeback, D., Dekhtyar, A., Hayes, J. H., Holden, J. and Kong, W. New Ideas and Emerging Results Track: Towards Overcoming Human Analyst Fallibility in the Requirements Tracing Process. Accepted, ICSE 2011 NIER track.
[5]
Cuddeback, D., Dekhtyar, A. and Hayes, J. 2010. Automated Requirements Traceability: The Study of Human Analysts. Proceedings of the 2010 18th IEEE International Requirements Engineering Conference (Washington, DC, USA, 2010), 231--240.
[6]
Dekhtyar, A., Hayes, J. H. and Larsen, J. 2007. Make the Most of Your Time: How Should the Analyst Work with Automated Traceability Tools? Proceedings of the Third International Workshop on Predictor Models in Software Engineering (Washington, DC, USA, 2007), 4--.
[7]
Egyed, A., Graf, F. and Grunbacher, P. 2010. Effort and Quality of Recovering Requirements-to-Code Traces: Two Exploratory Experiments. Proceedings of the 2010 18th IEEE International Requirements Engineering Conference (Washington, DC, USA, 2010), 221--230.
[8]
Gotel, O. and Finkelstein, C. 1994. An analysis of the requirements traceability problem. (1994), 94--101.
[9]
Hayes, J. H. and Dekhtyar, A. 2005. Humans in the traceability loop: can't live with 'em, can't live without 'em. Proceedings of the 3rd international workshop on Traceability in emerging forms of software engineering (New York, NY, USA, 2005), 20--23.
[10]
Hayes, J. H., Dekhtyar, A. and Osborne, J. 2003. Improving Requirements Tracing via Information Retrieval. Proceedings of the 11th IEEE International Conference on Requirements Engineering (Washington, DC, USA, 2003), 138--.
[11]
Hayes, J. H., Dekhtyar, A. and Sundaram, S. 2005. Text mining for software engineering: how analyst feedback impacts final results. Proceedings of the 2005 international workshop on Mining software repositories (New York, NY, USA, 2005), 1--5.
[12]
Hayes, J. H., Dekhtyar, A. and Sundaram, S. K. 2006. Advancing Candidate Link Generation for Requirements Tracing: The Study of Methods. IEEE Trans. Softw. Eng. 32, 1 (2006), 4--19.
[13]
Hayes, J. H., Dekhtyar, A., Sundaram, S. K., Holbrook, E. A., Vadlamudi, S. and April, A. 2007. REquirements TRacing On target (RETRO): improving software maintenance through traceability recovery. ISSE. 3, 3 (2007), 193--202.
[14]
Marcus, A. and Maletic, J. I. 2003. Recovering Documentation-to-Source-Code Traceability Links using Latent Semantic Indexing. Software Engineering, International Conference on (Los Alamitos, CA, USA, 2003), 125.
[15]
Tichy, W. F. 2000. Hints for Reviewing Empirical Work in Software Engineering. Emp. Softw. Engg. 5, (Dec. 2000), 309--312.

Cited By

View all
  • (2021)On the effect of incompleteness to check requirement-to-method tracesProceedings of the 36th Annual ACM Symposium on Applied Computing10.1145/3412841.3442021(1465-1474)Online publication date: 22-Mar-2021
  • (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
  • (2021)What have we learnt from the challenges of (semi‐) automated requirements traceability? A discussion on blockchain applicabilityIET Software10.1049/sfw2.1203515:6(391-411)Online publication date: 4-Jul-2021
  • Show More Cited By

Index Terms

  1. How do we trace requirements: an initial study of analyst behavior in trace validation tasks

    Recommendations

    Comments

    Please enable JavaScript to view thecomments powered by Disqus.

    Information & Contributors

    Information

    Published In

    cover image ACM Conferences
    CHASE '11: Proceedings of the 4th International Workshop on Cooperative and Human Aspects of Software Engineering
    May 2011
    100 pages
    ISBN:9781450305761
    DOI:10.1145/1984642
    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

    Publisher

    Association for Computing Machinery

    New York, NY, United States

    Publication History

    Published: 21 May 2011

    Permissions

    Request permissions for this article.

    Check for updates

    Author Tags

    1. effort
    2. logging
    3. study of the analyst
    4. traceability

    Qualifiers

    • Research-article

    Conference

    ICSE11
    Sponsor:
    ICSE11: International Conference on Software Engineering
    May 21, 2011
    HI, Waikiki, Honolulu, USA

    Acceptance Rates

    CHASE '11 Paper Acceptance Rate 19 of 36 submissions, 53%;
    Overall Acceptance Rate 47 of 70 submissions, 67%

    Upcoming Conference

    ICSE 2025

    Contributors

    Other Metrics

    Bibliometrics & Citations

    Bibliometrics

    Article Metrics

    • Downloads (Last 12 months)8
    • Downloads (Last 6 weeks)0
    Reflects downloads up to 03 Jan 2025

    Other Metrics

    Citations

    Cited By

    View all
    • (2021)On the effect of incompleteness to check requirement-to-method tracesProceedings of the 36th Annual ACM Symposium on Applied Computing10.1145/3412841.3442021(1465-1474)Online publication date: 22-Mar-2021
    • (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
    • (2021)What have we learnt from the challenges of (semi‐) automated requirements traceability? A discussion on blockchain applicabilityIET Software10.1049/sfw2.1203515:6(391-411)Online publication date: 4-Jul-2021
    • (2021)Empirical evaluation of tools for hairy requirements engineering tasksEmpirical Software Engineering10.1007/s10664-021-09986-026:6Online publication date: 18-Aug-2021
    • (2019)Impact of Gamification on Trace Link Vetting: A Controlled ExperimentStructured Object-Oriented Formal Language and Method10.1007/978-3-030-15538-4_6(90-105)Online publication date: 8-Mar-2019
    • (2018)Vetting Automatically Generated Trace Links: What Information is Useful to Human Analysts?2018 IEEE 26th International Requirements Engineering Conference (RE)10.1109/RE.2018.00-52(52-63)Online publication date: Aug-2018
    • (2018)Adapting Word Embeddings to Traceability Recovery2018 International Conference on Information Systems and Computer Aided Education (ICISCAE)10.1109/ICISCAE.2018.8666883(255-261)Online publication date: Jul-2018
    • (2018)Second-Guessing in Tracing Tasks Considered Harmful?Requirements Engineering: Foundation for Software Quality10.1007/978-3-319-77243-1_6(92-98)Online publication date: 1-Mar-2018
    • (2017)Evaluation of Tools for Hairy Requirements and Software Engineering Tasks2017 IEEE 25th International Requirements Engineering Conference Workshops (REW)10.1109/REW.2017.25(284-291)Online publication date: Sep-2017
    • (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
    • Show More Cited By

    View Options

    Login options

    View options

    PDF

    View or Download as a PDF file.

    PDF

    eReader

    View online with eReader.

    eReader

    Media

    Figures

    Other

    Tables

    Share

    Share

    Share this Publication link

    Share on social media