Implementing requirements traceability: a case study

Ramesh, Balasubramaniam; Powers, T.; Stubbs, Curtis; Edwards, Michael

doi:10.1109/isre.1995.512549

Cited by 65 publications

(51 citation statements)

References 2 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…In [Ramesh et al 1995], the problem of relatively high costs of creating and maintaining traceability was identified, which can only be compensated by higher quality and reduced overall costs if traceability is applied purposefully. Leading to a traceability costbenefit problem.…”

Section: Empirical Work On Traceability Problemsmentioning

confidence: 99%

Continuous assessment of software traceability

Rempel

Mäder

2016

Proceedings of the 38th International Conference on Software Engineering Companion

View full text Add to dashboard Cite

Section: Empirical Work On Traceability Problemsmentioning

confidence: 99%

Continuous assessment of software traceability

Rempel

Mäder

2016

Proceedings of the 38th International Conference on Software Engineering Companion

View full text Add to dashboard Cite

“…Gotel and Finkelstein [1] studied requirements traceability practices and highlighted especially the demand for supporting prerequirements traceability. Ramesh and Jarke [5] conducted intensive interview studies with practitioners. As a conclusion they proposed two traceability reference models.…”

Section: Related Workmentioning

confidence: 99%

Requirements Traceability across Organizational Boundaries - A Survey and Taxonomy

Rempel

Mäder

Kuschke

et al. 2013

Requirements Engineering: Foundation for Software Quality

View full text Add to dashboard Cite

Abstract. [Context and motivation]Outsourcing of software development is an attractive business model. Companies expect cost reduction, enhanced efficiency, and exploited external resources. However, this paradigmatic shift also introduces challenges as stakeholders are spread across distinct organizations. [Question/problem] Requirements traceability supports stakeholders in satisfying information needs about developments and could be a viable way of addressing the challenges of interorganizational development. While requirements traceability has been the subject of significant research efforts, its application across organizational boundaries is a largely unexplored area. [Principal ideas/results] We followed a qualitative research approach. First, we developed a taxonomy identifying the needs of inter-organizational traceability. Second, we conducted semi-structured interviews with informants from 17 companies. Eventually, we applied qualitative content analysis to extract findings that supported and evolved our taxonomy. [Contribution] Practitioners planning and managing inter-organizational relationships can use our findings as a conceptual baseline to effectively leverage traceability in those settings. Effective traceability supports projects in accomplishing their primary goal of maximizing business value.

show abstract

“…In Figure 1, the traceability model, these concepts are captured including their traceability links. The traceability links that need to be captured in this traceability model depend on project specific information needs [10], but also on factors such as schedule and budget [27].…”

Section: Traceability Model and Concept Identificationmentioning

confidence: 99%