Evaluating software eng. methods and tools part 10: designing and running a quantitative case study

Authors:
Barbara Ann Kitchenham;Lesley M. Pickard
Affiliations:
Univ. of Keele, Staffs, UK;-
Venue:
ACM SIGSOFT Software Engineering Notes
Year:
1998

Citing 1
Cited 4

Experimentation in software engineering

IEEE Transactions on Software Engineering

Empirical Characterization of Session---Based Workload and Reliability for Web Servers

Empirical Software Engineering
Quality, productivity and economic benefits of software reuse: a review of industrial studies

Empirical Software Engineering
An empirical investigation of software reuse benefits in a large telecom product

ACM Transactions on Software Engineering and Methodology (TOSEM)
Exploratory case study research: Outsourced project failure

Information and Software Technology

Quantified Score

Hi-index	0.01

Visualization

Abstract

In the last article we considered how to identify the context for a case study and how to define and validate a case study hypothesis. In this article, we continue my discussion of the eight steps involved in a quantitative case study by considering the remaining six steps: selecting the host projects; identifying the method of comparison; minimising the effect of confounding factors, planning the case study, monitoring the case study, analysing the results.