Retrieved from https://studentshare.org/information-technology/1639390-predictive-vs-adaptive-sdlc
https://studentshare.org/information-technology/1639390-predictive-vs-adaptive-sdlc.
PREDICTIVE VS. ADAPTIVE SDLC Predictive vs. Adaptive SDLC Affiliation I would like to be the part of a project that used adaptive software development life cycle (SDLC) instead of predictive SDLC. Basically, agile software development approach is known as adaptive SDLC and the majority of software developers now adopts agile for a variety of reasons. In fact, a large number of books and articles have been written in favor of adaptive approach. This approach provides an excellent support for accommodating changes at any stage.
It is an admitted fact that a change is inevitable and it occurs all the time throughout the project. However, the predictive SDLC approach does not provide any support for handling these changes and if it does, these changes are costly to accommodate (Cao & Ramesh, 2008; Salo, 2006).Some of the benefits of agile include (Cao & Ramesh, 2008; Salo, 2006):It provides an excellent support for changes. In fact, the customer can ask for change at any time.It focuses on active customer involvement.
A product is developed in incrementsSome of the pitfalls of this approach are (Cao & Ramesh, 2008; Salo, 2006):These methodologies do not encompass considerable documentation that is an essential part of the project.Sometimes the customer cannot participate, which causes considerable delay in developmentSome of the advantages of predictive approach are outlined below (Cao & Ramesh, 2008; Salo, 2006):This approach heavily emphasizes on documentationNormally, these approaches are well-established so it is easy to follow them.
Some of the disadvantages of this approach are (Cao & Ramesh, 2008; Salo, 2006):These methodologies do not accommodate changes.The development of larger documents can take lots of time.The customer does not participate in the development process so their feedback comes very late.ReferencesCao, L., & Ramesh, B. (2008). Agile Requirements Engineering Practices: An Empirical Study. IEEE Software, Volume 25 Issue 1, pp. 60-67.Salo, O. (2006). Enabling Software Process Improvement in Agile Software Development Teams and Organisations.
Finland: VTT Technical Research Centre.
Read More