Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revision | Last revisionBoth sides next revision |
| 78:process_architecture [2022/04/12 20:06] – emr | 78:process_architecture [2022/04/12 20:13] – emr |
|---|
| {{ https://doc.stagesasaservice.com/lib/plugins/ckgedit/fckeditor/userfiles/image/75/processarchitecture4.png?nolink&1000x239 }} | {{ 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 ‘Lifecycle Management’. The other process areas directly interface with process elements in this workspace. | Above is an example of process architecture. Elements like phases & milestones or value streams have cross-process validity. They are defined in a workspace called ‘Lifecycle Management’. The other process areas directly interface with elements in this workspace, e.g. associating work products with milestones. |
| |
| Furthermore, all the process areas (including Lifecycle Management) 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). | Furthermore, all the process areas (including Lifecycle Management) 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). |