Author Topic: SDLC Methodology  (Read 602 times)


  • Global Moderator
  • Newbie
  • *****
  • Posts: 2
SDLC Methodology
« on: October 24, 2016, 09:06:46 am »
How do we select an SDLC methodology and know which SDLC is ideal for the project we work on?


  • Guest
Re: SDLC Methodology
« Reply #1 on: November 16, 2016, 10:49:45 pm »
A company selects an SDLC based on the client's requirements.
 Also, it depends on,
 The nature of the requirements (if there is scope for changes in the requirements),
 Time Span - Long Term or short term
 If client needs an early delivery of a working software,
 Risk involved,


  • Global Moderator
  • Newbie
  • *****
  • Posts: 13
Re: SDLC Methodology
« Reply #2 on: April 17, 2017, 05:38:47 pm »
It depends on the type of the project and project requirements.
The following are the methodologies and their usage as per the project scenarios.
1. Sequential - When the client is well defined requirements in the beginning of the project and the phases are covered one at a time.
2. Iterative - It develops iterations of the service/ product and focuses on high quality and less risk.
3. Evolutionary - It is good for large and critical projects where lot of risk is involved.
4. Agile - When requirements are not clear initially. Here the product/service goes through change requests and client wants the deliverables at short timespans.

We usually follow agile as with changing trends, we have changing mindsets and requirements and that can be easily accommodated in an agile project.


  • Newbie
  • *
  • Posts: 26
Re: SDLC Methodology
« Reply #3 on: September 19, 2017, 04:53:58 pm »
The type of project and project requirements plays an important role in selecting the type of SDLC methodology and model to be used :-

1. Sequential : When its a small project and all the requirements are very well known, one can use this methodology.

2. Iterative : When the requirements of the complete system are clearly defined and understood. When the project is big.

3. Evolutionary : It is good for large and critical projects where lot of risk is involved.

4. Agile : When the requirements are not clear initially and there is a high chance of Change requests, this methodology can be used.


  • Global Moderator
  • Newbie
  • *****
  • Posts: 10
Re: SDLC Methodology
« Reply #4 on: October 10, 2017, 05:03:46 pm »
the different SDLC methodologies are:
1. waterfall
2. spiral
3. iterative/ rational
4. scrum / agile
 the selection of methodology depends on the type of requirement of the project


  • Global Moderator
  • Newbie
  • *****
  • Posts: 11
Re: SDLC Methodology
« Reply #5 on: November 11, 2017, 09:42:30 am »
Software development life cycle (SDLC) is important for the software project success, the good software engineer should have the enough experience and knowledge to prefer an choose one model than another based on the project context.

Therefore, it may be required to choose the right SDLC model according to the specific concerns and requirements of the project. I wrote another article on how to choose the right SDLC, you can follow this link for more information.

In this article, we will explore the different types of SDLC models and the advantages and disadvantages of each one and when to use them.

Types of Software developing life cycles (SDLC)
Waterfall Model
V-Shaped Model
Evolutionary Prototyping Model
Spiral Method (SDM)
Iterative and Incremental Method
Agile development


  • Global Moderator
  • Newbie
  • *****
  • Posts: 1
Re: SDLC Methodology
« Reply #6 on: November 28, 2017, 03:00:04 pm »
SDLC is a process followed for a software project, within a software organization. It consists of a detailed plan describing how to develop, maintain, replace and alter or enhance specific software. The life cycle defines a methodology for improving the quality of software and the overall development process.
 There are a number of different SDLC methodologies that can be used to deliver projects and in this post, Below is the overview of the different SDLC models out there and their advantages and disadvantages.

1. Waterfall Model
Waterfall is the oldest and most straightforward of the structured SDLC methodologies. There are strict phases and each phase needs to be completed first before going to the next phase. There is no going back.Each phase relies on information from the previous stage and has its own project plan.

2.V Model
V Model is also known as the Verification and Validation model, was the next logical step from the Waterfall model with the aim of introducing testing at each stage of development rather than at the end of the project.
The advantage of V Model is that each stage has a corresponding testing activity which helps to identify missing requirements, and incorrect design early in the life cycle.

The disadvantage is that the each stage has to wait for the previous stage to be finalized and signed off.
3.Iterative model
The basic idea behind this method is to develop a system through repeated cycles (iterative) and in smaller portions at a time (incremental), allowing software developers to take advantage of what was learned during the development of earlier parts or versions of the system.

4.Spiral model
The development team in Spiral-SDLC model starts with a small set of requirement and goes through each development phase for those set of requirements. The development team adds functionality for the additional requirement in every-increasing spirals until the application is ready for the production phase.

The agile model is a combination of both iterative and incremental model by breaking a product into components where on each cycle or iteration, a working model of a component is delivered.
The Agile model emphasizes collaboration, as the customers, developers and testers work together throughout the project.

An advantage of the Agile model is that it quickly delivers a working product and is considered a very realistic development approach.
One disadvantage of this model is that because it depends heavily on customer interaction, the project can head the wrong way if the customer is not clear about the requirements or the direction he or she wants to go.


  • Global Moderator
  • Newbie
  • *****
  • Posts: 6
Re: SDLC Methodology
« Reply #7 on: December 05, 2017, 12:49:01 pm »
Software Development Life Cycle (SDLC) is a process used by the software industry to design, develop and test high quality softwares. It is important for the software project success. It consists of a detailed plan describing how to develop, maintain, replace and alter or enhance specific software.
Here are five SDLC methodologies, or models, that development teams use in this effort:
1. Agile
2. Waterfall
3. Iterative
4. Spiral
5. V-shape Model


Agile SDLC model is a combination of iterative and incremental process models with focus on process adaptability and customer satisfaction by rapid delivery of working software product. Agile Methods break the product into small incremental builds. These builds are provided in iterations. Each iteration typically lasts from about one to three weeks. Every iteration involves cross functional teams working simultaneously on various areas like −

Requirements Analysis
Unit Testing and
Acceptance Testing


The Waterfall Model was the first Process Model to be introduced. It is also referred to as a linear-sequential life cycle model. It is very simple to understand and use. In a waterfall model, each phase must be completed before the next phase can begin and there is no overlapping in the phases.

The Waterfall model is the earliest SDLC approach that was used for software development.

The waterfall Model illustrates the software development process in a linear sequential flow. This means that any phase in the development process begins only if the previous phase is complete. In this waterfall model, the phases do not overlap.


In the Iterative model, iterative process starts with a simple implementation of a small set of the software requirements and iteratively enhances the evolving versions until the complete system is implemented and ready to be deployed.

An iterative life cycle model does not attempt to start with a full specification of requirements. Instead, development begins by specifying and implementing just part of the software, which is then reviewed to identify further requirements. This process is then repeated, producing a new version of the software at the end of each iteration of the model.


The spiral model combines the idea of iterative development with the systematic, controlled aspects of the waterfall model. This Spiral model is a combination of iterative development process model and sequential linear development model i.e. the waterfall model with a very high emphasis on risk analysis. It allows incremental releases of the product or incremental refinement through each iteration around the spiral.


The V-model is an SDLC model where execution of processes happens in a sequential manner in a V-shape. It is also known as Verification and Validation model.

The V-Model is an extension of the waterfall model and is based on the association of a testing phase for each corresponding development stage. This means that for every single phase in the development cycle, there is a directly associated testing phase. This is a highly-disciplined model and the next phase starts only after completion of the previous phase.