Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revision | |||
| en:safeav:softsys:lifecycleconfigmansupp [2026/06/17 15:08] – karlisberkolds | en:safeav:softsys:lifecycleconfigmansupp [2026/06/17 16:12] (current) – karlisberkolds | ||
|---|---|---|---|
| Line 34: | Line 34: | ||
| Maintainability is a safety property over the product life. Autonomous systems often operate for years, while software dependencies and hardware platforms change much faster. A safe architecture needs separation between safety-critical and non-safety functions, explicit compatibility matrices, reproducible builds, update and rollback mechanisms, and a release process that prevents configuration drift. Over-the-air updates and software-defined features can reduce service cost and add capability, but they also transform validation into a continuing obligation after the first product release. | Maintainability is a safety property over the product life. Autonomous systems often operate for years, while software dependencies and hardware platforms change much faster. A safe architecture needs separation between safety-critical and non-safety functions, explicit compatibility matrices, reproducible builds, update and rollback mechanisms, and a release process that prevents configuration drift. Over-the-air updates and software-defined features can reduce service cost and add capability, but they also transform validation into a continuing obligation after the first product release. | ||
| - | ====== | + | ====== |
| Configuration management is implemented through a set of recurring activities. Configuration identification defines what is controlled and how items are named. Configuration control defines how proposed changes are reviewed, approved, implemented and verified. Status accounting records the current and historical state of configuration items. Configuration audits confirm that documentation, | Configuration management is implemented through a set of recurring activities. Configuration identification defines what is controlled and how items are named. Configuration control defines how proposed changes are reviewed, approved, implemented and verified. Status accounting records the current and historical state of configuration items. Configuration audits confirm that documentation, | ||
