Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
76:compliance [2021/02/19 16:43] – emr | 76:compliance [2024/02/15 00:00] (current) – external edit 127.0.0.1 | ||
---|---|---|---|
Line 1: | Line 1: | ||
====== Manage Compliance ====== | ====== Manage Compliance ====== | ||
- | Development of complex products is always a regulated environment. Examples are standards set by governing bodies like the FAA or FDA, ISO or IEEE standards, quality, safety, security, environmental, | + | Development of complex products is always a regulated environment. Examples are standards set by governing bodies like the FAA or FDA, ISO or IEEE standards, quality, safety, security, environmental, |
Stages enables process managers to map their processes against standards, detect and close gaps, and generate evidence for audits, assessments, | Stages enables process managers to map their processes against standards, detect and close gaps, and generate evidence for audits, assessments, | ||
- | **Watch our basic videos on compliance [[https:// | + | **Watch our intro videos on compliance [[https:// |
- | ===== Map Whole Processes against Standard Requirements ===== | + | ===== Map Processes against Standard Requirements ===== |
The basic idea is to break down the standard documents into their individual requirements and map the processes against those requirements. The standard requirements are modeled as a process, which is marked as a [[: | The basic idea is to break down the standard documents into their individual requirements and map the processes against those requirements. The standard requirements are modeled as a process, which is marked as a [[: | ||
Line 51: | Line 51: | ||
This perspective is configurable, | This perspective is configurable, | ||
+ | |||
+ | ===== Map to Standard Requirements within Process Context ===== | ||
+ | |||
+ | While modeling a process it can be useful to directly map new elements to compliance requirements. This can be done directly from the '' | ||
+ | |||
+ | [[https:// | ||
+ | |||
+ | To create a mapping, click or tap on the context menu in the compliance box, select the reference model, and assign the current element to a specific compliance requirement via search or browse. You can also add a comment to this specific mapping via the '' | ||
+ | |||
+ | As you are mapping from the element view, it is not possible to adjust the coverage or leave general notes on the whole standard requirements. To do this, use the functionality described [[: | ||
+ | |||
+ | ===== View Mappings in Reference Model ===== | ||
+ | |||
+ | Starting with Stages version 7.10, compliance mappings are also visible on the reference model side. | ||
+ | |||
+ | [[https:// | ||
+ | |||
+ | In the above example, the mappings to various process elements are displayed directly in the Automotive SPICE reference model. | ||
===== Show Compliance Traceability ===== | ===== Show Compliance Traceability ===== | ||
Line 65: | Line 83: | ||
Finally, the traces can be exported to Excel via the normal report Excel export. | Finally, the traces can be exported to Excel via the normal report Excel export. | ||
- | |||
- | ===== Map Single Process Elements to Standard Requirements ===== | ||
- | |||
- | TODO | ||
===== Show Compliance Gaps ===== | ===== Show Compliance Gaps ===== |