Work it through
Read two reports together
For this fixture’s two-direction bit metric, all tracked toggles occurred. Explicit one-bin-per-value functional coverage is only 50%.
Neither result proves that mode decoding produced the right behavior.
Your next page is on its way.
Chapter 1 · Strategy & code metrics
Connect requirements to measurable evidence and read statement, branch, condition, toggle, and FSM coverage without overclaiming correctness.

A worked mechanism
Structural activity and a required value set measure different things.
three observations
A two-bit mode follows 00 → 11 → 00.
both directions exercised
Each bit makes both a 0→1 and a 1→0 transition.
only 2 of 4 values seen
The specification requires 00, 01, 10, and 11.
2 distinct functional holes
Generate 01 and 10, observe them, and check their behavior.
Work it through
For this fixture’s two-direction bit metric, all tracked toggles occurred. Explicit one-bin-per-value functional coverage is only 50%.
Neither result proves that mode decoding produced the right behavior.
Actual code-coverage definitions, reset exclusions, and X/Z counting depend on the tool configuration. The four required values here are a stated example, not a universal mode specification.
Keep the same three-sample trace for both calculations and inspect missing value bins alongside checker results.
The language bench / coverage
// Sample a reconstructed transfer once, at acceptance.
if (valid && ready) cg.sample(opcode, size);
// Required: READ/WRITE × sizes {1, 4, 8}
// Size 16 ignored; size 0 illegal; at_least = 1Question directory
Open an authored answer, then connect it to the evidence diagram and the related practice-bank prompt.
Coverage is useful when every goal traces to a requirement or risk, samples a meaningful event, and complements a checker that establishes correctness.
Functional coverage records planned scenarios, code coverage exposes exercised implementation structure, and checkers decide correctness. Traceability explains why the combined evidence supports a requirement.
Code coverage reports exercised implementation structure. Functional coverage reports whether authored behaviors, values, transitions, and combinations were observed. Neither says by itself that the observed result was correct.
Every instrumented construct can execute while important data combinations, orderings, error cases, or protocol outcomes remain absent or unchecked.
Each item needs a requirement or risk, measurable observation, sampling definition, checker relationship, target, owner, and policy for unreachable or excluded behavior.
Code metrics reveal which implementation structures were exercised. They are powerful gap detectors, but a hit says nothing by itself about whether the behavior was intended or correct.
if (valid) send();true ✓false ○mode[1:0]00→11 ✓01 never seenA line may execute while one branch outcome never occurs, a condition may be masked, or an FSM transition may remain unseen. Diagnose the specific hole before changing stimulus or excluding logic.
Statement coverage records executed operations, branch coverage records control outcomes, and condition coverage examines Boolean operands or combinations that may be masked inside a taken branch.
A bit may toggle because of reset or incidental traffic without exercising its intended function, while a multi-bit field can have full bit toggles and still miss important encoded values.
First establish why it is unreachable in the verified configuration. Remove dead logic when appropriate, or use formal evidence and a narrowly reviewed exclusion when the behavior is intentionally impossible.