Logo des Repositoriums

Auflistung nach Autor:in "Rempel, Patrick"

1 - 3 von 3
  • Zeitschriftenartikel
    A Framework for Traceability Tool Comparison
    (Softwaretechnik-Trends: Vol. 32, No. 3, 2012) Rempel, Patrick; Lehnert, Steffen; Kuschke, Tobias; Farooq, Qurat-Ul-Ann
    Patrick Rempel, Steffen Lehnert, Tobias Kuschke, Qurat-Ul-Ann Farooq Ilmenau University of Technology Ilmenau, Germany {patrick.rempel, steffen.lehnert, tobias.kuschke, qurat-ul-ann.farooq}@tu-ilmenau.de Abstract
  • Konferenzbeitrag
    A quality model for the systematic assessment of requirements traceability
    (Software Engineering 2016, 2016) Rempel, Patrick; Mäder, Patrick
    Traceability is an important quality of software requirements and allows to describe and follow their life throughout a development project. The importance of traceable requirements is reflected by the fact that requirements standards, safety regulations, and maturity models explicitly demand for it. In practice, traceability is created and maintained by humans, which make mistakes. In result, existing traces are potentially of dubious quality but serve as the foundation for high impact development decisions. We found in previous studies that practitioners miss clear guidance on how to systematically assess the quality of existing traces. In this paper, we review the elements involved in establishing traceability in a development project and derive a quality model that specifies per element the acceptable state (Traceability Gate) and unacceptable deviations (Traceability Problem) from this state. We describe and formally define how both, the acceptable states and the unacceptable deviations can be detected in order to enable practitioners to systematically assess their project's traceability. We evaluated the proposed model through an expert survey. Participating experts considered the quality model to be complete and attested that its quality criteria are of high relevance. However, experts weight the occurrence of different traceability problems with different criticality. This information is useful for practitioners to quantify the impact of traceability problems and to prioritize the assessment of traceability elements.
  • Konferenzbeitrag
    Traceability gap analysis for assessing the conformance of software traceabilityto relevant guidelines
    (Software-engineering and management 2015, 2015) Rempel, Patrick; Mäder, Patrick; Kuschke, Tobias; Cleland-Huang, Jane
    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. We present an approach, which parses a guideline to extract a Traceability Model depicting software artifact types and their prescribed traces. It then analyzes the traceability data within a project to identify areas of traceability failure. Missing traceability paths, redundant and/or inconsistent data, and other problems are highlighted. We used our approach to evaluate the traceability of seven safety-critical software systems and found that none of the evaluated projects contained traceability that fully conformed to its relevant guidelines.