MC/DC

MC/DC (Modified Condition/Decision Coverage) is a software testing coverage criterion that requires every individual condition in a Boolean decision to independently affect the overall decision outcome.

MC/DC is used in structural software testing to verify the correctness of complex logical decisions. It requires specific test cases that show each condition can independently change the outcome of a decision while all other conditions remain unchanged, providing stronger assurance than statement or decision coverage.

MC/DC is important because it uncovers logic faults that simpler coverage metrics can miss. By proving each condition independently affects system behavior, MC/DC significantly reduces the risk of systematic software failures in safety-critical systems such as automotive, aerospace, rail, and industrial control.

MC/DC is required or strongly recommended by the following functional safety standards:

·       ISO 26262 (Automotive – ASIL D)

·       IEC 61508 (Industrial Safety)

·       DO-178C / DO-330 (Avionics)

·       EN 50128 (Railway Systems)

·       ISO/SAE 21434 (Automotive Cybersecurity)

MC/DC is more rigorous than statement and decision coverage because it proves the independent influence of each condition, not just code execution or decision outcomes.

Coverage metric comparison:

• Statement Coverage: Verifies that each executable line of code has been executed at least once during testing.

• Decision (Branch) Coverage: Verifies that each decision evaluates to both true and false outcomes.

• MC/DC (Modified Condition/Decision Coverage): Verifies that each individual condition within a decision can independently affect the decision outcome.

In ISO 26262, the required software coverage level depends on the Automotive Safety Integrity Level (ASIL). MC/DC is recommended for ASIL A, B, and C, and is highly recommended and effectively mandatory in practice for ASIL D software.

ISO 26262-6:2018, Clause 9.4.4 identifies MC/DC as a key verification method for detecting errors in complex logical expressions used in safety-critical automotive software.

MC/DC benefits multiple stakeholders across the safety-critical software lifecycle:

·       Software engineers detect complex logic defects early in development.

·       Safety managers demonstrate compliance with functional safety standards.

·       Project managers reduce late-stage rework and certification risks.

·       End users benefit from safer and more reliable systems.