Skip to content
STIMSMITH

Verification Plan

Concept

A verification plan is a structured artifact in hardware and system verification that documents the design under verification, its functional specification, coverage goals, and the verification activities (and often correction activities) required across development phases. In assertion-based functional verification (ABV) it bundles the design description, functional and code coverage targets, and the assertions that check for errors and measure coverage. At the system level it is cast as a sequential decision problem that selects verification and correction activities across development phases. Automatic test-program generators such as IBM Genesys and Genesys-Pro are designed to consume the knowledge captured in a verification plan in order to produce functional test programs for microprocessor designs.

First seen 5/23/2026
Last seen 6/9/2026
Evidence 6 chunks
Wiki v3

WIKI

Verification Plan

Definition

A verification plan is an artifact used in functional verification that specifies what must be verified, how it will be verified, and how completely it has been verified. The cited literature describes the verification plan in three complementary ways:

READ FULL ARTICLE →

NEIGHBORHOOD

3 nodes · 3 edges
graph · Verification Plan · depth=1

RELATIONSHIPS

3 connections
Genesys-Pro ← uses 90% 3e
Genesys-Pro's new language reduces effort needed to define and maintain a verification plan.
Simulation-based Functional Verification ← uses 100% 1e
Simulation-based verification starts with a verification plan that enumerates behaviors to check.
Genesys ← uses 1e
Genesys uses a verification plan to induce smart sets of tests for verification tasks.

CITATIONS

5 sources
5 citations — click to expand
[1] In ABV of an RTL design, the verification plan bundles the design description and functional specification, functional coverage goals, code coverage goals, and the assertions used to check for errors and to drive coverage. Assertion Based Functional Verification of March Algorithm Based MBIST Controller
[2] A verification plan for an ABV-driven RTL block (e.g. MBIST controller) typically contains functional coverage goals, code coverage goals, and assertions, and the level/quality of verification is measured against the plan's coverage targets (the cited case reached ~100% on most functional metrics, with 25 directed tests vs. up to 88 random cases and ~97% total functional coverage). Assertion Based Functional Verification of March Algorithm Based MBIST Controller
[3] At the system level, verification planning is a sequential decision-making problem that specifies verification activities (VAs) and correction activities (CAs) across development phases; jointly planning VAs and CAs as a JVCS is an open problem because their activity spaces differ. A UCB-based Tree Search Approach to Joint Verification-Correction Strategy for Large Scale Systems
[4] The Genesys microprocessor verification methodology relies on a verification plan that induces smart sets of tests carrying out the verification tasks, and was applied to verify an x86 design, with the paper arguing it could have helped avoid known escape bugs such as the Pentium floating-point bugs. Functional verification methodology for microprocessors using the Genesys test-program generator. Application to the x86 microprocessors family (DATE 1999)
[5] Genesys-Pro is the main test-generation tool for functional verification of IBM processors (including several complex processors) and its template language considerably reduces the effort needed to define and maintain knowledge specific to an implementation and verification plan. Genesys-Pro: Innovations in test program generation for functional processor verification (IEEE D&T)