Differences

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

--- 75:modeling-routine-process [2020/09/22 18:23] – aakr
+++ 75:modeling-routine-process [2024/02/15 00:00] (current) – external edit 127.0.0.1
@@ Line 1: / Line 1: @@
-====== Modeling Routine Processes ======
+====== Model and Use Generic Processes ======
-In different phases of product development cycle, there are fairly routine processes which are repeated in different workflows. For example, joint review as a sub-process is executed for different types of work product like a project plan, system design architecture, etc. Though the processes will differ, some of the sub-processes like review go through same steps to achieve the end result.
+In different phases of product development cycle, some of the processes are repeated in various workflows. For example, joint review as a sub-process is executed to review different types of work product like a project plan, system design, etc. Although processes will differ, generic processes like review go through same steps to achieve the end result.
-In Stages, such routine processes can be modeled once and reused in workflows which consume the process.
+In Stages, such processes can be modeled once and reused in workflows which consume the process.
-===== Define a routine process =====
+===== Define a Generic Process =====
-Model the routine process process in a workflow. The details of this routine process should be generic enough for it to be consumed in other workflows.
+Model the generic process process in a workflow. The details of this process should be general enough for it to be consumed in other workflows.
-Joint Review Process is a typical peer review that happens at differents areas of product development lifecycle. It is held within development phases, between milestone reviews, on completion of work products. Defining it as a routine process allows to keep the details of the process consistent and standard across any form of review.
+Joint Review Process is a typical peer review that happens at differents areas of product development lifecycle. It is held within development phases, between milestone reviews, on completion of work products. Defining it as a generic process allows to keep the details of the process consistent and standard across any form of review.
-[[https://doc.stagesasaservice.com/lib/exe/fetch.php?tok=a7aead&media=https://doc.stagesasaservice.com/lib/plugins/ckgedit/fckeditor/userfiles/image/75/jointreview.png|{{  https://doc.stagesasaservice.com/lib/plugins/ckgedit/fckeditor/userfiles/image/75/jointreview.png?direct&900x227  }}]]The activities in this routine process contain generic work products (e.g. work product under review) and roles (e.g. Joint Review Coordinator) which can further be assigned to specific work products or roles in the process where they are consumed as sub-process.
+[[https://doc.stagesasaservice.com/lib/exe/fetch.php?tok=a7aead&media=https://doc.stagesasaservice.com/lib/plugins/ckgedit/fckeditor/userfiles/image/75/jointreview.png|{{  https://doc.stagesasaservice.com/lib/plugins/ckgedit/fckeditor/userfiles/image/75/jointreview.png?direct&900x227  }}]]The activities in this process contain generic work products (e.g. work product under review) and roles (e.g. Joint Review Coordinator) which can further be assigned to specific work products or roles in the process where they are consumed as sub-process.
 [[https://doc.stagesasaservice.com/lib/exe/fetch.php?tok=498810&media=https://doc.stagesasaservice.com/lib/plugins/ckgedit/fckeditor/userfiles/image/75/preparejointreview.png|{{  https://doc.stagesasaservice.com/lib/plugins/ckgedit/fckeditor/userfiles/image/75/preparejointreview.png?direct&900x462  }}]]
-===== Use a Routine Process =====
+===== Use a Generic Process =====
-Only activities in a workflow can be linked to routine process. For example, in Project management, 'Review Software Project Plan' activity refers to the 'Joint Review' routine process to show how to perform the review. When a user clicks on this activity, they will view the joint review routine process below the project management workflow.
+Only activities in a workflow can be linked to generic process. For example, in Project management, 'Review Software Project Plan' activity refers to the 'Joint Review' workflow to show how to perform the review. When a user clicks on this activity, they will view the joint review process below the project management workflow.
-[[https://doc.stagesasaservice.com/lib/exe/fetch.php?tok=063206&media=https://doc.stagesasaservice.com/lib/plugins/ckgedit/fckeditor/userfiles/image/75/jointreviewdetails.png|{{  https://doc.stagesasaservice.com/lib/plugins/ckgedit/fckeditor/userfiles/image/75/jointreviewdetails.png?direct&900x531  }}]]To model a routine process into a workflow, select the activity (e.g. Review the Software Project Plan) and navigate to the widget ''Find Details in'' and select the routine process (e.g. Joint Review). Additionally, specify the work products, phase, roles and other details for the activity in context of the workflow it belongs.
+[[https://doc.stagesasaservice.com/lib/exe/fetch.php?tok=063206&media=https://doc.stagesasaservice.com/lib/plugins/ckgedit/fckeditor/userfiles/image/75/jointreviewdetails.png|{{  https://doc.stagesasaservice.com/lib/plugins/ckgedit/fckeditor/userfiles/image/75/jointreviewdetails.png?direct&900x531  }}]]To model a generic process into a workflow, select the activity (e.g. Review the Software Project Plan) and navigate to the widget ''Find Details in'' and select the generic process (e.g. Joint Review). Additionally, specify the work products, phase, roles and other details for the activity in context of the workflow it belongs.
 [[https://doc.stagesasaservice.com/lib/exe/fetch.php?tok=b4fee2&media=https://doc.stagesasaservice.com/lib/plugins/ckgedit/fckeditor/userfiles/image/75/finddetailsin.png|{{  https://doc.stagesasaservice.com/lib/plugins/ckgedit/fckeditor/userfiles/image/75/finddetailsin.png?direct&900x300  }}]]
+On the other hand, all the processes that use the generic process can be viewed in the ''Shows How to Perform'' widget of the generic process. A Joint Review process contains the peer review details which are used in review activities for different workflows like project management, system and component design, etc.
+[[https://doc.stagesasaservice.com/lib/exe/fetch.php?tok=f04a1a&media=https://doc.stagesasaservice.com/lib/plugins/ckgedit/fckeditor/userfiles/image/75/showstoperform.png|{{  https://doc.stagesasaservice.com/lib/plugins/ckgedit/fckeditor/userfiles/image/75/showstoperform.png?direct&400x504  }}]]
+===== Use Generic Processes to Simplify Process Architecture =====
+Product Development Process is a complex mesh of processes and sub-processes and same would typically reflect in the [[:73:process_architecture|process architecture]] in Stages. Generic processes can be used to bring standardization of sub-processes across products of similar nature.
+For example, system and software design workflow is a fairly complex, but standard process. The activities in this process typically remain the same for system and software design phase for different components. System and software design process can be used as a generic process for development of different components of the vehicle.
+This can help to greatly reduce the variance in components as well as channelize resources to create a sturdier system and software process.
+[[https://doc.stagesasaservice.com/lib/exe/fetch.php?tok=f1eef6&media=https://doc.stagesasaservice.com/lib/plugins/ckgedit/fckeditor/userfiles/image/75/pdproutineprocess.png|{{  https://doc.stagesasaservice.com/lib/plugins/ckgedit/fckeditor/userfiles/image/75/pdproutineprocess.png?direct&400x722  }}]]
+Use of such processes allows to baseline and release such generic processes in thier own workspace and be reused in other workspaces.