Differences

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

--- 72:modules [2018/07/05 14:11] – [Use process modules] bkkr
+++ 72:modules [2019/01/16 21:12] – emr
@@ Line 1: / Line 1: @@
-[[:72:start|Stages V7.2]]
 ====== Use process modules ======
-Just like a system or a system of systems, processes can be broken down into modules that are connected by interfaces. In many cases, these interfaces are work products. Benefits of using process modules are that changes can be applied quicker with less risk for the overall system, and review and approval cycles can be reduced allowing for quicker use, feedback, and improvement of the system. Process modules can also inherit from other modules which is useful in creating project- or program-specific processes.
+To efficiently manage a large process landscape, it can be broken down into modules. These modules can be connected via interfaces. Process modules can form a hierarchy or process architecture.
+Typical process modules are Requirements Engineering, Design, or Project Management. As process modules can be used to separate common from specific processes, a "Design" process module could be used to contain the common elements in a "Engine Design" and "Transmission Design" process module. See [[:how:best:product_lines|process variant management]] for more info.
+The only difference between a process and a process module is that a process module can be added to other processes or process modules, whereas a process can not be added anywhere else.
+===== Define a process module =====
+A process module resides in a workspace just like a normal process. In fact, the only thing that differentiates process modules from processes is this setting, which can be changed via the ''Management > Settings'' menu.
+SCREENSHOT
+If this setting is set to "Process Module", the module can be added to other processes.
+===== Adding process modules to a process =====
+Only specific versions of process modules can be added to other processes. This increases the consistency within your process architecture. Before adding modules to another process, a process version needs to be created for each one of them. See [[:72:versions|process version management]] for more info how to do this.
+Although it is technically possible to add the Working Version of a module to a process, it is not recommended to do so, because the content in the Working Version can change, so you do not know which version of the module content is being added.
+To add modules to a process, switch to the process you would like to add the modules to, and go to the ''Management > Process Modules'' menu.
+SCREENSHOT: modules main dialog
+In the first tab, you can find the list of already added modules. In the second tab you can find the list of processes that the current module has been added to.
+Click or tap on ''Add module'' to add new process modules. Select the modules either via browsing or by typing their names. Already selected modules will show up on the right side.
+SCREENSHOT: add module dialog
+Click or tap ''Next'' to select the versions for each module. Per default, the Valid Version of each module is selected.
+To add the modules, click or tap ''Next'' once more. The operation will run in the background, so you can continue working while the modules are being added.
+If the added modules have [[:general:processinterface|interfaces]] to other modules, which are already added, those interfaces will be converted to [[:general:process|normal associations]].
+===== Create a new process from process modules =====
+- Create new workspace
+- Select "Add Modules"
-Through the module-based approach, changes can be made instantly into all process instances, instead of having to wait for next publication of overall process documentation.
+===== Update process modules =====
-**Ex.** A car manufacturer has three different versions of a model. The differences in the models are the engines. The same process of making the body of the car is in all of the models. The entire process for the car was created and then the modules that are the same in each model are used for each.
+- Spot the outdated modules
-//Probably need a better example ^^^^^//
+- Update them one by one or multiple in sequence
-=== Create Process Modules ===
-=== Add Process Modules ===
+===== Remove process modules =====
-For a project- or program-specific workspace, adding process modules from the standard process is a convenient method to create a process.
+- Remove them
-**Steps:**
+===== Define interfaces between modules =====
-   - In your project- or program-specific workspace go to the management tab.
+- Remote associations
-  - Click 'Process Modules'
-  - Click '+ Add modules'
-  - Select the module
-      - If you know the name of the process module, type the name of it in the box with 'Start typing'. A drop down menu of available modules appears. Click the desired module and click 'Next' to add the module.
-      - If you want to search modules, click 'or browse modules.' On this menu, you can browse through the other workspaces to extract a module. Typically, you will take modules from the 'Standard Processes' folder. Click 'Save' to select the module then click 'Next' to add the module.
-  - Stages adds the module to the workspace.
-TBD
+- Become normal associations when both modules are added to one process