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
Next revisionBoth sides next revision
73:compliance [2019/04/04 11:20] fnpk73:compliance [2019/09/19 18:46] emr
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, or health standards, or market requirements like CMMI or Automotive SPICE. Assuring compliance with all relevant standards is a key aspect of process management.+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, or health standards, or market requirements like Automotive SPICE or CMMI. Assuring compliance with all relevant standards is a key aspect of process management.
  
 Stages enables process managers to map their processes against standards, detect and close gaps, and generate evidence for audits, assessments, and appraisals. Stages enables process managers to map their processes against standards, detect and close gaps, and generate evidence for audits, assessments, and appraisals.
Line 17: Line 17:
 To start the mapping, click or tap on the reference model name. Stages then shows the reference model, but only those parts that are covered by the assigned scopes. Use the navigation to drill down to the requirements. To start the mapping, click or tap on the reference model name. Stages then shows the reference model, but only those parts that are covered by the assigned scopes. Use the navigation to drill down to the requirements.
  
-To allow a quick overview which standard requirements are already mapped and where there are still gaps, the rating of each requirements is also shown in the navigation **<font inherit/inherit;;#ecf0f1;;#e74c3c>(1)</font>**.+To allow a quick overview which standard requirements are already mapped and where there are still gaps, the coverage of each requirement is also shown in the navigation **<font inherit/inherit;;#ecf0f1;;#e74c3c>(1)</font>**.
  
 To assign process content to a specific requirement, use the context menu in ''Compliance References'' box <font inherit/inherit;;#ecf0f1;;#e74c3c>**(2)**</font> . The assignment works exactly the same as in assigning process elements to each other. You can use the element comment for each assignment to record details about each mapping, e.g. which chapter of a work product covers the standard requirement. To assign process content to a specific requirement, use the context menu in ''Compliance References'' box <font inherit/inherit;;#ecf0f1;;#e74c3c>**(2)**</font> . The assignment works exactly the same as in assigning process elements to each other. You can use the element comment for each assignment to record details about each mapping, e.g. which chapter of a work product covers the standard requirement.
Line 23: Line 23:
 {{  :73:compliance-mapping.png?direct&801x393  }} {{  :73:compliance-mapping.png?direct&801x393  }}
  
-Finally, a set of mappings can be rated against a standard requirement. To set the rating, use the context menu in the ''Compliance Rating'' box <font inherit/inherit;;#ecf0f1;;#e74c3c>**(3)**</font> .+Finally, it can be defined how well a set of mappings covers a standard requirement. To set the coverage, use the context menu in the ''Compliance Coverage'' box <font inherit/inherit;;#ecf0f1;;#e74c3c>**(3)**</font> .
  
 {{  :73:compliance-rating.png?direct&300x247  }} {{  :73:compliance-rating.png?direct&300x247  }}
  
-Defining the correct rating is typically expert judgement, but you can use the following rating scheme as an orientation:+Defining the correct coverage is typically expert judgement, but you can use the following scheme as an orientation:
  
   * Zero Stars (None): The process does not cover the requirement at all.   * Zero Stars (None): The process does not cover the requirement at all.
Line 40: Line 40:
 {{ youtube>j5qlrl1jCUk?large&rel=0 }} {{ youtube>j5qlrl1jCUk?large&rel=0 }}
  
-The above video shows the whole sequence of actions to assign reference model scopes, map the process to the individual requirements, and finally rate the mappings.+The above video shows the whole sequence of actions to assign reference model scopes, map the process to the individual requirements, and finally determine the coverage of the mappings.
  
 ===== View Compliance in Process Context ===== ===== View Compliance in Process Context =====
Line 58: Line 58:
 {{  :73:compliance-traces.png?direct&800x444  }} {{  :73:compliance-traces.png?direct&800x444  }}
  
-To see the compliance requirements and the mapped process content, use the ''Simple''  view of the report. To see the individual mapping parameters, ratings, and notes, select the ''Detailed''  view. Both views contain direct links to the compliance requirements and the mapped process element. The links automatically open a new browser tab.+To see the compliance requirements and the mapped process content, use the ''Simple''  view of the report. To see the individual mapping parameters, coverage, and notes, select the ''Detailed''  view. Both views contain direct links to the compliance requirements and the mapped process element. The links automatically open a new browser tab.
  
 In some cases, it saves a lot of time to map reference models onto each other. If you would like to also include those indirect traces, switch on ''Include Mappings across Reference Models''. In some cases, it saves a lot of time to map reference models onto each other. If you would like to also include those indirect traces, switch on ''Include Mappings across Reference Models''.