Toward Reference Models of Requirements Traceability
By Balasubramaniam Ramesh, M. Jarke. IEEE Trans. Software Eng., 2001
1,006 citations recorded by the source corpus.
Subfields: Artificial Intelligence, Information Systems
View Paper: https://www.semanticscholar.org/paper/ca7b7a99fe204baf324832289579565d5792f88f
How researchers see this paper
The researchers whose trusted networks rank it highest, strongest advocate first. Every researcher gets a different order.
In Artificial Intelligence
- Jane Cleland-Huang
- Alex Dekhtyar
- Carl K. Chang
- Stefan Winkler
- Jane Huffman Hayes
- Jens Henning von Pilgrim
- Patrick Mäder
- Senthil Karthikeyan Sundaram
In Information Systems
- Jane Cleland-Huang
- Patrick Mäder
- Alex Dekhtyar
- Carl K. Chang
- Stefan Winkler
- Jane Huffman Hayes
- Jens Henning von Pilgrim
- Senthil Karthikeyan Sundaram
Citations in the corpus
- Event-Based Traceability for Managing Evolutionary Change (2003, methodology): “Artifacts are often made available for examination and analysis by all team members, while authorization to update artifacts is limited to specific workers [ 22 ].”
- Mind the gap: assessing the conformance of software traceability to relevant guidelines (2014, background): “Ramesh and Jarke [46] conducted a large practitioner and tool study on traceability.”
- Improving requirements tracing via information retrieval (2003, background): “They establish two specific models, a low-end model of traceability and a high-end model of traceability for more sophisticated users [20].”
- Advancing candidate link generation for requirements tracing: the study of methods (2006, background): “They establish two specific models, a low-end model of traceability and a high-end model of traceability for more sophisti cated users [41].”
- Software traceability: trends and future directions (2014, background): “Some exceptions include the work by Ramesh and Jarke [78] who conducted an extensive industrial study and developed several traceability reference models that captured artifact types and the links needed to support specific tasks such as requirements to design allocation.”
- A survey of traceability in requirements engineering and model-driven development (2010, methodology): “These “elements in a software development product”— such as documents, models, or code—are referred to as software configuration items by Pressman [151] or as artifacts, for example, by Gotel [73] and Ramesh and Jarke [156].”