A secondary analyses of Bradac et al. s prototype process-monitoring experiment

We report on the secondary analyses of some conjectures and empirical evidence presented in Bradac et al.’s prototype process-monitoring experiment, published previously in IEEE Transactions on Software Engineering. We identify 13 conjectures in the original paper, and re-analyse six of these conjectures using the original evidence. Rather than rejecting any of the original conjectures, we identify assumptions underlying those conjectures, identify alternative interpretations of the conjectures, and also propose a number of new conjectures. Bradac et al.’s study focused on reducing the project schedule interval. Some of our re-analysis has considered improving software quality. We note that our analyses were only possible because of the quality and quantity of evidence presented in the original paper. Reflecting on our analyses leads us to speculate about the value of ‘descriptive papers’ that seek to present ‘empirical material’ (together with an explicit statement of goals, assumptions and constraints) separate from the analyses that proceeds from that material. Such descriptive papers could improve the ‘public scrutiny’ of software engineering research and may respond, in part, to some researchers criticisms concerning the small amount of software engineering research that is actually evaluated. We also consider opportunities for further research, in particular opportunities for relating individual actions to project outcomes.

[1]  Dewayne E. Perry,et al.  People, organizations, and process improvement , 1994, IEEE Software.

[2]  Tom Rodden,et al.  Process Modelling and Development Practice , 1994, EWSPT.

[3]  Egon Berghout,et al.  Interrupts: Just a Minute Never Is , 1998, IEEE Softw..

[4]  Lucy A. Suchman,et al.  Office procedure as practical action: models of work and system design , 1983, TOIS.

[5]  Chris W. Clegg,et al.  The dynamics of work organization, knowledge and technology during software development , 1997, Int. J. Hum. Comput. Stud..

[6]  William Hughes Critical Thinking: An Introduction to the Basic Skills , 1992 .

[7]  Dewayne E. Perry,et al.  Studies in process simplification , 1997, Softw. Process. Improv. Pract..

[8]  Dewayne E. Perry,et al.  A study in process simplification , 1996, Proceedings of Software Process 1996.

[9]  Victor R. Basili,et al.  The SEL Adapts to Meet Changing Times , 1997 .

[10]  Barbara A. Kitchenham,et al.  Modeling Software Measurement Data , 2001, IEEE Trans. Software Eng..

[11]  F. Mcgarry Overview of the Software Engineering Laboratory , 1979 .

[12]  Austen Rainer,et al.  A catalogue of ‘analytic fragments’ of the behaviour of a software project , 2001 .

[13]  C. Billings,et al.  Journey to a Mature Software Process , 1994, IBM Syst. J..

[14]  Colin Potts,et al.  Software-engineering research revisited , 1993, IEEE Software.

[15]  Shari Lawrence Pfleeger,et al.  Towards a Framework for Software Measurement Validation , 1995, IEEE Trans. Software Eng..

[16]  Joyce J. Elam,et al.  Inside a software design team: knowledge acquisition, sharing, and integration , 1993, CACM.

[17]  L. G. Votta,et al.  Organizational congestion in large-scale software development , 1994, Proceedings of the Third International Conference on the Software Process. Applying the Software Process.

[18]  Austen Rainer Waiting in software projects: an exploratory study , 2003 .

[19]  Dewayne E. Perry,et al.  Understanding and Improving Time Usage in Software Development , 1995 .

[20]  Willemien Visser Organisation of design activities: opportunistic, with hierarchical episodes , 1994 .

[21]  Raymonde Guindon Designing the design process: exploiting opportunistic thoughts , 1990 .

[22]  Watts S. Humphrey,et al.  Three Process Perspectives: Organizations, Teams, and People , 2002, Ann. Softw. Eng..

[23]  Bill Curtis,et al.  A field study of the software design process for large systems , 1988, CACM.

[24]  Simon P. Davies,et al.  Characterizing the program design activity : neither strictly top-down nor globally opportunistic , 1991 .

[25]  Raymonde Guindon,et al.  Knowledge Exploited by Experts during Software System Design , 1990, Int. J. Man Mach. Stud..

[26]  William A. Florac,et al.  Statistical Process Control: Analyzing a Space Shuttle Onboard Software Process , 2000, IEEE Softw..

[27]  Robert L. Glass,et al.  Science and substance: a challenge to software engineers , 1994, IEEE Software.

[28]  Michiel van Genuchten,et al.  Why is Software Late? An Empirical Study of Reasons For Delay in Software Development , 1991, IEEE Trans. Software Eng..

[29]  Robert L. Glass,et al.  The software-research crisis , 1994, IEEE Software.

[30]  Allen S. Lee A Scientific Methodology for MIS Case Studies , 1989, MIS Q..

[31]  Ian Sommerville,et al.  Supporting Informality in the Software Process , 1994, EWSPT.

[32]  Paul Lukowicz,et al.  Experimental evaluation in computer science: A quantitative study , 1995, J. Syst. Softw..

[33]  Alec Fisher,et al.  The logic of real arguments: Philosophical assumptions , 2004 .