The DOI matches its Crossref record; 60 of the 63 references it cites were found in a registry or an index.
Toward reference models for requirements traceability
Abstract
Requirements traceability is intended to ensure continued alignment between stakeholder requirements and various outputs of the system development process. To be useful, traces must be organized according to some modeling framework. Indeed, several such frameworks have been proposed, mostly based on theoretical considerations or analysis of other literature. This paper, in contrast, follows an empirical approach. Focus groups and interviews conducted in 26 major software development organizations demonstrate a wide range of traceability practices with distinct low-end and high-end users of traceability. From these observations, reference models comprising the most important kinds of traceability links for various development tasks have been synthesized. The resulting models have been validated in case studies and are incorporated in a number of traceability tools. A detailed case study on the use of the models is presented. Four kinds of traceability link types are identified and critical issues that must be resolved for implementing each type and potential solutions are discussed. Implications for the design of next-generation traceability methods and tools are discussed and illustrated.
Overview
Integrity signals
Registry
Cites
Statistics
Verification
Claims the paper makes
Citations
Cites
Building Theories from Case Study Research
Eisenhardt, K. M. (1989) · The Academy of Management Review · doi:10.2307/258557 · Cited by 17,455
Focus Groups as Qualitative Research
Morgan, D. (1997) · doi:10.4135/9781412984287 · Cited by 8,863
Thick Description: Towards an Interpretive Theory of Culture
Geertz, C. (1973) · PhilPapers (PhilPapers Foundation) · doi:10.4324/9780203931950-11 · Cited by 4,209
The Sciences of the Artificial
Simon, H. A. (2019) · The MIT Press eBooks · doi:10.7551/mitpress/12107.001.0001 · Cited by 2,755
Hauser, J. R. (1988) · Harvard business review · Cited by 2,266
An analysis of the requirements traceability problem
Gotel, O. C. Z., & Finkelstein, C. W. (2002) · Proceedings of IEEE International Conference on Requirements Engineering · doi:10.1109/icre.1994.292398 · Cited by 1,246
gIBIS: a hypertext tool for exploratory policy discussion
Conklin, J., & Begeman, M. L. (1988) · ACM Transactions on Information Systems · doi:10.1145/58566.59297 · Cited by 1,086
Introduction to artificial intelligence
(2011) · Choice Reviews Online · doi:10.5860/choice.49-0903 · Cited by 1,085
Representing and using nonfunctional requirements: a process-oriented approach
Mylopoulos, J., Chung, L., & Nixon, B. A. (1992) · IEEE Transactions on Software Engineering · doi:10.1109/32.142871 · Cited by 1,019
Telos: representing knowledge about information systems
Mylopoulos, J., Borgida, A., Jarke, M., & Koubarakis, M. (1990) · ACM Trans. Inf. Syst. · doi:10.1145/102675.102676 · Cited by 904
Self-citation
Research works printed but not linked: 15
- Ramesh, Requirements TraceabilityTheory and Practice, 3, 397
- Pohl, Process Centered Requirements Eng
- Ramesh, Supporting Systems Development Using Knowledge Captured during Requirements Engineering, 18, 498
- Pohl, PRIMETowards ProcessIntegrated Modeling Environments, 8, 343
- Palmer, Traceability, 364
- Stehle, Requirements Traceability for Real-Time Systems
- Wright, Requirements TraceabilityWhat? Why? and How?
- Jarke, ConceptBaseA Deductive Object Base for Meta Data Management, 5, 167
- Constantopoulos, The Software Information BaseA Server for Reuse, 4, 1
- Lee, Design Rationale Capture and Use, 14, 24
- Goldman-Segall, Collaborative Virtual Communities Using Learning Constellations: A Multimedia Research Tool
- RDD-100: Requirements Driven Design, User Guide
- Dynamic Object Oriented Requirements SystemReference Manual
- SLATE User Manual
- 1992, Cadre/RQT User Manual
Cited by
Sorted by citations
Advancing candidate link generation for requirements tracing: the study of methods
Hayes, J. H., Dekhtyar, A., & Sundaram, S. K. (2006) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2006.3 · Cited by 507
A survey of traceability in requirements engineering and model-driven development
Winkler, S., & von Pilgrim, J. (2009) · Software & Systems Modeling · doi:10.1007/s10270-009-0145-0 · Cited by 315
Evolution of software in automated production systems: Challenges and research directions
Vogel‐Heuser, B., Fay, A., Schaefer, I., & Tichy, M. (2015) · Journal of Systems and Software · doi:10.1016/j.jss.2015.08.026 · Cited by 290
Improving requirements tracing via information retrieval
Hayes, J. H., Dekhtyar, A., & Osborne, J. (2004) · Journal of Lightwave Technology · doi:10.1109/icre.2003.1232745 · Cited by 289
Event-based traceability for managing evolutionary change
Cleland‐Huang, J., Chang, C. K., & Christensen, M. (2003) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2003.1232285 · Cited by 288
A rationale-based architecture model for design traceability and reasoning
Tang, A., Jin, Y., & Han, J. (2006) · Journal of Systems and Software · doi:10.1016/j.jss.2006.08.040 · Cited by 255
Contextualisation of business processes
Rosemann, M., Recker, J., & Flender, C. (2008) · International Journal of Business Process Integration and Management · doi:10.1504/ijbpim.2008.019347 · Cited by 253
Software traceability: trends and future directions
Cleland-Huang, J., Gotel, O. C. Z., Huffman Hayes, J., Mäder, P., & Zisman, A. (2014) · Future of Software Engineering Proceedings · doi:10.1145/2593882.2593891 · Cited by 309
Aizenbud-Reshef, N., Nolan, B. T., Rubin, J., & Shaham-Gafni, Y. (2006) · IBM Systems Journal · doi:10.1147/sj.453.0515 · Cited by 227
SOFTWARE TRACEABILITY: A ROADMAP
Spanoudakis, G., & Zisman, A. (2005) · WORLD SCIENTIFIC eBooks · doi:10.1142/9789812775245_0014 · Cited by 223
egoisst: a negotiation support system for electronic business-to-business negotiations in e-commerce
Schoop, M., Jertila, A., & List, T. (2003) · Data & Knowledge Engineering · doi:10.1016/s0169-023x(03)00065-x · Cited by 219
Rule-based generation of requirements traceability relations
Spanoudakis, G., Zisman, A., Pérez‐Miñana, E., & Krause, P. (2003) · Journal of Systems and Software · doi:10.1016/s0164-1212(03)00242-5 · Cited by 209
Best Practices for Automated Traceability
Cleland‐Huang, J., Berenbach, B., Clark, S., Settimi, R., & Romanova, E. (2007) · Computer · doi:10.1109/mc.2007.195 · Cited by 208
Requirements interaction management
Robinson, W. N., Pawlowski, S. D., & Volkov, V. Y. (2003) · ACM Computing Surveys · doi:10.1145/857076.857079 · Cited by 207
A survey of architecture design rationale
Tang, A., Babar, M. A., Gorton, I., & Han, J. (2006) · Journal of Systems and Software · doi:10.1016/j.jss.2006.04.029 · Cited by 207
A comparative study of architecture knowledge management tools
Tang, A., Avgeriou, P., Jansen, A. G. J., Capilla, R., & Babar, M. A. (2009) · Journal of Systems and Software · doi:10.1016/j.jss.2009.08.032 · Cited by 200
Boundary Objects in Design: An Ecological View of Design Artifacts
Mark, G. J., Lyytinen, K., & Bergman, M. (2007) · Journal of the Association for Information Systems · doi:10.17705/1jais.00144 · Cited by 194
A machine learning approach for tracing regulatory codes to product specific requirements
Cleland‐Huang, J., Czauderna, A., Gibiec, M., & Emenecker, J. (2010) · ACM/IEEE International Conference on Software Engineering: Companion Proceedings (ICSE-Companion) · doi:10.1145/1806799.1806825 · Cited by 189
A scenario-driven role engineering process for functional RBAC roles
Neumann, G., & Strembeck, M. (2002) · ACM Symposium on Access Control Models and Technologies (SACMAT) · doi:10.1145/507711.507717 · Cited by 176
An ontology-based approach to knowledge management in design processes
Brandt, S. C., Morbach, J., Miatidis, M., Theißen, M., Jarke, M., & Marquardt, W. (2007) · Computers & Chemical Engineering · doi:10.1016/j.compchemeng.2007.04.013 · Cited by 168
Self-citationUtilizing supporting evidence to improve dynamic requirements traceability
Cleland‐Huang, J., Settimi, R., Duan, C., & Zou, X. (2005) · IEEE International Requirements Engineering Conference (RE) · doi:10.1109/re.2005.78 · Cited by 164
Requirements engineering in automotive development: experiences and challenges
Weber, M., & Weisbrod, J. (2003) · IEEE Software · doi:10.1109/ms.2003.1159025 · Cited by 160
10 years of software architecture knowledge management: Practice and future
Capilla, R., Jansen, A., Tang, A., Avgeriou, P., & Babar, M. A. (2016) · Journal of Systems and Software · doi:10.1016/j.jss.2015.08.054 · Cited by 160
On integrating orthogonal information retrieval methods to improve traceability recovery
Gethers, M., Oliveto, R., Poshyvanyk, D., & Lucia, A. D. (2011) · IEEE International Conference on Software Maintenance (ICSM) · doi:10.1109/icsm.2011.6080780 · Cited by 158
A systematic review of requirements change management
Jayatilleke, S., & Lai, R. (2017) · Information and Software Technology · doi:10.1016/j.infsof.2017.09.004 · Cited by 150
Requirements Engineering and Technology Transfer: Obstacles, Incentives and Improvement Agenda
Kaindl, H., Brinkkemper, S., Bubenko, J. A., Farbey, B., Greenspan, S. J., Heitmeyer, C., Leite, J. C. S. D. P., Mead, N. R., Mylopoulos, J., & Siddiqi, J. (2002) · Requirements Engineering · doi:10.1007/s007660200008 · Cited by 150
Managing Evolutionary Method Engineering by Method Rationale
Rossi, M., Ramesh, B., Lyytinen, K., & Tolvanen, J. (2004) · Journal of the Association for Information Systems · doi:10.17705/1jais.00055 · Cited by 141
Self-citationRECOVERY OF TRACEABILITY LINKS BETWEEN SOFTWARE DOCUMENTATION AND SOURCE CODE
Marcus, A., Maletic, J. I., & Sergeyev, A. (2005) · International Journal of Software Engineering and Knowledge Engineering · doi:10.1142/s0218194005002543 · Cited by 139
The brave new world of design requirements
Jarke, M., Loucopoulos, P., Lyytinen, K., Mylopoulos, J., & Robinson, W. (2011) · Information Systems · doi:10.1016/j.is.2011.04.003 · Cited by 126
Self-citationA model-driven traceability framework for software product lines
Anquetil, N., Kulesza, U., Mitschke, R., Moreira, A., Royer, J.-C., Rummler, A., & Sousa, A. (2009) · Software & Systems Modeling · doi:10.1007/s10270-009-0120-9 · Cited by 124
Automating requirements traceability: Beyond the record & replay paradigm
Egyed, A. F., & Grünbacher, P. (2002) · IEEE/ACM International Conference on Automated Software Engineering (ASE) · doi:10.1109/ase.2002.1115010 · Cited by 123
Can LSI help reconstructing requirements traceability in design and test?
Lormans, M., & Arie Van Deursen, A. (2006) · Euromicro Conference on Software Maintenance and Reengineering (CSMR) · doi:10.1109/csmr.2006.13 · Cited by 120
Requirements Interdependencies: State of the Art and Future Challenges
Dahlstedt, Å. G., & Persson, A. (2006) · Springer eBooks · doi:10.1007/3-540-28244-0_5 · Cited by 117
Egyed, A. F., & Grünbacher, P. (2004) · IEEE Software · doi:10.1109/ms.2004.40 · Cited by 117
Requirements Reuse for Improving Information Systems Security: A Practitioner’s Approach
Toval, A., Nicolás, J., Morós, B., & García, F. (2002) · Requirements Engineering · doi:10.1007/pl00010360 · Cited by 117
Survey of Traceability Approaches in Model-Driven Engineering
Galvão, I., & Göknil, A. (2007) · IEEE International Enterprise Distributed Object Computing Conference (EDOC) · doi:10.1109/edoc.2007.42 · Cited by 115
Status Quo in Requirements Engineering
Wagner, S., Méndez, D., Felderer, M., Vetrò, A., Kalinowski, M., Wieringa, R. J., Pfahl, D., Conte, T. U., Christiansson, M.-T., Greer, D., et al. (2019) · ACM Transactions on Software Engineering and Methodology · doi:10.1145/3306607 · Cited by 115
Establishing Data Provenance for Responsible Artificial Intelligence Systems
Werder, K., Ramesh, B., & Zhang, R. (2022) · ACM Transactions on Management Information Systems · doi:10.1145/3503488 · Cited by 148
Self-citationReconciling software requirements and architectures with intermediate models
Grünbacher, P., Egyed, A. F., & Medvidović, N. (2004) · Software & Systems Modeling · doi:10.1007/s10270-003-0038-6 · Cited by 109
Weaving Models with the Eclipse AMW plugin
Fabro, M. D. D., Bézivín, J., & Valduriez, P. (2006) · Cited by 106
Supporting software evolution through dynamically retrieving traces to UML artifacts
Settimi, R., Cleland‐Huang, J., Khadra, O. B., Mody, J., Łukasik, W., & DePalma, C. (2004) · International Workshop on Principles of Software Evolution · doi:10.1109/iwpse.2004.1334768 · Cited by 106
A case study on value-based requirements tracing
Heindl, M., & Biffl, S. (2005) · ACM Joint European Software Engineering Conference and Symposium on the Foundations of Software Engineering (ESEC/FSE) · doi:10.1145/1081706.1081717 · Cited by 105
Gotel, O. C. Z., Cleland‐Huang, J., Hayes, J. H., Zisman, A., Egyed, A. F., Grünbacher, P., Dekhtyar, A., Antoniol, G., Maletic, J. I., & Mäder, P. (2011) · Springer eBooks · doi:10.1007/978-1-4471-2239-5_1 · Cited by 102
Mäder, P., & Egyed, A. F. (2014) · Empirical Software Engineering · doi:10.1007/s10664-014-9314-z · Cited by 97
Naming the pain in requirements engineering
Méndez, D., & Wagner, S. (2013) · International Conference on Evaluation and Assessment in Software Engineering (EASE) · doi:10.1145/2460999.2461027 · Cited by 97
Strategic Traceability for Safety-Critical Projects
Mäder, P., Jones, P. L., Zhang, Y., & Cleland‐Huang, J. (2013) · IEEE Software · doi:10.1109/ms.2013.60 · Cited by 97
Helping analysts trace requirements: an objective look
Hayes, J. H., Dekhtyar, A., Sundaram, S. K., & Howard, S. G. (2004) · doi:10.1109/re.2004.26 · Cited by 95
Rath, M., Rendall, J. B., Guo, J., Cleland‐Huang, J., & Mäder, P. (2018) · ACM/IEEE International Conference on Software Engineering: Companion Proceedings (ICSE-Companion) · doi:10.1145/3180155.3180207 · Cited by 94
Krishnamoorthi, R., & Mary, S. A. S. A. (2008) · Information and Software Technology · doi:10.1016/j.infsof.2008.08.007 · Cited by 90
Model-Driven User Requirements Specification using SysML
Soares, M. S., & Vrancken, J. (2008) · Journal of Software · doi:10.4304/jsw.3.6.57-68 · Cited by 90
When and how to visualize traceability links?
Marcus, A., Xie, X., & Poshyvanyk, D. (2005) · International Workshop on Traceability in Emerging Forms of Software Engineering (TEFSE) · doi:10.1145/1107656.1107669 · Cited by 83
Information Retrieval Methods for Automated Traceability Recovery
Lucia, A. D., Marcus, A., Oliveto, R., & Poshyvanyk, D. (2011) · Springer eBooks · doi:10.1007/978-1-4471-2239-5_4 · Cited by 83
On the role of semantics in automated requirements tracing
Mahmoud, A., & Niu, N. (2014) · Requirements Engineering · doi:10.1007/s00766-013-0199-y · Cited by 85
Méndez, D., & Wagner, S. (2014) · Information and Software Technology · doi:10.1016/j.infsof.2014.05.008 · Cited by 80
Managing requirements inconsistency with development goal monitors
Robinson, W. N., & Pawlowski, S. D. (1999) · IEEE Transactions on Software Engineering · doi:10.1109/32.824411 · Cited by 80
Ebert, C., & Man, J. D. (2005) · ACM/IEEE International Conference on Software Engineering: Companion Proceedings (ICSE-Companion) · doi:10.1145/1062455.1062554 · Cited by 80
Agile Requirements Definition: A View from Requirements Engineering
Eberlein, A. P.-G. (2002) · Cited by 78
Is Extreme Programming Just Old Wine in New Bottles
Merisalo-Rantanen, H., Tuunanen, T., & Rossi, M. (2005) · Journal of Database Management · doi:10.4018/jdm.2005100103 · Cited by 78
Nejati, S., Sabetzadeh, M., Falessi, D., Briand, L., & Coq, T. (2012) · Information and Software Technology · doi:10.1016/j.infsof.2012.01.005 · Cited by 77
Requirements engineering in automotive development-experiences and challenges
Weber, M., & Weisbrod, J. (2003) · IEEE International Requirements Engineering Conference (RE) · doi:10.1109/icre.2002.1048546 · Cited by 75
REQUIREMENTS TRACEABILITY: A SYSTEMATIC REVIEW AND INDUSTRY CASE STUDY
Torkar, R., Gorschek, T., FELDT, R. H., Svahnberg, M., Raja, U. A., & Kamran, K. (2012) · International Journal of Software Engineering and Knowledge Engineering · doi:10.1142/s021819401250009x · Cited by 73
XTraQue: traceability for product line systems
Jirapanthong, W., & Zisman, A. (2007) · Software & Systems Modeling · doi:10.1007/s10270-007-0066-8 · Cited by 73
Model Continuity in the Design of Dynamic Distributed Real-Time Systems
Hu, X., & Zeigler, B. P. (2005) · IEEE Transactions on Systems Man and Cybernetics - Part A Systems and Humans · doi:10.1109/tsmca.2005.851283 · Cited by 73
Traceability and management of dispersed product knowledge during design and manufacturing
Ouertani, M.-Z., Baïna, S., Gzara, L., & Morel, G. (2010) · Computer-Aided Design · doi:10.1016/j.cad.2010.03.006 · Cited by 71
A taxonomy for requirements engineering and software test alignment
Unterkalmsteiner, M., FELDT, R. H., & Gorschek, T. (2014) · ACM Transactions on Software Engineering and Methodology · doi:10.1145/2523088 · Cited by 71
QuaTrace: a tool environment for (semi-) automatic impact analysis based on traces
von Knethen, A., & Grund, M. (2003) · International Conference on Software Maintenance · doi:10.1109/icsm.2003.1235427 · Cited by 71
Semantics of trace relations in requirements models for consistency checking and inferencing
Göknil, A., Kurtev, I., van den Berg, K., & Veldhuis, J. (2009) · Software & Systems Modeling · doi:10.1007/s10270-009-0142-3 · Cited by 71
E-services: problems, opportunities, and digital platforms
Tiwana, A., & Ramesh, B. (2005) · Hawaii International Conference on System Sciences (HICSS) · doi:10.1109/hicss.2001.926311 · Cited by 71
Self-citationKeshta, I. M., Niazi, M., & Alshayeb, M. (2017) · IEEE Access · doi:10.1109/access.2017.2764490 · Cited by 71
The quest for Ubiquity: A roadmap for software and systems traceability research
Gotel, O. C. Z., Cleland‐Huang, J., Hayes, J. H., Zisman, A., Egyed, A. F., Grünbacher, P., & Antoniol, G. (2012) · IEEE International Requirements Engineering Conference (RE) · doi:10.1109/re.2012.6345841 · Cited by 70
Feature-driven requirement dependency analysis and high-level software design
Zhang, W., Mei, H., & Zhao, H. (2006) · Requirements Engineering · doi:10.1007/s00766-006-0033-x · Cited by 70
The Grand Challenge of Traceability (v1.0)
Gotel, O. C. Z., Cleland‐Huang, J., Hayes, J. H., Zisman, A., Egyed, A. F., Grünbacher, P., Dekhtyar, A., Antoniol, G., & Maletic, J. I. (2011) · Springer eBooks · doi:10.1007/978-1-4471-2239-5_16 · Cited by 70
Breaux, T. D., Antón, A. I., & Doyle, J. (2008) · ACM Transactions on Software Engineering and Methodology · doi:10.1145/1416563.1416565 · Cited by 73
Mind the gap: assessing the conformance of software traceability to relevant guidelines
Rempel, P., Mäder, P., Kuschke, T., & Cleland‐Huang, J. (2014) · ACM/IEEE International Conference on Software Engineering: Companion Proceedings (ICSE-Companion) · doi:10.1145/2568225.2568290 · Cited by 69
A Survey of the Use and Documentation of Architecture Design Rationale
Tang, A., Babar, M. A., Gorton, I., & Han, J. (2006) · Working IEEE/IFIP Conference on Software Architecture (WICSA) · doi:10.1109/wicsa.2005.7 · Cited by 69
A scoped approach to traceability management
Lago, P., Muccini, H., & van Vliet, H. (2008) · Journal of Systems and Software · doi:10.1016/j.jss.2008.08.026 · Cited by 68
Using Bayesian belief networks for change impact analysis in architecture design
Tang, A., Nicholson, A. E., Jin, Y., & Han, J. (2006) · Journal of Systems and Software · doi:10.1016/j.jss.2006.04.004 · Cited by 65
Systematic requirements recycling through abstraction and traceability
von Knethen, A., Paech, B., Kiedaisch, F., & Houdek, F. G. (2002) · IEEE International Requirements Engineering Conference (RE) · doi:10.1109/icre.2002.1048538 · Cited by 65
A collaborative decision framework for managing changes in e-Government services
Apostolou, D., Mentzas, G. N., Stojanović, L., Thönssen, B., & Lobo, T. P. (2010) · Government Information Quarterly · doi:10.1016/j.giq.2010.03.007 · Cited by 64
A feature-oriented approach to modeling requirements dependencies
Zhang, W., Mei, H., & Zhao, H. (2005) · IEEE International Requirements Engineering Conference (RE) · doi:10.1109/re.2005.6 · Cited by 64
A Survey on Usage Scenarios for Requirements Traceability in Practice
Bouillon, E., Mäder, P., & Philippow, I. (2013) · Lecture notes in computer science · doi:10.1007/978-3-642-37422-7_12 · Cited by 63
Motivation Matters in the Traceability Trenches
Mäder, P., Gotel, O. C. Z., & Philippow, I. (2009) · IEEE International Requirements Engineering Conference (RE) · doi:10.1109/re.2009.23 · Cited by 63
SUPPORTING SOFTWARE UNDERSTANDING WITH AUTOMATED REQUIREMENTS TRACEABILITY
Egyed, A. F., & Grünbacher, P. (2005) · International Journal of Software Engineering and Knowledge Engineering · doi:10.1142/s0218194005002464 · Cited by 63
Automating speculative queries through event-based requirements traceability
Cleland‐Huang, J., Chang, C. K., Sethi, G., Javvaji, K., Hu, H., & Xia, J. (2003) · IEEE International Requirements Engineering Conference (RE) · doi:10.1109/icre.2002.1048540 · Cited by 63
Rigorous identification and encoding of trace-links in model-driven engineering
Paige, R. F., Matragkas, N. D., Kolovos, D. S., Fernandes, K. J., Power, C., Olsen, G. K., & Zschaler, S. (2010) · Software & Systems Modeling · doi:10.1007/s10270-010-0158-8 · Cited by 61
User requirements modeling and analysis of software-intensive systems
Soares, M. S., Vrancken, J., & Verbraeck, A. (2010) · Journal of Systems and Software · doi:10.1016/j.jss.2010.10.020 · Cited by 59
Getting back to basics: Promoting the use of a traceability information model in practice
Mäder, P., Gotel, O. C. Z., & Philippow, I. (2009) · International Workshop on Traceability in Emerging Forms of Software Engineering (TEFSE) · doi:10.1109/tefse.2009.5069578 · Cited by 59
Pinheiro, F. A. (2004) · Springer eBooks · doi:10.1007/978-1-4615-0465-8_5 · Cited by 57
A heterogeneous solution for improving the return on investment of requirements traceability
Cleland‐Huang, J., Zemont, G., & Łukasik, W. (2004) · IEEE International Conference on Requirements Engineering · doi:10.1109/re.2004.3 · Cited by 56
Ståhl, D., Hallén, K., & Bosch, J. (2016) · Empirical Software Engineering · doi:10.1007/s10664-016-9457-1 · Cited by 55
Vlas, R. E., & Robinson, W. N. (2012) · Journal of Management Information Systems · doi:10.2753/mis0742-1222280402 · Cited by 55
Recognizing Humans Based on Gait Moment Image
Ma, Q., Wang, S., Nie, D., & Qiu, J. (2007) · ACIS International Conference on Software Engineering, Artificial Intelligence, Networking and Parallel/Distributed Computing (SNPD) · doi:10.1109/snpd.2007.307 · Cited by 55
Intentional Perspectives on Information Systems Engineering
Nurcan, S., Salinesi, C., Souveyet, C., & Ralyté, J. (2010) · Springer eBooks · doi:10.1007/978-3-642-12544-7 · Cited by 54
A Simulation Approach for Impact Analysis of Requirement Volatility Considering Dependency Change
Wang, J., Li, J., Wang, Q., Zhang, H., & Wang, H. (2012) · Lecture notes in computer science · doi:10.1007/978-3-642-28714-5_6 · Cited by 53
Scenario-Driven Role Engineering
Strembeck, M. (2010) · IEEE Security & Privacy · doi:10.1109/msp.2010.46 · Cited by 53
Effort and Quality of Recovering Requirements-to-Code Traces: Two Exploratory Experiments
Egyed, A. F., Gräf, F., & Grünbacher, P. (2010) · IEEE International Requirements Engineering Conference (RE) · doi:10.1109/re.2010.34 · Cited by 52
Model-Based Requirements Management in Gear Systems Design Based On Graph-Based Design Languages
Holder, K., Zech, A., Ramsaier, M., Stetter, R., Niedermeier, H.-P., Rudolph, S., & Till, M. (2017) · Applied Sciences · doi:10.3390/app7111112 · Cited by 52
Keenan, E., Czauderna, A., Leach, G., Cleland‐Huang, J., Shin, Y., Moritz, E., Gethers, M., Poshyvanyk, D., Maletic, J. I., Hayes, J. H., et al. (2012) · ACM/IEEE International Conference on Software Engineering: Companion Proceedings (ICSE-Companion) · doi:10.1109/icse.2012.6227244 · Cited by 52
Graph-based traceability: a comprehensive approach
Schwarz, H., Ebert, J., & Winter, A. (2009) · Software & Systems Modeling · doi:10.1007/s10270-009-0141-4 · Cited by 52
Identifying Crosscutting Concerns in Requirements Specifications
Rosenhainer, L. (2004) · Cited by 52
Metadata
- Authors
- Ramesh, B., & Jarke, M.
- Affiliations
- Georgia State University (US)
- Fraunhofer Institute for Applied Information Technology (DE)
- ORCID
- Venue
- IEEE Transactions on Software Engineering
- Published
- 2001
- Volume
- 27
- Issue
- 1
- Pages
- 58-93
- ISSN
- 0098-5589 (ISSN-L)
- OpenAlex
- W2045895677
- Cited by
- 912
- References
- 63
- Citations by year
- 2026: 15 · 2025: 13 · 2024: 14 · 2023: 13 · 2022: 8 · 2021: 22 · 2020: 19 · 2019: 16 · 2018: 28 · 2017: 30 · 2016: 35 · 2015: 38 · 2014: 35 · 2013: 47 · 2012: 69
- FWCI
- 92.83
- Type
- journal article
- Language
- en
- Open access
- closed
- Locations
- IEEE Transactions on Software Engineering (publishedVersion)
- Publikationsdatenbank der Fraunhofer-Gesellschaft (Fraunhofer-Gesellschaft) (submittedVersion)
- Fraunhofer-Publica (Fraunhofer-Gesellschaft) (submittedVersion)
- RWTH Publications (RWTH Aachen) (submittedVersion)
- Topics
- Physical Sciences › Computer Science › Information Systems › Software Engineering Techniques and Practices
- Physical Sciences › Computer Science › Software › Advanced Software Engineering Methodologies
- Physical Sciences › Computer Science › Information Systems › Software Engineering Research
- Keywords
- requirements traceability, reference model, traceability links, software development process, stakeholder needs, traceability tools, requirements engineering
About these checks
Registry, retraction, Cites and statistics results are computed, not judged, with one exception: a printed reference that no index lists is read once by a model before it counts as a citation error. Claims are extracted by a model and kept only when their quote appears verbatim in the text; each cited source is then checked, with a model’s help, for whether it says what the claim relies on. Those verdicts can be wrong — read the claim’s quote and the cited source before relying on one.
Statistics and arithmetic are recomputed, not judged.
Confidence bands are shown only for fields calibrated on our annotated test set. None is calibrated yet, so no band is shown.
What counts as a claim ›How we measure confidence ›How we check this ›
Are you an author, or do you see a problem with this page? Request a review
