The "gotcha" in all of this is the specification (or lack thereof, in comse cases) to define what needs to be tested and the relative importance of each item. That's what we struggle with. That, and the massive volume of data you could potentially be collecting (coverage) and how to manage that. Usually, we end of following Frank's methodology! :)
The toughest question to answer is always "are we done?" But products need to get finished and shipped anyway, which is probably what resulted in the old expression, "time to shoot the engineers and ship the product!"
Interesting to read about System on chip verification methodology.
That's a new world to me. I think I'll start reading a little more about it. The term IP is somewhat louring and to think there are companies doing that and selling that seems interesting.
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.