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
Software risk management: principles and practices
Boehm, B. W. (1991) · IEEE Software · doi:10.1109/52.62930 · Cited by 1,578
The Foundations of Cognitive Science
(1989) · The MIT Press eBooks · doi:10.7551/mitpress/3072.001.0001 · Cited by 1,444
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
Programs, life cycles, and laws of software evolution
Lehman, M. M. (1980) · Proceedings of the IEEE · doi:10.1109/proc.1980.11805 · Cited by 1,181
Popper, K. R., & Hudson, G. E. (1963) · Physics Today · doi:10.1063/1.3050617 · Cited by 1,071
Representing and using nonfunctional requirements: a process-oriented approach
Mylopoulos, J., Chung, L., & Nixon, B. (1992) · IEEE Transactions on Software Engineering · doi:10.1109/32.142871 · Cited by 1,018
Mastering the requirements process
Robertson, S., & Robertson, J. (2006) · Cited by 1,011
Four dark corners of requirements engineering
Zave, P., & Jackson, M. (1997) · ACM Transactions on Software Engineering and Methodology · doi:10.1145/237432.237434 · Cited by 734
A cost-value approach for prioritizing requirements
Karlsson, J., & Ryan, K. (1997) · IEEE Software · doi:10.1109/52.605933 · Cited by 726
Software Change Impact Analysis
Arnold, R. S. (1996) · Medical Entomology and Zoology · Cited by 665
Software maintenance and evolution: a roadmap
Bennett, K. H., & Rajlich, V. T. (2000) · Proceedings of the Conference on The Future of Software Engineering · doi:10.1145/336512.336534 · Cited by 606
Automated consistency checking of requirements specifications
Heitmeyer, C. L., Jeffords, R. D., & Labaw, B. G. (1996) · ACM Transactions on Software Engineering and Methodology · doi:10.1145/234426.234431 · Cited by 605
Managing conflicts in goal-driven requirements engineering
van Lamsweerde, A., Darimont, R., & Letier, E. (1998) · IEEE Transactions on Software Engineering · doi:10.1109/32.730542 · Cited by 595
Software requirements & specifications: a lexicon of practice, principles and prejudices
Jackson, M. (1995) · ACM Press/Addison-Wesley Publishing Co. eBooks · Cited by 575
A framework for expressing the relationships between multiple views in requirements specification
Nuseibeh, B., Kramer, J., & Finkelstein, A. (1994) · IEEE Transactions on Software Engineering · doi:10.1109/32.328995 · Cited by 540
Self-citationInquiry-based requirements analysis
Potts, C., Takahashi, K., & Anton, A. I. (1994) · IEEE Software · doi:10.1109/52.268952 · Cited by 522
Classification of research efforts in requirements engineering
Zave, P. (1997) · ACM Computing Surveys · doi:10.1145/267580.267581 · Cited by 428
Techniques for requirements elicitation
Goguen, J. A., & Linde, C. (2002) · [1993] Proceedings of the IEEE International Symposium on Requirements Engineering · doi:10.1109/isre.1993.324822 · Cited by 409
Software architecture: a roadmap
Garlan, D. (2000) · Proceedings of the Conference on The Future of Software Engineering · doi:10.1145/336512.336537 · Cited by 391
Prospects for an engineering discipline of software
Shaw, M. (1990) · IEEE Software · doi:10.1109/52.60586 · Cited by 346
On the inevitable intertwining of specification and implementation
Swartout, W., & Balzer, R. M. (1982) · Communications of the ACM · doi:10.1145/358557.358572 · Cited by 338
Applying Use Cases: A Practical Guide
Schneider, G., & Winters, J. P. (1998) · CERN Document Server (European Organization for Nuclear Research) · Cited by 334
ACRE: selecting methods for requirements acquisition
Maiden, N. A. M., & Rugg, G. (1996) · Software Engineering Journal · doi:10.1049/sej.1996.0024 · Cited by 310
Stakeholder identification in the requirements engineering process
Sharp, H., Finkelstein, A., & Galal, G. (1999) · Proceedings. Tenth International Workshop on Database and Expert Systems Applications. DEXA 99 · doi:10.1109/dexa.1999.795198 · Cited by 309 · cited 1×
“Users themselves are not homogeneous, and part of the elicitation process is to identify the needs of different user classes, such as novice users, expert users, occasional users, disabled users, and so on [73].”
BackgroundAcquiring COTS software selection requirements
Maiden, N., & Ncube, C. (1998) · IEEE Software · doi:10.1109/52.663784 · Cited by 290
Systems engineering: coping with complexity
(1998) · Engineering Management · doi:10.1049/em:19980613 · Cited by 288
Cognition in the Head and in the World: An Introduction to the Special Issue on Situated Action
Norman, D. A. (1993) · Cognitive Science · doi:10.1207/s15516709cog1701_1 · Cited by 283
The Requirements Apprentice: automated assistance for requirements acquisition
Reubenstein, H. B., & Waters, R. C. (1991) · IEEE Transactions on Software Engineering · doi:10.1109/32.75413 · Cited by 257
Exploiting reusable specifications through analogy
Maiden, N., & Sutcliffe, A. (1992) · Communications of the ACM · doi:10.1145/129852.129857 · Cited by 220
Requirements Engineering: Frameworks for Understanding
Wieringa, R. J. (1996) · University of Twente Research Information · Cited by 214
An analysis of errors and their causes in system programs
Endres, A. (1975) · ACM SIGPLAN Notices · doi:10.1145/390016.808455 · Cited by 200
Human computer interaction: Psychology, task analysis, and software engineering
Johnson, P. (1992) · Cited by 192
Operational prototyping: a new development approach
Davis, A. M. (1992) · IEEE Software · doi:10.1109/52.156899 · Cited by 176
Requirements gathering: the human factor
Holtzblatt, K., & Beyer, H. R. (1995) · Communications of the ACM · doi:10.1145/203356.203361 · Cited by 161
Practical Software Requirements: A Manual of Content and Style
Kovitz, B. (1998) · Cited by 143
Handling conflict between domain descriptions with computer-supported negotiation
Easterbrook, S. (1991) · Knowledge Acquisition · doi:10.1016/1042-8143(91)90007-a · Cited by 121
Self-citationSocial analysis in the requirements engineering process: from ethnography to method
Viller, S., & Sommerville, I. (2003) · IEEE International Requirements Engineering Conference (RE) · doi:10.1109/isre.1999.777980 · Cited by 106
A case history analysis of software error cause-effect relationships
Nakajo, T., & Kume, H. (1991) · IEEE Transactions on Software Engineering · doi:10.1109/32.83917 · Cited by 106
Integrating Obstacles in Goal-Driven Requirements Engineering
van Lamsweerde, A., Letier, E., & (belgium, B. L.-L.-N. (1998) · Cited by 104
CREWS-SAVRE: Scenarios for Acquiring and Validating Requirements
Maiden, N. (1998) · Automated Software Engineering · doi:10.1023/a:1008605412971 · Cited by 98
Dealing with security requirements during the development of information systems
Chung, L. (1993) · Notes on numerical fluid mechanics and multidisciplinary design · doi:10.1007/3-540-56777-1_13 · Cited by 94
CSCW: Cooperation or Conflict?
Easterbrook, S. (1993) · Computer supported cooperative work · doi:10.1007/978-1-4471-1981-4 · Cited by 93
Self-citationManaging inconsistencies in an evolving specification
Easterbrook, S., & Nuseibeh, B. (2002) · IEEE International Requirements Engineering Conference (RE) · doi:10.1109/isre.1995.512545 · Cited by 89
Self-citationFoundations of cognitive neuroscience
Posner, M. I. (1993) · The MIT Press eBooks · Cited by 43
Shaw, M. L. G., & Gaines, B. R. (1996) · Software Engineering Journal · doi:10.1049/sej.1996.0022 · Cited by 36
Systems, Management and Change: A Graphic Guide
Mayblin, B., Carter, R., & Martin, J. N. T. (1984) · Cited by 17
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
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.