Great article Shiv. A good DM system is indeed essential in any IC development. Every chip involves thousands of files to manage, and members of the team spread all over the world. Long gone are the days when we could get by using CVS and a local repository.
I'm interested in learning more about the integration of the bug tracking system with the DM system. In the past, those have always been separate, which costs extra time and can sometimes be error-prone.
Thanks again for the article.
This survey was exclusively focused on Design Data Management challenges, so no, the responses were not mutually exclusive. As to obtaining a clear indication of an actual problem, we can measure its magnitude in two ways:
On a relative scale, or an absolute one. We chose not to ask for a relative ranking of design management (DM) as compared to other design problems. Instead we obtained absolute measurements on the magnitude of the DM issue by quantifying its average impact on tapeout delay and designer overhead.
With regard to considering design management separately, I agree they are intertwined with the design problems, as commercial design management
systems can be deployed across all the tools in design and verification flows. In this case, our goal was to measure the relative rankings of the areas where engineers and their management felt Design Management systems would added the most value. We explicitly asked: "What are the 3 main reasons to use a Design Management system?"
All the areas mentioned by respondents are important to design. However, there are unique problems with tracking bugs (e.g. through designs and derivatives) and team collaboration, for which the respondents indicated DM is especially well-suited, so these ranked currently at the top of their list.
I personally see 'better IP and derivative reuse' as an area for which DM systems will be more broadly used over the next couple of years and is a strong focus now at IC Manage.
Hi Shiv, this is interesting data. I have some questions though. Are the responses mutually exclusive? Meaning, if somebody said design data management issues were the problem, did they feel the other things were OK? The reason I ask this question is that, I am curious about the focus point in your article. I don't think you can consider the design data management individually, which might be a byproduct of other problems (like bug tracking - 68%, team collaboration - 65%, easy access - 44%...).
Also, one more question I had was whether this survey only focused on data management questions or were data management questions grouped together with other questions. If so, then it is a much clear indication of an actual problem. If all the questions were about data/design management, then it might be useful to understand what percentage of people in your sample feel data management is the biggest tapeout bottle neck,
Thanks for the post; it was insightful.
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.