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.
- {1} Basili, V. R., Selby, R. W. and Hutchens, D. H. Experimentation in software engineering. IEEE Transactions on Software Engineering, SE. 12(7), 1986, pp 758-773. Google ScholarDigital Library
- {2} Glass, R. L. Pilot studies: What, why and how. The Software Practitioner, January 1995, pp 4-11.Google Scholar
Index Terms
- Evaluating software eng. methods and tools part 10: designing and running a quantitative case study
Recommendations
Evaluating software engineering methods and tool part 1: The evaluation context and evaluation methods
In the last five issues of SIGSOFT Notes, Shari Lawrence Pfleeger has discussed the use of formal experiments to evaluate software engineering methods and tools [1]. Shari's articles were based on work she performed for the U.K. DESMET project which ...
Evaluating software engineering methods and tools, part 7: planning feature analysis evaluation
When planning a feature analysis based evaluation of a method or tool the following areas should be addressed and included in the evaluation project plan:1. scope of the evaluation,2. basis of the evaluation,3. roles and responsibilities,4. procedures,...
Part three: new books on writing computer user documentation
When I began teaching computer user documentation, there were very few books on the subject...and the few that existed weren't very good (John O'Rourke's <u>Writing for the Reader</u> (1976) excepted). Much has changed since--most notably the increasing ...
Comments