Differences

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

--- 72:modules [2018/06/25 13:04] – [Use process modules] bkkr
+++ 72:modules [2020/11/24 17:34] (current) – removed aakr
@@ Line 1: / Line 1: @@
-[[:72:start|Stages V7.2]]
-====== Use process modules ======
-Engineering processes can be broken down into process modules that are connected by interfaces. All processes conform to the metamodel, so the process modules also conform to the metamodel. Certain projects contain the same parts of a different process, which is the process module. Stages allows a process module to be used in multiple different project- or program-specific processes so that you only need to make the process one time rather than creating it for every project. By breaking down processes into process modules, changes can be made quicker and with less risk for the overall system, and review and approval cycles can be reduced allowing for an earlier practical use.
-**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.
-//Probably need a better example ^^^^^//
-TBD
-Just like a system or a system of systems, processes can be broken down into modules that are connected by interfaces. Benefits of using process modules are that changes can be applied quicker with less risk for the overall system, and review and approval cycels 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.
-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.
-^^^ I will put this in a better order and transitions later