Abstract

The waterfall life cycle model suffers from a number of problems but in spite of this, it continues to be the most widely used life cycle model. A different life cycle approach is proposed that emphasizes the product life cycle rather than the project life cycle, quality management priorities rather than project management priorities and views of quality rather than views of the project schedule. A quality management tool based on different views of quality is used to identify the “gaps” that inevitably exist between a user’s needs, the requirements specification and the product that is delivered. This is followed by a brief discussion of how these “gaps” can be closed.

Keywords

Life Cycle Model Quality Software Waterfall 

Preview

Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

References

  1. 1.
    Laplante, P.A., Neill, C.J.: The Demise of the Waterfall Model and Other Urban Myths. Game Development 1(10) (February 2004)Google Scholar
  2. 2.
    Royce, W.: Managing the Development of Large Software Systems. In: Proceedings of IEEE WESCON (1970)Google Scholar
  3. 3.
    A Guide to the Project Management Body of Knowledge (PMBOK), The Project Management Institute (also available as IEEE Std 1490-2003) (2000)Google Scholar
  4. 4.
    Beck, K.: eXtreme Programming explained. Addison-Wesley, Reading (2000)Google Scholar
  5. 5.
    Powell, R.R.: Wabi Sabi Simple, Adams Media (2004)Google Scholar
  6. 6.
    AS 2561-1982: Guide to the determination and use of quality costs, Standards Australia (1982)Google Scholar
  7. 7.
    Garviv, D.: What Does ’Product Quality’ Really Mean? Sloan Management Review, 25–45 (Fall 1984)Google Scholar
  8. 8.
    George, M.L., et al.: The Lean Six Sigma Pocket Toolbook: A Quick Reference Guide to 100 Tools for Improving Quality and Speed. McGraw-Hill, New York (2004)Google Scholar
  9. 9.
    Boehm, B.: Escaping the software tar pit: model clashes and how to avoid them. In: SIGSOFT Software Engineering Notes, January 1999, vol. 24 (1999)Google Scholar
  10. 10.
    Glossary of Software Testing Terms, http://www.testingstandards.co.uk/glossary.htm (retrieved on August 1, 2008)
  11. 11.
    IEEE Std 1028-1997 IEEE Standard for Software Reviews, Institute of Electrical Engineers (1992)Google Scholar
  12. 12.
    OMG Unified Modeling Language (OMG UML), Superstructure, V2.1.2, Object management Group, OMG (2007)Google Scholar
  13. 13.
    Bersoff, E.H.: Elements of Software, Configuration Management. In: Dorfman, M., Thayer, R.H. (eds.) Software Engineering, IEEE Computer Society Press, Los Alamitos (1997)Google Scholar
  14. 14.
    Peng, W.W., Wallace, D.R.: Software Error Analysis. NIST Special Publication 500-209 (1993)Google Scholar
  15. 15.
    Beizer, B.: Software Testing Techniques. Van Nostrand Reinhold, New York (1990)Google Scholar
  16. 16.
    Boehm, B.: A spiral model of software development and enhancement. In: SIGSOFT Software Engineering (1986)Google Scholar
  17. 17.
    Cosby, P.: Quality is Free, New American Library (1979)Google Scholar

Copyright information

© Springer-Verlag Berlin Heidelberg 2009

Authors and Affiliations

  • Phil Robinson
    • 1
  1. 1.Lonsdale SystemsPerthAustralia

Personalised recommendations