Mind the gap: assessing the conformance of software traceability to relevant guidelines

@article{Rempel2014MindTG,
  title={Mind the gap: assessing the conformance of software traceability to relevant guidelines},
  author={Patrick Rempel and Patrick M{\"a}der and Tobias Kuschke and Jane Cleland-Huang},
  journal={Proceedings of the 36th International Conference on Software Engineering},
  year={2014}
}
Many guidelines for safety-critical industries such as aeronautics, medical devices, and railway communications, specify that traceability must be used to demonstrate that a rigorous process has been followed and to provide evidence that the system is safe for use. In practice, there is a gap between what is prescribed by guidelines and what is implemented in practice, making it difficult for organizations and certifiers to fully evaluate the safety of the software system. In this paper we… 

Figures and Tables from this paper

Traceability Gap Analysis for Assessing the Conformance of Software Traceability to Relevant Guidelines

TLDR
This work proposes formalisms, metrics, and tool support for evaluating traceability coverage with respect to a project’s relevant guidelines in order to identify areas of traceability failure, and facilitates the identification of such problems for an initial certification and continuously throughout the software development lifecycle.

A quality model for the systematic assessment of requirements traceability

TLDR
A quality model is derived that specifies per element the acceptable state (traceability Gate) and unacceptable deviations (Traceability Problem) from this state and formally defines how both, the acceptable states and the unacceptable deviations can be detected in order to enable practitioners to systematically assess their project's traceability.

Supporting the Systematic Assessment of Requirements Traceability-A Quality Model

TLDR
A quality model is derived that specifies per element the acceptable state (Traceability Gate) and unacceptable deviations from this state and formally defines how both, the acceptable states and the unacceptable deviations can be detected in order to enable practitioners to systematically assess their project’s traceability.

Software traceability: trends and future directions

TLDR
This paper builds upon a prior body of work to highlight the state-of-the-art in software traceability, and to present compelling areas of research that need to be addressed.

Detecting safety‐related components in statecharts through traceability and model slicing

TLDR
This paper proposes a technique based on statecharts, which is used to model the behavior of software, and fault tree safety analysis, to build a metamodel of traceability between fault trees and state charts to bridge their traceability gap.

Model-based specification of safety compliance needs for critical systems: A holistic generic metamodel

Supporting Quality Assurance with Automated Process-Centric Quality Constraints Checking

TLDR
Results show that trace links are often corrected or completed after the fact and thus timely and automated constraint checking support has significant potential on reducing rework.

Trace Link Evolution across Multiple Software Versions in Safety-Critical Systems

  • Mona Rahimi
  • Computer Science
    2016 IEEE/ACM 38th International Conference on Software Engineering Companion (ICSE-C)
  • 2016
TLDR
The goal of this dissertation is to deliver an accurate, Scalable, and practical approach for supporting trace linkevolution across a diverse set of software artifacts including requirements, source code and safety cases.

Preventing Defects: The Impact of Requirements Traceability Completeness on Software Quality

TLDR
The strong impact of traceability completeness on the defect rate suggests that traceability is of great practical value for any kind of software development project, even if it is not mandated by a standard or regulation.

Introducing Traceability Information Models in Connected Health Projects

TLDR
The main contribution of this paper is to present an approach for the connected health industry to start dealing with traceability challenges, and show that considerable advantages can be obtained by introducing a TIM into the modeling process.
...

References

SHOWING 1-10 OF 62 REFERENCES

A quality model for the systematic assessment of requirements traceability

TLDR
A quality model is derived that specifies per element the acceptable state (traceability Gate) and unacceptable deviations (Traceability Problem) from this state and formally defines how both, the acceptable states and the unacceptable deviations can be detected in order to enable practitioners to systematically assess their project's traceability.

Software traceability: trends and future directions

TLDR
This paper builds upon a prior body of work to highlight the state-of-the-art in software traceability, and to present compelling areas of research that need to be addressed.

A Model-Driven Engineering Approach to Support the Verification of Compliance to Safety Standards

TLDR
The approach is illustrated by showing how the concepts in the domain of sub-sea control systems can be aligned with the evidence requirements in the IEC61508 standard, which is one of the most commonly used certification standard for control systems.

Getting back to basics: Promoting the use of a traceability information model in practice

TLDR
The typical decisions involved in creating a basic traceability information model are highlighted, a simple UML-based representation for its definition is suggested, and its central role in the context of a modeling tool is illustrated.

Creating Safety Requirements Traceability for Assuring and Recertifying Legacy Safety-Critical Systems

  • Janice HillS. Tilley
  • Computer Science
    2010 18th IEEE International Requirements Engineering Conference
  • 2010
TLDR
A Legacy Systems Risk Database was built to manage the projects data and create the traceability between a safety process improvement model (+SAFE), the NASA software safety requirements, the safety taxonomy and software safety risks.

SafetyMet: A Metamodel for Safety Standards

TLDR
The benefits of the use of the metamodel, its limitations, and open issues are discussed in order to clearly present the aspects of safety compliance that are facilitated and those that are not addressed.

Toward Reference Models of Requirements Traceability

TLDR
Four kinds of traceability link types are identified and critical issues that must be resolved for implementing each type and potential solutions are discussed, and implications for the design of next-generation traceability methods and tools are discussed and illustrated.

Enabling traceability reuse for impact analyses: A feasibility study in a safety context

  • Markus BorgO. GotelK. Wnuk
  • Computer Science
    2013 7th International Workshop on Traceability in Emerging Forms of Software Engineering (TEFSE)
  • 2013
TLDR
This work mined the trace links in documented IA reports, creating a semantic network of the resulting traceability, and rendering the resulting network amenable to visual analyses, and provides initial suggestions as to how the knowledge embedded in such a network can be (re-)used to advance support for IA.

An analysis of the requirements traceability problem

  • O. GotelA. Finkelstein
  • Computer Science
    Proceedings of IEEE International Conference on Requirements Engineering
  • 1994
TLDR
The distinction between pre-requirements specification (pre-RS) traceability and post-RS traceability is introduced to demonstrate why an all-encompassing solution to the problem is unlikely, and to provide a framework to understand its multifaceted nature.
...