🔄 SDLC & Process Models
282 words
1 min read
Visual companion
Python
Type and operator map
Python Week 1: the first filter for runtime behavior
View
Revision summary
What this note is really saying
Short form
# 🔄 SDLC & Process Models ## 1. 🎯 Learning Objectives - Compare Waterfall, Agile, and hybrid process models - Trace the phases of each SDLC model - Choose the right model given project characteristics - Explain Scrum ceremonies: sprint planning, daily stand-up, review, retrospective ## 2.
🔄 SDLC & Process Models
1. 🎯 Learning Objectives
- Compare Waterfall, Agile, and hybrid process models
- Trace the phases of each SDLC model
- Choose the right model given project characteristics
- Explain Scrum ceremonies: sprint planning, daily stand-up, review, retrospective
2. 📖 Core Content
3.1 What is SDLC?
The Software Development Lifecycle (SDLC) is a structured process for planning, creating, testing, and deploying software. It provides a framework for teams to deliver high-quality software predictably.
3.2 Waterfall Model
Sequential phases: Requirements → Design → Implementation → Testing → Deployment → Maintenance
Pros: Simple, predictable, good documentation. Cons: Inflexible, late feedback, poor for changing requirements. When to use: Well-understood requirements, regulatory compliance, small projects.
3.3 Agile Model
Iterative development with continuous customer feedback. Based on the Agile Manifesto:
- Individuals and interactions over processes and tools
- Working software over comprehensive documentation
- Customer collaboration over contract negotiation
- Responding to change over following a plan
3.4 Scrum Framework
Roles: Product Owner, Scrum Master, Development Team Artifacts: Product Backlog, Sprint Backlog, Increment Events: Sprint Planning, Daily Scrum, Sprint Review, Sprint Retrospective
3.5 Kanban
Visual workflow management using a Kanban board: To Do → In Progress → In Review → Done. Focus: Limit work-in-progress (WIP), continuous flow.
3.6 Waterfall vs Agile Decision Table
| Factor | Waterfall | Agile |
|---|---|---|
| Requirements | Fixed upfront | Evolving |
| Customer involvement | At milestones | Continuous |
| Documentation | Heavy | Minimal sufficient |
| Team size | Large possible | Small, cross-functional |
| Risk management | Early planning | Continuous adaptation |
4. 📝 Practice Questions
Q1: Which SDLC model is best for a project with unclear, evolving requirements?Answer: Agile (Scrum). The iterative nature allows requirements to emerge through customer feedback. Waterfall would fail because requirements cannot be fully specified upfront. Join Discord NextRequirements Engineering