Using Developer-tool-Interactions to Expand Tracing Capabilities

Expanding current software traceability methodologies offers opportunities to significantly support development activities. State-of-the-art traceability frameworks use tracing data at specific points in time. This data includes information about development artefacts and their relations, which may be used for analysis, visualisation and similar purposes. In between those points in time, developers create, modify or delete requirements, diagrams, source code and other relevant artefacts. We propose to capture such artefact interactions in order to enrich the tracing data. By applying existing approaches in the field of developer-tool interaction analysis to the enriched data, we aim at supporting the developer’s work. In this paper, we present the overall approach, along with our development of a modular framework which may be used to capture the desired data from various tools, manage it and finally enable the execution of developer-interaction analyses.

[1]  Bernd Brügge,et al.  Monitoring user interactions for supporting failure reproduction , 2013, 2013 21st International Conference on Program Comprehension (ICPC).

[2]  Johannes Schneider,et al.  Mining Sequences of Developer Interactions in Visual Studio for Usage Smells , 2017, IEEE Transactions on Software Engineering.

[3]  Yang Li,et al.  Which Traceability Visualization Is Suitable in This Context? A Comparative Study , 2012, REFSQ.

[4]  Alexander Sahm,et al.  Assisting engineers in switching artifacts by using task semantic and interaction history , 2010, RSSE '10.

[5]  D. A. Meedeniya,et al.  Tool support for traceability management of software artefacts with DevOps practices , 2017, 2017 Moratuwa Engineering Research Conference (MERCon).

[6]  Mohsen Vakilian,et al.  A Practical Guide to Analyzing IDE Usage Data , 2015, The Art and Science of Analyzing Software Data.

[7]  Padma Iyenghar,et al.  A model-based framework encompassing a complete workflow from specification until validation of timing requirements in embedded software systems , 2016, Software Quality Journal.

[8]  Mohamed Yassine Haouam,et al.  Towards Automated Traceability Maintenance in Model Driven Engineering , 2016 .

[9]  Janice Singer,et al.  NavTracks: supporting navigation in software maintenance , 2005, 21st IEEE International Conference on Software Maintenance (ICSM'05).

[10]  Paul Grünbacher,et al.  Automating Software Traceability in Very Small Companies: A Case Study and Lessons Learne , 2006, 21st IEEE/ACM International Conference on Automated Software Engineering (ASE'06).

[11]  Julia Rubin,et al.  Model traceability , 2006, IBM Syst. J..

[12]  Manfred Broy,et al.  Seamless Model-Based Development: From Isolated Tools to Integrated Model Engineering Environments , 2010, Proceedings of the IEEE.

[13]  Nan Niu,et al.  Supporting requirements traceability through refactoring , 2013, 2013 21st IEEE International Requirements Engineering Conference (RE).

[14]  Nicolas Anquetil,et al.  A model-driven traceability framework for software product lines , 2010, Software & Systems Modeling.

[15]  Walid Maalej,et al.  Automatically detecting developer activities and problems in software development work , 2012, 2012 34th International Conference on Software Engineering (ICSE).

[16]  Olly Gotel,et al.  An analysis of the requirements traceability problem , 1994, Proceedings of IEEE International Conference on Requirements Engineering.

[17]  Richard N. Taylor,et al.  Software traceability with topic modeling , 2010, 2010 ACM/IEEE 32nd International Conference on Software Engineering.

[18]  Ståle Walderhaug,et al.  Towards a Generic Solution for Traceability in MDD , 2006 .

[19]  Scott R. Klemmer,et al.  What would other programmers do: suggesting solutions to error messages , 2010, CHI.

[20]  Indika Perera,et al.  Establishing traceability links among software artefacts , 2014, 2014 14th International Conference on Advances in ICT for Emerging Regions (ICTer).

[21]  Patrick Mäder,et al.  Software traceability: trends and future directions , 2014, FOSE.