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
Last revisionBoth sides next revision
73:custom_reference_models [2019/10/16 22:58] – emr73:custom_reference_models [2022/04/04 14:24] – emr
Line 11: Line 11:
  
 To define the scopes for a new reference model, use ''Management > Compliance'' and switch to the ''Scopes'' tab. It is only visible if the process kind of the current workspace is set to Reference Model (see above). You can create and delete scopes and add reference model elements to them. To efficiently add or remove multiple elements, use the ''Add all elements'', ''Add all elements in folders'', and ''Remove all elements actions'' in the ''…'' menu: To define the scopes for a new reference model, use ''Management > Compliance'' and switch to the ''Scopes'' tab. It is only visible if the process kind of the current workspace is set to Reference Model (see above). You can create and delete scopes and add reference model elements to them. To efficiently add or remove multiple elements, use the ''Add all elements'', ''Add all elements in folders'', and ''Remove all elements actions'' in the ''…'' menu:
 +
 +{{:73:compliance-scopes-multiselect.png?nolink&800x259}}
  
 Per convention, each reference model should have a **Default **scope, which contains all reference model required that are typically mapped to. Per convention, each reference model should have a **Default **scope, which contains all reference model required that are typically mapped to.
Line 16: Line 18:
  
 Reference models can also be mapped onto other reference models. For example, it may make sense to map evidence tables in the appendices of some standards onto the standard requirements themselves and then trace your processes only onto the evidence tables. The Compliance Traceability report can then use the cross-reference-model-mappings to show compliance to the original standard without having to map to it directly. Reference models can also be mapped onto other reference models. For example, it may make sense to map evidence tables in the appendices of some standards onto the standard requirements themselves and then trace your processes only onto the evidence tables. The Compliance Traceability report can then use the cross-reference-model-mappings to show compliance to the original standard without having to map to it directly.
 +
 +===== Version Management of Reference Models =====
 +
 +The standard version management for reference models is not supported, so reference models can only have one version.
 +
 +If you need to version reference models, the models need to be copied to different workspaces, e.g. "Automotive SPICE 3.1" and "Automotive SPICE 4.0".
 +
 +**When reference models are imported into Stages 7.8 or later, the automatically created version "V0" should be deleted and the working version should be marked valid.**