Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revision | Last revisionBoth sides next revision | ||
| general:reference_model [2019/03/27 20:06] – emr | general:reference_model [2019/03/28 21:36] – emr | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ====== Reference Model ====== | + | ====== Reference Model and Scope ====== |
| A **Reference Model** is a process content that other processes can be mapped against via the Stages compliance mapping capability. | A **Reference Model** is a process content that other processes can be mapped against via the Stages compliance mapping capability. | ||
| - | Examples for reference models are Automotive SPICE, CMMI, or ISO standards. Reference models can be either imported as content packages created by Method Park or created directly by customers. | + | Examples for reference models are CMMI, Automotive SPICE, or ISO standards. Reference models can be either imported as content packages created by Method Park or created directly by customers. |
| + | |||
| + | 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. Per convention, each reference model has a **Default Scope**, which contains all reference model required that are typically mapped to. | ||