9P3YToou0BGr (Gast)
| | properties do not necessarily rlatee to features. One approach is to have a single property describe a single transaction (e.g. the movement of data from input to output of the design along with any transformations on the data, and adherence to protocols of course). Since the development of the implementation is likely to move from simple transactions to more complex transactions (and add various sideband outputs in along the way), so would the development of the properties. As well as a very robust unit, you would also end up with- a set of assertions reflecting any assumptions made in the design (e.g. on input behaviour)- and potentially a set of functional coverage points reflecting interesting interactions between the unit and surrounding unitsto feed up into your top-level verification.So I think it's an idea with plenty of potential. |