WK1: Comparing Sequential and Iterative Development Models (Session 2)

• Software Development Lifecycles
• Higher Education (degree)

Welcome to Session 2

SDLC Models and Risk Management

Module Lecturer: Dr Raghav Kovvuri

Email: [e-mail]

Session Objectives

• Understand different SDLC models.
• Compare sequential and iterative approaches.
• Identify appropriate models for different scenarios.
• Understand risk management in SDLC.

Sequential Models Overview

Traditional Approaches

• Step-by-step progression.
• Clear documentation.
• Defined stages.
• Structured approach.

Water Fall Model

Phases:

1. Requirements.
2. Design.
3. Implementation.
4. Verification.
5. Maintenance.

Advantages: Clear structure, Easy to understand,  Well-documented, Clear deliverables.

Disadvantages: Inflexible, Late testing, difficult to change, High risk

V-Model

Verification and Validation model:

• Test planning in parallel.
• Enhanced quality control.

Phases:

• Requirements ↔ Acceptance Testing.
• Design ↔ System Testing.
• Development ↔ Unit Testing.

Iterative Models Overview

• Flexible development.
• Regular feedback.
• Continuous improvement.
• Risk management focus.

Modern Approaches

Agile Methodology

Core Principles

• Customer collaboration.
• Responding to change.
• Working software.
• Team interaction.

Key Features

• Sprints.
• Daily meetings.
• Backlog management.
• Continuous delivery.

Spiral Model

Risk-driven process:

• Prototyping.
• Regular reviews.
• Customer feedback.

Phases:

• Planning.
• Risk Analysis.
• Engineering.
• Evaluation.

Model Selection Criteria

Factors to Consider

• Project size.
• Requirements clarity.
• Time constraints.
• Budget.
• Team experience.
• Risk factors.

Analysis Task

Read the Digital Banking Case Study (available in Canvas)

Choose which development model you would use:

• Sequential Model OR Iterative Development Model

Write Your Analysis to Discussions:

• Explain your choice and reasoning
• Address main challenges and risks
• Describe how you'll handle security & compliance

Remember:

• Read case study carefully
• Support your choice with examples
• Consider all requirements
• Think about practical implementation