Why were the practitioners of alternative software development methods not satisfied with the traditional waterfall method?
Answers
There were a lot of reasons why the practitioners of alternate software development methods were not satisfied with the traditional waterfall development.
The traditional waterfall development employed the use of one-sided development flow which involved different stages like conception, initiation, analysis, design, construction, testing, deployment and maintenance.
All of the reason was directly or indirectly related to the risk factor associated with the waterfall method. Since a mistake made in an earlier stage can prove to be very expensive later on. Moreover, such a methodology could not be implemented with object-oriented programming.
There were numerous reasons why alternative software development methods practitioners were dissatisfied with traditional waterfall development.
Traditional waterfall development used a one-sided development flow, including stages such as conception, initiation, analysis, design, building, testing, deployment, and maintenance.
All of the reasons were related to the risk element associated with the waterfall approach, either directly or indirectly. Because a mistake made at an early stage can cost a lot of money later. Furthermore, object-oriented programming could not be used to build such an approach.
#SPJ2