Certifications and regualtions are all "after-the-fact" solutions. We need to understand the fundamental issues before we can regulate them or cause people to be certified to meet some bar. I've seen little discussion of the underlying problems and that's what is bothering me. All of this talk about software makes it sound like there is an easy fix (for everyone knows that software is easy... of course it's not, but that's the conception). I suspect there is no easy fix; the systems are simply too complex so all of the handwaving that used to work will now fail. We need to get back to fundamentals and understand (then mitigate) failure modes.
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.