Learn › The category

What is software maintenance? The four types, and which AI can do

Software maintenance is everything done to software after it first works, to keep it working: fixing what breaks, adapting it as its surroundings change, improving it, and heading off problems. It has four standard types. Two of them have clear signals and clear checks, which makes them work an AI system can do on its own.

The four types

TypeWhat it meansExample
CorrectiveFixing something that is brokenA page crashes when a field is empty
AdaptiveKeeping up with a changing environmentA package you use releases a new version; a host changes how it builds
PerfectiveMaking it better for usersA faster search, a clearer screen
PreventiveFixing things before they cause troublePatching a security flaw before anyone exploits it; adding a test where a bug appeared

Corrective work is what most people picture. Adaptive work is the one that surprises people: the world your software runs in keeps moving even when your code does not.

Why it never gets done

Maintenance competes with building, and building wins. A new feature has a deadline and someone asking for it. An upgrade does not.

So maintenance is done in the gaps, or when something forces it. A crash sits for three weeks because it is not quite urgent. Packages drift a year behind. Then a security flaw is published and the upgrade that was easy is now hard.

The cost shows up as slowness. Every change takes longer because the ground under it is uneven.

Which types AI can do

A task can be handed to an AI system when two things exist: a signal that says it needs doing, and a check that says it is done.

TypeSignal and check exist?Can AI do it on its own?
CorrectiveYes. An error, and a test that passes once it is fixedYes, for bugs that can be reproduced
AdaptiveYes. A new version or a failed build, and tests that pass on the changeYes, for upgrades and build fixes
PreventivePartly. A published flaw is a clear signal; “this might break one day” is notYes for known flaws and secrets; no for hunches
PerfectiveNo. “Better” is a judgment about your usersNo. This stays with people

That split is the idea behind autonomous software maintenance: hand the work that can be checked to a system that finds it on its own, and keep the work that needs judgment.

What Bugstack covers

Bugstack does autonomous software maintenance. By type:

  • Corrective: it fixes crashes your app reports, a failing build on your main branch, and a failed deploy on Render.
  • Adaptive: it scans your packages every day and opens upgrade pull requests for npm.
  • Preventive: it checks for vulnerable packages every four hours and opens the fix; it scans for committed secrets every night; it runs a security audit when you ask.
  • Perfective: not covered. Bugstack does not build features or decide what your product should do.

Every change arrives as a pull request, and a new repository starts with you merging each one.

Questions

What are the four types of software maintenance?

Corrective (fixing faults), adaptive (keeping up with a changing environment), perfective (improving it for users) and preventive (fixing problems before they occur).

How much does software maintenance cost?

It varies widely by system. It is commonly described as a large share of the lifetime cost of software, because a system is built once and then maintained for years.

Can software maintenance be automated?

The corrective, adaptive and much of the preventive work can, where there is a clear signal and a clear check. Deciding how to improve a product cannot.

See it work on your own code.

$100 a month

Includes $100 of usage credit every month. Start with a 14-day trial: $50 of credit and a first security audit on us. A card is required.