At the Design and Verification Conference last February, there was a panel ("Where Does Design End and Verification Begin?") that discussed the impact of new verification tools that focus on just one problem area and thereby enable more effective verifcation. Engineers no longer have to create a solution out of their own dynamic simulator, static analyzer, or ABV tools.
In the example of Meridian clock-domain-crossing (CDC) verification, a mix of structural, formal and dynamic methods operating under-the-hood, ensure that an SoC will not fail with a metastability issue. Other examples are state-of-the art Lint analysis, and X-propagation and reset verfication / optimization.
At Real Intent, we call this new category Static Verfication. Gary Smith calls them Verification Apps. I see these as important addition to our tool chest so engineers don't design SoCs that we cannot verify.
Drones are, in essence, flying autonomous vehicles. Pros and cons surrounding drones today might well foreshadow the debate over the development of self-driving cars. In the context of a strongly regulated aviation industry, "self-flying" drones pose a fresh challenge. How safe is it to fly drones in different environments? Should drones be required for visual line of sight – as are piloted airplanes? Join EE Times' Junko Yoshida as she moderates a panel of drone experts.