Differences

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

--- 75:remoteassociations [2020/11/19 04:25] – aakr
+++ 75:remoteassociations [2024/02/15 00:00] (current) – external edit 127.0.0.1
@@ Line 1: / Line 1: @@
-====== Manage Remote Associations ======
+====== Manage Process Interfaces ======
-One of the key capabilities of Stages is reuse of process elements. If a role, work product or guidance has been created in one workspace, it can be used in another process in a different workspace. This creates **remote associations** between the two workspaces.
+One of the key principles of Stages is that every process element should only be modeled once. If a role, work product or guidance has been created in one workspace, it can be used in another process in a different workspace. This creates **[[:general:processinterface|process interfaces]] **between the two workspaces.
-Remote associations allows central creation and management of process elements in the process they belong to. It also fosters communication between functions about their dependencies on each other. If an element is coming from another workspace, it is has a double arrow next to the name. In below Change Management process example, an activity requires Project Manager and Risk Manager roles which reside in Project Management workspace, to be consulted and this creates a remote association between the workspaces.
+Process interfaces allows creation and management of process elements in the processes they belong to. It also fosters communication between functions about their dependencies on each other. Process interfaces are indicated by double-arrow icon and name of workspace they belong to. In the following example, an activity in the Change Management process requires the consultation of the Project Manager and Risk Manager roles which reside in the Project Management workspace. This creates a process interface between the two workspaces.
 [[https://doc.stagesasaservice.com/lib/exe/fetch.php?tok=d58a0d&media=https://doc.stagesasaservice.com/lib/plugins/ckgedit/fckeditor/userfiles/image/75/remoteassoc_1.png|{{  https://doc.stagesasaservice.com/lib/plugins/ckgedit/fckeditor/userfiles/image/75/remoteassoc_1.png?direct&400x307  }}]]
-Remote associations are created by simply selecting a role, work product, guidance and other elements from another workspace using the [[:73:modeling|Browse]] option to add association.
+Process interfaces are created by typically selecting roles or work products from another workspace within the same workspace collection (//**TODO: see here for details**// ) or by using the [[:73:modeling|Browse]] option when adding the association.
 ===== Impact on Process Version =====
-One of the recommendations for process versioning is to not set working version as valid due to the impact on remote associations. During the life of the process (e.g. Change Management), if the ''working version'' is set as valid; and the processes (e.g. Requirements Management) it has remote associations with have a separate ''valid and working version'', then the remote associations will be linked to working and valid versions separately and appear twice (e.g. remote association to work product Functional Specification)
+One of the recommendations for process versioning is to not set working version as valid due to the impact on process interfaces.
+During the life of the source process (e.g. Change Management), if the ''working version'' is set as valid; and the target processes (e.g. Requirements Management) it interfaces with have a separate ''valid'' and ''working version,'' then the source process will show two interfaces (e.g. interface to work product Functional Specification).
 [[https://doc.stagesasaservice.com/lib/exe/fetch.php?tok=982af9&media=https://doc.stagesasaservice.com/lib/plugins/ckgedit/fckeditor/userfiles/image/74/workingversionasvalidcm_1.png|{{  https://doc.stagesasaservice.com/lib/plugins/ckgedit/fckeditor/userfiles/image/74/workingversionasvalidcm_1.png?direct&900x425  }}]]
@@ Line 17: / Line 19: @@
 [[https://doc.stagesasaservice.com/lib/exe/fetch.php?tok=9c89e3&media=https://doc.stagesasaservice.com/lib/plugins/ckgedit/fckeditor/userfiles/image/74/workingasvalidissue_1.png|{{  https://doc.stagesasaservice.com/lib/plugins/ckgedit/fckeditor/userfiles/image/74/workingasvalidissue_1.png?direct&700x319  }}]]
-If Change Management continues to have working as valid version, it can lead to some unintended consequences. One, end users will find this confusing and not know which input to refer back to. Secondly, a modeler might manually choose to delete on the duplicates. In this case, if the input without the V (i.e. the one linking back to working version) is deleted and later Change Management process is released and marked valid, then the working version will no longer have the remote association as it was previously deleted. This might potentially introduce an error in working and future baselined version of missing remote associations.
+If Change Management continues to have working as valid version, it can lead to some unintended consequences. One, end users will find this confusing and not know which input to refer back to. Secondly, a modeler might manually choose to delete one of the duplicates. In this case, if the input without the V (i.e. the one linking back to working version) is deleted and later Change Management process is released and marked valid, then the working version will no longer have the process interface as it was previously deleted. This might potentially introduce an error in working and future baselined version of missing process interfaces.
+===== Manage Process Version in context of Process Interface =====
+The recommended practice is// when a process where the interfaces are modeled in the working version is baselined by creating a process version, then the process(es) which have such associations should also have working version baselined by creating a new process version. //
+In the following example, Project Manager from Project Management Process is added as 'Consulted' for Create Change Request ''activity'' in Change Management process.[[https://doc.stagesasaservice.com/lib/exe/fetch.php?tok=e3c5d0&media=https://doc.stagesasaservice.com/lib/plugins/ckgedit/fckeditor/userfiles/image/73/remoteassoc_cm_consulting.png|{{  https://doc.stagesasaservice.com/lib/plugins/ckgedit/fckeditor/userfiles/image/73/remoteassoc_cm_consulting.png?direct&600x450  }}]]
+This process interface reflects in working version of both the workspaces.
+[[https://doc.stagesasaservice.com/lib/exe/fetch.php?tok=b115de&media=https://doc.stagesasaservice.com/lib/plugins/ckgedit/fckeditor/userfiles/image/73/remoteassoc_pm_consulting.png|{{  https://doc.stagesasaservice.com/lib/plugins/ckgedit/fckeditor/userfiles/image/73/remoteassoc_pm_consulting.png?direct&600x432  }}]]
+If after establishing interface shown above Change Management workspace has process version released, while the Project Management does not, then as shown below newly released process version will fail to show the interface with Project Manager as Consulted role.
+[[https://doc.stagesasaservice.com/lib/exe/fetch.php?tok=0043de&media=https://doc.stagesasaservice.com/lib/plugins/ckgedit/fckeditor/userfiles/image/75/remoteassoc_cm_noshow.png|{{  https://doc.stagesasaservice.com/lib/plugins/ckgedit/fckeditor/userfiles/image/75/remoteassoc_cm_noshow.png?direct&600x398  }}]]To fix this issue, a new process version of Project Management should also be released. Once the process is baselined, interfaces will appear on both sides.
+In summary, a process interface appears on both sides only when both of the workspaces are either in working or both have a distinct version.
+===== Transformation in Integrated Processes =====
+When processes which interface with each other are integrated in the same workspace, then the interfaces are transformed into regular process association in the [[:75:useprocessmodules|integrated workspace]]. In below example, roles belong to Change Management, Project Management, Risk Management and System & Software Design process modules have been integrated into Software Engineering workspace. As all the processes and roles now reside in the same workspace, the interface appear as regular associations.
+[[https://doc.stagesasaservice.com/lib/exe/fetch.php?tok=4c5070&media=https://doc.stagesasaservice.com/lib/plugins/ckgedit/fckeditor/userfiles/image/75/remoteassoc_integrated.png|{{  https://doc.stagesasaservice.com/lib/plugins/ckgedit/fckeditor/userfiles/image/75/remoteassoc_integrated.png?direct&300x343  }}]]