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
Flagged first, then by citations
3 of the 63 references couldn’t be matched to a known paper.
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
Items 101–200 of 910
Change-oriented requirements traceability. Support for evolution of embedded systems
von Knethen, A. (2002) · International Conference on Software Maintenance · doi:10.1109/icsm.2002.1167808 · Cited by 52
Process knowledge management with traceability
Ramesh, B. (2002) · IEEE Software · doi:10.1109/ms.2002.1003454 · Cited by 51
Self-citationAssessing the effect of requirements traceability for software maintenance
Mäder, P., & Egyed, A. F. (2012) · IEEE International Conference on Software Maintenance (ICSM) · doi:10.1109/icsm.2012.6405269 · Cited by 50
Plausible and adaptive requirement traceability structures
Spanoudakis, G. (2002) · Proceedings/Proceedings of the ... International Conference on Software Engineering and Knowledge Engineering · doi:10.1145/568760.568786 · Cited by 50
Helping analysts trace requirements:an objective look
Hayes, J. H., Dekhtyar, A., Sundaram, S. K., & Howard, S. (2004) · IEEE International Requirements Engineering Conference (RE) · doi:10.1109/icre.2004.1335682 · Cited by 50
Using a Hypertext Model for Traceability Link Conformance Analysis
Maletic, J. I., Munson, E. V., Marcus, A., & Nguyen, T. N. (2003) · Cited by 49
Tackling the term-mismatch problem in automated trace retrieval
Guo, J. L. C., Gibiec, M., & Cleland-Huang, J. (2017) · Empirical Software Engineering · doi:10.1007/s10664-016-9479-8 · Cited by 51
A Metamodeling Approach for Reasoning about Requirements
Göknil, A., Kurtev, I., & van den Berg, K. (2008) · Lecture notes in computer science · doi:10.1007/978-3-540-69100-6_21 · Cited by 48
Traceability and SysML design slices to support safety inspections
Briand, L., Falessi, D., Nejati, S., Sabetzadeh, M., & Yue, T. (2014) · ACM Transactions on Software Engineering and Methodology · doi:10.1145/2559978 · Cited by 47
Supporting event based traceability through high-level recognition of change events
Cleland‐Huang, J., Chang, C. K., & Ge, Y. (2003) · IEEE Annual International Computer Software and Applications Conference (COMPSAC) · doi:10.1109/cmpsac.2002.1045069 · Cited by 47
Traceability in Agile Projects
Cleland‐Huang, J. (2011) · Springer eBooks · doi:10.1007/978-1-4471-2239-5_12 · Cited by 46
Mohan, K., Xu, P., Cao, L., & Ramesh, B. (2008) · Decision Support Systems · doi:10.1016/j.dss.2008.03.003 · Cited by 46
Self-citation10.1.1 Toward an Evolutionary System of Systems Architecture
Selberg, S. A., & Austin, M. A. (2008) · INCOSE International Symposium · doi:10.1002/j.2334-5837.2008.tb00863.x · Cited by 46
Forces on Architecture Decisions - A Viewpoint
van Heesch, U., Avgeriou, P., & Hilliard, R. (2012) · Working IEEE/IFIP Conference on Software Architecture (WICSA) · doi:10.1109/wicsa-ecsa.212.18 · Cited by 46
Grand challenges, benchmarks, and TraceLab
Cleland‐Huang, J., Czauderna, A., Dekhtyar, A., Gotel, O., Hayes, J. H., Keenan, E., Leach, G., Maletic, J. I., Poshyvanyk, D., Shin, Y., et al. (2011) · International Workshop on Traceability in Emerging Forms of Software Engineering (TEFSE) · doi:10.1145/1987856.1987861 · Cited by 46
New Opportunities for Integrated Formal Methods
Gleirscher, M., Foster, S., & Woodcock, J. (2019) · ACM Computing Surveys · doi:10.1145/3357231 · Cited by 45
Method rationale in method engineering
Rossi, M., Tolvanen, J., Ramesh, B., Lyytinen, K., & Kaipala, J. (2005) · Hawaii International Conference on System Sciences (HICSS) · doi:10.1109/hicss.2000.926680 · Cited by 45
Self-citationSupporting evolutionary development by feature models and traceability links
Riebisch, M. (2004) · IEEE International Conference and Workshop on the Engineering of Computer-Based Systems (ECBS) · doi:10.1109/ecbs.2004.1316721 · Cited by 44
Supporting traceability and inconsistency management between software artifacts
Olsson, T., & Grundy, J. (2002) · Figshare · Cited by 44
Status Quo in Requirements Engineering: A Theory and a Global Family of Surveys
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. (2018) · Research Portal (Queen's University Belfast) · doi:10.18419/opus-10379 · Cited by 43
A study to support agile methods more effectively through traceability
Espinoza, A., & Garbajosa, J. (2011) · Innovations in Systems and Software Engineering · doi:10.1007/s11334-011-0144-5 · Cited by 43
Reconstructing requirements coverage views from design and test using traceability recovery via LSI
Lormans, M., & Arie Van Deursen, A. (2005) · International Workshop on Traceability in Emerging Forms of Software Engineering (TEFSE) · doi:10.1145/1107656.1107665 · Cited by 43
Trace Queries for Safety Requirements in High Assurance Systems
Cleland‐Huang, J., Heimdahl, M. P. E., Hayes, J. H., Lutz, R. R., & Maeder, P. (2012) · Lecture notes in computer science · doi:10.1007/978-3-642-28714-5_16 · Cited by 42
Scenarios of Traceability in Model to Text Transformations
Olsen, G. K., & Oldevik, J. (2007) · Springer eBooks · doi:10.1007/978-3-540-72901-3_11 · Cited by 42
The illusion of requirements in software development
Ralph, P. (2012) · Requirements Engineering · doi:10.1007/s00766-012-0161-4 · Cited by 41
Vlas, R. E., & Robinson, W. N. (2011) · Hawaii International Conference on System Sciences (HICSS) · doi:10.1109/hicss.2011.28 · Cited by 41
Software Architecture Design Reasoning: A Case for Improved Methodology Support
Tang, A., Han, J., & Vasa, R. (2009) · IEEE Software · doi:10.1109/ms.2009.46 · Cited by 41
A Meta Model for Artefact-Orientation: Fundamentals and Lessons Learned in Requirements Engineering
Méndez, D., Penzenstadler, B., Kuhrmann, M., & Broy, M. (2010) · Lecture notes in computer science · doi:10.1007/978-3-642-16129-2_14 · Cited by 40
Traceability-based knowledge integration in group decision and negotiation activities
Mohan, K., & Ramesh, B. (2005) · Decision Support Systems · doi:10.1016/j.dss.2005.05.026 · Cited by 40
Self-citationTheorizing in Information Systems Research Using Focus Groups
Bélanger, F. (2012) · AJIS. Australasian journal of information systems/AJIS. Australian journal of information systems/Australian journal of information systems · doi:10.3127/ajis.v17i2.695 · Cited by 40
Automating Software Traceability in Very Small Companies: A Case Study and Lessons Learne
Neumuller, C., & Grünbacher, P. (2006) · IEEE/ACM International Conference on Automated Software Engineering (ASE) · doi:10.1109/ase.2006.25 · Cited by 39
Impact of Knowledge Support on the Performance of Software Process Tailoring
Xu, P., & Ramesh, B. (2008) · Journal of Management Information Systems · doi:10.2753/mis0742-1222250308 · Cited by 39
Self-citationRule-Based Maintenance of Post-Requirements Traceability Relations
Mäder, P., Gotel, O. C. Z., & Philippow, I. (2008) · IEEE International Requirements Engineering Conference (RE) · doi:10.1109/re.2008.24 · Cited by 39
Traceability for Model Driven, Software Product Line Engineering
Anquetil, N., Grammel, B., Galvão, I., Noopen, J., Khan, S., Arboleda, H., Rashid, A., & Garcia, R. (2008) · University of Twente Research Information · Cited by 38
Vicente-Chicote, C., Morós, B., & Toval, A. (2007) · The Journal of Object Technology · doi:10.5381/jot.2007.6.9.a22 · Cited by 38
Tracing Software Requirements Artifacts.
Zisman, A., Spanoudakis, G., Pérez‐Miñana, E., & Krause, P. (2003) · Software Engineering Research and Practice · Cited by 38
Using code ownership to improve IR-based Traceability Link Recovery
Diaz, D., Bavota, G., Marcus, A., Oliveto, R., Takahashi, S., & Lucia, A. D. (2013) · International Conference on Program Comprehension · doi:10.1109/icpc.2013.6613840 · Cited by 37
An empirical study on project-specific traceability strategies
Rempel, P., Mäder, P., & Kuschke, T. (2013) · IEEE International Requirements Engineering Conference (RE) · doi:10.1109/re.2013.6636719 · Cited by 37
A FRAMEWORK FOR COMPARING REQUIREMENTS TRACING EXPERIMENTS
Hayes, J. H., & Dekhtyar, A. (2005) · International Journal of Software Engineering and Knowledge Engineering · doi:10.1142/s021819400500252x · Cited by 37
Requirement-Centric Traceability for Change Impact Analysis: A Case Study
Li, Y., Li, J., Yang, Y., & Li, M. (2008) · Springer eBooks · doi:10.1007/978-3-540-79588-9_10 · Cited by 36
Göknil, A., Kurtev, I., & van den Berg, K. (2013) · Journal of Systems and Software · doi:10.1016/j.jss.2013.10.006 · Cited by 36
Gray links in the use of requirements traceability
Niu, N., Wang, W., & Gupta, A. (2016) · ACM Joint European Software Engineering Conference and Symposium on the Foundations of Software Engineering (ESEC/FSE) · doi:10.1145/2950290.2950354 · Cited by 36
Liebenberg, M., & Jarke, M. (2023) · Information Systems · doi:10.1016/j.is.2023.102182 · Cited by 35
Self-citationGrammel, B., & Kastenholz, S. (2010) · doi:10.1145/1814392.1814394 · Cited by 35
Maté, A., & Trujillo, J. C. (2012) · Information Systems · doi:10.1016/j.is.2012.05.003 · Cited by 35
The impact of traceability on software maintenance and evolution: A mapping study
Tian, F., Wang, T., Liang, P., Wang, C., Khan, A. A., & Babar, M. A. (2021) · Journal of Software Evolution and Process · doi:10.1002/smr.2374 · Cited by 49
Just Enough Requirements Traceability
Cleland‐Huang, J. (2006) · IEEE Annual International Computer Software and Applications Conference (COMPSAC) · doi:10.1109/compsac.2006.57 · Cited by 35
Cleland‐Huang, J., Hayes, J. H., & Domel, J. M. (2009) · International Workshop on Traceability in Emerging Forms of Software Engineering (TEFSE) · doi:10.1109/tefse.2009.5069575 · Cited by 35
Understanding context-awareness in business process design
Rosemann, M., Recker, J., Flender, C., & Ansell, P.-D. (2006) · Kölner Universitäts PublikationsServer (Universität zu Köln) · Cited by 35
Identifying tacit knowledge-based requirements
Stone, A., & Sawyer, P. (2006) · IEE Proceedings - Software · doi:10.1049/ip-sen:20060034 · Cited by 35
An industrial case study in reconstructing requirements views
Lormans, M., Arie Van Deursen, A., & Groß, H.-G. (2008) · Empirical Software Engineering · doi:10.1007/s10664-008-9078-4 · Cited by 34
Capturing software traceability links from developers' eye gazes
Walters, B. M., Shaffer, T., Sharif, B., & Kagdi, H. (2014) · International Conference on Program Comprehension · doi:10.1145/2597008.2597795 · Cited by 34
Traceability Techniques: A Critical Study
Bashir, M. F., & Qadir, M. A. (2006) · IEEE International Multitopic Conference (INMIC) · doi:10.1109/inmic.2006.358175 · Cited by 34
Risk management with enhanced tracing of requirements rationale in highly distributed projects
Heindl, M., & Biffl, S. (2006) · doi:10.1145/1138506.1138512 · Cited by 34
Deciding to Adopt Requirements Traceability in Practice
Blaauboer, F. A., Sikkel, K., & Aydın, M. N. (2007) · Notes on numerical fluid mechanics and multidisciplinary design · doi:10.1007/978-3-540-72988-4_21 · Cited by 33
Automatic Support for Traceability in a Generic Model Management Framework
Boronat, A., Carsi, J. A., & Ramos, I. (2005) · Lecture notes in computer science · doi:10.1007/11581741_23 · Cited by 33
A trace model for system requirements changes on embedded systems
von Knethen, A. (2002) · International Workshop on Principles of Software Evolution · doi:10.1145/602461.602465 · Cited by 33
A Traceability Framework to Enable Circularity in the Built Environment
Davari, S., Jaberi, M., Yousfi, A., & Poirier, E. (2023) · Sustainability · doi:10.3390/su15108278 · Cited by 32
A visual language for modeling and executing traceability queries
Mäder, P., & Cleland‐Huang, J. (2012) · Software & Systems Modeling · doi:10.1007/s10270-012-0237-0 · Cited by 32
A Traceability Approach for i* and UML Models
Filho, G. A. A. C., Zisman, A., & Spanoudakis, G. (2003) · Cited by 32
Requirements uncertainty: influencing factors and concrete improvements
Ebert, C., & Man, J. D. (2005) · ACM/IEEE International Conference on Software Engineering: Companion Proceedings (ICSE-Companion) · doi:10.1109/icse.2005.1553601 · Cited by 32
Yuniarti, R., Masudin, I., Rusdiansyah, A., & Handayani, D. I. (2023) · International Journal of Industrial Engineering and Operations Management · doi:10.1108/ijieom-10-2022-0045 · Cited by 31
An LLM-based Approach to Recover Traceability Links between Security Requirements and Goal Models
Hassine, J. (2024) · International Conference on Evaluation and Assessment in Software Engineering (EASE) · doi:10.1145/3661167.3661261 · Cited by 31
A framework for developing home automation systems: From requirements to code
Sánchez, P., Buendía, M. J., Rosique, F., Álvarez, B., & Iborra, A. (2011) · Journal of Systems and Software · doi:10.1016/j.jss.2011.01.052 · Cited by 31
Evolving software trace links between requirements and source code
Rahimi, M., & Cleland‐Huang, J. (2017) · Empirical Software Engineering · doi:10.1007/s10664-017-9561-x · Cited by 31
Tang, A., & Han, J. (2005) · IEEE International Conference and Workshop on the Engineering of Computer-Based Systems (ECBS) · doi:10.1109/ecbs.2005.17 · Cited by 31
Why Eliciting and Managing Legal Requirements Is Hard
Kiyavitskaya, N., Krausová, A., & Zannone, N. (2008) · doi:10.1109/relaw.2008.10 · Cited by 31
Supporting product line development through traceability
Jirapanthong, W., & Zisman, A. (2005) · Asia-Pacific Software Engineering Conference (APSEC) · doi:10.1109/apsec.2005.101 · Cited by 31
Which Traceability Visualization Is Suitable in This Context? A Comparative Study
Li, Y., & Maalej, W. (2012) · Lecture notes in computer science · doi:10.1007/978-3-642-28714-5_17 · Cited by 34
Automating performance-related impact analysis through event based traceability
Cleland‐Huang, J., Chang, C. K., & Wise, J. C. (2003) · Requirements Engineering · doi:10.1007/s00766-003-0175-z · Cited by 31
Analysis of crosscutting across software development phases based on traceability
van den Berg, K., Conejero, J. M., & Hernández, J. (2006) · doi:10.1145/1137639.1137647 · Cited by 31
Image Fusion Based on Wavelet Transform
Jian, M., Dong, J., & Zhang, Y. (2007) · ACIS International Conference on Software Engineering, Artificial Intelligence, Networking and Parallel/Distributed Computing (SNPD) · doi:10.1109/snpd.2007.110 · Cited by 31
Model-based a-posteriori integration of engineering tools for incremental development processes
Becker, S. M., Haase, T. A., & Westfechtel, B. (2004) · Software & Systems Modeling · doi:10.1007/s10270-004-0071-0 · Cited by 31
A holistic approach to managing software change impact
Chen, C., & Chen, P.-C. (2009) · Journal of Systems and Software · doi:10.1016/j.jss.2009.06.052 · Cited by 30
Mirakhorli, M. T., & Cleland‐Huang, J. (2011) · IEEE International Conference on Software Maintenance (ICSM) · doi:10.1109/icsm.2011.6080779 · Cited by 30
Learning effective query transformations for enhanced requirements trace retrieval
Dietrich, T., Cleland‐Huang, J., & Shin, Y. (2013) · IEEE/ACM International Conference on Automated Software Engineering (ASE) · doi:10.1109/ase.2013.6693117 · Cited by 30
Scope analysis: identifying the impact of changes in business process models
Soffer, P. (2005) · Software Process Improvement and Practice · doi:10.1002/spip.242 · Cited by 30
The Need for a Unifying Traceability Scheme
Limón, A. E., & Garbajosa, J. (2005) · Cited by 30
Software Architecture in Practice: Challenges and Opportunities
Wan, Z., Zhang, Y., Xia, X., Jiang, Y., & Lo, D. (2023) · Proceedings of the 31st ACM Joint European Software Engineering Conference and Symposium on the Foundations of Software Engineering · doi:10.1145/3611643.3616367 · Cited by 30
“Traceability of architecture knowledge improves understandability of software architectures, helps to locate relevant knowledge, enables impact analysis of architectural changes, and facilitates design review, evaluation and assessment [50, 78].”
BackgroundSoftware architecture review by association
Tang, A., & Lau, M. F. (2014) · Journal of Systems and Software · doi:10.1016/j.jss.2013.09.044 · Cited by 33
Towards the prioritization of system test cases
Srikanth, H., Banerjee, S. K., Williams, L. A., & Osborne, J. A. (2013) · Software Testing Verification and Reliability · doi:10.1002/stvr.1500 · Cited by 29
Sarkkinen, J., & Karsten, H. (2005) · Information Systems Journal · doi:10.1111/j.1365-2575.2005.00196.x · Cited by 29
Visual Support In Automated Tracing
Cleland‐Huang, J., & Habrat, R. (2007) · International Workshop on Requirements Engineering Visualization (REV) · doi:10.1109/rev.2007.7 · Cited by 29
Capra: A Configurable and Extendable Traceability Management Tool
Maro, S., & Steghöfer, J.-P. (2016) · IEEE International Requirements Engineering Conference (RE) · doi:10.1109/re.2016.19 · Cited by 29
Krogmann, K. (2010) · Repository KITopen (Karlsruhe Institute of Technology) · doi:10.5445/ir/1000022278 · Cited by 29
The Need for Traceability in Heterogeneous Systems: A Systematic Literature Review
Mustafa, N., & Labiche, Y. (2017) · IEEE Annual International Computer Software and Applications Conference (COMPSAC) · doi:10.1109/compsac.2017.237 · Cited by 28
Hajri, I., Göknil, A., Pastore, F., & Briand, L. (2020) · Empirical Software Engineering · doi:10.1007/s10664-020-09853-4 · Cited by 28
Handayani, D. I., Masudin, I., Rusdiansyah, A., & Suharsono, J. (2021) · Logistics · doi:10.3390/logistics5030059 · Cited by 28
Change Impact Analysis based on Formalization of Trace Relations for Requirements
Göknil, A., Kurtev, I., & van den Berg, K. (2008) · University of Twente Research Information · Cited by 28
Analyzing and Systematizing Current Traceability Schemas
Espinoza, A., Alarcón, P. P., & Garbajosa, J. (2006) · IEEE Software Engineering Workshop (SEW) · doi:10.1109/sew.2006.12 · Cited by 28
A proposed model for reuse of software requirements in requirements catalog
Pacheco, C., García, I., Calvo-Manzano, J. A., & Arcilla, M. (2014) · Journal of Software Evolution and Process · doi:10.1002/smr.1698 · Cited by 28
Managing variability with traceability in product and service families
Mohan, K., & Ramesh, B. (2003) · Hawaii International Conference on System Sciences (HICSS) · doi:10.1109/hicss.2002.993995 · Cited by 28
Self-citationEvolution of XML schemas and documents from stereotyped UML class models: A traceable approach
Domínguez, E., Lloret, J., Pérez, B., ́guez, Á. R., Rubio, Á. L., & Zapata, M. A. (2010) · Information and Software Technology · doi:10.1016/j.infsof.2010.08.001 · Cited by 27
On Warehouses, Lakes, and Spaces: The Changing Role of Conceptual Modeling for Data Integration
Jarke, M., & Quix, C. (2017) · Springer eBooks · doi:10.1007/978-3-319-67271-7_16 · Cited by 27
Self-citationTools and Technologies for Architecture Knowledge Management
Liang, P., & Avgeriou, P. (2009) · Springer eBooks · doi:10.1007/978-3-642-02374-3_6 · Cited by 27
Requirements Evolution and What (Research) to Do about It
Ernst, N., Mylopoulos, J., & Wang, Y. (2009) · Lecture notes in business information processing · doi:10.1007/978-3-540-92966-6_11 · Cited by 27
Traceability and completeness checking for agent-oriented systems
Filho, G. A. D. A. C., & Zisman, A. (2008) · ACM Symposium on Applied Computing · doi:10.1145/1363686.1363706 · Cited by 27
Tuunanen, T., & Rossi, M. (2004) · 37th Annual Hawaii International Conference on System Sciences, 2004. Proceedings of the · doi:10.1109/hicss.2004.1265420 · Cited by 33
Traceability in the Supply Chain
Kros, J. F., Liao, Y., Kirchoff, J. F., & Zemanek, J. E. (2018) · International Journal of Applied Logistics · doi:10.4018/ijal.2019010101 · Cited by 27
Knowledge Support in Software Process Tailoring
Xu, P. (2005) · Hawaii International Conference on System Sciences (HICSS) · doi:10.1109/hicss.2005.380 · Cited by 27
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