Recognize different maintenance goals

Corrective work repairs a known fault, such as an export that drops records. Adaptive work keeps software usable when its environment changes, such as an external API update. Perfective work improves qualities like usability or maintainability, while preventive work addresses latent problems before they become operational failures.

Use these categories to clarify intent rather than enforce a rigid label. One dependency upgrade may address compatibility and a known vulnerability. Record the actual expected outcome and verification so the team can prioritize the work without arguing over which single category owns the ticket.

Maintain the surrounding system as well as code

Review configuration, build tooling, deployment procedures, integrations, and operational documentation alongside application changes. A small source edit can fail if the release process depends on obsolete tools or undocumented credentials. Maintenance needs a reproducible environment and people who understand the affected business workflow.

Illustrative scenario: a payment provider changes its webhook signature format. The team must update verification, preserve retry handling, check stored event processing, and rehearse the deployed configuration. Editing the parser alone does not complete the adaptive maintenance task if authentic events are still rejected in production.

Plan and verify maintenance deliberately

Triage requests by user impact, urgency, change frequency, and uncertainty. Assign an owner, acceptance condition, and release path to each selected item. Keep emergency fixes visible in the same history so repeated incidents can reveal a structural problem that deserves planned improvement instead of another isolated patch.

Verify the affected behavior and adjacent integration paths before release, then observe the result against the original need. Document remaining constraints and retire obsolete workarounds when safe. Maintenance is an ongoing capability of a product team, even when individual tasks are delivered through bounded engagements.

Working sheet

Common maintenance categories
CategoryIllustrative taskVerification focus
CorrectiveRepair incorrect date filteringPreviously failing date cases
AdaptiveUpdate an external API integrationNew contract and compatibility checks
PerfectiveSimplify a frequently changed rule moduleMaintainability goal and stable behavior
PreventiveRemove a latent resource leakResource lifetime and failure-path checks
Download this worksheet (CSV)

Preventive maintenance

Schedule work from observed risk: an unsupported dependency, an expiring certificate, a restore procedure that was never exercised or a repeatedly flaky check. Give each item a verifiable completion condition.

Batch small dependency updates where appropriate, but keep rollback possible. A preventive task should leave a recorded check result and owner, not only a calendar reminder.

Questions about what is software maintenance?

Is maintenance only fixing bugs?

No. It also includes adapting to environmental changes, improving qualities, and preventing future failures.

Is software maintenance the same as CMMS?

No. This page concerns maintaining application software. CMMS generally concerns managing maintenance of physical assets and equipment.

How should I use the working sheet?

Download the CSV and replace the sample rows with evidence from your repository. Record a clear acceptance check and an owner for each item. Keep unresolved assumptions visible rather than treating the example as a completed assessment.

Sources and further reading

Examples are illustrative. They are not customer results, security guarantees, or a substitute for checking the documentation for your installed version.

Make the next change verifiable.

Getzilla is an open source workflow for changes to existing repositories. Inspect the project, define acceptance checks, and keep independent review in the loop.

See the repository workflow See current access and pricing