Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revision | Next revisionBoth sides next revision |
| 73:tailoring_definition [2019/03/26 23:42] – emr | 73:tailoring_definition [2019/03/26 23:43] – emr |
|---|
| 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&800x354 }} | {{ :73:tailoringdefinition-processarchitecture.png?direct&601x266 }} |
| |
| To prevent this, common questions that affect multiple process modules should be defined in a parent process module, e.g. "Common Elements", that is integrated into every process area module. 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 parent process module, e.g. "Common Elements", that is integrated into every process area module. 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. |