Iqbal Arshad, corporate vice president of innovation products at Motorola, slept in his office many nights when his team was designing the Motorola Droid smartphone. If he had had better tool support for system-level power management, driver development, system integration, and software-defined hardware development, maybe he could have slept at home.
Arshad spoke Thursday, June 17 at the Design Automation Conference, and delivered one of the most riveting keynote speeches I've heard. He not only provided an inside look at the design of the Droid; he spoke eloquently about design challenges and frustrations, and called on the EDA community to take notice and find a new approach.
"I don't think we need more tools for component automation," Arshad said. "I think the answer is something different - something we can think about and all do as a community." Probably without realizing it, he went on to describe some of the key points in the recent EDA360 vision paper, and called for the kind of new thinking and collaboration that paper advocates.
Click here to read more ...