Software development life cycle (SDLC) is important for the software project success, the good software engineer should have enough experience and knowledge to prefer a 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.
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
Water Fall Model:
The Waterfall Model is a linear sequential flow. In which progress is seen as flowing steadily downwards (like a waterfall) through the phases of software implementation. 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. The waterfall approach is the earliest approach and most widely known that was used for software development.
Projects which not focus on changing the requirements, for example, projects initiated from a request for proposals (RFPs), the customer has a very clear documented requirements
- Easy to explain to the users.
- Structures approach.
- Stages and activities are well defined.
- Helps to plan and schedule the project.
- Verification at each stage ensures early detection of errors/misunderstanding.
- Each phase has specific deliverables.
- Assumes that the requirements of a system can be frozen.
- Very difficult to go back to any stage after it finished.
- A little flexibility and adjusting scope is difficult and expensive.
- Costly and required more time, in addition to the detailed plan.
It is an extension of the waterfall model, Instead of moving down in a linear way, the process steps are bent upwards after the implementation and coding phase, to form the typical V shape. The major difference between the V-shaped model and waterfall model is the early test planning in the V-shaped model.
- Software requirements clearly defined and known
- Software development technologies and tools are well-known
- Simple and easy to use
- Each phase has specific deliverables.
- Higher chance of success over the waterfall model due to the development of test plans early on during the life cycle.
- Works well for where requirements are easily understood.
- Verification and validation of the product in the early stages of product development.
- Very inflexible, like the waterfall model.
- Adjusting scope is difficult and expensive.
- The software is developed during the implementation phase, so no early prototypes of the software are produced.
- The model doesn’t provide a clear path for problems found during testing phases.
- Costly and required more time, in addition to a detailed plan
It refers to the activity of creating prototypes of software applications, for example, incomplete versions of the software program being developed. It is an activity that can occur in software development. It used to visualize some component of the software to limit the gap of misunderstanding the customer requirements by the development team. This also will reduce the iterations may occur in a waterfall approach and hard to be implemented due to the inflexibility of the waterfall approach. So, when the final prototype is developed, the requirement is considered to be frozen. It has some types, such as:
- Throwaway prototyping: Prototypes that are eventually discarded rather than becoming a part of the finally delivered software
- Evolutionary prototyping: prototypes that evolve into the final system through iterative incorporation of user feedback
- Incremental prototyping: The final product is built as separate prototypes. At the end, the separate prototypes are merged in an overall design
Extreme prototyping: used at web applications mainly. Basically, it breaks down web development into three phases, each one based on the preceding one. The first phase is a static prototype that consists mainly of HTML pages. In the second phase, the screens are programmed and fully functional using a simulated services layer. In the third phase, the services are implemented.
This process can be used with any software developing life cycle model. While this shall be chosen when you are developing a system has user interactions. So, if the system does not have user interactions, such as a system does some calculations shall not have prototypes.
- Insufficient analysis
- User confusion of prototype and finished system.
- Developer misunderstanding of user objectives.
- Excessive development time of the prototype.
- The expense of implementing prototyping.
- Reduced time and costs, but this can be a disadvantage if the developer loses time in developing the prototypes.
- Improved and increased user involvement.
Spiral Model (SDM)
It is combining elements of both design and prototyping-in-stages, in an effort to combine advantages of top-down and bottom-up concepts. This model of development combines the features of the prototyping model and the waterfall model. The spiral model is favored for large, expensive, and complicated projects.
This model uses many of the same phases as the waterfall model, in essentially the same order, separated by planning, risk assessment, and the building of prototypes and simulations.
It is used in the large applications and systems which built-in small phases or segments.
- Estimates (i.e. budget, schedule, etc.) become more realistic as work progressed because important issues are discovered earlier.
- Early involvement of developers.
- Manages risks and develops the system into phases.
- High cost and time to reach the final product.
- Needs special skills to evaluate the risks and assumptions.
- Highly customized limiting re-usability.
Iterative and Incremental Model
It is developed to overcome the weaknesses of the waterfall model. It starts with initial planning and ends with deployment with the cyclic interactions in between. 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.
It can consist of mini waterfalls or mini V-Shaped model
It is used in shrink-wrap application and large system which built-in small phases or segments. Also, can be used in a system which has separate components, for example, ERP system.
Which we can start with the budget module as a first iteration and then we can start with the inventory module and so forth.
- Produces business value early in the development lifecycle.
- Better use of scarce resources through proper increment definition.
- Can accommodate some change requests between increments.
- More focused on customer value than the linear approaches.
- Problems can be detected earlier.
- Requires heavy documentation.
- Follows a defined set of processes.
- Defines increments based on function and feature dependencies.
- Requires more customer involvement than the linear approaches.
- Partitioning the functions and features might be problematic.
- Integration between iteration can be an issue if this is not considered during the development.
It is based on iterative and incremental development, where requirements and solutions evolve through collaboration between cross-functional teams.
It can be used with any type of project, but it needs more engagement from the customer and to be interactive. Also, it can be used when the customer needs to have some functional requirement ready in less than three weeks and the requirements are not clear enough.
- Decrease the time required to avail some system features.
- Face to face communication and continuous inputs from customer representative leaves no space for guesswork.
- The end result is the high-quality software in the least possible time duration and satisfied customer.
- The ability and collaboration of the customer to express user needs.
- Documentation is done at later stages.
- Reduce the usability of components.
- Needs special skills for the team.