Identifying Implicit Process Variables To Support Future Empirical Work
Open Access
- 8 October 2003
- conference paper
- Published by Sociedade Brasileira de Computação
- p. 1-14
Abstract
The most basic questions that researchers must address when introducing a new process or technique are what is the intended effect of that process and can that effect be demonstrated empirically. As the understanding of a process progresses, researchers become interested in more sophisticated questions about a process or technique, such as studying the relationship between a particular type of variable and the outcome of the process. Quite often, researchers will find few, if any, studies in the literature that explicitly identify and analyze the effects of potential variables on the process. This paper proposes a methodology to aid in performing a literature search to be used as a basis for new research into these types of variables. The methodology provides guidance on making use of a large range of studies from which to extract potential variables. Throughout the paper, the methodology is illustrated with a specific example. The example focuses on searching for variables that deal with individual variations among software inspectors that affect their performance during an inspection. At the end of the example, after following the steps of the methodology, a list of potential variables among software inspectors is identified. The paper concludes with the next steps to be taken concerning the identified variables and hypotheses.Keywords
This publication has 11 references indexed in Scilit:
- Software Defect Reduction Top-10 List2005
- The Impact of Background and Experience on Software InspectionsEmpirical Software Engineering, 2004
- An experimental comparison of reading techniques for defect detection in UML design documentsJournal of Systems and Software, 2000
- Assessing software review meetings: results of a comparative analysis of two experimental studiesIEEE Transactions on Software Engineering, 1997
- A Replicated Experiment to Assess Requirements Inspection TechniquesEmpirical Software Engineering, 1997
- The empirical investigation of Perspective-Based ReadingEmpirical Software Engineering, 1996
- An experimental study of fault detection in user requirements documentsACM Transactions on Software Engineering and Methodology, 1992
- Experience with Fagan's inspection methodSoftware: Practice and Experience, 1992
- N-Fold inspection: a requirements analysis techniqueCommunications of the ACM, 1990
- Design and code inspections to reduce errors in program developmentIBM Systems Journal, 1976