The DOI matches its Crossref record; 7 of the 7 references it cites were found in a registry or an index.
Case studies for method and tool evaluation
Abstract
Case studies help industry evaluate the benefits of methods and tools and provide a cost-effective way to ensure that process changes provide the desired results. However, unlike formal experiments and surveys, case studies do not have a well-understood theoretical basis. This article provides guidelines for organizing and analyzing case studies so that they produce meaningful results.>
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
(1984) · Cited by 81,983
Design and code inspections to reduce errors in program development
Fagan, M. E. (1976) · IBM Systems Journal · doi:10.1147/sj.153.0182 · Cited by 1,492
Experimentation in software engineering
Basili, V. R., Selby, R. W., & Hutchens, D. H. (1986) · IEEE Transactions on Software Engineering · doi:10.1109/tse.1986.6312975 · Cited by 553
Science and substance: a challenge to software engineers
Fenton, N., Pfleeger, S. L., & Glass, R. L. (1994) · IEEE Software · doi:10.1109/52.300094 · Cited by 265
Self-citationEvaluating Software Engineering Technologies
Card, D. N., Garry, F. E. M., & Page, G. (1987) · IEEE Transactions on Software Engineering · doi:10.1109/tse.1987.233495 · Cited by 90
Current usage of case software
Necco, C. R., Tsai, N., & Holgeson, K. W. (1989) · doi:10.5555/64536.64537 · Cited by 30
The effects of inspections on software quality and productivity
(1986) · Microprocessors and Microsystems · doi:10.1016/0141-9331(86)90234-6 · Cited by 18
Cited by
Guidelines for conducting and reporting case study research in software engineering
Runeson, P., & Höst, M. (2009) · Empirical Software Engineering · doi:10.1007/s10664-008-9102-8 · Cited by 3,862
“2000) and reporting (Jedlitschka and Pfahl 2005), measurements (Basili and Weiss 1984; Fenton and Pfleeger 1996; van Solingen and Berghout 1999), and systematic reviews (Kitchenham 2007), while only little is written on case studies in software engineering (Höst and Runeson 2007; Kitchenham et al. 1995; Wohlin et al.…”
BackgroundSelecting Empirical Methods for Software Engineering Research
Easterbrook, S., Singer, J., Storey, M.-A., & Damian, D. (2008) · Guide to Advanced Empirical Software Engineering · doi:10.1007/978-1-84800-044-5_11 · Cited by 1,167
Do, H., Elbaum, S., & Rothermel, G. (2005) · Empirical Software Engineering · doi:10.1007/s10664-005-3861-2 · Cited by 1,146
Test case prioritization: a family of empirical studies
Elbaum, S., Malishevsky, A. G., & Rothermel, G. (2002) · IEEE Transactions on Software Engineering · doi:10.1109/32.988497 · Cited by 943
Software quality: the elusive target [special issues section]
Kitchenham, B., & Pfleeger, S. L. (1996) · IEEE Software · doi:10.1109/52.476281 · Cited by 545
Self-citationWandersman, A., Chien, V. H., & Katz, J. (2012) · American Journal of Community Psychology · doi:10.1007/s10464-012-9509-7 · Cited by 422
“The need for greater information quality control has produced a variety of tools for information quality assurance (see Lee et al. 2002; Kitchenham et al. 1995, Mizzaro 2003; Whiting et al. 2003) Conduct an outcome evaluation (GTO step 8) This step involves assessing the extent to which the desired…”
BackgroundThe Future of Empirical Methods in Software Engineering Research
Sjoberg, D. I. K., Dyba, T., & Jorgensen, M. (2007) · Future of Software Engineering (FOSE '07) · doi:10.1109/fose.2007.30 · Cited by 389
Assessing Organizational Capabilities: Reviewing and Guiding the Development of Maturity Grids
Maier, A. M., Moultrie, J., & Clarkson, P. J. (2012) · IEEE Transactions on Engineering Management · doi:10.1109/tem.2010.2077289 · Cited by 318
Fenton, N. E., & Neil, M. (2000) · Proceedings of the Conference on The Future of Software Engineering · doi:10.1145/336512.336588 · Cited by 317
Evaluation and Measurement of Software Process Improvement—A Systematic Literature Review
Unterkalmsteiner, M., Gorschek, T., Islam, A. K. M. M., Cheng, C. K., Permadi, R. B., & Feldt, R. (2012) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2011.26 · Cited by 291
Empirical Research Methods in Software Engineering
Wohlin, C., Höst, M., & Henningsson, K. (2003) · Lecture Notes in Computer Science · doi:10.1007/978-3-540-45143-3_2 · Cited by 270
Context in industrial software engineering research
Petersen, K., & Wohlin, C. (2009) · 2009 3rd International Symposium on Empirical Software Engineering and Measurement · doi:10.1109/esem.2009.5316010 · Cited by 270
Enabling high-level application development for the Internet of Things
Patel, P., & Cassou, D. (2015) · Journal of Systems and Software · doi:10.1016/j.jss.2015.01.027 · Cited by 252
A fog computing-based architecture for medical records management
Silva, C. A., Aquino, G. S., Melo, S. R. M., & Egídio, D. J. B. (2019) · Wireless Communications and Mobile Computing · doi:10.1155/2019/1968960 · Cited by 50
A mapping study on documentation in Continuous Software Development
Theunissen, T., van Heesch, U., & Avgeriou, P. (2022) · Information and Software Technology · doi:10.1016/j.infsof.2021.106733 · Cited by 40
Metadata
- Authors
- Kitchenham, B., Pickard, L., & Pfleeger, S. L.
- Venue
- IEEE Software
- Published
- 1995-07
- Volume
- 12
- Issue
- 4
- Pages
- 52-62
- ISSN
- 0740-7459 (ISSN-L)
- OpenAlex
- W2164765430
- Cited by
- 601
- References
- 7
- FWCI
- 26.14
- Type
- journal article
- Language
- en
- Open access
- closed
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.