Differences

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

--- 75:instantiate [2020/06/11 21:26] – [Create a new workspace] aakr
+++ 75:instantiate [2024/02/15 00:00] (current) – external edit 127.0.0.1
@@ Line 1: / Line 1: @@
 ====== Instantiate a Process in a Workspace ======
-The process of instantiation is taking the standard process and giving it details of a “real” context. It allows to set up project or program specific instances without recreating standard processes each time.
+Process instantiation is using a standard process and tailoring it for a specific project, program, or team context.
-In Stages, process instance can be created for specific projects, products or programs by integrating predefined standard processes. This is combined with the powerful feature of on-demand ability to update these process instances, when newer versions of standard processes are released.
+Some advantages of process instantiation are
+  * The version of a process instance can be kept stable. Even if the standard process from which it was initially derived from is being updated, the instance will not be impacted until a decision is being made to update it to a newer version.
+  * Program, project, or other teams can rely on the defined process in their instance. Only the relevant processes are contained in this instance. Everything else is being tailored out.
+  * Project-specific work products can be managed directly in the process instance. Team members can directly access them, regardless of where they are actually stored (e.g. Sharepoint, SVN, Integrity). Project and program managers can see the status of work products across different storage repositories.
 ===== Role of Process Architecture and Tailoring =====
@@ Line 13: / Line 17: @@
 ===== Create a new workspace =====
-In order to instantiate a process for a new program or project, [[:72:manage_workspaces|new workspace]][[:73:workspaces|(s)]] must be created by the administrator. The location and level of the workspace is determing by the process architecture. New workspaces(s) for instantiated process allows control over process versioning, permission control, user addition as well as ability to push the instantiated processes into engineering tools like JIRA, RTC. Milestones and phases specific to project or program can also be modeled withint this workspace.
+In order to instantiate a process for a new program or project, [[:73:workspaces|new workspace(s)]] must be created by the administrator. The location and level of the workspace is determing by the process architecture. New workspaces(s) for instantiated process allows control over process versioning, permission control, user addition as well as ability to push the instantiated processes into engineering tools like JIRA, RTC. Milestones and phases specific to project or program can also be modeled within this workspace.
 [[https://doc.stagesasaservice.com/lib/exe/fetch.php?tok=cdb9c1&media=https://doc.stagesasaservice.com//lib/plugins/ckgedit/fckeditor/userfiles/image/75/newworkspace.png|{{  https://doc.stagesasaservice.com//lib/plugins/ckgedit/fckeditor/userfiles/image/75/newworkspace.png?direct&800x382  }}]]
@@ Line 19: / Line 23: @@
 [[https://doc.stagesasaservice.com/lib/exe/fetch.php?tok=55b2b0&media=https://doc.stagesasaservice.com/lib/plugins/ckgedit/fckeditor/userfiles/image/75/projectc_newworkspace_1.png|{{  https://doc.stagesasaservice.com/lib/plugins/ckgedit/fckeditor/userfiles/image/75/projectc_newworkspace_1.png?direct&300x295  }}]]
-Existing standard process will then be integrated into this new workspace by using the ''Add modules'' option. All the process elements and tailoring rules from standard process variants are inherited in the instantiated process.
+Existing standard process will then be integrated into this new workspace by using the ''Add modules''  option. All the process elements and tailoring rules from standard process variants are inherited in the instantiated process.
 [[https://doc.stagesasaservice.com/lib/exe/fetch.php?tok=41e55b&media=https://doc.stagesasaservice.com/lib/plugins/ckgedit/fckeditor/userfiles/image/75/instantiation_addmodule.png|{{  https://doc.stagesasaservice.com/lib/plugins/ckgedit/fckeditor/userfiles/image/75/instantiation_addmodule.png?direct&1400x344  }}]]
-The recommended practice is to choose ''valid version'' of a release variant to instantiate for a new project or program.
+The recommended practice is to choose ''valid version''  of a release variant to instantiate for a new project or program.
 [[https://doc.stagesasaservice.com/lib/exe/fetch.php?tok=7618b7&media=https://doc.stagesasaservice.com/lib/plugins/ckgedit/fckeditor/userfiles/image/75/instantiation_validversion.png|{{  https://doc.stagesasaservice.com/lib/plugins/ckgedit/fckeditor/userfiles/image/75/instantiation_validversion.png?direct&800x341  }}]]
 ===== Use Tailoring =====
@@ Line 38: / Line 41: @@
 Next step would be add specific details like assigning users to roles and adding project specific work products.
+===== Assign user to a role =====
-===== Assign users =====
 A project manager can assign users for a given project or program. The user should already be present in Stages user list. This can be done by assigning the user to a role within the program or project.
@@ Line 46: / Line 48: @@
 [[https://doc.stagesasaservice.com/lib/exe/fetch.php?tok=aaa744&media=https://doc.stagesasaservice.com/lib/plugins/ckgedit/fckeditor/userfiles/image/75/instantiation_users.png|{{  https://doc.stagesasaservice.com/lib/plugins/ckgedit/fckeditor/userfiles/image/75/instantiation_users.png?direct&800x312  }}]]
 =====   =====
 =====   =====
 ===== Working with CM Systems =====
@@ Line 58: / Line 57: @@
 Stages can interact with configuration management systems like Sharepoint, Subversion, Integrity to work with remotely stored files. Stages administator is responsible for this configuration.
+Refer to [[:75:workwithfiles|working with files]] section for more details.
-===== Initialize Process Execution Systems =====
+=====   =====