Wei-Keat Kong
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.
- 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. Google Scholar
Digital Library
- 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. Google ScholarDigital Library
- Cuddeback, D. Automated Requirements Traceability: the Study of Human Analysts. Ph.D. Thesis, Cal Poly, CA., 2010.Google Scholar
- 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. Google ScholarDigital Library
- 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. Google ScholarDigital Library
- 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--. Google ScholarDigital Library
- 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. Google ScholarDigital Library
- Gotel, O. and Finkelstein, C. 1994. An analysis of the requirements traceability problem. (1994), 94--101.Google Scholar
- 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. Google ScholarDigital Library
- 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--. Google ScholarDigital Library
- 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. Google ScholarDigital Library
- 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. Google ScholarDigital Library
- 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.Google Scholar
- 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. Google ScholarDigital Library
- Tichy, W. F. 2000. Hints for Reviewing Empirical Work in Software Engineering. Emp. Softw. Engg. 5, (Dec. 2000), 309--312. Google ScholarDigital Library
Index Terms
- How do we trace requirements: an initial study of analyst behavior in trace validation tasks
Recommendations
Toward improved traceability of non-functional requirements
TEFSE '05: Proceedings of the 3rd international workshop on Traceability in emerging forms of software engineeringThis position paper examines current practices and challenges for tracing non-functional requirements (NFRs). Anecdotal evidence suggests that many organizations do not effectively trace NFRs and that functional changes are often implemented with very ...
Toward Reference Models for Requirements Traceability
Requirements traceability is intended to ensure continued alignment between stakeholder requirements and various outputs of the system development process. To be useful, traces must be organized according to some modeling framework. Indeed, several such ...
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