Skip to main content
SpringerLink
Log in

Software — A performing science?

  • Published:
Annals of Software Engineering

Abstract

Technical issues are important for software work, but so are personal disciplines, teamworking skills, and application‐domain knowledge. Also, much like an artistic performance, first‐class software engineering requires constant practice, good technique, and effective coaching. The challenge of producing high‐quality large‐scale software products is substantial today and will be even more demanding in the future. Without concerted action, we cannot expect software organizations' capabilities to improve. To address these problems, the Software Engineering Institute (SEI) has developed the Personal Software Process (PSP) and the Team Software Process (TSP). This paper addresses the problems of software engineering and discusses the intellectual nature of software work. It then reviews the characteristics of this kind of work and describes the principal conditions for effective software performance. In the conclusion, the author makes some observations about the challenges ahead and the future actions required.

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

Access this article

Log in via an institution

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

Instant access to the full article PDF.

Institutional subscriptions

Similar content being viewed by others

References

  • Dyer, M. (1992), The Cleanroom Approach to Quality Software Development, Wiley, New York.

    Google Scholar 

  • Fagan, M. (1976), “Design and Code Inspections to Reduce Errors in Program Development,” IBM Systems Journal 15, 3.

  • Fagan, M. (1986), “Advances in Software Inspections,” IEEE Transactions on Software Engineering SE-12, 7.

  • Ferguson, P., W.S. Humphrey, S. Khajenoori, S. Macke, and A. Matvya (1997), “Introducing the Personal Software Process: Three Industry Case Studies,” IEEE Computer 30, 5, 24–31.

    Google Scholar 

  • Humphrey, W.S. (1995), A Discipline for Software Engineering, Addison-Wesley, Reading, MA.

    Google Scholar 

  • Humphrey, W.S. (1996), “Using a Defined and Measured Personal Software Process,” IEEE Software 13, 3, 77–88.

    Article  Google Scholar 

  • Humphrey, W.S. (1997), Introduction to the Personal Software Process, Addison-Wesley, Reading, MA.

    Google Scholar 

  • Humphrey, W.S. (1998), “Three Dimensions of Process Improvement, Part III: The Team Process,” Crosstalk 11, 2, 14–17.

    MathSciNet  Google Scholar 

  • Humphrey, W.S. (2000), Introduction to the Team Software Process, Addison-Wesley, Reading, MA.

    Google Scholar 

  • Johnson, J. (1995), “Chaos: The Dollar Drain of Project Failure,” Application Development Trends, 41–47.

  • Keil, M., P.E. Cule, K. Lyytinen, and R.C. Schmidt, (1998), “A framework for Identifying Software Project Risks,” Communications of the ACM 41, 11, 76–83.

    Article  Google Scholar 

  • Paulk, M.C. et al.(1995), The Capability Maturity Model: Guidelines for Improving the Software Process, Addison-Wesley, Reading, MA.

    Google Scholar 

  • Webb, D. and W.S. Humphrey (1999), “Using the TSP on the TaskView Project,” Crossstalk 12, 2, 3–10.

    Google Scholar 

Download references

Authors
  1. Watts S. Humphrey
    View author publications

    You can also search for this author in PubMed Google Scholar

Rights and permissions

Reprints and permissions

About this article

Cite this article

Humphrey, W.S. Software — A performing science?. Annals of Software Engineering 10, 261–271 (2000). https://doi.org/10.1023/A:1018995818261

Download citation

  • Issue Date:

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

Keywords

Search

Navigation