liveBook · Manning

Maintenance

Maintenance is the ongoing work of operating, correcting, repairing, adapting, updating, or supporting an existing system or content to preserve or improve its functioning.

How 2 Manning books explain it

Machine Learning System Design

The ongoing work of keeping existing system functionality working as its environment changes.

How it is used
Keeps existing ML system functionality working as customers, datasets, infrastructure, and organizational circumstances change.
How deep it goes
Develops an ownership and support checklist with organizational examples, but does not provide a technical incident-response procedure.
Examples
Contrasts a retailer’s stakeholder sign-offs and RACI matrix with an image-search company’s component owners and two-level on-call rotation.
What you can do after
Operate/configure it by assigning support roles, arranging incident coverage, maintaining documentation, and making incremental fixes.

Read how Machine Learning System Design explains maintenance →

Lead Developer Career Guide

The ongoing operational work of preserving, repairing, and updating software so that it continues to function reliably.

How it is used
Schedules recurring operational work to prevent downtime and errors and preserve system stability.
How deep it goes
Contrasts scheduled prevention with reactive recovery and gives an automation example, without specifying individual maintenance tasks.
Examples
Uses overnight automated maintenance with email alerts and places the maintenance phase after testing in waterfall projects.
What you can do after
Operate automated maintenance processes with email alerts to reduce manual checks and emergencies.

Read how Lead Developer Career Guide explains maintenance →

Related concepts

These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.