“Shipping first time code is like going intodebt. A little debt speeds development so longas it is paid back promptly with a rewrite...The danger occurs when the debt is notrepaid. Every minute spent on not-quite-rightcode counts as interest on that debt. Entireengineering organizations can be brought to astand-still under the debt load of anunconsolidated implementation, object-oriented or otherwise.” Ward Cunningham
Technical DebtAs soon as you payit, less work youneed to fix it!
Sometimes clients doesntFACTS know exactly what requirements they need in their software Design solutions based on one requirement can be different if others are consideredThese facts create a risk to deliverwrong software to the client!
Traditional software engineeruses he same approach of other types of engineering projects!
Identify all Create a Construct basedrequirements complete project on the project Deliver the Test to verify the software requirements
Cost of Change Curve Using traditional style, it is cheaper to change in theCOST beginning TIME
Traditional software engineer put a lot of effort on requirements and project to avoid changes!