Core concept
Software Maintenance
Software maintenance is the work after delivery to correct defects, adapt to new environments, improve…
27 min12 Interview12 GATEGATEInterview
Level
Advanced
Topic tags
Software maintenance, Software Engineering, It Software
Useful for
GATE favourite, Interview ask
Source
Software Engineering
What you'll learn in this topic
- Corrective fixes faults; adaptive adjusts to environment; perfective adds value; preventive reduces future cost
- Maintainability is designed in (structure, docs, tests), not only performed later
- Regression testing protects existing behaviour after changes
- Asked in GATE / university drills (12 practice items)
Worked Examples
Step-by-step solved problems
- 1.Classify maintenance
- 2.Conceptual check — Software Maintenance
Common Mistakes
Avoid these errors in exams & interviews
- Calling every post-release change “corrective”
- Ignoring regression risk when praising quick patches
- Assuming maintenance is only bug fixing
Practice Questions
Strengthen your concepts with questions
24+
Practice Questions
Interview Questions
Most asked interview problems
12
Interview Questions
GATE Questions
Previous year GATE questions
12
GATE Questions
Applications in real world
Design checks
Core engineering calculations
Plant work
Troubleshooting on site
Interviews
GATE / campus rounds
Product teams
Day-to-day engineering use
Visual concept
Problem
Model
Compute
Verify
Model the physics, compute, then verify against limits.
Recommended Book
Software Engineering
Software Engineering
Roger Pressman
Read: Syllabus unit
Related Topics
What should I learn next?
Nearby topics on your path
University exams
Important Topic
Industry relevance
High
Concept difficulty
Hard
Average time
27 min
See how this topic connects to real it & software careers
Learn from engineers who use this concept in their daily work.
Introduction
This Engineering360 topic classifies maintenance and explains cost drivers. You name the four maintenance types with examples and explain why regression tests and modular design matter for safe change.
Key relations & formulas
maintenance types: corrective, adaptive, perfective, preventive
maintenance cost often dominates lifetime cost of long-lived systems
legacy risk rises when knowledge and test suites are missing
maintenance cost often dominates lifetime cost of long-lived systems
legacy risk rises when knowledge and test suites are missing
Notation and sign conventions
Symbol and sign-convention guide for the equations listed under Key relations & formulas.
Keep SI units consistent end-to-end (do not mix mm with m, or N with kN, in one substitution).
Symbol guide:
• Use symbols exactly as defined in your prescribed text for this unit.
• Use symbols exactly as defined in your prescribed text for this unit.
Sign convention: lock the textbook’s positive sense (force, moment, rotation, heat, or flow) before substituting. A correct symbolic setup still earns method marks in most Indian university papers even if arithmetic slips.
Write relations with symbols exactly as in Software Engineering — Roger Pressman before substituting numbers.
Concept in depth
Delivery is not the end of engineering. Users find defects (corrective), platforms change (adaptive), new features are requested (perfective), and teams refactor to reduce risk (preventive). Poor structure, missing tests, and lost domain knowledge make maintenance expensive — which is why design-for-maintenance and continuous integration matter. Exam questions often give a scenario and ask which maintenance type applies.
Assumptions and validity limits
State assumptions explicitly before using any relation for software maintenance — steady state, uniform properties, linear elastic material, ideal gas, incompressible flow, etc., as applicable.
Wrong assumptions invalidate the entire solution even when the formula is correct. In Software Engineering viva and GATE descriptive questions, listing valid assumptions often earns separate marks.
Step-by-step problem approach
1. Read the question and list given data with SI units (common in Software Engineering papers).
2. Draw a neat labelled diagram where applicable — examiners in Indian universities award diagram marks even when arithmetic slips.
3. Identify which relation from this topic applies to software maintenance.
4. Use equation 1: maintenance types: corrective, adaptive, perfective, preventive.
5. Use equation 2: maintenance cost often dominates lifetime cost of long-lived systems.
6. Substitute values, compute, and verify units and sign (direction).
7. State conclusion in one line — e.g. safe/unsafe, stable/unstable, feasible/infeasible.
2. Draw a neat labelled diagram where applicable — examiners in Indian universities award diagram marks even when arithmetic slips.
3. Identify which relation from this topic applies to software maintenance.
4. Use equation 1: maintenance types: corrective, adaptive, perfective, preventive.
5. Use equation 2: maintenance cost often dominates lifetime cost of long-lived systems.
6. Substitute values, compute, and verify units and sign (direction).
7. State conclusion in one line — e.g. safe/unsafe, stable/unstable, feasible/infeasible.
Applications & exam relevance
Software Maintenance appears in product teams and IT services. In Indian it software curricula this topic is tested because it connects theory to SDLC, requirements, design, quality, and maintenance.
GATE and semester exams often combine software maintenance with earlier units — revise prerequisites before attempting mixed problems.
Industry interview panels sometimes ask: "Where did you use software maintenance?" — answer with a lab, mini-project, or plant visit example if possible.
Common mistakes in exams
• Calling every post-release change “corrective”
• Ignoring regression risk when praising quick patches
• Assuming maintenance is only bug fixing
• Ignoring regression risk when praising quick patches
• Assuming maintenance is only bug fixing
Quick revision checklist
Before attempting software maintenance problems, confirm you can:
1. Corrective fixes faults; adaptive adjusts to environment; perfective adds value; preventive reduces future cost
2. Maintainability is designed in (structure, docs, tests), not only performed later
3. Regression testing protects existing behaviour after changes
2. Maintainability is designed in (structure, docs, tests), not only performed later
3. Regression testing protects existing behaviour after changes
Revise the solved examples in Software Engineering — Roger Pressman and one previous-year GATE or university paper for this unit.