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.
Goal-Oriented Mutation Testing with Focal Methods
Software Engineers’ Information Seeking Behavior in Change Impact Analysis – An Interview Study
Aligning Requirements and Testing: Working Together toward the Same Goal
Supporting Change Impact Analysis Using a Recommendation System: An Industrial Case Study in a Safety-Critical Context
Practitioners’ Perspectives on Change Impact Analysis for Safety-Critical Software – A Preliminary Analysis
TuneR: A Framework for Tuning Software Engineering Tools with Hands-on Instructions in R
An Industrial Survey of Safety Evidence Change Impact Analysis Practice
A Multi-Case Study of Agile Requirements Engineering and the Use of Test Cases as Requirements
