Differences

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

--- 73:process_architecture [2020/09/21 04:27] – aakr
+++ 73:process_architecture [2024/02/15 00:00] (current) – external edit 127.0.0.1
@@ Line 5: / Line 5: @@
 In Stages, since each of the processes resides in its own workspace, process architecture is represented by the hierarchy of the workspaces. Before integrating it into the next process in the hierarchy, it is recommended that each process should be baselined (versioned) and only the [[:general:validversion|valid version]] of the process should be integrated.
-{{  https://doc.stagesasaservice.com/lib/plugins/ckgedit/fckeditor/userfiles/image/73/processarchitecture3_1.png?nolink&900x300  }}
+{{  https://doc.stagesasaservice.com/lib/plugins/ckgedit/fckeditor/userfiles/image/75/processarchitecture4.png?nolink&1000x239  }}
-Above is an example of process architecture. Since common elements like phases & milestones, common roles (e.g. stakeholders) are defined at the corporate level, they have been defined in a workspace called ‘Common Elements’. This workspace is then integrated into each Process Area workspace.
+Above is an example of process architecture. Global elements like phases & milestones, common roles (e.g. stakeholders) are defined at the corporate level, they have been defined in a workspace called ‘Lifecycle Management’. The other process areas contain discipline specific processes within them which interface with 'Lifecycle Management' process elements.
 Furthermore, all the process areas are integrated into a single Standard Process workspace called ‘Software Engineering’ which contains all their process elements (workflows, activities, roles, phases & milestones, work products, and guidance).