Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
| en:safeav:softsys:configuration [2025/10/17 15:33] – created agrisnik | en:safeav:softsys:configuration [2026/04/24 09:32] (current) – removed raivo.sell | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ====== Configuration Concepts and Challenges ====== | ||
| - | |||
| - | In software engineering, | ||
| - | * The correct versions of software components are used. | ||
| - | * Changes are controlled, reviewed, and documented. | ||
| - | * The entire system remains consistent and reproducible across teams and environments. | ||
| - | |||
| - | According to ISO/ | ||
| - | “A discipline applying technical and administrative direction and surveillance to identify and document the functional and physical characteristics of a configuration item, control changes to those characteristics, | ||
| - | |||
| - | In other words, Configuration Management keeps the software stable while it evolves. Configuration management exists to: | ||
| - | * **Ensure traceability** – every change can be traced to its origin (e.g., requirement, | ||
| - | * **Prevent chaos** – without CM, multiple developers could overwrite each other’s work or deploy incompatible versions. | ||
| - | * **Enable collaboration** – teams distributed globally can work on the same product using consistent artefacts. | ||
| - | * **Maintain compliance** – in safety-critical domains (automotive, | ||
| - | * **Support automation** – CI/CD pipelines rely on version-controlled repositories and configuration metadata. | ||
