Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Next revision
Previous revision
262:collectionmigration [2026/09/28 19:26] – created - external edit 127.0.0.1262:collectionmigration [2026/11/19 12:21] (current) – Goetz, Sebastian
Line 1: Line 1:
-====== Migrate process interface handling ======+====== Migrate process interface handling to workspace collections ======
  
-If you have used workspace groups to control process interfaces, you need to create workspace collections to group the workspaces that should continue to have interfaces between each other.+With Stages 26.1, the way Stages decides **between which workspaces process interfaces are created** has changed. The workspace settings **Group** and **Common Elements** no longer exist. Their purpose is now fulfilled by **[[262:process_architecture#use_workspace_collections_to_control_process_interfaces|workspace collections]]**.
  
-Examples are+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 are remodeled.
  
-  * all modelling workspaces that will be integrated into standard process workspaces +===== Background: What are process interfaces? =====
-  * standard process workspaces that should have interfaces to organizational processes+
  
-If you have used "common elements" workspaces, those workspaces need to be added to all workspace collections that should have interfaces to them.+A process interface is an association from an element in one workspace to an element in **another** workspace, e.g. a work product of the "Software Development" process that is associated with a milestone defined in the "Lifecycle Management" workspace.
  
-Please note that updating process modules in and copying elements into workspaces that are __not__ part of any workspace collection, will __not__ result in any process interfaces anymore.+Process interfaces are created automatically, mainly in the following situations: 
 +  * **Import of processes** into a workspace 
 +  * **Module update** – process modules are integrated or updated in a workspace 
 +  * **Copy of processes** or process elements into a workspace
  
-**//Modelling tip://** after the upgrade to 26.1, use the "[[262:remoteassociations|Process Interfaces]]" menu to find out about current process interfaces of a particular workspace and add workspace collections accordingly.+In all these cases Stages searches for suitable target elements in other workspaces. **Which workspaces are searched** is what has changed. Therefore the new collection-based behavior mainly affects these three operations.
  
-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/interfaces were created to workspaces outside of this group. It was used to isolate e.g. one program from other programs.
 +  * **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:** Importing processes into, updating process modules in, or copying processes into a workspace that is **not part of any workspace collection** will **not** create any process interfaces anymore. This also applies if you did **not** use the Group setting before.
 +
 +**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:remoteassociations|Process Interfaces]] menu of each relevant workspace to see its current process interfaces.
 +  - **Define collections:** For each set of workspaces that should have interfaces to each other, create a workspace collection via ''Administration > Workspaces > Collections'' (see the examples below).
 +  - **Add shared workspaces:** Add workspaces that were flagged as **Common Elements** to every collection that needs interfaces to them.
 +  - **Verify:** Perform a module update in a representative workspace of every collection and check via the [[262:remoteassociations|Process Interfaces]] menu that the expected interfaces exist – and that no unwanted interfaces were created.
 +
 +//Tip:// Use speaking names for collections that describe their purpose, e.g. "Program A", "Standard Process Development" or "Organizational Processes".
 +
 +===== Examples =====
 +
 +The following examples are based on the process architecture described in [[262:process_architecture|Define a Process Architecture]].
 +
 +==== Example 1: Process areas integrated into a standard process ====
 +
 +**Setup up to 7.12:** The process area workspaces "Requirements Engineering", "Software Development" and "Testing" have interfaces to each other (e.g. a work product of Requirements Engineering is input to an activity in Testing). They are integrated as modules into the standard process workspace "Software Engineering".
 +
 +**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, Software Development, Testing, Software Engineering |
 +
 +**Result:** When a process area is updated in "Software Engineering", the interfaces between the process areas are created correctly.
 +
 +==== Example 2: Common elements workspace (e.g. Lifecycle Management) ====
 +
 +**Setup up to 7.12:** The workspace "Lifecycle Management" defines phases, milestones and value streams that are used by all process areas. It was flagged as **Common Elements**, so that all workspaces – even those inside a group – could create interfaces to it.
 +
 +**Setup from 26.1:** Add "Lifecycle Management" to every collection that needs interfaces to its elements:
 +
 +^ Collection ^ Member workspaces ^
 +| Standard Process Development | **Lifecycle Management**, Requirements Engineering, Software Development, Testing, Software Engineering |
 +| Program A | **Lifecycle Management**, Program A, Component A1 Hardware, Component A2 Software |
 +| Program B | **Lifecycle Management**, Program B, Component B1 Hardware, Component B2 Software, Component B3 Software |
 +
 +**Result:** All workspaces can reference phases and milestones of "Lifecycle Management". The same approach applies to other shared workspaces, e.g. organizational processes or a company-wide role catalog.
 +
 +==== Example 3: Isolated programs (previously Group) ====
 +
 +**Setup up to 7.12:** "Program A" and "Program B" both integrate the same "Software Engineering" process. Each program consists of several workspaces (program, hardware and software components). To prevent "Program A" from creating interfaces to the components of "Program B", each program was set up as a **Group**.
 +
 +**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:** "Program A" only has interfaces to "Component A1 Hardware" and "Component A2 Software" – even though the same process modules are integrated in the components of "Program B". Component workspaces may even use different tailorings or versions of the same module and still interface correctly with their parent program.
 +
 +==== Example 4: Standard process with interfaces to organizational processes ====
 +
 +**Setup up to 7.12:** The standard process "Software Engineering" has interfaces to the organizational processes "Quality Management" and "Human Resources", e.g. roles or templates defined there.
 +
 +**Setup from 26.1:**
 +
 +^ Collection ^ Member workspaces ^
 +| Organizational Processes | Software Engineering, Quality Management, Human Resources |
 +
 +**Result:** "Software Engineering" is now member of two collections ("Standard Process Development" and "Organizational Processes"). Interface targets are searched in the workspaces of **both** collections.
 +
 +==== 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:** The collections make visible which workspaces belong together and where process interfaces can be created.
 +  * **Robustness:** The interface search uses internal identifiers instead of names. Workspaces can therefore be named arbitrarily.
 +  * **Better search results:** End users get the expected results when using the search scope "Recommended Workspaces", because it is based on the same collections.