Stages Documentation

Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
Next revisionBoth sides next revision
73:process_architecture [2020/08/06 16:07] – [Define a Process Architecture] aakr73:process_architecture [2020/08/06 16:10] – [Define a Process Architecture] aakr
Line 5: Line 5:
 In Stages, since each of the process resides in its own workspace, process architecture is represented by hierarchy of the workspaces. Before been integrated 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. In Stages, since each of the process resides in its own workspace, process architecture is represented by hierarchy of the workspaces. Before been integrated 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.png?direct&900x299  }}+{{  https://doc.stagesasaservice.com/lib/plugins/ckgedit/fckeditor/userfiles/image/73/processarchitecture3_1.png?nolink&900x300  }}
  
 Above is an example of process architecture. Since common elements like phases & milestones, common roles (e.g. stakeholders) are defined at corporate level, they have been defined in workspace called ‘Common Elements’. This workspace is then integrated into each Process Area workspace. Above is an example of process architecture. Since common elements like phases & milestones, common roles (e.g. stakeholders) are defined at corporate level, they have been defined in workspace called ‘Common Elements’. This workspace is then integrated into each Process Area workspace.