9.3. SDLC Models

• Linear, sequential model. • Each phase must be completed before the next begins. • Best for: Small, well-defined projects.

The Waterfall Model is a straightforward approach to software development. It follows a strict sequence where each phase, such as requirements gathering, design, implementation, testing, and deployment, must be completed in that order. Once a phase is finished, you cannot go back to it without starting the whole process over. This method works best for small projects where requirements are clear from the beginning.

Think of the Waterfall Model like building a house. You first complete the foundation before moving on to the structure, the roof, and then the interior. If you discover a problem with the foundation after building the walls, it means you have to dismantle parts of the house to fix it, which can be costly and time-consuming.

• Extension of Waterfall with testing at every stage. • Focuses on: Quality and validation.

The V-Model takes the basic principles of the Waterfall Model and adds an emphasis on testing and validation at each phase. For every development phase, there is a corresponding testing phase. For example, during the design phase, validation tests are planned to ensure the design meets the requirements. The V-Model improves quality assurance as it ensures that any issues can be identified and rectified early.

Imagine a chef preparing a meal. Instead of waiting until the final dish is presented to taste it, the chef samples ingredients and checks the seasoning at each step—like tasting the sauce while it's simmering and before serving. This way, adjustments can be made along the way to ensure overall quality.

• Starts with a small set of requirements and iteratively enhances the product. • Each cycle produces a version of the software.

The Iterative Model allows for a small set of requirements to be addressed in cycles or iterations. After completing one iteration, the team receives feedback and can make improvements in the next cycle. This approach enables developers to build a basic version of the product quickly and then refine it based on user feedback, making it adaptable to changing needs.

Consider a sculptor working with clay. The sculptor starts with a rough shape and gradually refines it. After each iteration, the sculptor may step back, assess the work, and decide to change certain aspects based on feelings or feedback from others. This iterative approach helps create a finished piece that better meets the artist's vision.

• Combines iterative development with risk analysis. • Each loop = planning + risk analysis + engineering + evaluation.

The Spiral Model emphasizes risk management by combining elements of iterative development with a focus on risk assessment. Each cycle or 'loop' consists of four phases: planning, risk analysis, engineering (development), and evaluation. This helps teams to identify potential risks early and develop strategies to mitigate those risks while continuously building and refining the software.

Think of the Spiral Model as a mountain climber’s journey. Before each ascent, the climber evaluates the route, identifies potential hazards like loose rocks or sudden weather changes, and formulates a plan. As they climb, they continuously assess their progress and adapt their strategy based on conditions, ensuring safety and success.

• Popular in modern development. • Emphasizes: o Incremental delivery o Customer collaboration o Flexibility to change • Uses Scrum, Kanban, or Extreme Programming (XP).

The Agile Model promotes a flexible and collaborative approach to software development. It emphasizes delivering software in small, functional increments rather than at the end of a long project for better feedback and adaptation. Teams frequently collaborate with stakeholders and are open to changing requirements as a project progresses, ensuring the final product aligns closely with user needs. Agile practices include methodologies like Scrum, Kanban, or Extreme Programming (XP).

Imagine a group of musicians jamming together. They start with a few notes and gradually build the song by adding riffs and harmonies based on feedback from each other and the audience. This active collaboration and willingness to change the tune based on feedback make the final performance more engaging and aligned with the listeners' preferences.

--