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
73:tailoring_definition [2020/01/16 11:49] – [Basic Concepts] vtbr73:tailoring_definition [2024/02/15 00:00] (current) – external edit 127.0.0.1
Line 4: Line 4:
  
 Process tailoring is a key capability to deal with variance in development projects and programs. It allows process authors to define rules when projects or programs can deviate from the standard processes. Process tailoring is a key capability to deal with variance in development projects and programs. It allows process authors to define rules when projects or programs can deviate from the standard processes.
- 
  
 ===== Basic Concepts ===== ===== Basic Concepts =====
Line 22: Line 21:
 Finally, no set of tailoring rules can ever contain every possible variation. For that reason, every process needs to be reviewed after applying the rules-based tailoring and it must be possible to **perform manual tailoring adjustments**. Finally, no set of tailoring rules can ever contain every possible variation. For that reason, every process needs to be reviewed after applying the rules-based tailoring and it must be possible to **perform manual tailoring adjustments**.
  
-These manual adjustments can be made using the 3dot menu of the respective element. {{  :73:950de0076a3909ce24c13142249f75a8.png}}+These manual adjustments can be made by users with ''Manual Tailoring Modify''  permissions using the 3dot menu of the respective element: 
 + 
 +{{  :73:c4618505f079ff563b5a2293f503d28e.png?direct&  }}
  
  
 ===== Define Simple Tailoring Rules ===== ===== Define Simple Tailoring Rules =====
  
-To define tailoring questions and answers, use the ''Management > Tailoring''  menu. It can be accessed by users with ''Process Modify''  permissions. New questions can be created via the ''+''  button on the left <font inherit/inherit;;#ffffff;;#e74c3c>**(1)**</font>.+To define tailoring questions and answers, use the ''Management > Tailoring'' menu. It can be accessed by users with ''Process Modify'' permissions. New questions can be created via the ''+'' button on the left **(1)**.
  
-{{  :73:tailoringdefinition-main.png?direct&801x393  }}+{{  :73:tailoringdefinition-main.png?direct&900x442  }}
  
-To test the tailoring rules, use ''Start Tailoring''<font inherit/inherit;;#ffffff;;#e74c3c>**(2)**</font> and follow the steps of the tailoring assistant (see [[:73:tailor_process|here for more info]]). To reset the tailoring to the default state, use the ''Reset Tailoring''  action **<font inherit/inherit;;#ffffff;;#e74c3c>(3)</font>**. To see both options, make sure you are in the ''Working Version''.+The questions will be asked and the answers will be displayed in the same order as they are modeled. To change this order, use the ''Sort'' operation in the ''…'' menu.
  
-The answers for each question can be defined via the ''…''  menu of the question and selecting the ''Add Answer''  action. To assign dependent elements to an answer use the ''…''  menu of the respective action. To remove process elements in case of a specific answer, assigning elements to the ''Remove, if selected''  action is sufficient.+To test the tailoring rules, use ''Start Tailoring''**(2)** and follow the steps of the tailoring assistant (see [[:73:tailor_process|here for more info]]). To reset the tailoring to the default state, use the ''Reset Tailoring'' action **(3)**. To see both options, make sure you are in the ''Working Version''. 
 + 
 +The answers for each question can be defined via the ''…'' menu of the question and selecting the ''Add Answer'' action. To assign dependent elements to an answer use the ''…'' menu of the respective action. To remove process elements in case of a specific answer, assigning elements to the ''Remove, if selected'' action is sufficient.
  
 [[:73:tailoringdefinition-definedependency.png?media=73:tailoringdefinition-definedependency.png|{{  :73:tailoringdefinition-definedependency.png?nolink&801x513  }}]] [[:73:tailoringdefinition-definedependency.png?media=73:tailoringdefinition-definedependency.png|{{  :73:tailoringdefinition-definedependency.png?nolink&801x513  }}]]
Line 39: Line 42:
 For more complex scenarios, you can also use the other actions, e.g. ''Add, If Selected''. For more complex scenarios, you can also use the other actions, e.g. ''Add, If Selected''.
  
-{{ youtube>Ez6SPJyNgtc?large&rel=0 }}+ {{ youtube>Ez6SPJyNgtc?large&rel=0 }}
  
 The above video shows how to define tailoring questions, answers, and their dependencies. The above video shows how to define tailoring questions, answers, and their dependencies.
 +
  
 ===== Define Dependent Tailoring Rules ===== ===== Define Dependent Tailoring Rules =====
  
-You can create questions below other answers, so the questions and answers form a tree. The question below will only be asked, if the parent answer is being selected when a user steps through the tailoring assistant.+You can create questions below other answers, so the questions and answers form a tree. The question below will only be asked if the parent answer is being selected when a user steps through the tailoring assistant. The assistant hereby follows the "depth-first" principle. 
 + 
 +To add a question below an answer, use the ''…'' menu of the answer and select the ''Define Question'' action. 
 + 
 +When you assign one process element to several answers in this tailoring tree, there can be conflicts whether the element shall be removed or added. To solve these conflicts, the following rules will be applied: 
 + 
 +  * The tailoring of the question that hangs lower in the tailoring tree - and is, therefore, more specific - wins. 
 +  * The tailoring of the answer to which the element is more directly attached wins. (".. if selected" wins against "… if other selected") 
 +  * If there are contradicting tailorings on the same question level, adding wins over removing. 
 + 
 +After these conflicts have been resolved, the remaining tailoring results will be applied in one step to the process elements.
  
-To add a question below an answer, use the ''…''  menu of the answer and select the ''Define Question''  action. 
  
 ===== Manage Tailoring for multiple Process Modules ===== ===== Manage Tailoring for multiple Process Modules =====
Line 53: Line 66:
 When building a multi-level process architecture (see [[:73:process_architecture|more detail here]]), defining the tailoring dependencies at the right module level is key. If you define process areas as separate process modules, some questions might affect the tailoring in several process areas at the same time. For example, the selection of a safety integrity level or development assurance level might impact the requirements management as well as the design and validation process areas. Defining this question in each of the modules would result in the same question being asked multiple times, if those modules are integrated into one workspace. When building a multi-level process architecture (see [[:73:process_architecture|more detail here]]), defining the tailoring dependencies at the right module level is key. If you define process areas as separate process modules, some questions might affect the tailoring in several process areas at the same time. For example, the selection of a safety integrity level or development assurance level might impact the requirements management as well as the design and validation process areas. Defining this question in each of the modules would result in the same question being asked multiple times, if those modules are integrated into one workspace.
  
-{{  :73:tailoringdefinition-processarchitecture.png?direct&601x266  }}+[[https://doc.stagesasaservice.com/lib/exe/fetch.php?media=73:tailoringdefinition-processarchitecture.png|{{  :73:tailoringdefinition-processarchitecture.png?direct&601x266  }}]]
  
 To prevent this, common questions that affect multiple process modules should be defined in a process module, that is integrated into every process area module, e.g. "Common Elements". Each module can then define its own tailoring dependencies to those common questions. When the process modules are integrated into one workspace, the tailoring dependencies will be merged into a single question again. When the tailoring assistant is run, common questions will only be asked once, but affect elements from all integrated process areas. To prevent this, common questions that affect multiple process modules should be defined in a process module, that is integrated into every process area module, e.g. "Common Elements". Each module can then define its own tailoring dependencies to those common questions. When the process modules are integrated into one workspace, the tailoring dependencies will be merged into a single question again. When the tailoring assistant is run, common questions will only be asked once, but affect elements from all integrated process areas.
Line 63: Line 76:
 Under some circumstances, the opposite behavior might be useful: start with a process that has all elements tailored away and based on the given answers, only the selected elements are tailored in. To select this behavior, use the ''…''  menu in the tailoring assistant and select ''Change Tailoring Mode''. Under some circumstances, the opposite behavior might be useful: start with a process that has all elements tailored away and based on the given answers, only the selected elements are tailored in. To select this behavior, use the ''…''  menu in the tailoring assistant and select ''Change Tailoring Mode''.
  
-{{  :73:tailoringdefinition-tailoringmode.png?direct&600x191  }}+[[https://doc.stagesasaservice.com/lib/exe/fetch.php?media=73:tailoringdefinition-tailoringmode.png|{{  :73:tailoringdefinition-tailoringmode.png?direct&600x191  }}]]
  
 Note that the defined tailoring dependencies will work in reverse when the mode is changed, so you might need to completely redefine them after changing the mode. Note that the defined tailoring dependencies will work in reverse when the mode is changed, so you might need to completely redefine them after changing the mode.