VIP turns protocol rules into observable, checkable behavior — but only for the boundaries it sees.
Separate sequence intent, driver activity, sampled monitor events and independently checked expectations.
Choose active versus passive from stimulus ownership at each boundary, not simply block versus chip level.
VIP models the spec, not your RTL — integration assumptions can differ.
Applies verification methodology to all protocol topics in the course.
No. The monitor must establish the actual acceptance events; stalls, cancellation or stimulus errors can change the count.