Lesson 6B: Software Development Life Cycle

Software Development Life Cycle (SDLC) Models

The Software Development Life Cycle (SDLC) is a structured approach used to design, develop, test, and deploy
high-quality software. It ensures that the software meets customer requirements, adheres to industry standards,
and is completed within budget and time constraints. Various SDLC models exist, each with unique
methodologies to manage the software development process efficiently. Choosing the appropriate SDLC model
depends on project requirements, complexity, team structure, and business goals.

Learning Objectives

By the end of this lesson, students should be able to:

1. Describe the purpose and importance of software development models.

2. Compare and contrast various software development models.
3. Identify the advantages and disadvantages of different models.
4. Select an appropriate model based on project requirements.

Common Software Development Models

Each software development model follows a unique approach to completing a project. Below are the most
commonly used models:

1. Waterfall Model

The Waterfall Model is a linear and sequential approach where progress flows in one direction—like a
waterfall. It consists of distinct phases:

Phases of the Waterfall Model

1. Requirement Analysis – Collect and analyze software requirements through meetings with stakeholders,
feasibility studies, and requirement documentation.
2. System Design – Define the architecture and technical specifications, including software and hardware
requirements, UI design, and database design.
3. Implementation – Write and integrate the code following predefined specifications, adhering to coding
standards and development best practices.
4. Testing – Identify and fix bugs through unit testing, integration testing, system testing, and user
acceptance testing (UAT).
5. Deployment – Release the product for use, either through a full-scale rollout or phased implementation.
6. Maintenance – Address issues, apply updates, and make enhancements based on user feedback and
emerging requirements.

How It Works?

• The Waterfall Model follows a linear, sequential approach where each phase must be completed before
moving to the next.
• It emphasizes thorough planning and documentation at the beginning to ensure clear project direction.
• Testing occurs only after development is completed, which can lead to discovering defects late in the
process.
• Since each phase is dependent on the previous one, revisiting earlier stages is difficult and costly.
• It is best suited for projects with well-defined requirements where minimal changes are expected.

Advantages

• Simple and easy to manage due to its structured nature.

• Clear documentation and well-structured phases ensure proper tracking.
• Well-suited for projects with well-defined requirements where little change is expected.
• Facilitates better resource planning and cost estimation upfront.

Disadvantages

• Difficult to accommodate changes later in the process, making it inflexible.

• Testing happens late in the cycle, increasing the risk of failure if defects are discovered.
• Not suitable for complex or long-term projects where requirements may evolve over time.
• Client feedback is incorporated only after the project is nearly completed, which may lead to
misalignment with expectations.

Best Used For

✓ Projects with clear and stable requirements.

✓ Projects where changes are unlikely during development.

Example: Developing a payroll management system for a small business.

2. V-Model (Verification and Validation Model)

An extension of the Waterfall Model, the V-Model emphasizes verification (before coding) and validation
(after coding). Every development phase has a corresponding testing phase to ensure software quality.

Phases of the V-Model

Verification (Before Coding)

1. Requirement Analysis – Define clear and complete software and business requirements.
2. System Design – Plan system architecture, components, and database structures.
3. Architectural Design – Design the high-level system structure, including modules and data flow.
4. Module Design – Define the specifications, interfaces, and interactions of individual modules.

Validation (After Coding)

5. Unit Testing – Test each module separately to verify functionality.

6. Integration Testing – Validate interactions between integrated modules.
7. System Testing – Evaluate the entire system for compliance with business and functional
requirements.
8. Acceptance Testing – Ensure the software meets end-user expectations before deployment.

How It Works?

• The V-Model follows a sequential structure, where each development phase has a corresponding testing
phase.
• Unlike the Waterfall Model, testing begins early, reducing the risk of costly fixes later.
• Each phase must be verified before moving to the next stage.
• This model helps detect and fix issues early, improving software reliability.

Advantages

• Early defect detection and correction of defects.

• Well-structured testing process, ensuring higher software reliability.
• Effective for projects requiring strict validation and compliance.
 Disadvantages

• Not suitable for projects with evolving requirements.

• High initial cost due to extensive testing.

Best Used For

✓ Critical systems like medical, aerospace, and banking applications.

✓ Projects with clearly defined requirements that do not change.

Example: Developing software for a medical device where accuracy and validation are crucial.

3. Iterative Model

The Iterative Model builds software through repeated cycles (iterations), allowing enhancements and
refinements at each stage based on feedback. Unlike the Waterfall Model, changes can be made after each
iteration, making it more flexible.

Phases of Iterative Model

1. Initial Planning – Identify project goals, high-level requirements, and risks.

2. Requirements Gathering – Collect detailed user requirements for the current iteration.
3. Analysis & Design – Design system architecture, workflows, and database structures based on the
requirements.
4. Implementation – Develop functional components based on the design.
5. Testing – Conduct unit and integration testing to validate functionality.
6. Evaluation – Review user feedback, assess the iteration's success, and identify necessary
improvements.
7. Repeat Process – Refine and enhance the system in subsequent iterations until deployment.
8. Deployment – Once the system meets all requirements and passes final validation, it is deployed for
real-world use.
How It Works?

• The development process is divided into small, manageable iterations rather than a single sequential
flow.
• Each iteration results in a working version of the software, with incremental feature improvements.
• After every iteration, feedback is gathered, and necessary modifications are made before moving to the
next cycle.
• The process continues until the final product meets all requirements.

Advantages

• Allows incremental development and continuous improvement.

• Adapts to requirement changes without affecting overall project structure.
• Provides early working versions of the product for feedback.

Disadvantages

• May require more time and resources due to repeated iterations.

• Needs strong planning and documentation to avoid scope creep.

Best Used For

✓ Large-scale projects with evolving requirements.

✓ Applications requiring frequent enhancements based on user feedback.

Example: Developing an e-commerce platform where features like payment methods and recommendation
systems are refined over time.
4. Spiral Model

The Spiral Model is an iterative development approach that integrates risk assessment and prototyping.
Unlike linear models, it follows a cyclic process, allowing teams to refine and validate the system
continuously. Each loop in the spiral represents a development phase, progressively improving the product
while identifying and mitigating risks. This model is particularly beneficial for high-risk, large-scale
projects requiring frequent evaluation and adaptation.

Phases if Spiral Model

1. Determine Objectives, Alternatives, and Constraints

o Define the project's scope, goals, and performance expectations.
o Identify multiple solution approaches and select the most viable one.
o Establish benchmarks, success criteria, and constraints (e.g., budget, time, resources).
2. Evaluate Alternatives, Identify, and Resolve Risks
o Perform a comprehensive risk analysis to assess potential issues.
o Develop prototypes to test critical components and validate feasibility.
o Use models, simulations, and benchmarks to compare different solutions.
o Address risk factors early to avoid costly changes in later phases.
3. Develop and Verify the Next-Level Product
o Define detailed software and system requirements based on previous insights.
o Design system architecture, including hardware, databases, and user interfaces.
 o Implement functional components, ensuring adherence to design specifications.
o Conduct unit testing, integration testing, and system validation to ensure reliability.
4. Plan the Next Phase
o Assess current phase outcomes and project progress.
o Identify improvements and potential risks for the next iteration.
o Revise project plans, allocate resources, and adjust schedules accordingly.
o Set objectives and key deliverables for the next loop in the spiral.
5. Review and Commit to the Next Iteration
o Conduct a comprehensive review with stakeholders.
o Decide whether to proceed, refine, or pivot based on feedback and project insights.
o Prioritize development tasks for the next cycle, ensuring alignment with business goals.

How It Works?

• The development process moves outward in a spiral, refining the system at each loop.
• Risk analysis is conducted early in every cycle, minimizing potential failures later.
• Prototypes validate concepts before full-scale implementation, reducing uncertainty.
• The model emphasizes adaptability, allowing incremental improvements and optimizations.

Advantages

• Strong risk management and early problem identification.

• Highly flexible, accommodating changes at different development stages.
• Iterative prototyping ensures user feedback is incorporated early.
• Ideal for large-scale and high-risk projects requiring continuous assessment.

Disadvantages

• More costly and time-intensive due to continuous iterations.

• Requires experienced risk management and project planning expertise.
• Complexity may increase as additional iterations are added.

Best Used For

✓ High-risk projects where frequent reassessment is crucial (e.g., defense, finance, aerospace).
✓ Large-scale software systems requiring continuous evaluation and improvement.
✓ Complex applications where evolving requirements necessitate iterative refinements.
5. Agile Model

The Agile Model emphasizes iterative development, flexibility, and customer collaboration. Unlike traditional
models, Agile focuses on delivering software incrementally in short cycles called sprints.

Phases of Agile Model

1. Requirements Analysis – Define high-priority features and create a backlog.

2. Design – Develop the architecture, UI, and technical plan for the iteration.
3. Development (Coding) – Implement functional components of the software.
4. Testing & Debugging – Perform continuous testing to ensure quality and detect errors early.
5. Release – Deploy the working product to users for evaluation.
6. Maintenance & User Feedback – Collect feedback to refine and improve the system in the next iteration.

How It Works?

• The development process follows a cyclical approach where each phase repeats in iterations.
• Each iteration delivers a working software increment, allowing continuous improvements based on
user feedback.
• The process begins with requirement analysis, followed by design, coding, testing, release, and
maintenance.
• Testing is integrated into every cycle to ensure high-quality software.
• User feedback from each release informs modifications in the next iteration.
• Agile encourages adaptive planning and rapid responses to change, promoting team collaboration.

Advantages

• Highly flexible and adaptable to changing requirements.

• Faster software delivery through incremental releases.
• Continuous customer feedback ensures alignment with expectations.
Disadvantages

• Requires strong collaboration and communication within the team.

• Difficult to estimate time and budget due to evolving requirements.

Best Used For

✓ Dynamic projects with evolving requirements.

✓ Startups and software-as-a-service (SaaS) applications.

Example: Developing a mobile application with frequent feature updates.

6. DevOps Model

The DevOps Model integrates development and operations teams to enable continuous integration, delivery,
and deployment of software. It emphasizes automation, collaboration, and rapid software release cycles.

Phases of DevOps Model

1. Plan – Define project goals, architecture, and workflows.

2. Develop – Write and test code, ensuring integration with existing systems.
3. Build – Automate the build process to create deployable artifacts.
4. Test – Continuously test new code to detect errors early.
5. Release & Deploy – Automatically deploy software to production environments.
6. Operate & Monitor – Track system performance and resolve issues in real-time
 How It Works?

• Development and IT operations teams work together throughout the software lifecycle.
• Continuous integration (CI) ensures that new code is automatically tested and merged.
• Continuous deployment (CD) enables frequent and automated software releases.
• Monitoring and feedback loops improve system performance and stability.
• Automation tools like Jenkins, Docker, and Kubernetes streamline development and deployment
processes.

Advantages

• Faster software delivery and deployment cycles.

• Improved collaboration between development and IT operations teams.
• Automation reduces human errors and improves efficiency.

Disadvantages

• Requires expertise in automation tools and cloud-based infrastructure.

• Initial setup and implementation can be complex and time-consuming.

Most Suitable For

✓ Cloud-based applications and web services.

✓ Projects requiring continuous integration and delivery.

Example: Deploying an e-commerce website with frequent updates and high availability.

Each SDLC model has its strengths and weaknesses. Selecting the right model depends on project requirements,
budget, risk factors, and customer involvement. By understanding these models, development teams can choose
the best approach for delivering successful software applications.