The DOI matches its Crossref record; 56 of the 56 references it cites were found in a registry or an index.
Requirements engineering: a roadmap
Open accessAbstract
Key Research PointersBetter modelling and analysis of problem domains, as opposed to the behaviour of s oflwa re.Development of richer models for capturing and analysing non-functional requirements.Bridging the gap between requirements elicitation approaches based on contextual enquiry and more formal specification and analysis techniques.Better understanding of the impact of software architectural choices on the prioritisation and evolution of requirements.Reuse of requirements models to facilitate the development of system families and the selection of COTS.Multi-disciplinary training for requirements practitioners.
Overview
The claims and statistics of this paper haven’t been checked yet.
Free: it reads the open-access text and checks the first 5 claims that cite a source we can check. Create a free account to check every claim.
Integrity signals
Registry
Cites
Statistics
Verification
Claims the paper makes
The claims and statistics of this paper haven’t been checked yet.
Free: it reads the open-access text and checks the first 5 claims that cite a source we can check. Create a free account to check every claim.
Self-check
Percentages, sums and reported differences re-computed from the paper’s own numbers.
The self-check needs the paper’s full text.
Citations
Cites
The Structure of Scientific Revolutions
Kuhn, T. S., & Schlegel, R. (1963) · Physics Today · doi:10.1063/1.3050879 · Cited by 35,538
Software Engineering Economics
Boehm, B. W. (2001) · Pioneers and Their Contributions to Software Engineering · doi:10.1007/978-3-642-48354-7_5 · Cited by 5,981
Conjectures and Refutations: The Growth of Scientific Knowledge.
Hutchison, T. W., & Popper, K. R. (1964) · Economica · doi:10.2307/2551371 · Cited by 4,197
Conjectures and Refutations: The Growth of Scientific Knowledge.
Hesse, M., & Popper, K. R. (1965) · The Philosophical Quarterly · doi:10.2307/2218271 · Cited by 4,189
Holzmann, G. J. (1997) · IEEE Transactions on Software Engineering · doi:10.1109/32.588521 · Cited by 3,803
Hauser, J. R. (1988) · Harvard business review · Cited by 2,266
On Non-Functional Requirements in Software Engineering
Chung, L., & do Prado Leite, J. C. S. (2009) · Lecture Notes in Computer Science · doi:10.1007/978-3-642-02463-4_19 · Cited by 2,247
Goal-directed requirements acquisition
Dardenne, A., van Lamsweerde, A., & Fickas, S. (1993) · Science of Computer Programming · doi:10.1016/0167-6423(93)90021-g · Cited by 1,976
Non-Functional Requirements in Software Engineering
Chung, L., Nixon, B. A., Yu, E., & Mylopoulos, J. (2000) · Springer eBooks · doi:10.1007/978-1-4615-5269-7 · Cited by 1,690
Towards modelling and reasoning support for early-phase requirements engineering
Yu, E. S. K. (2002) · Proceedings of ISRE '97: 3rd IEEE International Symposium on Requirements Engineering · doi:10.1109/isre.1997.566873 · Cited by 1,579
Cited by
Research Directions in Requirements Engineering
Cheng, B. H. C., & Atlee, J. M. (2007) · Future of Software Engineering (FOSE '07) · doi:10.1109/fose.2007.17 · Cited by 660
Requirements Elicitation: A Survey of Techniques, Approaches, and Tools
Zowghi, D., & Coulin, C. (2006) · Engineering and Managing Software Requirements · doi:10.1007/3-540-28244-0_2 · Cited by 430
Software engineering for security: a roadmap
Devanbu, P. T., & Stubblebine, S. (2000) · Proceedings of the Conference on The Future of Software Engineering · doi:10.1145/336512.336559 · Cited by 418
Understanding the requirements for developing open source software systems
Scacchi, W. (2002) · IEE Proceedings - Software · doi:10.1049/ip-sen:20020202 · Cited by 403
Vlaar, P. W. L., van Fenema, P. C., & Tiwari, V. (2008) · MIS Quarterly · doi:10.2307/25148839 · Cited by 340
Naming the pain in requirements engineering: Contemporary problems, causes, and effects in practice
Fernández, D. M., Wagner, S., Kalinowski, M., Felderer, M., Mafra, P., Vetrò, A., Conte, T., Christiansson, M.-T., Greer, D., Lassenius, C., et al. (2017) · Empirical Software Engineering · doi:10.1007/s10664-016-9451-7 · Cited by 300
Activity labeling in process modeling: Empirical insights and recommendations
Mendling, J., Reijers, H. A., & Recker, J. (2010) · Information Systems · doi:10.1016/j.is.2009.03.009 · Cited by 262
RE challenges in multi-site software development organisations
E. Damian, D., & Zowghi, D. (2003) · Requirements Engineering · doi:10.1007/s00766-003-0173-1 · Cited by 254
Damian, D. E., & Zowghi, D. (2002) · Proceedings IEEE Joint International Conference on Requirements Engineering ICRE-02 · doi:10.1109/icre.2002.1048545 · Cited by 202
Key Challenges in Early-Stage Software Startups
Giardino, C., Bajwa, S. S., Wang, X., & Abrahamsson, P. (2015) · Lecture Notes in Business Information Processing · doi:10.1007/978-3-319-18612-2_5 · Cited by 169
“Effective requirements elicitation would improve knowledge acquisition by engaging stakeholders in understanding the product concept and underlying problems that need to be addressed [20].”
BackgroundBogina, V., Hartman, A., Kuflik, T., & Shulner-Tal, A. (2022) · International Journal of Artificial Intelligence in Education · doi:10.1007/s40593-021-00248-0 · Cited by 142
“Their proposal is based on the 6 stages of the problem solving process (Nuseibeh and Easterbrook 2000): (1) objective finding, (2) fact finding (related to the goals surfaced in the previous stage), (3) problem finding (different ways to frame the problem), (4) idea finding, (5) solution finding and (6) acceptance fin…”
BackgroundRequirements engineering for artificial intelligence systems: A systematic mapping study
Ahmad, K., Abdelrazek, M., Arora, C., Bano, M., & Grundy, J. (2023) · Information and Software Technology · doi:10.1016/j.infsof.2023.107176 · Cited by 132
Raghu, A., Praveen, D., Peiris, D., Tarassenko, L., & Clifford, G. (2015) · BMC Medical Informatics and Decision Making · doi:10.1186/s12911-015-0148-4 · Cited by 89
Dodig Crnkovic, G., & Çürüklü, B. (2012) · Ethics and Information Technology · doi:10.1007/s10676-011-9278-2 · Cited by 90
Teixeira, L., Ferreira, C., & Santos, B. S. (2012) · Computer Methods and Programs in Biomedicine · doi:10.1016/j.cmpb.2010.10.007 · Cited by 76
A Study of Emotions in Requirements Engineering
Colomo-Palacios, R., Hernández-López, A., García-Crespo, Á., & Soto-Acosta, P. (2010) · Communications in Computer and Information Science · doi:10.1007/978-3-642-16324-1_1 · Cited by 50
Scaling up software architecture analysis
Kazman, R., Gagliardi, M., & Wood, W. (2012) · Journal of Systems and Software · doi:10.1016/j.jss.2011.03.050 · Cited by 31
Using a grounded theory approach for exploring software product management challenges
Jantunen, S., & Gause, D. C. (2014) · Journal of Systems and Software · doi:10.1016/j.jss.2014.03.050 · Cited by 31
A Knowledge Management Framework in Software Requirements Engineering Based on the SECI Model
Chikh, A. (2011) · Journal of Software Engineering and Applications · doi:10.4236/jsea.2011.412084 · Cited by 20
van de Kar, E., & den Hengst, M. (2009) · Electronic Markets · doi:10.1007/s12525-008-0002-y · Cited by 19
Esnaola, L. M., Ramón, H. D., & Lanzarini, L. C. (2026) · Empirical Software Engineering · doi:10.1007/s10664-026-10813-7 · Cited by 2
Metadata
- Authors
- Nuseibeh, B., & Easterbrook, S.
- Venue
- Proceedings of the Conference on The Future of Software Engineering
- Publisher
- ACM
- Published
- 2000-05
- Pages
- 35-46
- OpenAlex
- W2124405605
- Cited by
- 1,830
- References
- 56
- FWCI
- 27.43
- Type
- conference paper
- Language
- en
- Open access
- gold
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
Data sources
Bibliographic data: Semantic Scholar, OpenAlex, Crossref.
Contains information from the Semantic Scholar Academic Graph Datasets, made available under the ODC Attribution License (ODC-BY 1.0).
Semantic Scholar’s data is described in: Kinney, R., et al. (2023). The Semantic Scholar Open Data Platform. arXiv:2301.10140.