Information Technology Reference
In-Depth Information
2.12 Conclusion
Variety in SDLC models and frameworks is great. We have discussed the most
prominent ones, but there are numerous other models, many of them hybrid in
nature and designed to respond to speci
c needs of speci
c projects or simply to
attempt a
flawless approach by combining various models and reducing their
individual weaknesses. This great variety means that the process of choosing which
model to adopt for a particular development project can be complicated. Never-
theless, there are certain fundamental aspects of the project that can facilitate the
decision.
The requirements of the system play a key role. If requirements are strict and
immutable, the team might adopt a waterfall approach, but if requirements are
expected to change often, or are not clearly de
ned at the start, the team will
probably adopt a more agile and/or iterative approach.
The deadline for the development of the system is also an important factor. It is
clear that if the schedule is tighter, a rigid step-by-step model based on extensive
documentation and late testing would be unreasonably slow,
thus excluding
waterfall models.
The project
uential factors. The larger the
project, the more rigid the model tends to be, because a large team comprised of
many developers makes agile responses more complicated. The location of the
teams is also a factor: If the teams involved in the project are geographically
dispersed, a waterfall-like model is probably the best approach, for the clarity of its
stages and tasks. An agile development, where tight communication is important, is
an approach that is more bene
'
is dimension is one of the most in
cial to small teams working closer together.
Finally, resources should always be taken into account. Projects that involve
intricate dynamics and demand the use of peculiar expertise and technology are
easier to accomplish with models of strict planning, such as the waterfall (Executive
Brief
2008
).
Choosing the right model for a project is a crucial step of system development,
so as IS continues to be fundamental to modern business and organizational con-
texts, SDLC models will continue to be developed, researched, and utilized.
References
Agarwal, R., Prasad, J., Tanniru, M., & Lynch, J. (2000). Risks of rapid application development.
Communications of the ACM, 43(11), 177
188.
Ambler, S. (2009). The Agile system development life cycle (SDLC). Retrieved from
http://www.
Balaji, S., Murugaiyan, M., (2012). Waterfall vs. V-Model vs. Agile: A comparative study on
SDLC. International Journal of Information Technology and Business Management 2(1),
26
-
30.
Beck, K., Beedle, M., Van Bennekum, A., Cockburn, A., Cunningham, W., Fowler, M., Grenning,
J., Highsmith, J., Hunt, A., Jeffries, R., Kern, J., Marick, B., Martin, R., Mellor, S., Schwaber,
-
Search WWH ::
Custom Search