Maintenance
Maintenance is the process of modifying software after delivery to correct defects, improve quality, adapt to new environments, or enhance functionality.
“The process of modifying a component or system after delivery to correct defects, improve quality characteristics, or adapt to a changed environment.”
(Definition reproduced from the ISTQB Glossary. Copyright belongs to ISTQB.)
View the complete ISTQB GlossaryWhat is Maintenance?
Software maintenance continues throughout the operational life of a product and often represents the largest portion of software lifecycle effort.
Types: Corrective, adaptive, perfective, and preventive maintenance are common categories.
Ongoing activity: Maintenance continues after software release.
Testing impact: Every change requires verification and regression testing.
Real World Example
A regulated product team is preparing a release where Maintenance appears in reviews, test design conversations, or defect triage rather than as an isolated glossary word.
The risk is that the team treats Maintenance as interchangeable with nearby ISTQB terms. That makes test scope blurry and can lead to weak evidence for the release decision.
The tester anchors the discussion in the official definition, asks where the concept appears in the product, and designs examples that show the difference between Maintenance and similar ideas.
The page becomes useful in practice because Maintenance is connected to a specific testing decision, not memorized as a detached definition.
Practice Questions
Question 1
Which statement BEST describes Maintenance in the context of ISTQB terminology?
Question 2
A tester needs to explain Maintenance to a non‑technical stakeholder. Which approach is MOST appropriate?
Test your knowledge with real ISTQB-style questions
You’ve learned Maintenance. Test your understanding with topic-specific questions in our Mock Exams.