TimeTracer: a tool for back in time traceability replaying (bibtex)
by Christoph Mayr-Dorn, Michael Vierhauser, Felix Keplinger, Stefan Bichler, Alexander Egyed
Abstract:
Ensuring correct trace links between different types of artifacts (requirements, architecture, or code) is crucial for compliance in safety-critical domains, for consistency checking, or change impact assessment. The point in time when trace links are created, however, (i.e., immediately during development or weeks/months later) has a significant impact on its quality. Assessing quality thus relies on obtaining a historical view on artifacts and their trace links at a certain point in the past which provides valuable insights on when, how, and by whom, trace links were created. This work presents TimeTracer, a tool that allows engineers to go back in time - not just to view the history of artifacts but also the history of trace links associated with these artifacts. TimeTracer allows easy integration with different development support tools such as Jira; and it stores artifacts, traces, and changes thereof in a unified artifact model.
Reference:
TimeTracer: a tool for back in time traceability replaying (Christoph Mayr-Dorn, Michael Vierhauser, Felix Keplinger, Stefan Bichler, Alexander Egyed), In ICSE '20: 42nd International Conference on Software Engineering, Companion Volume, Seoul, South Korea, 27 June - 19 July, 2020 (Gregg Rothermel, Doo-Hwan Bae, eds.), ACM, 2020.
Bibtex Entry:
@Conference{DBLP:conf/icse/Mayr-DornVKBE20,
  author    = {Christoph Mayr-Dorn and Michael Vierhauser and Felix Keplinger and Stefan Bichler and Alexander Egyed},
  booktitle = {{ICSE} '20: 42nd International Conference on Software Engineering, Companion Volume, Seoul, South Korea, 27 June - 19 July, 2020},
  title     = {TimeTracer: a tool for back in time traceability replaying},
  year      = {2020},
  editor    = {Gregg Rothermel and Doo{-}Hwan Bae},
  pages     = {33--36},
  publisher = {{ACM}},
  abstract  = {Ensuring correct trace links between different types of artifacts (requirements, architecture, or code) is crucial for compliance in safety-critical domains, for consistency checking, or change impact assessment. The point in time when trace links are created, however, (i.e., immediately during development or weeks/months later) has a significant impact on its quality. Assessing quality thus relies on obtaining a historical view on artifacts and their trace links at a certain point in the past which provides valuable insights on when, how, and by whom, trace links were created. This work presents TimeTracer, a tool that allows engineers to go back in time - not just to view the history of artifacts but also the history of trace links associated with these artifacts. TimeTracer allows easy integration with different development support tools such as Jira; and it stores artifacts, traces, and changes thereof in a unified artifact model.},
  bibsource = {dblp computer science bibliography, https://dblp.org},
  biburl    = {https://dblp.org/rec/conf/icse/Mayr-DornVKBE20.bib},
  doi       = {10.1145/3377812.3382141},
  file      = {:Conferences/ICSE TOOL 2020 - TimeTracer A Tool for Time Traceability Replaying/TimeTracer A Tool for Back in Time Traceability Replaying-preprint.pdf:PDF},
  keywords  = {FWF P29415, FWF J3998, Pro2Future, LIT Secure and Correct Systems Lab},
  timestamp = {Mon, 07 Dec 2020 00:00:00 +0100},
  url       = {https://doi.org/10.1145/3377812.3382141},
}
Powered by bibtexbrowser