Process Life Cycle Models
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:
Coding and debugging
KeywordsWicked 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.
- Beck, K. Extreme Programming Explained: Embrace Change. (Boston, MA: Addison-Wesley, 2000).Google Scholar
- Cockburn, A. Agile Software Development. (Boston, MA: Addison-Wesley, 2002).Google Scholar
- 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
- DeMarco, T. Controlling Software Projects: Management, Measurement and Estimation. (Upper Saddle River, NJ: Yourdon Press, 1983.)Google Scholar
- Martin, R. C. Agile Software Development, Principles, Patterns, and Practices. (Upper Saddle River, NJ: Prentice Hall, 2003.)Google Scholar
- McConnell, S. Rapid Development: Taming Wild Software Schedules. (Redmond, WA: Microsoft Press, 1996.)Google Scholar
- Paulk, M. C. The Capability Maturity Model: Guidelines for Improving the Software Process. (Reading, MA: Addison-Wesley, 1995.)Google Scholar
- Royce, W. W. Managing the Development of Large Software Systems. Proceedings of IEEE WESCON, IEEE Press. (1970)Google Scholar
- Takeuchi, H. and I. Nonaka. “The New New Product Development Game.” Harvard Business Review 64(1): 137–146. (1986)Google Scholar
© John Dooley 2011