SDLC is an acronym for Software Development Life Cycle. It is also sometimes referred to as System Development Life Cycle. In simple words it the process or method applied to create or alter software projects. Each of these methodologies defines unique way to create a new software module or program. So what basically are the sdlc methodologies? There are basically five common types of approach and methodologies which builds the foundation pillar of the SDLC, viz- Waterfall model, Incremental Model, Spiral model, Prototyping model and Win-Win Spiral Model.

SDLC Definition

SDLC is a process used by IT analysts in order to develop or redesign high quality software system which meets both the customer and the real world requirement taking into consideration all associated aspects of pros and cons of software testing, analysis and post process maintenance. Continue reading →

The spiral Model includes the iterative nature of the prototyping model and the linear nature of the waterfall model. This approach is ideal for developing software that is revealed in various versions.

In each iteration of the spiral approach, software development process follows the phase-wise linear approach. At the end of first iteration, the customer evaluates the software and provides the feedback. Based on the feedback, software development process enters into the next iteration and subsequently follows the linear approach to implement the feedback suggested by the customer. The process of iteration continues throughout the life of the software. Continue reading →

Prototyping approach, also known as evolutionary approach, came to picture because of failures that occurred in the final version of the software application developed using the waterfall approach. The failure generally occurs because of the changes in the requirement of the proposed system or because of the gap in understanding the customer requirement by the development team. A gap in the first version of the developed application, inevitably leads to the need for redoing the application. To overcome these limitations, the concept of prototyping was introduced. Continue reading →

The Win-Win spiral approach is an extension of the spiral approach. The phase in this approach is same as the phase in the spiral approach. The only difference is that at the time of the identifying the requirements, the development team and the customer hold discussion and negotiate on the requirements that need to be included in the current iteration of the software. Continue reading →

In an incremental Model, software requirements are initially broken downed into varied serviceable modules. These useable modules constitute a corresponding task gather. A send activity move is chainlike to rank the prompt units with a variety of activities to be performed in every operable effort. Every useful endeavor is implemented in an increment and the last product is achieved after all the useful units are implemented in the development process. Continue reading →

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. The waterfall approach does not define the process to go back to the previous phase to handle changes in requirement. Therefore, different projects may follow different approaches to handle such situations.

The waterfall approach is the earliest approach that was used for software development. Initially, most projects followed the waterfall approach because they did not focus on changing requirements. Continue reading →