Differences

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

--- 72:understand [2018/11/05 22:06] – emr
+++ 72:understand [2020/07/06 13:51] – [Activities] alz
@@ Line 1: / Line 1: @@
-====== Understand Processes ======
+====== Understand Process Content ======
 Process content in Stages is normally structured by separating the different dimensions of **WHAT**, **WHO**, **WHEN**, and **HOW**.
@@ Line 8: / Line 8: @@
   * **HOW **is it done: **Guidance **  (Practices, Templates, Checklists, Tools, etc.)
 Stages supports customizing the process meta-model (element types, names, associations), so <font inherit/inherit;;#2ecc71;;inherit>**your Stages instance might have a different structure and use a different terminology**</font>.
 ===== Understand process elements =====
-Every process has a start page that can be reached by clicking or tapping on the ''Processes''  menu in the left-hand navigation. The start page normally contains an image showing a high-level overview of the process, e.g. a V-model diagram for a product development process.
+Every process has a start page that can be reached by using the ''Processes''  menu in the left-hand navigation. The start page normally contains an image showing a high-level overview of the process, e.g. a V-model diagram for a product development process.
 {{  :72:content-main.png?direct&300x493  }}
-To drill down into a process, click or tap on ''Activities'', ''Work Products'', ''Roles'', ''Phases and Milestones'', or ''Guidance''. You can then drill further down by clicking or tapping in the navigation menu or in the main page showing the content.
+To drill down into a process, use the ''Activities'', ''Work Products'', ''Roles'', ''Phases and Milestones'', or ''Guidance'' menus. You can then drill further down by clicking or tapping in the navigation menu or in the main page showing the content.
 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 29: / Line 30: @@
 The flow diagram displays the sequence of the activities from left to right.
-{{  :72:content-flow-simple.png?direct&799x235  }}
+[[https://doc.stagesasaservice.com/lib/exe/fetch.php?media=72:content-flow-simple.png|{{  :72:content-flow-simple.png?direct&799x235  }}]]
 With the filter menu located at the top right of the diagram you can display additional information, e.g. the input and output work products, the responsible roles, the phases, or the interfaces (= where the current activity flow consumes or produces work products from or for other flows). You can also choose to see the whole diagram on one screen ("Fit to page") for best overview, or with scroll bars for best detail understanding.
-{{  :72:content-flow-inputoutputs.png?direct&801x440  }}
+[[https://doc.stagesasaservice.com/lib/exe/fetch.php?media=72:content-flow-inputoutputs.png|{{  :72:content-flow-inputoutputs.png?direct&801x440  }}]]
 === Table ===
@@ Line 39: / Line 40: @@
 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.
-{{  :72:content-table.png?direct&800x332  }}
+[[https://doc.stagesasaservice.com/lib/exe/fetch.php?media=72:content-table.png|{{  :72:content-table.png?direct&800x332  }}]]
 With the filter menu you can choose to display the suppliers (= producers) and customers (= consumers), the inputs and outputs, or the responsible roles.
@@ Line 47: / Line 48: @@
 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.
-{{  :72:content-grid.png?direct&802x157  }}
+[[https://doc.stagesasaservice.com/lib/exe/fetch.php?media=72:content-grid.png|{{  :72:content-grid.png?direct&802x157  }}]]
+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 row.
 ==== Work Products ====
@@ Line 107: / Line 109: @@
 {{  :72:content-perspectives.png?direct&300x417  }}
-**<font inherit/inherit;;#ffffff;;#e74c3c>(1)</font> Viewing**: The viewing perspective is meant to be used by all users. It shows the most important details of a process element.
+**<font inherit/inherit;;#ffffff;;#e74c3c>(1)</font> 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, a diagram, and its associations with other elements.
-**<font inherit/inherit;;#ffffff;;#e74c3c>(2)</font> Modeling**: The modeling perspective should be used by process modelers when defining processes. It uses a slightly different layout than the viewing perspective, shows additional details, e.g. the activity sequence, element properties, and attributes that are only of interest for the modelers.
+**<font inherit/inherit;;#ffffff;;#e74c3c>(2)</font> 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, e.g. the activity sequence, element properties, and attributes that are only of interest for the modelers.
-**<font inherit/inherit;;#ffffff;;#e74c3c>(3)</font> Compliance**: The compliance perspective shows the list of standard requirements that a process element satisfies, e.g. an Automotive SPICE base practice, or a specific requirement of ISO 9001.
+**<font inherit/inherit;;#ffffff;;#e74c3c>(3)</font> Compliance**: This perspective can be used to understand which standard requirements are satisfied with a specific activity, work product, or guidance. Typical standards are CMMI, Automotive SPICE, or ISO 9001.