Glossary · Change, versions and configuration
Deprecation path
In systems engineering, a deprecation path is a controlled plan for announcing, replacing, migrating and removing an old version or function. It gives dependents a defined period and a defined route to move away from what is being retired.
- Data and interfaces
- Systems engineering
- Technical documentation
In one sentence
A deprecation path plans how an old version or function is announced, replaced, migrated and finally removed without surprising dependents.
Example
A robot manufacturer announces that a legacy I/O mapping will be removed in two releases, publishes the replacement mapping and a migration guide, and keeps both active during the transition.
Explained in context
Context cards connect this term with others to answer one question. Also in British English and German.
How it applies
- Integrated systems: Define the steps: announcement, availability of the replacement, migration period, removal date. Each step should be traceable to a lifecycle state such as deprecated or retired.
- Machine safety: If a deprecated function is part of a safety function or its diagnostics, removal is a safety-relevant change and goes through change control.
- Technical documentation: Mark deprecated functions in manuals and interface documents, name the replacement and state the removal version. Remove the content only when the function is actually gone from all supported versions.
- Evidence: Keep evidence for the old function as long as supported installations still use it.
Deprecation vs. removal
Deprecation announces that something will go away and discourages new use. Removal is the actual breaking change. A deprecation path exists to make the removal predictable.