Glossary · Change, versions and configuration
Version compatibility
In systems engineering, version compatibility is the defined ability of system or interface versions to work together without unacceptable behavior. It is stated as a matrix of versions that have been specified and verified to work together.
- Data and interfaces
- Systems engineering
- Verification
In one sentence
Version compatibility defines which system and interface versions may work together, backed by tests rather than assumptions.
Example
An integrator keeps a compatibility matrix for a production line listing which robot controller, safety PLC and MES interface versions have been tested together.
How it applies
- Integrated systems: Maintain a compatibility matrix covering protocol, data model and behavior versions. “Compatible” should always mean “verified together”.
- Machine safety: Unacceptable behavior includes silent misinterpretation, not only communication failure. Include safety-relevant reactions in compatibility tests.
- Evidence: Link the matrix to the configuration baseline and to the test results. An untested combination is not compatible by default.
- Technical documentation: Operating and service documents should state which versions a spare part or update is compatible with, so that field replacements do not create an unverified integrated system.
Subtypes
Backward compatibility covers new versions working with old peers and data; forward compatibility covers current versions handling future extensions.