Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
72:understand [2021/07/01 12:04] – [Guidance] ohh | 72:understand [2024/02/15 00:00] (current) – external edit 127.0.0.1 | ||
---|---|---|---|
Line 7: | Line 7: | ||
* **WHEN **does it have to be done: **Phases** | * **WHEN **does it have to be done: **Phases** | ||
* **HOW **is it done: **Guidance ** (Practices, Templates, Checklists, Tools, etc.) | * **HOW **is it done: **Guidance ** (Practices, Templates, Checklists, Tools, etc.) | ||
- | Stages supports customizing the process meta-model (element types, names, associations), | + | Stages supports customizing the process meta-model (element types, names, associations), |
+ | **your Stages instance might have a different structure and use a different terminology** . | ||
===== Understand process elements ===== | ===== Understand process elements ===== | ||
Line 14: | Line 14: | ||
Every process has a start page that can be reached by using the '' | Every process has a start page that can be reached by using the '' | ||
- | {{ : | + | [[https:// |
- | To drill down into a process, use the '' | + | To drill down into a process, use the '' |
The arrow up icon brings you one level up. You can also use the browser back and forward buttons to navigate back where you came from and forth where you already were. | The arrow up icon brings you one level up. You can also use the browser back and forward buttons to navigate back where you came from and forth where you already were. | ||
Line 30: | Line 30: | ||
The flow diagram displays the sequence of the activities from left to right. | The flow diagram displays the sequence of the activities from left to right. | ||
- | [[https:// | + | [[https:// |
- | With the filter menu located at the top right of the diagram | + | With the filter menu located at the top right of the diagram |
+ | **(2)** | ||
[[https:// | [[https:// | ||
Line 40: | Line 41: | ||
The table diagram is best suited to understand the dependencies of the current activity flow with other flows. The activity flow goes from the top to the bottom and per default shows the input and output work products of every activity and the activity flow producing or consuming those work products. | The table diagram is best suited to understand the dependencies of the current activity flow with other flows. The activity flow goes from the top to the bottom and per default shows the input and output work products of every activity and the activity flow producing or consuming those work products. | ||
- | {{ https:// | + | [[https:// |
=== Grid === | === Grid === | ||
Line 46: | Line 47: | ||
The grid view offers a very reduced visualization of the activity flow. It shows the activities in sequence, either through direct predecessor or successor activities, or through inputs and output work products. | The grid view offers a very reduced visualization of the activity flow. It shows the activities in sequence, either through direct predecessor or successor activities, or through inputs and output work products. | ||
- | {{ https:// | + | [[https:// |
Activities that can be executed in parallel are shown in the same column. | Activities that can be executed in parallel are shown in the same column. | ||
- | |||
==== Work Products ==== | ==== Work Products ==== | ||
- | Work products are the inputs for and outputs of activities. They are also part of the **WHAT** dimension. Work products can also associated with milestones to model at which point in time certain work products need to be in a certain state. | + | Work products are the inputs for and outputs of activities. They are also part of the **WHAT** |
Stages typically visualizes three different aspects of work products: | Stages typically visualizes three different aspects of work products: | ||
Line 75: | Line 75: | ||
This diagram shows the state in which work product is consumed in activities or workflows and the state in which it is delivered at the end of the activity or a workflow. | This diagram shows the state in which work product is consumed in activities or workflows and the state in which it is delivered at the end of the activity or a workflow. | ||
- | {{ https:// | + | [[https:// |
==== Roles ==== | ==== Roles ==== | ||
- | Roles describe **WHO** should perform work in a process. They can be associated with activities, typically in a **RASIC** format: **R**esponsible, | + | Roles describe **WHO** |
In projects, programs, or other process instances, roles can be assigned to persons. | In projects, programs, or other process instances, roles can be assigned to persons. | ||
Line 86: | Line 85: | ||
==== Phases and Milestones ==== | ==== Phases and Milestones ==== | ||
- | Phases and milestones describe the time dimension or the **WHEN** of the process. | + | Phases and milestones describe the time dimension or the **WHEN** |
- | {{ https:// | + | [[https:// |
Phases are typically associated with the activities that need to be performed within a specific phase. Milestones describe when specific work products need to be in a certain state. | Phases are typically associated with the activities that need to be performed within a specific phase. Milestones describe when specific work products need to be in a certain state. | ||
- | |||
==== Guidance ==== | ==== Guidance ==== | ||
The guidance describes **HOW **to perform the work in a process. Guidance can consist of many different elements, e.g., practices, checklists, templates, tools, training, or links to other web resources. | The guidance describes **HOW **to perform the work in a process. Guidance can consist of many different elements, e.g., practices, checklists, templates, tools, training, or links to other web resources. | ||
+ | |||
=== Supplements === | === Supplements === | ||
Line 101: | Line 100: | ||
Supplements are guidance elements collected automatically from the output, parent, and child elements of an element. | Supplements are guidance elements collected automatically from the output, parent, and child elements of an element. | ||
- | |||
===== Understand process element details and associations ===== | ===== Understand process element details and associations ===== | ||
Line 107: | Line 105: | ||
Every process element, e.g. activity or work product, is described on one page. Every element can have a description and several associations to other elements, e.g. defining the responsible role and the input and output work products for an activity. | Every process element, e.g. activity or work product, is described on one page. Every element can have a description and several associations to other elements, e.g. defining the responsible role and the input and output work products for an activity. | ||
- | {{ https:// | + | [[https:// |
Depending on the size of your screen and your device you might see this information in different layouts: two columns for normal screens, three columns on wide screens, or only one column on small screens or mobile devices. | Depending on the size of your screen and your device you might see this information in different layouts: two columns for normal screens, three columns on wide screens, or only one column on small screens or mobile devices. | ||
Line 114: | Line 112: | ||
[[https:// | [[https:// | ||
- | |||
===== Using different perspectives ===== | ===== Using different perspectives ===== | ||
Line 122: | Line 119: | ||
[[https:// | [[https:// | ||
- | **<font inherit/ | + | ** (1) Viewing**: The viewing perspective is meant to be used by all users. It shows the most important information about a process element, e.g. its description, |
- | **<font inherit/ | + | ** (2) Modeling**: The modeling perspective is best used by process modelers when defining processes. It uses a three-column layout on large screens to ease modeling process with a minimal set of interactions. It also show additional details not shown in the viewing perspective, |
- | **<font inherit/ | + | ** (3) Compliance**: |