Content deleted Content added
Added links. |
m →RC/DC |
||
Line 33:
'''Reinforced condition/decision coverage''' ('''RC/DC''') is a stronger version of the MC/DC coverage criterion, suitable for [[safety-critical system]]s.<ref>{{cite article| title=From MC/DC to RC/DC: formalization and analysis of control-flow testing criteria | first1=S.A. | last1=Vilkomir | authorlink1=Sergiy Vilkomir | first2=J.P. | last2=Bowen | authorlink2=Jonathan Bowen | journal=[[Formal Aspects of Computing]] | volume=18 | number=1 | pages=42–62 | date=2006 | publisher=[[Springer Nature]] | doi=10.1007/s00165-005-0084-7 }}</ref> It was originally proposed by [[Sergiy Vilkomir]] in 2002.<ref>{{cite article| title=Reinforced condition/decision coverage (RC/DC): A new criterion for software testing | first1=S.A. | last1=Vilkomir | authorlink1=Sergiy Vilkomir | first2=J.P. | last2=Bowen | authorlink2=Jonathan Bowen | work=International Conference of B and Z Users | publisher=[[Springer-Verlag]] | series=[[Lecture Notes in Computer Science]] | volume=2272 | pages=291–308 | date=2002 | doi=10.1007/3-540-45648-1_15 }}</ref>
A second publication refutes this claim and indicates that MCDC (at least the Unique Cause Strong MCDC "UCMS" or Masking) variants of MCDC have superior coverage to the referenced Reinforced condition/decision coverage (RC/DC) {{cn}}.
==See also==
| |||