Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
| 262:collectionmigration [2026/09/28 19:26] – created - external edit 127.0.0.1 | 262:collectionmigration [2026/11/19 12:21] (current) – Goetz, Sebastian | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ====== Migrate process interface handling ====== | + | ====== Migrate process interface handling |
| - | If you have used workspace groups to control | + | With Stages 26.1, the way Stages decides **between which workspaces |
| - | Examples | + | If your Stages installation used one of these settings, or if your processes rely on process interfaces between workspaces, you need to set up workspace collections after the upgrade. This page explains what has changed and shows how typical setups |
| - | * all modelling workspaces that will be integrated into standard | + | ===== Background: What are process interfaces? ===== |
| - | * standard process workspaces that should have interfaces | + | |
| - | If you have used " | + | A process interface is an association from an element in one workspace |
| - | Please note that updating | + | Process interfaces are created automatically, |
| + | * **Import of processes** into a workspace | ||
| + | * **Module update** – process modules | ||
| + | * **Copy of processes** or process | ||
| - | **//Modelling tip://** after the upgrade to 26.1, use the " | + | In all these cases Stages searches for suitable target elements in other workspaces. |
| - | As a result, process interface creation should now be much more transparent and easier to control. | + | ===== What has changed ===== |
| + | ^ ^ Up to Stages 7.12 ^ From Stages 26.1 ^ | ||
| + | ^ Controlling mechanism | Workspace settings **Group** and **Common Elements** | **Workspace collections** | | ||
| + | ^ Workspaces searched for interface targets | Depending on the Group / Common Elements settings | **All workspaces in all collections** the current workspace belongs to | | ||
| + | ^ Workspace is in no group / no collection | Interfaces could be created to all workspaces | **No** process interfaces are created | | ||
| + | ^ Shared workspace (e.g. lifecycle, organizational processes) | Flagged as **Common Elements** workspace | Added as member to **every collection** that needs interfaces to it | | ||
| + | |||
| + | In detail: | ||
| + | * **Group** – a workspace flagged as group ensured that no associations/ | ||
| + | * **Common Elements** – a workspace flagged as common elements lifted this restriction. Its elements could be referenced from inside any group. | ||
| + | * **Workspace collections** – instead of excluding workspaces, you now explicitly define which workspaces belong together. A workspace can be member of several collections. Interfaces are only created to workspaces that share at least one collection with the current workspace. | ||
| + | |||
| + | **Important: | ||
| + | |||
| + | **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 ===== | ||
| + | |||
| + | - **Before the upgrade:** Document your current setup. Note which workspaces were flagged as **Group** and which as **Common Elements**, and which workspaces have interfaces to each other. | ||
| + | - **After the upgrade (on the test system):** Use the [[262: | ||
| + | - **Define collections: | ||
| + | - **Add shared workspaces: | ||
| + | - **Verify:** Perform a module update in a representative workspace of every collection and check via the [[262: | ||
| + | |||
| + | //Tip:// Use speaking names for collections that describe their purpose, e.g. " | ||
| + | |||
| + | ===== Examples ===== | ||
| + | |||
| + | The following examples are based on the process architecture described in [[262: | ||
| + | |||
| + | ==== Example 1: Process areas integrated into a standard process ==== | ||
| + | |||
| + | **Setup up to 7.12:** The process area workspaces " | ||
| + | |||
| + | **Setup from 26.1:** Create one collection that contains all workspaces that make up the standard process: | ||
| + | |||
| + | ^ Collection ^ Member workspaces ^ | ||
| + | | Standard Process Development | Requirements Engineering, | ||
| + | |||
| + | **Result:** When a process area is updated in " | ||
| + | |||
| + | ==== Example 2: Common elements workspace (e.g. Lifecycle Management) ==== | ||
| + | |||
| + | **Setup up to 7.12:** The workspace " | ||
| + | |||
| + | **Setup from 26.1:** Add " | ||
| + | |||
| + | ^ Collection ^ Member workspaces ^ | ||
| + | | Standard Process Development | **Lifecycle Management**, | ||
| + | | Program A | **Lifecycle Management**, | ||
| + | | Program B | **Lifecycle Management**, | ||
| + | |||
| + | **Result:** All workspaces can reference phases and milestones of " | ||
| + | |||
| + | ==== Example 3: Isolated programs (previously Group) ==== | ||
| + | |||
| + | **Setup up to 7.12:** " | ||
| + | |||
| + | **Setup from 26.1:** Create one collection per program: | ||
| + | |||
| + | ^ Collection ^ Member workspaces ^ | ||
| + | | Program A | Program A, Component A1 Hardware, Component A2 Software | | ||
| + | | Program B | Program B, Component B1 Hardware, Component B2 Software, Component B3 Software | | ||
| + | |||
| + | **Result:** " | ||
| + | |||
| + | ==== Example 4: Standard process with interfaces to organizational processes ==== | ||
| + | |||
| + | **Setup up to 7.12:** The standard process " | ||
| + | |||
| + | **Setup from 26.1:** | ||
| + | |||
| + | ^ Collection ^ Member workspaces ^ | ||
| + | | Organizational Processes | Software Engineering, | ||
| + | |||
| + | **Result:** " | ||
| + | |||
| + | ==== Example 5: Workspace without any interfaces ==== | ||
| + | |||
| + | **Setup up to 7.12:** A standalone workspace (e.g. a sandbox or training workspace) was not meant to have interfaces to other workspaces. | ||
| + | |||
| + | **Setup from 26.1:** Do **not** add the workspace to any collection. No process interfaces will be created for it. | ||
| + | |||
| + | ===== Additional benefits ===== | ||
| + | |||
| + | * **Transparency: | ||
| + | * **Robustness: | ||
| + | * **Better search results:** End users get the expected results when using the search scope " | ||