Skip to main content
SpringerLink
Log in
Book cover

Managing Software Engineering Knowledge pp 29–47Cite as

An Investigation into Software Development Process Knowledge

  • Chapter

Abstract

Knowledge management elevates individual knowledge to the organizational level by capturing and sharing information and turning it into organizational knowledge. In order to provide a better understanding of the most serious software project risks and the interrelations among risks, we collected software project data from developers. This data includes information about senior management, customers and users, requirements, estimation and scheduling, the project manager, the software development process, and development personnel. In order to elevate our data to organizational knowledge we conducted a variety of studies on this data and found that the most critical success factor was good requirements. Other critical success factors were either influenced by the requirements, or themselves influenced the development of the requirements.

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

Chapter
USD   29.95
Price excludes VAT (USA)
  • Available as PDF
  • Read on any device
  • Instant download
  • Own it forever
eBook
USD   84.99
Price excludes VAT (USA)
  • Available as EPUB and PDF
  • Read on any device
  • Instant download
  • Own it forever
Softcover Book
USD   109.00
Price excludes VAT (USA)
  • Compact, lightweight edition
  • Dispatched in 3 to 5 business days
  • Free shipping worldwide - see info
Hardcover Book
USD   109.99
Price excludes VAT (USA)
  • Durable hardcover edition
  • Dispatched in 3 to 5 business days
  • Free shipping worldwide - see info

Tax calculation will be finalised at checkout

Purchases are for personal use only

Learn about institutional subscriptions

Preview

Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

References

  1. Amoako-Gyampah K., White K.B., (1997) When is user involvement not user involvement. Information strategy: the executive’s journal, 13: 40–45

    Google Scholar 

  2. Baccarini D., (1999) The logical framework method for defining project success. Project management journal, 30: 25–32

    Google Scholar 

  3. Basili V, Belady L., Boehm B., Brooks F., Browne J., DeMillo R., Feldman S.I., Green C., Lampson B., Lawrie D., Leveson N., Lynch N., Weiser M., Wing J. (1999) Final report. In: NSF workshop on a software research program for the 21st century, software engineering notes, 24: 3

    Google Scholar 

  4. Beizer B. (1984) Software system testing and quality assurance. Van Nostrand Reinhold Company, New York, USA

    Google Scholar 

  5. Bennatan E.M. (2000) On time, within budget. John Wiley and Sons, UK

    Google Scholar 

  6. Boehm B.W., Basili V., (2000) Gaining intellectual control of software development. IEEE Software, 33: 27–33

    Google Scholar 

  7. Boehm B.W., (1981) Software engineering economics. Prentice Hall, Englewood Cliffs, NJ, USA

    Google Scholar 

  8. Boehm B.W. (1991) Software risk management: principles and practices. IEEE Software, 1: 32–41

    Article  Google Scholar 

  9. Brooks F.P. Jr., (1975) The mythical man month. Essays on software engineering, Addison Wesley, USA

    Google Scholar 

  10. Carr M.J., Konda S., Monarch I., Ulrich C., Walker C. (1993) Taxonomy-based risk identification. Software engineering institute, Carnegie-Mellon university, technical report CMU/SEI-93-TR-6

    Google Scholar 

  11. Charette R.N., (1989) Engineering risk analysis and management. McGraw-Hill New York, USA

    Google Scholar 

  12. Clavadetscher C. (1998) User involvement key to success. IEEE Software, 15: 30–32

    Article  Google Scholar 

  13. Cohen J. (1960) A coefficient of agreement for nominal scales. Educational and psychological measurement, 20: 37–46

    Article  Google Scholar 

  14. Davis F.D. (1989) Perceived usefulness, perceived ease of use and user acceptance of information technology. MIS quarterly, 13: 319–339

    Article  Google Scholar 

  15. DeMarco T. (2001) Keynote speech at the international conference on software metrics, London, April 4

    Google Scholar 

  16. DeMarco T., (1991) Non-technical issues in software engineering. In: Proceedings of IEEE Conference on software engineering, Austin, Texas, pp. 149–150

    Google Scholar 

  17. DeMarco T., (1995) What “lean and mean” really means. IEEE Software, 12: 101–102

    Article  Google Scholar 

  18. DeMarco T., Lister T. (1989) Software development: state of the art vs state of the Practice. In: Proceedings of IEEE conference on software engineering, Pittsburgh, USA, pp. 271–275

    Google Scholar 

  19. DeMarco T., Lister T. (1999) Peopleware: productive projects and teams. Dorset House Publishing Co. New York, NY

    Google Scholar 

  20. Evanco W., Procaccino J.D., Verner J.M. (2002) Software project success: a path analysis. Submitted to IEEE transaction on engineering management

    Google Scholar 

  21. Fenton N.E., Neil M. (2002) Software metrics: roadmap. In: Finkelstein A. (Ed.), The future of software engineering, 22nd international conference on software engineering, ACM press, pp. 357–370

    Google Scholar 

  22. Garrity E.J., Saunders G.L. (1998) Introduction to information systems success measurement. In: Garrity E., Saunders L. (Eds.), Information system success measurement, Idea publishing group, Hershey, Pennsylvania, pp. 1–12

    Google Scholar 

  23. Gefen D. (2000) It is not enough to be responsive: the role of cooperative intentions in MRP II Adoption. The DATA BASE for advances in information systems, 31: 65–79

    Google Scholar 

  24. Gefen D., Keil M. (1998) The impact of developer responsiveness on perceptions of usefulness and ease of use: an extension of the technology acceptance model. The DATA BASE for advances in information systems, 29: 35–49

    Article  Google Scholar 

  25. Gefen D., Straub D. (2000) The relative importance of perceived ease-of-use in IS adoption: a study of e-commerce adoption. JAIS, 1: 1–30

    Google Scholar 

  26. Glass RL., (1998) Software runaways. Prentice-Hall, Upper Saddle River, New Jersey

    Google Scholar 

  27. Glass R.L. (1999) Evolving a new theory of project success. Communications of the ACM, 42: 17–19

    Google Scholar 

  28. Hagerty N. (2000) Understanding the link between IT project manager skills and project success: research in progress. In: Proceedings of SIGCPR conference, Evanston, IL, USA, pp. 192–195

    Google Scholar 

  29. Hair J.F., Jr., Anderson R.E., Tatham R.L., Black W.C. (1995) Multivariate data analysis with readings. Prentice Hall, Englewood Cliffs, NJ

    Google Scholar 

  30. Higuera R., Haimes Y. (1996) Software risk management. Software engineering institute, Technical report, CMU/SEI-TR-012

    Google Scholar 

  31. Hoffman T. (1999) Study: 85% of IT departments fail to meet business needs. Computerworld, 33: 24

    Google Scholar 

  32. Humphrey W.S. (1988) Characterizing the software process: a maturity framework. IEEE Software, 5: 73–79

    Article  Google Scholar 

  33. Ishman M. (1998) Measuring information systems success at the individual level in cross-cultural environments. In: Garrity E., Saunders L. (Eds.), Information system success measurement, Idea publishing group, Hershey, Pennsylvania, pp. 60–68

    Google Scholar 

  34. Johnston J. (1999): (The Standish group), Turning CHAOS into success. Software magazine, 19: 30–39

    Google Scholar 

  35. Johnston J. (1999): (The Standish group) The ghost of Christmas future: small movements spell where big shifts will come. Software magazine, 19: 15–17

    Google Scholar 

  36. Jones C, (1995) Patterns of large systems failure and success IEEE Computer, 28: 86–87

    Google Scholar 

  37. Katchigan S.K. (1986) Statistical analysis - an introduction to interdisciplinary introduction to Univariate and multivariate methods. Radius press, New York, USA

    Google Scholar 

  38. Keil M., (1995) Pulling the plug: software project management and the problems of project escalation. MIS quarterly, 19: 421–444

    Article  Google Scholar 

  39. Keil M., Montealegre R. (2000) Cutting your losses: extricating your organization when a big project goes awry. Sloan management review, 41: 55–68

    Google Scholar 

  40. Kellner M.I. (1991) Non-technical numbers in software engineering (Panel Session Overview). ICSE, Austinn, USA, pp. 149–150

    Google Scholar 

  41. Linberg K.R. (1999) Software developer perceptions about software project failure: a case study. Journal of systems and software, 49: 177–192

    Article  Google Scholar 

  42. McConnell S. (1996) Rapid development. Microsoft Press, Redmond, Washington

    Google Scholar 

  43. Miles M., Huberman M. (1994) Qualitative data analysis: an expanded sourcebook, Sage Publication, USA

    Google Scholar 

  44. Nolan A.J. (1999) Learning from success. IEEE Software, 16: 97–105

    Article  Google Scholar 

  45. NSF (2000) Final report. In: NSF workshop on a software research program for the 21st century http://www.cs.umd.edu/projects/SoftEng/tame/nsfw98/FinalRep.rtf (accessed 17th April, 2003)

    Google Scholar 

  46. Paulk M., Curtis B., Chrissis M., Webster C. (1993) Capability maturity model for software. In: Technical report, CMU/SEI-93-TR-024, Software engineering institute, Carnegie Mellon, Pittsburgh, USA

    Google Scholar 

  47. Pedhazur E.J. (1982) Multiple regression in behavioral research: explanation and prediction. Holt, Rinehart and Winston, New York, NY, USA

    Google Scholar 

  48. Pinto J.K., Mandel S.J. (1990) The causes of project failure. IEEE transactions on engineering management, 34: 269–276

    Article  Google Scholar 

  49. Pinto J.K., Slevin D.P. (1988) Project success: definitions and measurement techniques. Project management journal, 19: 67–72

    Google Scholar 

  50. Pfleeger S.L. (1998) Software engineering: theory and practice. Prentice-Hall, ( Englewood Cliffs, NJ

    Google Scholar 

  51. Pressman R. (1996) Software engineering: a practitioners approach, McGraw Hill, London, UK

    Google Scholar 

  52. Pressman R. (1998) Fear of trying: the plight of rookie project managers. IEEE Software, 15: 50–54

    Article  Google Scholar 

  53. Procaccino J.D., Verner J.M. (2000) Early risk factors for software development. In: Proceedings of the 12th European software control and metrics conference, London, pp.107–116

    Google Scholar 

  54. Procaccino J.D., Verner J.D., Overmyer S.P., Darter, M. (2002) Case study: factors For early prediction of software development success. Information and software technology, 44: 53–62

    Article  Google Scholar 

  55. Procaccino J.D., Verner J.D. (2002) Software practitioner’s perception of project success: a pilot study. International journal of the computer, the Internet and management, 10: 20–30

    Google Scholar 

  56. Raz T., Michael E. (2002) Use and benefits for project risk management. International journal of project management, 19: 9–12

    Article  Google Scholar 

  57. Reifer D.J. (2002) A little bit of knowledge is a dangerous thing. IEEE Software, 19: 14–15

    Article  Google Scholar 

  58. Ropponen J., Lyytinen K. (2000) Components of software development risk: how to address them? A project manager survey. IEEE transactions on software engineering, 26: 98–112

    Article  Google Scholar 

  59. Rus I., Lindvall M. (2002) Knowledge management in software engineering. IEEE Software, 19: 26–38

    Article  Google Scholar 

  60. Schenk K.D., Vitalari N.P., Shannon D. (1998) Differences between novice and expert systems analysts: what do we know and what do we do? Journal of management information systems, 15: 9–51

    Google Scholar 

  61. Standish Group (1994) CHAOS, http://www.pm2go.com/sample_research (accessed date 17th April)

    Google Scholar 

  62. Schumacker R.E., Richard G.L. (1996) A beginner’s guide to structural equation modeling. Lawrence Erlbaum Associates, Mahwah, NJ, USA

    Google Scholar 

  63. Verner J., Evanco W. (2000) The state of the practice of software effort estimation in business organizations. In: Proceedings of ESCOM-SCOPE, Munich, Germany, pp. 229–237

    Google Scholar 

  64. Verner J.,W., Evanco W., Cerpa N. (2002) How important is effort estimation to software development success? Submitted to the journal of empirical software engineering research

    Google Scholar 

  65. Verner J.M, Overmyer S.P., McCain, K.W. (1999) In the 25 years since the mythical man-month what have we learned about project management? Information and software technology, 4: 1021–1026

    Article  Google Scholar 

  66. Wang Y., Court I., Ross M., Staples G., King G., Dorling A. (1997) Quantitative evaluation of SPICE, CMM, ISO 9000 and BOOTSTRAP. In: Proceedings of the 3rd IEEE international symposium on software engineering standards, IEEE computer society press, USA, pp. 57–68

    Google Scholar 

  67. Ward S.C., Chapman C.B. (1995) Risk management perspective on the project lifecycle. International journal of project management, 13: 145–149

    Article  Google Scholar 

  68. Wateridge J. (1995) IT projects: a basis for success. International journal of project management, 13: 169–172

    Article  Google Scholar 

  69. Wateridge J. (1998) How can IS/IT projects be measured for success? International journal of project management, 16: 59–63

    Article  Google Scholar 

  70. Wohlin C., Mayrhauser A. von, Host M., Regnell B. (2000) Subjective evaluation as A tool for learning from software project success. Information and software technology, 42: 983–992

    Article  Google Scholar 

  71. Wohlin C., Amscheler Andrews A. (2001) Assessing project success using subjective evaluation factors. Software quality journal, 9: 43–70

    Article  Google Scholar 

  72. Woodroof J., Kasper G.M. (1998) A conceptual development of process and outcome user satisfaction. In: Garrity E., Saunders L. ( Eds. ), Information system success

    Google Scholar 

Download references

Authors
  1. June M. Verner
    View author publications

    You can also search for this author in PubMed Google Scholar

  2. William M. Evanco
    View author publications

    You can also search for this author in PubMed Google Scholar

Editor information

Editors and Affiliations

  1. School of Information Systems, Technology and Management, University of New South Wales, NSW, 2052, Sydney, Australia

    Aybüke Aurum  & Meliha Handzic  & 

  2. School of Computer Science and Engineering, University of New South Wales, NSW, 2052, Sydney, Australia

    Ross Jeffery

  3. Dept. of Software Engineering and Computer Science, Blekinge Institute of Technology, Box 520, SE-372 25, Ronneby, Sweden

    Claes Wohlin

Rights and permissions

Reprints and permissions

Copyright information

© 2003 Springer-Verlag Berlin Heidelberg

About this chapter

Cite this chapter

Verner, J.M., Evanco, W.M. (2003). An Investigation into Software Development Process Knowledge. In: Aurum, A., Jeffery, R., Wohlin, C., Handzic, M. (eds) Managing Software Engineering Knowledge. Springer, Berlin, Heidelberg. https://doi.org/10.1007/978-3-662-05129-0_2

Download citation

  • DOI: https://doi.org/10.1007/978-3-662-05129-0_2

  • Publisher Name: Springer, Berlin, Heidelberg

  • Print ISBN: 978-3-642-05573-7

  • Online ISBN: 978-3-662-05129-0

  • eBook Packages: Springer Book Archive

Publish with us

Policies and ethics

Search

Navigation