All EDA companies share a common business objective: convincing customers to buy their tools over the competition. Among other marketing tasks, we search for graphics that best express the value of our tools, graphics that customers can look at and immediately understand. Having worked on many charts and graphs myself over the years, I’ll admit it’s not an easy job to find or develop just the right illustration. But every once-in-awhile I stumble across an image that makes simple and elegant sense.
System level simulation tools, of which SystemVision is a prime example, help design teams leverage modeling and analysis methods to improve system quality and performance. But how do development tools help designers realize these benefits? The explanation starts with the figures below.
This first image illustrates a traditional high-level system development flow where system integration is verified and fine-tuned using system prototypes and bench testing. The vertical axis represents relative effort required for a particular design task; the horizontal axis represents progressing time in the development process. System development tasks are grouped into three broad categories: Definition; Integration & Test; Reliability, Warranty & Rework. The point of the graphic is to illustrate the relative effort and cost associated with fixing system problems. Fixing a problem in the Definition phase is the least expensive. If a problem isn’t detected until the Integration & Test phase, costs to fix it are an order of magnitude higher than in the Definition phase. And if a problem isn’t found until the Reliability, Warranty & Rework phase, repair costs increase two orders of magnitude above fixing the problem at the Definition phase. Design teams using this development flow may use simulation and analysis tools for some development tasks, but hardware prototyping and test are the core of their performance verification process.
Contrast the hardware prototype-centric flow with the more simulation-and-analysis-centric flow illustrated in this second graphic, which shows the relative benefits of using system level analysis tools from early in the development process. In this flow, much of the effort (vertical scale) is shifted to the Definition phase where costs associated with finding and fixing problems are the lowest. Design teams use simulation and analysis to verify and fine tune the system definition before proceeding to detailed development. Virtual prototypes, developed using software models rather than hardware components, and analyzed using simulation rather than testbench instrumentation, are the means for analyzing and troubleshooting system integration and peformance issues. Finding problems at the Definition phase significantly reduces Integration & Test phase costs which, in turn, dramatically reduce Reliability, Warranty & Rework phase costs.
While these two diagrams are meant only to illustrate general “Effort & Cost versus Time” system development and performance verification concepts, the interpretation is clear: the earlier design teams can find system problems, the cheaper the problems are to fix. Adopting the right development methodology is key, starting with selecting design tools that can be used througout more phases of the development flow.