Goal-Driven Software Development Process: Difference between revisions

Revision as of 01:29, 10 March 2011

Revision as of 07:14, 6 October 2011

Line 13:

== Justification ==

The first argument to embrace the GDP principles is the aspect of requirements. When developing a software, the strong concentration on requirements (e.g. typical for the [[waterfall model]]) causes excessive costs and reduced quality of the outcome, mainly due to the following reasons<ref name="GDSD" />:

* Requirements are usually not identical with business objectives because of the author’s limited knowledge about technical possibilities and their costs – such requirements tend to include unnecessary expensive wishes while excluding technically simple features that would provide substantial benefit.