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:tailoring_definition [2019/04/04 11:19] fnpk73:tailoring_definition [2020/03/30 20:20] emr
Line 3: Line 3:
 One of the most important aspects of product development processes is variance. No two products were ever developed with exactly the same process. Processes always vary, based on target customers, technology, available budgets, market regulations, and many more characteristics. One of the most important aspects of product development processes is variance. No two products were ever developed with exactly the same process. Processes always vary, based on target customers, technology, available budgets, market regulations, and many more characteristics.
  
-Process tailoring is a key capability to deal with variance in development projects and programs. It allows process authors to define ruleswhen 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 20: Line 20:
  
 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 by users with ''Manual Tailoring Modify''  permissions using the 3dot menu of the respective element:
 +
 +[[https://doc.stagesasaservice.com/lib/exe/detail.php?id=73:tailoring_definition&media=73:c4618505f079ff563b5a2293f503d28e.png|{{:73:c4618505f079ff563b5a2293f503d28e.png}}]]
  
 ===== Define Simple Tailoring Rules ===== ===== Define Simple Tailoring Rules =====
Line 25: Line 29:
 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 <font inherit/inherit;;#ffffff;;#e74c3c>**(1)**</font>.
  
-{{  :73:tailoringdefinition-main.png?direct&801x393  }}+[[https://doc.stagesasaservice.com/lib/exe/fetch.php?media=73:tailoringdefinition-main.png|{{  :73:tailoringdefinition-main.png?direct&801x393  }}]] 
 + 
 +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.
  
 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''. 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''.
Line 49: Line 55:
 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 59: Line 65:
 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.