As follows : Break the development cycle into phases: a) Envisioning phase b) Planning phasec) Developing phase d) Stabilizing phase.
Usually code is fouled up after it has been successfully developed. So "stabilizing phase" sounds like it could work.
Do I need a "Stabilizing Phase" in the software development cycle ?
The stabilizing one is the phase at which after you have been testing and finding bugs you have gone without finding new ones. It is not a great thing to skip because you may have introduced bugs fixing old ones, which is what this phase detects.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment