I am totally in agreement with you then. The current functional coverage is badly architected and does not scale. Companies have too many problems relating use case coverage to functional coverage poinbt. I think use cases are the key and these can be broken down into ways in whgich use cases can be satisfied. Problem is that EDA companies have too much invested in functional coverage to want to change.
no, I am asking how to define function coverage efficiently. Now we can only extract cover points from design spec, and it is for verification only. Above discussion looks like related to expanding functional coverage to system level. I am wondering how to achieve it. And how to organize it and make it as "simple" as code coverage.
who should be the person to define the system level functional coverage matrics? How to prove it is complete. If it is not a complete matrics, it is meaningless to target it and if it is too complex, quite difficuit to get 100%. Functional coverage is not like code coverage with which we have a good reference. (RTL code)
What are the engineering and design challenges in creating successful IoT devices? These devices are usually small, resource-constrained electronics designed to sense, collect, send, and/or interpret data. Some of the devices need to be smart enough to act upon data in real time, 24/7. Are the design challenges the same as with embedded systems, but with a little developer- and IT-skills added in? What do engineers need to know? Rick Merritt talks with two experts about the tools and best options for designing IoT devices in 2016. Specifically the guests will discuss sensors, security, and lessons from IoT deployments.