Differences

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

--- 72:modules [2018/06/11 20:40] – [Use process modules] bkkr
+++ 72:modules [2019/01/16 21:12] – emr
@@ Line 1: / Line 1: @@
-[[:72:start|Stages V7.2]]
 ====== Use process modules ======
-All processes follow the metamodel, but have differences in the logistics. There are certain activities that will be the same in certain processes. You can create a module to easier make a new process. The module is a specific part of the process. You can create modules and then insert them into processes instead of creating each individual step again.
+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"
+===== Update process modules =====
+- Spot the outdated modules
+- Update them one by one or multiple in sequence
+===== Remove process modules =====
+- Remove them
+===== Define interfaces between 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.
+- Remote associations
-TBD
+- Become normal associations when both modules are added to one process