SDLC Models · Complete Notes + PYQs & Interactive MCQs for GATE & Rajasthan Computer Teacher 2026

SDLC Models · Complete Notes

GATE CSE · ISRO · UGC NET · Rajasthan Computer Teacher · NIELIT · PSUs

2026 Syllabus High Weightage 31 Interactive MCQs PYQs Included Enhanced Notes

Introduction to SDLC

The System Development Life Cycle (SDLC) is a structured, systematic process used to plan, design, develop, test, deploy, and maintain high-quality software. It serves as the backbone of Software Engineering and is a critical topic in GATE CSE, ISRO, UGC NET, NIELIT, and State Computer Teacher examinations.

📌 Core Objective: Deliver high-quality software that meets or exceeds customer expectations, within budget and on schedule, while managing risks effectively.
🔑 Key Benefit: Reduces project failure risk by 40-60%
🔑 Key Benefit: Improves team communication and stakeholder alignment
🔑 Key Benefit: Ensures quality through systematic testing at each phase
🔑 Key Benefit: Provides clear documentation and project visibility

Quick-Reference Comparison Matrix

Perfect for last-minute revision

SDLC Model Core Focus / DNA Best Suited For Key Weakness / Risk
WaterfallLinear, document-drivenStable, fixed requirementsHigh risk; no working software until late
PrototypeVisualizing user needsUnclear/evolving requirementsScope creep; throwaway code costs
SpiralRisk managementLarge, complex, high-risk projectsExpensive; requires expert risk analysts
V-ModelParallel Verification & ValidationSafety-critical systemsRigid; poor handling of dynamic changes
AgileCustomer collaborationDynamic, rapidly changing requirementsLacks strict documentation footprint
RADComponent-based reuseSystems built in under 60–90 daysRequires highly skilled developers
IncrementalModular deliveryLarge projects with phased deliveryRequires good modular design
IterativeContinuous refinementProjects needing frequent feedbackCan lead to scope creep

8 Phases of SDLC

Memory Trick: P F A D C T D M — "Please Find A Doctor, Call The Doctor Immediately."
1. Planning

Define objectives, budget, timeline, team, risks. Output: Project Plan

2. Feasibility Study

Check practicality — TELOS (Technical, Economic, Legal, Operational, Schedule).

3. Requirement Analysis

Gather functional & non-functional requirements. Output: SRS

4. System Design

HLD (architecture) + LLD (algorithms, logic).

5. Coding

Implementation using languages like Java, Python, C++.

6. Testing

Unit → Integration → System → Acceptance.

7. Deployment

Release to end users (launch, installation).

8. Maintenance

CAPA — Corrective, Adaptive, Perfective, Preventive.

💡 SRS Boundary Rule: The Software Requirement Specification (SRS) acts as a legal and technical bridge. It marks the formal transition from the Requirement Analysis phase to the System Design phase.

SDLC Models — In-Depth Analysis

Each model fits different project needs. Below is a detailed breakdown with advantages, disadvantages, and real-world applicability.

Waterfall Classic

Linear sequence; one phase completes before the next begins.

✅ Simple & well-documented
✅ Easy to manage
❌ Rigid & inflexible
❌ Late feedback

Best for: Stable, fixed requirements like government projects, banking systems.

Prototype Visual

Build a working prototype early to gather user feedback.

✅ Better understanding
✅ Early user feedback
❌ Scope creep
❌ Increased cost

Best for: Unclear or evolving requirements, UI/UX design projects.

Spiral Risk-Driven

Iterative cycles with risk analysis at each phase.

✅ Excellent risk management
✅ Flexible
❌ Expensive
❌ Requires skilled analysts

Best for: Large, high-risk projects like defense systems, aerospace software.

V-Model Testing Parallel

Development and testing phases are matched in a V-shape.

✅ Testing starts early
✅ High quality
❌ Rigid
❌ Poor for dynamic changes

Best for: Safety-critical systems — medical devices, aircraft control.

Agile Modern

Iterative, customer-centric development with sprints.

✅ Quick response to change
✅ Frequent delivery
❌ Light on documentation
❌ Requires customer availability

Best for: Dynamic, rapidly changing requirements — startups, web apps, mobile apps.

RAD Fast

Rapid Application Development — reuse components, fast delivery.

✅ Speed
✅ User feedback
❌ Needs expert developers
❌ Not for large teams

Best for: 60–90 day projects, internal business applications.

Incremental Modular

Software built and delivered in small increments.

✅ Early delivery
✅ Easy testing
❌ Requires good modular design

Best for: Large projects with phased delivery, ERP systems.

Iterative Continuous

Repeated cycles with continuous improvement.

✅ Early feedback
✅ Evolving quality
❌ Can lead to scope creep

Best for: Projects needing frequent feedback, research & development.

Big Bang Minimal

Minimal planning; suitable only for very small projects.

✅ Simple
✅ Flexible
❌ High risk
❌ Unpredictable

Best for: Very small projects, college assignments, proof-of-concepts.

Agile Frameworks — Scrum, XP & Kanban

Agile is not a single model but an umbrella methodology with several operational frameworks. These are frequently tested in exams.

Scrum

Fixed-length iterations (Sprints): 1–4 weeks. Daily stand-ups, sprint planning, sprint review, and retrospective.

Roles: Product Owner, Scrum Master, Development Team.

Most Popular

XP (Extreme Programming)

Engineering-focused: Pair programming, test-driven development (TDD), continuous integration, refactoring.

Key Practices: Small releases, simple design, collective ownership.

Technical

Kanban

Visual workflow management: Continuous delivery with no fixed iterations. Work items move through stages (To Do → In Progress → Done).

Key Metric: Lead time & cycle time.

Continuous

Software Maintenance — CAPA Framework

CAPA — Corrective, Adaptive, Perfective, Adaptive — "Correct And Perfect Always"
Corrective

Fix bugs and errors. The most common type of maintenance. Addresses defects discovered after delivery.

Adaptive

Adapt to environment changes. OS upgrades, new hardware, regulatory changes, new database versions.

Perfective

Enhance features or performance. Add new functionality requested by users, improve usability, increase speed.

Preventive

Prevent future failures. Refactoring, code restructuring, improving maintainability, updating documentation.

📊 Exam Tip: Corrective Maintenance accounts for ~60% of maintenance effort, while Perfective Maintenance accounts for ~20%.

Exam Shortcut: Maintenance Types ⚡

GATE & Rajasthan Computer Teacher Shortcut

Whenever you see:

Fix bugs Correct errors Repair defects Resolve faults

👉 Answer: Corrective Maintenance ✅

⭐ Golden Formula: CAPA

C
Correct Bugs
Fixing errors & defects
A
Adapt to Changes
Environment & OS updates
P
Perfect the Software
Add new features & improve
P
Prevent Future Problems
Refactoring & restructuring

🧠 Remember: Correct Bugs, Adapt to Changes, Perfect the Software, Prevent Future Problems.

Easy Memory Trick 🧠 — TELOS Robot

Imagine a TELOS Robot 🤖 standing at the entrance of every project.

Before anyone enters, the robot asks only five questions:

🛠️ T
Technical
Tools & Technology?
💰 E
Economic
Enough money?
⚖️ L
Legal
Allowed by law?
😊 O
Operational
Okay for users?
⏰ S
Schedule
Time available?
If every answer is "Yes"... 🚪 The robot opens the gate. If even one answer is "No"... 🚫 The project stops.
📌 TELOS = Technical, Economic, Legal, Operational, Schedule — All checked during the Feasibility Study phase.

Super Memory Formula — SDLC Phases

"What are we building? Can we build it? What features? How? Build! Find bugs! Give it! Improve!"

1. Planning → What are we building?
2. Feasibility Study → Can we build it? ✅ (TELOS)
3. Requirement Analysis → What features are needed?
4. Design → How will we build it?
5. Coding → Build the software
6. Testing → Find bugs
7. Deployment → Give it to users
8. Maintenance → Improve and fix it
🧠 Quick Acronym: P F R D C T D M — "Please Find Requirements, Design, Code, Test, Deploy, Maintain"

V-Model Memory Trick — Testing Symmetry

"User wants it → Acceptance checks it" — Visualize the V-Model testing pyramid

👤 User wants it → Acceptance checks it
🏗️ Whole System → System Testing
🔗 Modules Together → Integration Testing
🧩 Single Module → Unit Testing

🔁 The V-Model pairs each development phase with a corresponding testing phase.

⭐ Golden Rule for V-Model

📄 User Requirements → ✅ Acceptance Testing
🏛️ System Design → ✅ System Testing
📐 Architecture Design → ✅ Integration Testing
🧩 Module Design → ✅ Unit Testing

🧠 Quick Check: If a question asks which test validates a specific design phase — look at the left column and match it to the right!

Exam Tip 🚀

Whenever you see words like:

TELOS Technical Feasibility Economic Feasibility Project viability Should we start this project?

👉 Immediately think: Feasibility Study

⚡ Exam Shortcut: Any question about checking if a project is possible, viable, or should be started — the answer is almost always the Feasibility Study phase.

One-Line Exam Trick ⭐

Unclear Requirements → Prototype Model

⚡ Exam Shortcut: If the question mentions "unclear", "evolving", or "vague" requirements — the answer is almost always Prototype Model.

Super Memory Formula — Model Selection

"Fixed Requirements → Waterfall" & "Unclear Requirements → Prototype"

📄
Fixed Requirements
Waterfall
• Stable • Document-driven
❓
Unclear Requirements
Prototype ✅
• Evolving • Visual feedback
⚠️
High Risk
Spiral
• Risk-driven • Iterative
🔄
Frequent Changes
Agile
• Adaptive • Customer-centric
🧪
Testing Focus
V-Model
• Parallel testing • Safety
🚀
Fast Development
RAD
• 60-90 days • Reuse
Quick Decision Tree: Fixed Req → Waterfall | Unclear → Prototype | High Risk → Spiral | Frequent Changes → Agile | Safety-Critical → V-Model

High-Weightage Revision Points

🧠 The SRS Boundary Rule: The Software Requirement Specification (SRS) acts as a legal and technical bridge. It marks the formal transition from the Requirement Analysis phase to the System Design phase.

⚡ Risk Analysis Quadrant: The Spiral Model works as an evolutionary cycle. If a question mentions "quadrants", "radial circles", or "iterative prototyping mixed with risk tracking," immediately look for Spiral Model.

✅ The V-Model Symmetry: In the V-model, Unit Testing validates the Module/Low-Level Design, while Acceptance Testing validates the original User Requirements.

📈 Agile vs. Traditional: Agile is iterative, customer-driven, and adaptive. Traditional models (Waterfall, V-Model) are sequential, document-driven, and predictive.

Exam Tip 2026: Focus on Agile vs. Traditional models (Waterfall/V-Model). Most state-level and national exams heavily emphasize Agile metrics, Scrum roles, and maintenance definitions (CAPA).
📌 Waterfall Key Point: No overlap between phases. Each phase's output is the input for the next.
📌 Spiral Key Point: Four quadrants: Determine Objectives, Identify Risks, Develop & Test, Plan Next Iteration.
📌 Agile Key Point: The Agile Manifesto (2001) values individuals & interactions, working software, customer collaboration, and responding to change.
📌 RAD Key Point: Uses prototyping and component-based development to achieve rapid delivery.
Interactive MCQs · 31 Questions
सही: 0 गलत: 0 शेष: 31
0 / 31

परिणाम

0 / 31

बहुत अच्छा!

0 सही
0 गलत
0 अनुत्तरित

ऊपर 'पुनः प्रयास' बटन से दोबारा प्रयास करें

Conclusion

The System Development Life Cycle (SDLC) is the backbone of software engineering and a high-weightage topic in competitive exams. Mastery of the phases, models, and maintenance types — combined with regular practice of PYQs — will significantly boost your score in GATE CSE, Rajasthan Computer Teacher, NIELIT, ISRO, UGC NET, and other technical recruitment exams.

Keep revising, and good luck with your 2026 exam preparation!

SDLC Notes 2026 • GATE · ISRO · UGC NET · Rajasthan Teacher • System Analysis & Design • 31 Interactive MCQs