Every program has a life cycle. It doesn’t matter how large or small the program is, or how many people are working on the project - all programs go through the same steps:
  1. 1.


  2. 2.

    Requirements gathering/exploration/modeling

  3. 3.


  4. 4.

    Coding and debugging

  5. 5.


  6. 6.


  7. 7.

    Maintenance/software evolution

  8. 8.




Wicked Problem User Story Software Development Project Pair Programming Evolutionary Prototype 
These keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.


Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.


  1. Beck, K. Extreme Programming Explained: Embrace Change. (Boston, MA: Addison-Wesley, 2000).Google Scholar
  2. Cockburn, A. Agile Software Development. (Boston, MA: Addison-Wesley, 2002).Google Scholar
  3. DeGrace, P. and L. H. Stahl. Wicked Problems, Righteous Solutions: A Catalogue of Modern Software Engineering Paradigms. (Englewood Cliffs, NJ: Yourdon Press, 1990.)Google Scholar
  4. DeMarco, T. Controlling Software Projects: Management, Measurement and Estimation. (Upper Saddle River, NJ: Yourdon Press, 1983.)Google Scholar
  5. Martin, R. C. Agile Software Development, Principles, Patterns, and Practices. (Upper Saddle River, NJ: Prentice Hall, 2003.)Google Scholar
  6. McConnell, S. Rapid Development: Taming Wild Software Schedules. (Redmond, WA: Microsoft Press, 1996.)Google Scholar
  7. Paulk, M. C. The Capability Maturity Model: Guidelines for Improving the Software Process. (Reading, MA: Addison-Wesley, 1995.)Google Scholar
  8. Rising, L. and N. S. Janoff. “The Scrum Software Development Process for Small Teams.” IEEE Software 17(4): 26–32. (2000)CrossRefGoogle Scholar
  9. Royce, W. W. Managing the Development of Large Software Systems. Proceedings of IEEE WESCON, IEEE Press. (1970)Google Scholar
  10. Takeuchi, H. and I. Nonaka. “The New New Product Development Game.” Harvard Business Review 64(1): 137–146. (1986)Google Scholar

Copyright information

© John Dooley 2011

Authors and Affiliations

  • John Dooley

There are no affiliations available

Personalised recommendations