Professional Documents
Culture Documents
Next, it defines the requirements of the new system. It then creates the software
through the stages of analysis, planning, design, development, testing, and
deployment. By anticipating costly mistakes like failing to ask the end-user or
client for feedback, SLDC can eliminate redundant rework and after-the-fact.
Waterfall
Agile
Iterative
V-Shaped
3.1 WATERFALL
Some experts argue that the Waterfall model was never meant to be a process
model for real projects (check out the discussion on this topic on Stack
Exchange). Regardless, the Waterfall model is widely considered the oldest of
the structured SDLC methodologies. It’s also a very straightforward approach:
finish one phase, then move on to the next. No going back. Each stage relies on
information from the previous stage and has its own project plan.
The downside of Waterfall is its rigidity. Sure, it’s easy to understand and simple
to manage. But early delays can throw off the entire project timeline. With little
room for revisions once a stage is completed, problems can’t be fixed until you
get to the maintenance stage. This model doesn’t work well if flexibility is needed
or if the project is long term and ongoing. (Robert Half, May 2019)
3.2 AGILE
The Agile model has been around for about a decade. But lately, it has become
a major driving force behind software development in many organizations. Some
businesses value the Agile methodology so much that they are now applying it to
other types of projects, including non-tech initiatives.
In the Agile model, “fast failure” is a good thing. The approach produces ongoing
release cycles, each featuring small, incremental changes from the previous
release. At each iteration, the product is tested. The Agile model helps teams
identify and address small issues on projects before they evolve into more
significant problems, and engage business stakeholders and get their feedback
throughout the development process.
As part of their embrace of this methodology, many teams are also applying an
Agile framework known as Scrum to help structure more complex development
projects. Scrum teams work in “sprints,” which usually last two to four weeks, to
complete assigned tasks. Daily Scrum meetings help the whole team monitor progress
throughout the project. And the ScrumMaster is tasked with keeping the team focused
on its goal. (Robert Half[ CITATION Ris \l 1033 ], May 2019)
3.3 ITERATIVE
The Iterative model is repetition incarnate. Instead of starting with fully known
requirements, project teams implement a set of software requirements, then test,
evaluate and pinpoint further requirements. A new version of the software is
produced with each phase, or iteration. Rinse and repeat until the complete
system is ready.
Advantages of the Iterative model over other common SDLC methodologies is
that it produces a working version of the project early in the process, and makes
it less expensive to implement changes. One disadvantage: Repetitive processes
can consume resources quickly.
(Robert Half, May 2019)
4.0 BIBLIOGRAPHY
Alexandria, Alvander., April 8,2019. https://stackify.com/what-is-sdlc/
Robert Half..May 2019. https://www.roberthalf.com/blog/salaries-and-skills/6-basic-sdlc-
methodologies
Dharmendra Kumar,May 21,2020
https://www.geeksforgeeks.org/software-engineering-sdlc-v-model/
Rishabh Sinha, Oct 9,2020 https://www.esds.co.in/blog/introduction-to-software-
development-life-cycle-sdlc-phases-models/#sthash.l8i9aHJ0.HdMDnlM4.dpbs
5.0 HOW RISK IS MANAGED IN THESE LIFECYCLE
the risks of Waterfall methodology are mitigated and expired with the help of Waterfall risk
management. It uses a number of tools typical for Waterfall. Their main feature is the ability to
create charts. The risks in Waterfall are also managed with the help of charts.
The risk chart begins when the risk is detected. After that the managers follow its development.
If the risk develops along with the project, its line in the chart goes up. In such cases the
developers and managers try to find the product features that are strengthening the risk and
replace them. If the risk line in the chart goes down along with the project development, the risk
is considered low prioritized.
The risk charts in Waterfall are subdivided into three sections. The first of them begins when the
risk is detected and ends when the developers start to search for its solution. The second phase
lasts until the solution is found. The third phase is the phase of risk removal. It ends in the risk
expiry date. Such model of risk management allows Waterfall developers to avoid lots of bugs in
their production and improve its quality and customer acceptance.