The DOI matches its Crossref record; 85 of the 85 references it cites were found in a registry or an index.
Requirements Engineering: Best Practice
Open accessOverview
Integrity signals
Registry
Cites
Statistics
Verification
Claims the paper makes
Claims other papers make about this one
Each is checked against this paper’s own text: does it say what the citing paper says it does?
In the citing paper
“The integration of multiple stakeholders in requirements engineering (for an overview, see [28]) are therefore increasingly required by ethics codes as well as laws.”
From AI for the Common Good?! Pitfalls, challenges, and ethics pen-testing (2019) · cites this paper as [28]
Citations
Cites
A Simple Sequentially Rejective Multiple Test Procedure
(1979) · Scandinavian Journal of Statistics · doi:10.2307/4615733 · Cited by 21,526
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
Experimentation in Software Engineering: An Introduction
Wohlin, C., Runeson, P., Höst, M., Ohlsson, M. C., Regnell, B., & Wesslén, A. (2011) · Lund University Publications (Lund University) · Cited by 2,214
Experimentation in Software Engineering
Wohlin, C., Runeson, P., Höst, M., Ohlsson, M. C., Regnell, B., & Wesslén, A. (2000) · Kluwer international series in software engineering · doi:10.1007/978-1-4615-4625-2 · Cited by 1,775
Designing and Conducting Survey Research: A Comprehensive Guide
Rea, L. M., & Parker, R. (1992) · Cited by 1,761
Goal-oriented requirements engineering: a guided tour
van Lamsweerde, A. (2002) · IEEE International Requirements Engineering Conference (RE) · doi:10.1109/isre.2001.948567 · Cited by 1,723
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,692
Structured Analysis and System Specification
DeMarco, T. (2002) · Software Pioneers · doi:10.1007/978-3-642-59412-0_33 · Cited by 1,449
Cockburn, A. (2000) · Cited by 1,409
Technology roadmapping—A planning framework for evolution and revolution
Phaal, R., Farrukh, C. J. P., & Probert, D. R. (2004) · Technological Forecasting and Social Change · doi:10.1016/s0040-1625(03)00072-6 · Cited by 1,229
Ben-Menachem, M. (2001) · ACM SIGSOFT Software Engineering Notes · doi:10.1145/505894.505918 · Cited by 1,035
Structured Analysis (SA): A Language for Communicating Ideas
Ross, D. T. (1977) · IEEE Transactions on Software Engineering · doi:10.1109/tse.1977.229900 · Cited by 867
Research Directions in Requirements Engineering
Cheng, B. H. C., & Atlee, J. M. (2007) · Future of Software Engineering (FOSE) · doi:10.1109/fose.2007.17 · Cited by 673
Version models for software configuration management
Conradi, R., & Westfechtel, B. (1998) · ACM Computing Surveys · doi:10.1145/280277.280280 · Cited by 586
From object-oriented to goal-oriented requirements analysis
Mylopoulos, J., Chung, L., & Yu, E. (1999) · Communications of the ACM · doi:10.1145/291469.293165 · Cited by 581
Negotiation Analysis: The Science and Art of Collaborative Decision Making
Raiffa, H., Richardson, J., & Metcalfe, D. (2007) · Harvard University Press eBooks · doi:10.2307/j.ctv1cbn3p6 · Cited by 525
Inquiry-based requirements analysis
Potts, C., Takahashi, K., & Anton, A. I. (1994) · IEEE Software · doi:10.1109/52.268952 · Cited by 522
Engineering and Managing Software Requirements
(2005) · Springer eBooks · doi:10.1007/3-540-28244-0 · Cited by 492
Systems and Software Verification: Model-Checking Techniques and Tools
Bérard, B., Bidoit, M., Finkel, A., Laroussinie, F., Petit, A., Petrucci, L., & Schnoebelen, P. (2001) · Cited by 488
Rettig, M. (1994) · Communications of the ACM · doi:10.1145/175276.175288 · Cited by 440
Comparing detection methods for software requirements inspections: a replicated experiment
Porter, A. A., Votta, L. G., & Basili, V. R. (1995) · IEEE Transactions on Software Engineering · doi:10.1109/32.391380 · Cited by 431
Cleanroom Software Engineering
Mills, H. D., Dyer, M., & Linger, R. C. (1987) · IEEE Software · doi:10.1109/ms.1987.231413 · Cited by 431
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
A systematic literature review of software requirements prioritization research
Achimugu, P., Selamat, A., Ibrahim, R., & Mahrin, M. N. (2014) · Information and Software Technology · doi:10.1016/j.infsof.2014.02.001 · Cited by 419
A conceptual framework for understanding business processes and business process modelling
Melão, N. F., & Pidd, M. (2000) · Information Systems Journal · doi:10.1046/j.1365-2575.2000.00075.x · Cited by 394
Generic semantics of feature diagrams
Schobbens, P., Heymans, P., Trigaux, J.-C., & Bontemps, Y. (2006) · Computer Networks · doi:10.1016/j.comnet.2006.08.008 · Cited by 388
Generating statechart designs from scenarios
Whittle, J., & Schumann, J. (2000) · Proceedings of the 22nd international conference on Software engineering - ICSE '00 · doi:10.1145/337180.337217 · Cited by 358
Davis, A., Dieste, O., Hickey, A., Juristo, N., & Moreno, A. M. (2006) · 14th IEEE International Requirements Engineering Conference (RE'06) · doi:10.1109/re.2006.17 · Cited by 334
UML 2 AND THE UNIFIED PROCESS : Practical Object-oriented Analysis and Design
Arlow, J., & Neustadt, I. (2015) · Cited by 292
The rise and fall of the Chaos report figures
Eveleens, J. L., & Verhoef, C. (2010) · IEEE Software · doi:10.1109/ms.2009.154 · Cited by 282
Developing groupware for requirements negotiation: lessons learned
BOEHM, B. W., Grünbacher, P., & Briggs, R. O. (2001) · IEEE Software · doi:10.1109/52.922725 · Cited by 282
Requirements engineering: The state of the practice
Neill, C. J., & Laplante, P. A. (2003) · IEEE Software · doi:10.1109/ms.2003.1241365 · Cited by 277
Structure Analysis and System Specification
DeMarco, T. (1979) · Springer eBooks · doi:10.1007/978-3-642-48354-7_9 · Cited by 259
A Unified Model of Requirements Elicitation
HICKEY, A. M., & DAVIS, A. M. (2004) · Journal of Management Information Systems · doi:10.1080/07421222.2004.11045786 · Cited by 253
Scenarios, Stories, Use Cases: Through the Systems Development Life-Cycle
Alexander, I. F., & Maiden, N. (2004) · International Linear Collider · Cited by 250
Elicitation technique selection: how do experts do it?
Hickey, A. M., & Davis, A. M. (2004) · Journal of Lightwave Technology · doi:10.1109/icre.2003.1232748 · Cited by 224
Requirements Abstraction Model
Gorschek, T., & Wohlin, C. (2005) · Requirements Engineering · doi:10.1007/s00766-005-0020-7 · Cited by 223
User-interface tools: introduction and survey
Myers, B. A. (1989) · IEEE Software · doi:10.1109/52.16898 · Cited by 222
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
Hassenzahl, M., Beu, A., & Burmester, M. (2001) · IEEE Software · doi:10.1109/52.903170 · Cited by 204
Apprenticing with the customer
Beyer, H. R., & Holtzblatt, K. (1995) · Communications of the ACM · doi:10.1145/203356.203365 · Cited by 193
Kanban and Scrum - Making the Most of Both
Kniberg, H. (2010) · Cited by 189
A field study of requirements engineering practices in information systems development
Emam, K. E., & Madhavji, N. H. (2002) · IEEE International Requirements Engineering Conference (RE) · doi:10.1109/isre.1995.512547 · Cited by 181
Provoking Creativity: Imagine What Your Requirements Could Be Like
Maiden, N., Gizikis, A., & Robertson, S. (2004) · IEEE Software · doi:10.1109/ms.2004.1331305 · Cited by 175
Pohl, K., & Rupp, C. (2011) · CERN Document Server (European Organization for Nuclear Research) · Cited by 164
A systematic review on strategic release planning models
Svahnberg, M., Gorschek, T., FELDT, R. H., Torkar, R., Saleem, S. B., & Shafique, M. U. (2009) · Information and Software Technology · doi:10.1016/j.infsof.2009.11.006 · Cited by 162
Experiences using lightweight formal methods for requirements modeling
Easterbrook, S., Lutz, R. R., Covington, R. G., Kelly, J. C., Ampo, Y., & Hamilton, D. (1998) · IEEE Transactions on Software Engineering · doi:10.1109/32.663994 · Cited by 159
Alvarez, R., & Urla, J. (2002) · ACM SIGMIS Database the DATABASE for Advances in Information Systems · doi:10.1145/504350.504357 · Cited by 157
Towards a Reference Framework for Software Product Management
van de Weerd, I., Brinkkemper, S., Nieuwenhuis, R., Versendaal, J., & Bijlsma, A. (2006) · IEEE International Requirements Engineering Conference (RE) · doi:10.1109/re.2006.66 · Cited by 147
A methodology and tool support for managing business rules in organisations
Bajec, M., & Krisper, M. (2004) · Information Systems · doi:10.1016/j.is.2004.05.003 · Cited by 136
Measuring the flow in lean software development
Petersen, K., & Wohlin, C. (2010) · Software Practice and Experience · doi:10.1002/spe.975 · Cited by 121
Higher quality requirements specifications through natural language patterns
Denger, C., Berry, D. M., & Kamsties, E. (2003) · doi:10.1109/swste.2003.1245428 · Cited by 116
Requirements - Understanding project sociology by modeling stakeholders
Alexander, I. F., & Robertson, S. (2004) · IEEE Software · doi:10.1109/ms.2004.1259199 · Cited by 113
Describing the practice of introspection.
Vermersch, P. (2009) · Journal of Consciousness Studies · Cited by 111
Ten steps towards systematic requirements reuse
Lam, W., McDermid, J. A., & Vickers, A. J. (1997) · Requirements Engineering · doi:10.1007/bf02813029 · Cited by 110
Web services computing: advancing software interoperability
Chung, J., Lin, K.-J., & Mathieu, R. G. (2003) · Computer · doi:10.1109/mc.2003.1236469 · Cited by 101
Requirements by Collaboration: Workshops for Defining Needs
Gottesdiener, E. (2002) · CERN Document Server (European Organization for Nuclear Research) · Cited by 88
On shared understanding in software engineering: an essay
Glinz, M., & Fricker, S. A. (2014) · Computer Science - Research and Development · doi:10.1007/s00450-014-0256-x · Cited by 85
Self-citationHandshaking with Implementation Proposals: Negotiating Requirements Understanding
Fricker, S., Gorschek, T., Byman, C., & Schmidle, A. (2010) · IEEE Software · doi:10.1109/ms.2010.44 · Cited by 63
Self-citationBusiness process archeology using MARBLE
Pérez‐Castillo, R., de Guzmán, I. G., & Piattini, M. G. (2011) · Information and Software Technology · doi:10.1016/j.infsof.2011.05.006 · Cited by 59
Power and politics in requirements engineering: embracing the dark side?
Milne, A., & Maiden, N. (2012) · Requirements Engineering · doi:10.1007/s00766-012-0151-6 · Cited by 58
A Lightweight Innovation Process for Software-Intensive Product Development
Gorschek, T., Fricker, S., Palm, K., & Kunsman, S. (2009) · IEEE Software · doi:10.1109/ms.2009.164 · Cited by 55
Self-citationProduct strategy for high technology companies : accelerating your business to web speed
McGrath, M. E. (2001) · Cited by 54
Good requirements practices are neither necessary nor sufficient
Davis, A. M., & Zowghi, D. (2004) · Requirements Engineering · doi:10.1007/s00766-004-0206-4 · Cited by 49
Understanding the Customer: What Do We Know about Requirements Elicitation?
Dieste, Ó., Juristo, N., & Shull, F. J. (2008) · IEEE Software · doi:10.1109/ms.2008.53 · Cited by 48
Boyle, L. N., Barfield, W., & Mannering, F. (1995) · Transportation Research Part C Emerging Technologies · doi:10.1016/0968-090x(95)00001-y · Cited by 48
Using data mining and recommender systems to scale up the requirements process
Cleland‐Huang, J., & Mobasher, B. (2008) · doi:10.1145/1370700.1370702 · Cited by 47
Need-based requirements change management
Kobayashi, A., & Maekawa, M. (2002) · IEEE International Conference and Workshop on the Engineering of Computer-Based Systems (ECBS) · doi:10.1109/ecbs.2001.922419 · Cited by 45
Tests and Requirements, Requirements and Tests: A Möbius Strip
Martin, R. C., & Melnik, G. (2008) · IEEE Software · doi:10.1109/ms.2008.24 · Cited by 44
Automatic extraction of glossary terms from natural language requirements
Dwarakanath, A., Ramnani, R., & Sengupta, S. (2013) · IEEE International Requirements Engineering Conference (RE) · doi:10.1109/re.2013.6636736 · Cited by 35
Automatic Validation and Correction of Formalized, Textual Requirements
Holtmann, J., Meyer, J., & von Detten, M. (2011) · IEEE International Conference on Software Testing, Verification and Validation Workshops (ICSTW) · doi:10.1109/icstw.2011.17 · Cited by 28
Goal-Oriented Requirements Communication in New Product Development
Fricker, S., Gorschek, T., & Glinz, M. (2008) · International Workshop on Software Product Management (IWSPM) · doi:10.1109/iwspm.2008.2 · Cited by 27
Self-citationAn Analysis of Empirical Requirements Engineering Survey Data
Paech, B., Koenig, T., Borner, L., & Aurum, A. (2006) · Springer eBooks · doi:10.1007/3-540-28244-0_19 · Cited by 23
Comparison of Requirements Hand-off, Analysis, and Negotiation: Case Study
Fricker, S., & Glinz, M. (2010) · IEEE International Requirements Engineering Conference (RE) · doi:10.1109/re.2010.29 · Cited by 22
Self-citationKhurum, M., Fricker, S., & Gorschek, T. (2014) · Information and Software Technology · doi:10.1016/j.infsof.2014.06.010 · Cited by 20
Self-citationRelease Planning with Feature Trees: Industrial Case
Fricker, S., & Schumacher, S. (2012) · Lecture notes in computer science · doi:10.1007/978-3-642-28714-5_26 · Cited by 17
Self-citationRequirement engineering elicitation methods
Rouibah, K., & Al‐Rafee, S. (2009) · Information Management & Computer Security · doi:10.1108/09685220910978086 · Cited by 17
Very Lightweight Requirements Modeling
Glinz, M. (2010) · IEEE International Requirements Engineering Conference (RE) · doi:10.1109/re.2010.73 · Cited by 16
Norms and standards in modular medical architectures
Thüemmler, C., Mival, O., Benyon, D., Buchanan, W. J., Paulin, A., Fricker, S., Fiedler, M., Grøttland, A., Jell, T., Magedanz, T., et al. (2013) · IEEE International Conference on e-Health Networking, Applications and Services (Healthcom) · doi:10.1109/healthcom.2013.6720705 · Cited by 13
Self-citationSimulation-Driven Creation, Validation and Evolution of Behavioral Requirements Models
Glinz, M., Seybold, C., & Meier, S. (2007) · Cited by 11
Domain Driven Development and Feature Driven Development for Development of Decision Support Systems
Danėnas, P., & Garšva, G. (2012) · Communications in computer and information science · doi:10.1007/978-3-642-33308-8_16 · Cited by 5
Pragmatic Requirements Communication: The Handshaking Approach
Fricker, S. (2009) · Zurich Open Repository and Archive (University of Zurich) · Cited by 5
Self-citationIn press: On Shared Understanding in Software Engineering: an Essay
Glinz, M., & Fricker, S. (2014) · Cited by 3
Self-citation
Research works printed but not linked: 4
- Glinz M, Fricker S (2013) On shared understanding in software engineering, Software engineering 2012. Aachen, Germany
- Schmidt M (2002) The business case guide. Solution Matrix, Boston
- Davis A (2005) Just enough requirements management. Dorset House Publishing, New York
- IEEE (1990) IEEE standard glossary of software engineering terminology 610.12-1990
Cited by
Rezaei, M., Jafari‐Sadeghi, V., Cao, D., & Mahdiraji, H. A. (2021) · Technological Forecasting and Social Change · doi:10.1016/j.techfore.2021.120724 · Cited by 90
Natsiavas, P., Rasmussen, J., Voss-Knude, M., Votis, K., Coppolino, L., Campegiani, P., Cano, I., Marí, D., Faiella, G., Clemente, F., et al. (2018) · BMC Medical Informatics and Decision Making · doi:10.1186/s12911-018-0664-0 · Cited by 40
Werner, C., Li, Z. S., Ernst, N., & Damian, D. (2020) · IEEE International Requirements Engineering Conference (RE) · doi:10.1109/re48521.2020.00021 · Cited by 42
Video as a By-Product of Digital Prototyping: Capturing the Dynamic Aspect of Interaction
Karras, O., Unger‐Windeler, C., Glauer, L., & Schneider, K. A. (2017) · IEEE International Requirements Engineering Conference Workshops (REW) · doi:10.1109/rew.2017.16 · Cited by 23
On the Use of Domain and System Knowledge Modeling in Goal-Based Event-B Specifications
Mammar, A., & Laleau, R. (2016) · Lecture notes in computer science · doi:10.1007/978-3-319-47166-2_23 · Cited by 20
Metadata
- Authors
- Fricker, S. A., Grau, R., & Zwingli, A.
- Affiliations
- Blekinge Institute of Technology (SE)
- Corresponding author
- Fricker, Samuel A.
- ORCID
- Fricker, Samuel A.
- Venue
- Requirements Engineering for Digital Health
- Publisher
- Springer International Publishing
- Published
- 2014-10-11
- Pages
- 25-46
- OpenAlex
- W1544524595
- Cited by
- 61
- References
- 85
- Citations by year
- 2026: 2 · 2025: 3 · 2024: 9 · 2023: 6 · 2022: 4 · 2021: 10 · 2020: 4 · 2019: 5 · 2018: 10 · 2017: 5 · 2016: 2 · 2015: 1
- FWCI
- 10.51
- Type
- book chapter
- Language
- en
- Open access
- green
- urn.kb.se
- Licence
- other-oa
- www.springernature.com/gp/researchers/text-and-data-mining (tdm)
- www.springernature.com/gp/researchers/text-and-data-mining (vor)
- Locations
- Springer eBooks (publishedVersion)
- Diva portal (Dalarna University Library) (submittedVersion, other-oa)
- Topics
- Physical Sciences › Computer Science › Information Systems › Software Engineering Techniques and Practices
- Physical Sciences › Computer Science › Software › Advanced Software Engineering Methodologies
- Physical Sciences › Engineering › Control and Systems Engineering › Systems Engineering Methodologies and Applications
- Keywords
- requirements engineering, best practices, requirements specification, requirements validation, industrial practice, software project success factors, requirements engineering techniques
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.
