Difference between revisions of "Model Coverage"

From T-VEC Wiki
Jump to: navigation, search
 
 
Line 1: Line 1:
Potential users of T-VEC often ask questions about code coverage, usually modified condition decision coverage (MC/DC) versus model coverage. At the higher levels of safety and criticality, DO-178B requires evidence showing 100% structural code coverage (or more stringent coverage) from tests executed against the code.  
+
Potential users of T-VEC often ask questions about code coverage, usually modified condition decision coverage (MC/DC) versus model coverage. At the higher levels of safety and criticality, DO-178B requires evidence showing 100% structural code coverage (or more stringent coverage) from tests executed against the code. See also [[VGS_Advanced_Topics#Extended MCDC Coverage|Extended MC/DC Coverage]].
  
 
==Model Coverage==
 
==Model Coverage==
As shown in below, TAF/T-VEC provide model coverage; that is, from the model, the tools check to make sure that a test vector is produced for every translated thread of the model. If a test vector is not produced, the model has a defect, and the coverage report provides a link to that particular thread where the model defect is likely to exist.  
+
As shown in below, T-VEC provides model coverage; that is, from the model, the tools check to make sure that a test vector is produced for every [[Modeling#Low Level Representation|DCP]] in the model. If a test vector is not produced, the model has a defect, and the coverage report provides a link to that particular thread where the model defect is likely to exist.  
  
 
[[Image:Model_Coverage_vs_Code_Coverage.jpg|Model Coverage Versus Code Coverage]]
 
[[Image:Model_Coverage_vs_Code_Coverage.jpg|Model Coverage Versus Code Coverage]]
 +
 +
==Code Coverage==
  
 
The following definitions apply to structural testing and the associated code coverage:
 
The following definitions apply to structural testing and the associated code coverage:

Latest revision as of 16:32, 19 May 2007