Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
73:custom_reference_models [2019/04/02 18:38] – emr | 73:custom_reference_models [2024/02/15 00:00] (current) – external edit 127.0.0.1 | ||
---|---|---|---|
Line 8: | Line 8: | ||
===== Reference Model Scopes ===== | ===== Reference Model Scopes ===== | ||
+ | Typically a process has to comply only with a specific section of a reference model. For example, a project management process only needs to comply with the Project Planning, Project Monitoring & Control, and Integrated Project Management process areas of the CMMI-DEV standard. Therefore the reference models are normally broken down into **Scopes**, which contain a subset of all reference model requirements. | ||
+ | |||
+ | To define the scopes for a new reference model, use '' | ||
+ | |||
+ | {{: | ||
+ | |||
+ | Per convention, each reference model should have a **Default **scope, which contains all reference model required that are typically mapped to. | ||
===== Cross-Reference Models ===== | ===== Cross-Reference Models ===== | ||
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. " | ||
+ | |||
+ | **When reference models are imported into Stages 7.8 or later, the automatically created version " | ||