Markus Borg

Software Engineering Researcher

Menu Skip to content
  • Home
  • Blog
  • Publications
  • Activities
  • Teaching
  • Software
  • PhD Thesis
  • CV
  • Swe-SE-SCI

Tag: traceability

Traceability has been discussed in software engineering since the start. Already at the pioneering NATO Working Conference on Software Engineering in 1968, Randall argued that a developed software system should “contain explicit traces of the design process”. The most commonly cited traceability definition is tailored for requirements: “the ability to describe and follow the life of a requirement, in both forwards and backwards direction” (Gotel and Finkelstein, 1994). I like the definition presented in the traceability book edited by Cleland-Huang et al. (2012) stating that traceability is “the potential for traces to be established and used” and a trace link is “an association forged between two trace artifacts” (e.g., dependency, refinement or conflict). During my PhD studies, a lot of my work was related to understanding and supporting traceability.

May 4, 2019May 23, 2019mrksbrg

Towards New Ways of Evaluating Methods of Supporting Requirements Management and Traceability Using Signal-to-Noise Ratio

November 5, 2018November 22, 2018mrksbrg

Goal-Oriented Mutation Testing with Focal Methods

May 22, 2017August 27, 2019mrksbrg

Software Engineers’ Information Seeking Behavior in Change Impact Analysis – An Interview Study

January 16, 2017July 13, 2018mrksbrg

Aligning Requirements and Testing: Working Together toward the Same Goal

October 24, 2016July 12, 2018mrksbrg

Supporting Change Impact Analysis Using a Recommendation System: An Industrial Case Study in a Safety-Critical Context

September 20, 2016July 12, 2018mrksbrg

Practitioners’ Perspectives on Change Impact Analysis for Safety-Critical Software – A Preliminary Analysis

May 3, 2016July 12, 2018mrksbrg

TuneR: A Framework for Tuning Software Engineering Tools with Hands-on Instructions in R

April 11, 2016July 12, 2018mrksbrg

An Industrial Survey of Safety Evidence Change Impact Analysis Practice

April 5, 2016July 13, 2018mrksbrg

A Multi-Case Study of Agile Requirements Engineering and the Use of Test Cases as Requirements

December 1, 2014July 12, 2018mrksbrg

Challenges and Practices in Aligning Requirements with Verification and Validation: A Case Study of Six Companies

Posts navigation

1 2 →

Recent Publications

  • Requirements on Technical Debt: Dare to Specify Them! February 20, 2023
  • Pipeline Infrastructure Required to Meet the Requirements on AI December 27, 2022
  • Can RE Help to Better Prepare Industrial AI for the Commercial Scale? October 30, 2022
  • topics
  • methods
  • venues
  • projects
agile architecture automotive computer vision digitalization information retrieval issue management machine learning meta open source performance public sector recommendation systems requirements engineering safety security simulators sports teaching testing traceability visualization
case study design science experience report experiment interviews literature review proof-of-concept statistical analysis survey
A-TEST AIRE AITest CESI CSEET CSMR DEVOPS DVCon EASE EMSE ENASE ESEM Euromicro GISE HÖGUTB ICSE ICST IEEE Software IoT4Emergency IST ITEQS JASE JSEP LUPed MALETS MaLTeSQuE MARCH NAWGFEST NODALIDA PROFES RET SASSUR SEAMS SEFAIAS SQJ SQUADE TEFSE TinyToCS ToG TSE XP
AIQ EASE. ORION PIMM SECONDS SMILE TESTOMAT

Categories

  • Book Chapters
  • Columns
  • Conference Papers
  • Journal Papers
  • Misc. Publications
  • Workshop Papers
My Tweets
Proudly powered by WordPress | Theme: Apostrophe by WordPress.com.