Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
73:custom_reference_models [2019/10/16 22:50] – emr | 73:custom_reference_models [2019/10/16 22:59] – emr | ||
---|---|---|---|
Line 10: | Line 10: | ||
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. | 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 '' | + | 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. | Per convention, each reference model should have a **Default **scope, which contains all reference model required that are typically mapped to. |