[dv] Update checklist As discussed in SRAM Ctrl V2 review, updated these checklist 1. Updated the description for “pre_verified_sub_modules_v2” 2. Updated V2S checklist to add an item for FPV Signed-off-by: Weicai Yang <weicai@google.com>
diff --git a/doc/project/checklist.md b/doc/project/checklist.md index c42921b..0a0eac9 100644 --- a/doc/project/checklist.md +++ b/doc/project/checklist.md
@@ -345,6 +345,8 @@ ### PRE_VERIFIED_SUB_MODULES_V1 Sub-modules that are pre-verified with their own testbenches have already reached V1 or a higher stage. +The coverage level of the pre-verified sub-modules that are not tracked (i.e., not taken through the verification milestones), meets or exceeds the V1 milestone requirement. +They are clearly cited in the DV document and the coverage of these sub-modules can be excluded in the IP-level testbench. ### DESIGN_SPEC_REVIEWED @@ -413,7 +415,7 @@ ### FPV_ALL_ASSERTIONS_WRITTEN -All assertions are implemented and are 90% proven. +All assertions (except security countermeasure assertions) are implemented and are 90% proven. Each output of the module has at least one forward and one backward assertion check. The FPV proof run converges within reasonable runtime. @@ -453,6 +455,7 @@ ### PRE_VERIFIED_SUB_MODULES_V2 Sub-modules that are pre-verified with their own testbenches have already reached V2 or a higher stage. +The coverage level of the pre-verified sub-modules that are not tracked (i.e., not taken through the verification milestones), meets or exceeds the V2 milestone requirement. ### SEC_CM_PLANNED @@ -490,10 +493,15 @@ ## V2S -### SEC_CM_VERIFIED +### FPV_SEC_CM_PROVEN <!-- TODO, add the link to cm verif methodology doc --> -Security countermeasures are verified. +All security countermeasure assertions are proven in FPV. + +### SIM_SEC_CM_VERIFIED + +<!-- TODO, add the link to cm verif methodology doc --> +Security countermeasures are verified in simulation. ## V3 @@ -550,6 +558,7 @@ ### PRE_VERIFIED_SUB_MODULES_V3 Sub-modules that are pre-verified with their own testbenches have already reached the V3 stage. +The coverage level of the pre-verified sub-modules that are not tracked (i.e., not taken through the verification milestones), meets the V3 milestone requirement. ### NO_ISSUES_PENDING