Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revision | |||
| 262:collectionmigration [2026/11/19 11:59] – Goetz, Sebastian | 262:collectionmigration [2026/11/19 12:21] (current) – Goetz, Sebastian | ||
|---|---|---|---|
| Line 32: | Line 32: | ||
| **Existing process interfaces are kept** during the upgrade. Collections only affect interfaces that are newly created by future imports, module updates or copy operations. | **Existing process interfaces are kept** during the upgrade. Collections only affect interfaces that are newly created by future imports, module updates or copy operations. | ||
| + | |||
| + | **Reference models** (e.g. standards such as Automotive SPICE or ISO 26262) do **not** need to be added to workspace collections – just as they did not need to be part of a group in Stages 7.12. Compliance mappings to reference models are still transferred during imports, module updates and copy operations. | ||
| ===== Migration procedure ===== | ===== Migration procedure ===== | ||
| Line 45: | Line 47: | ||
| ===== Examples ===== | ===== Examples ===== | ||
| + | The following examples are based on the process architecture described in [[262: | ||
| ==== Example 1: Process areas integrated into a standard process ==== | ==== Example 1: Process areas integrated into a standard process ==== | ||