NAME: NJOBEH BRANDON

POPULAR SDLC MODELS

Waterfall Model

The Waterfall model, also known as the linear-sequential life cycle model, is primarily a
linear project management approach. It involves a step-by-step process for developing
software applications, sequentially progressing through stages. The process begins with
gathering stakeholder and user requirements at the project’s outset. Subsequently, a sequential
project plan is developed to meet those specific needs. The term “Waterfall” is q uite
descriptive, signifying the software development process unfolding in distinct phases, with
each starting only after the completion of the previous phase.

Phases of the Waterfall SDLC Model:

 Advantages of the Waterfall SDLC Model:

• It is easy to use and understand.

• It handles each process individually with no overlaps, ensuring clarity and

organization.

• It is well-suited for smaller projects with clearly understood requirements.

• It is straightforward and helps identify critical points in the development cycle.

• It helps to classify and prioritize tasks easily.

Disadvantages of the Waterfall SDLC Model:

Despite several advantages, the Waterfall model has some shortcomings. Here are some of the
limitations of the Waterfall SDLC model.

• The software is considered ready after completing the last stage.

• It involves high levels of risk and uncertainty.

• It is unsuitable for complex and object-oriented projects.

• This SDLC model is unsuitable for long-term projects.

Applications of the Waterfall SDLC Model:

In this section, we will learn about some practical applications of the Waterfall SDLC model.

• Large-scale Software Development Projects: It is frequently used in large-scale

software development projects. Its structured and sequential approach is beneficial to
ensure timely and budget-compliant project completion.

• Safety-Critical Systems: It is commonly applied in developing safety-critical systems

like aerospace or medical systems. Its usage is essential in environments where errors
or defects could have severe consequences.
 • Government and Defense Projects: It often opts for government and defense projects
due to its rigorous and structured nature. This approach ensures that the project meets
all requirements and is delivered on time.

• Projects with Well-defined Requirements: It best suits projects with well-defined

requirements. Its sequential nature demands a clear understanding of project objectives
and scope.

V-Shaped Model

The V-model, or Verification and Validation model, extends the traditional Waterfall model
by aligning development (verification) and testing (validation) and stages. This implies that
each phase is directly connected to the testing phase in the software development process,
forming a comprehensive and rigorous approach shaped like a ‘V.’ The left half of the V
represents Verification, the right half represents Validation, and both are connected by a
coding phase, creating its distinctive V shape.

Phases of the V-Model (Verification):

 Advantages of the V-Model:

In this section, we will delve into the benefits of the V-model within the SDLC model.

• It provides guidelines focusing on one phase at a time.

• It makes use of a simple and easy-to-understand framework.

• It establishes specific deliverables, making task delegation and progress tracking easy.

• It includes a review process for each phase to ensure accuracy.

• It promotes high-quality design and development.

• It includes exhaustive documentation for each phase.

Disadvantages of the V-Model:

Despite many advantages, the V-model has several shortcomings that can impact its
effectiveness:

• It is a structured approach that can be time-consuming for large projects.

• It is a rigid structure that can make alterations challenging.

• It delays implementation, reducing early prototype opportunities.

• It changes during software project execution and may require updates across all
phases.

Applications of the V-Model:

In this section, we will delve into the applications of the V-model within the SDLC model.

• Structured Software Development: It provides a systematic and structured approach

to software development, contributing to enhanced organization and overall efficiency.
 • Alignment of Development and Testing: It emphasizes the alignment of development
and testing activities; this SDLC model enables the early identification and resolution
of defects.

• Thorough Verification and Validation: It ensures comprehensive verification and

validation. This SDLC model rigorously tests the software throughout the entire
development lifecycle.

• Documentation and Traceability: It strongly emphasizes documentation and

traceability, promoting transparency and simplifying future enhancements.

• Adherence to Regulatory Requirements: It is commonly used in industries with

strict regulatory requirements. This SDLC model helps in compliance and adherence to
established guidelines.

• Collaboration and Communication: This SDLC model encourages collaboration

between development and testing teams, enhancing communication and teamwork.

• Project Management and Control: It serves as a framework for project management

and control; this SDLC model facilitates progress tracking and efficient resource
management.

Iterative Model

In the Iterative model, you initiate the software development process by implementing small
requirements set. Over successive iterations, these versions are enhanced until the entire
software application is ready for deployment. This approach enables continuous
improvements and changes at each development stage, eliminating the need to wait until the
project’s completion.

The advantage lies in having a functional piece of software early in the lifecycle, as the
iterative model starts with a basic execution of a limited set of requirements. This iterative
refinement continues until the complete application is implemented and ready for distribution.
Each release in the Iterative model adheres to a specific and predetermined time frame, known
as an iteration.

The repetitive process facilitates the creation of new software versions in each cycle. Lasting
from two to six weeks, each iteration involves the development of a distinct component of the
system, which is then integrated with earlier features. Importantly, bugs and errors from
previous iterations do not carry over, showcasing the model’s flexibility to incorporate user
feedback in every cycle.

Below, we will learn each phase in the Iterative model in detail.

Phases of the Iterative SDLC Model:

The Iterative model comprises seven stages or phases: requirement gathering, design,
implementation, testing, deployment, review, and maintenance. Let us get into more detail on
understanding each phase below.
 Advantages of the Iterative SDLC Model:

• It allows you to obtain working software early in the development lifecycle.

• It allows you to incorporate new functionalities at any point in development.

• It is cost-effective due to lower expenses for changing requirements than other models.

• It gives quick feedback from end-users and stakeholders and facilitates timely
implementation into the software application.

• It helps identify errors and bugs in the software application early in the iterative
process.

• It is suitable for smaller development teams to meet for this model compared to other
process models.

Disadvantages of the Iterative SDLC Model:

Despite many advantages, the Iterative SDLC model has several limitations that can impact its
effectiveness:

• It poses problems related to system architecture as all requirements are not gathered
upfront.

• It may not be the best choice for smaller projects due to its inherent complexity.

• It can be more resource-intensive than the Waterfall model.

• It requires specialized skills for risk analysis to evaluate risks in the system.

• It manages the entire iterative process and can be challenging due to its dynamic
nature.
 Applications of the Iterative SDLC Model:

• Clearly Defined System Requirements: It facilitates a smooth development process

when the requirements of the complete system are clearly defined and understood by
the development expertise.

• Evolution of Functionalities: It allows major system requirements to be defined

initially; however, some functionalities or requested enhancements may evolve.

• Flexibility in Resource Allocation: It allows flexibility in resource allocation if

resources with the required skill set are unavailable and planned to be used on a
contract basis for specific iterations.

• Opportunity for Skill Enhancement: It offers an opportunity for skill enhancement

when the development team uses and learns a new technology while working on the
project.

• Adaptation to High-Risk Features: It allows adaptation to evolving project

requirements if some high-risk features and goals may change.

• Time-to-Market Constraint Advantage: It provides the advantage of delivering

functional software in incremental releases when there is a time-to-market constraint.

Spiral Model

The Spiral model segments the software development life cycle into repetitive architecture
and prototyping stages, seamlessly merging iterative development with the structured aspects
of the Waterfall model. It’s a unique blend, emphasizing risk analysis and proving beneficial
by allowing the incorporation of elements from multiple process models based on unique risk
patterns, ensuring an efficient development process.

It is one of the most flexible methodologies, providing developers with significant freedom to
develop highly personalized software applications. The transition to the next stage occurs
even if the previous one is not fully completed, showcasing its adaptability and flexibility in
handling diverse development scenarios.

Phases in the Spiral SDLC Model:

The Spiral model comprises four stages or phases: determining objectives, risk analysis and
resolving, developing and testing, reviewing and planning for the next phase. A project
cyclically traverses these stages, forming a spiral within the model.

Advantages of the Spiral SDLC Model:

• It accommodates changing requirements, fostering flexibility throughout development.

• It allows for the extensive use of prototypes, facilitating a tangible representation of

the system’s evolving features.

• It enables more accurate requirement capture, enhancing the understanding of project

needs.

• It provides early user visibility, promoting transparency and aligning development

with user expectations.
 • It supports effective risk management by segmenting development into smaller parts,
enabling the prioritized development of riskier components. This helps in more
effective risk management.

Disadvantages of the Spiral SDLC Model:

Despite many advantages, the Spiral SDLC model has several limitations that can impact its
effectiveness:

• It becomes more complex due to its iterative and evolving nature.

• It may not be clear early in the process, introducing uncertainty.

• It may not be suitable for small or low-risk projects, potentially leading to increased
expenses.

• It requires careful navigation and oversight throughout the development life cycle.

• Its spiral may continue indefinitely, raising concerns about project timelines and
closure.

• Many intermediate stages necessitate extensive documentation, which can be a

drawback due to the associated resource investment.

Applications of the Spiral SDLC Model:

In this section, we will delve into the applications of the Spiral SDLC model.

• Modular Incremental Delivery: It divides software development into modules,

allowing incremental delivery to the customer from project inception. This modular
approach facilitates early customer engagement and adapts well to changing
requirements.
 • Adaptive and Flexible Development: It is a step-by-step process that supports an
adaptive and flexible development process. It accommodates changes seamlessly
during development, making improvements at each stage. This iterative nature is
advantageous for projects requiring responsiveness to evolving needs, making it
particularly suitable for web-based applications and integrated into mobile application
development for mobile apps.

Agile Model

The Agile model presents a highly practical and adaptive software testing and development
approach. Designed to meet the specific requirements of each project, it seamlessly integrates
Iterative and Incremental process models. The primary objective is to achieve adaptability and
user satisfaction by swiftly delivering functional software applications.

In Agile, projects are divided into cycles characterized by short time limits, ensuring the rapid
delivery of software. These cycles, referred to as iterations, typically span one to three weeks
within a Time Box timeframe.

Within each iteration in the Agile model, the development team concentrates on creating
small, incremental software builds. The Time Box, a fixed end date, determines the maximum
duration for delivering an iteration to clients. To meet deadlines, there are instances where the
team might opt to limit the functionality within a Time Box. This iterative and time -bound
approach ensures a focused and efficient development process.

Phases of the Agile SDLC Model:

The Agile model comprises six stages or phases: requirement gathering, design requirement,
development, test, deployment, and review. Let us get into more detail on understanding each
phase below.
 Advantages of the Agile SDLC Model:

• It enhances the ability to swiftly revert to previous stages with minimal time and low
costs in the Agile model.

• It boosts flexibility for development teams within the Agile model, allowing for
adaptability and responsive adjustments.

• It ensures short and well-defined Agile iteration, streamlining the development process
for better manageability.

• It embeds flexibility in the software project, effectively minimizing risks through the
Agile approach.

• It facilitates the easy release of the initial version of your operational software
application in Agile, showcasing progress sooner.

• It demands minimal resource requirements, enabling more efficient allocation of

resources in Agile.

• It enhances teamwork and encourages cross-training among team members, fostering a

collaborative environment within Agile.
 Disadvantages of the Agile model:

Despite many advantages, the Agile SDLC model has several limitations that can impact its
effectiveness:

• It measures the final software application cost might prove difficult in the Agile
model, adding a layer of complexity to your project management.

• Its new changes may not always seamlessly interact with the developed architecture,
potentially causing complications.

• Its software application might not meet its scheduled market release deadline, which
introduces uncertainty in your project timeline.

• It depends heavily on users, and their impact can steer the project in unexpected
directions, sometimes leading to challenging situations.

Applications of the Agile SDLC Model:

• Customer Satisfaction is a Top Priority: Its foremost goal is to ensure customer

satisfaction by delivering valuable software early and continuously.

• Embrace Changing Requirements: It welcomes changes in requirements, even in the

later stages of development, to adapt and enhance the software.

• Frequent Delivery of Working Software: It delivers the software regularly, aiming

for intervals ranging from a couple of weeks to a couple of months, with a preference
for shorter timescales.

• Empower Motivated Individuals: it builds projects around motivated individuals.

Provide them with the necessary environment, support, and trust to complete their
tasks successfully.

• Working Software as the Measure of Progress: It gauges progress primarily by

developing working software, emphasizing its functionality and tangible outcomes.
• Simplicity and Minimizing Unnecessary Work: It embraces simplicity – the art of
maximizing the amount of work not done – as an essential principle in the
development process.

• Effective Communication Through Face-to-Face Conversations: It acknowledges

that face-to-face conversations are the most efficient and effective means of conveying
information within a development team.

• Progress Gauged by Completed Work: It measures progress by the amount of work

completed, emphasizing tangible outcomes over theoretical advancements.

• Commitment to Excellence: It upholds a commitment to excellence and consistently

strives for the highest standards in software development.

• Leverage Change for Competitive Advantage: It embraces change as an opportunity

to gain a competitive edge, recognizing its potential for innovation and improvement.
Comparison Of The Five Most Popular SDLC Models:
1. Waterfall Model:
o Characteristics: Linear and sequential, with each phase completed before
moving to the next.
o Strengths: Simple to explain, allows for error verification.
o Weaknesses: Inflexible, does not allow changes, long cycle time.
o Use Case: Ideal for well-understood problems and short-duration projects.
2. Agile Model:
o Characteristics: Incremental and iterative, focusing on adapting to
changing requirements.
o Strengths: Rapid growth, high-quality outcomes, minimal resources
needed.
o Weaknesses: Requires frequent communication, can lead to higher costs.
o Use Case: Suitable for projects with changing requirements and high
uncertainty45.
3. V-Model:
o Characteristics: Combines Waterfall and Agile, allowing for flexibility
and adaptability.
o Strengths: Balances the rigidity of Waterfall with the flexibility of Agile.
o Weaknesses: Requires careful planning and execution.
o Use Case: Suitable for projects that require both structured phases and
flexibility.
4. Spiral Model:
o Characteristics: Incremental and iterative, with a focus on risk
management.
o Strengths: Effective for projects with high uncertainty.
o Weaknesses: May lead to longer project durations.
o Use Case: Ideal for projects where risk management is critical.
5. IRERATIVE Model
o Characteristics: Incremental development, focusing on delivering small,
manageable chunks of software.
 o Strengths: Reduces risk, allows for continuous improvement.
o Weaknesses: May lead to higher costs and complexity.
o Use Case: Suitable for projects that can be divided into manageable
chunks

This comparison highlights the strengths and weaknesses of each model, helping you choose the
most suitable approach for any project.