Nothing Special   »   [go: up one dir, main page]

Skip to main content
Log in

Directions and Methodologies for Empirical Software Engineering Research

  • Published:
Empirical Software Engineering Aims and scope Submit manuscript

Abstract

This report summarises and builds on the results of the “Directions and Methodologies for Empirical Software Engineering Research” group discussion. In particular, we considered the strengths, weaknesses, opportunities and threats to empirical software engineering research in light of the discussions and presentations during the workshop. The following sections describe each of these aspects of our discussion in turn. In addition, to finalise our discussion we agreed on a three-point plan for future work.

This is a preview of subscription content, log in via an institution to check access.

Access this article

Subscribe and save

Springer+ Basic
$34.99 /Month
  • Get 10 units per month
  • Download Article/Chapter or eBook
  • 1 Unit = 1 Article or 1 Chapter
  • Cancel anytime
Subscribe now

Buy Now

Price excludes VAT (USA)
Tax calculation will be finalised during checkout.

Instant access to the full article PDF.

Similar content being viewed by others

References

  • Basili, V. R., and Rombach, H. D. 1988. The TAME project: Towards improvement-oriented software environments. IEEE Transactions on Software Engineering 14(6): 758–774.

    Google Scholar 

  • Courtney, R. E., and Gustafson, D. A. 1993. Shotgun correlations in software measures. Software Engineering Journal 8(1): 5–13.

    Google Scholar 

  • Fenton, N. E., Pfleeger, S. L., and Glass, R. L. 1994. Science and substance: A challenge to software engineers. IEEE Software 11(4): 86–95.

    Google Scholar 

  • Fenton, N. E., and Pfleeger, S. L. 1996. Software Metrics, A Practical and Rigorous Approach. International Thompson Computer Press.

  • Glass, R. L. 1994. The software research crisis. IEEE Software 11(6): 42–47.

    Google Scholar 

  • Galliers, R. D. 1991. Choosing appropriate information systems research approaches: a revised taxonomy. Information Systems Research: Contemporary Approaches and Emergent Traditions, Eds. Nissen, H. E., Klein, H. K., and Hirshheim, R. North Holland: Elsevier Science Publishers B. V., 327–345.

  • Harrison, R., and Wells, M. J. 1999. Multidisciplinary and interdisciplinary research methods and their impact on software and systems design. Workshop on Empirical Studies of Software Maintenance, Oxford.

  • Kitchenham, B. A. 1996. Series on experimentation in software engineering. ACM Software Engineering Notes.

  • Lehman, M. M., and Belady, L. A. 1976. A model of large system development. IBM Systems Journal 15(3): 225–252.

    Google Scholar 

  • Nandhakumar, J., and Jones, M. 1997. Too close for comfort? Distance and engagement in interpretive information systems research. Information Systems Journal 7: 109–131.

    Google Scholar 

  • Pfleeger, S. L. 1993. Lessons learned in building a corporate metrics program. IEEE Software 67–74.

  • Pulford, K., Kuntzmann-Combelles, A., and Shirlaw, S. 1996. A Quantitative Approach to Software Management. Addison Wesley.

  • Scanlan, D. A. 1989. Structured flowcharts outperform pseudocode: an experimental comparison. IEEE Software 6(5): 28–36.

    Google Scholar 

  • Seaman, C. B. 1999. Information sources for software maintenance: a proposal. Proceedings of the Workshop on Empirical Studies of Software Development and Evolution (ESSDE'99) LA, 96–100.

  • Shneiderman, B. 1984. Measuring computer program quality and comprehension. International Journal of Man-Machine Studies 3: 465–478.

    Google Scholar 

  • Zelkowitz, M. V., and Wallace, D. 1998. Experimental models for validating technology. IEEE Computer 31(5): 28–31.

    Google Scholar 

Download references

Author information

Authors and Affiliations

Authors

Rights and permissions

Reprints and permissions

About this article

Cite this article

Harrison, R., Badoo, N., Barry, E. et al. Directions and Methodologies for Empirical Software Engineering Research. Empirical Software Engineering 4, 405–410 (1999). https://doi.org/10.1023/A:1009877923978

Download citation

  • Issue Date:

  • DOI: https://doi.org/10.1023/A:1009877923978

Keywords

Navigation