# Checkers / models

**URL:** <https://verificationacademy.com/forums/t/checkers-models/31635>\
**Category:** UVM\
**Tags:** UVM\
**Created:** [March 22, 2016, 8:54pm UTC](https://verificationacademy.com/forums/t/checkers-models/31635 "2016-03-22T20:54:24Z")\
**Posts on this page:** 1\
**Showing post:** 16

<div class="post-metadata">

**Author:** ![chr\_sue](https://verificationacademy.com/forums/user_avatar/verificationacademy.com/chr_sue/32/1199_2.png) [@chr\_sue](https://verificationacademy.com/forums/u/chr_sue)\
**Post date:** [April 17, 2016, 6:36am UTC](https://verificationacademy.com/forums/t/checkers-models/31635/16 "2016-04-17T06:36:41Z")

</div>

_In reply to [ben@SystemVerilog.us](https://verificationacademy.com/forums/t/checkers-models/31635/15):_

This is what I said, there are areas where you should use assertion checkers. These FSM - a counter is a simple FSM - and interfaces like UARTs.  
To give you an example from my professional life: We had to verify an image processing chip to verify with a lot of algorithmic stuff inside. There was C++ model available (several thousands lines of code). We used this as reference model in a scoreboard. You’ll never have a chance to verify this behavior with assertions only.  
Christoph Suehnel

> **[UVM Coach Dr. Christoph Suehnel - Home](https://www.christoph-suehnel.de)**
>
> Dr. Christoph Suehnel, Oberammergau

---

_[View the full topic](https://verificationacademy.com/forums/t/checkers-models/31635)._
