- Shopping Bag ( 0 items )
In Component Design by Example, Ben attacks the design reuse problem. This topic
is timely and important. The Electronic Design Automation community has spent the
most of the last decade foreshadowing the emergence and importance of design re-use
and "IP" to obtain the next level of productivity gains. It is only in recently that we have
seen more frequent occurrences of design reuse. In the past few years, our customers
have begun to utilize various sizes and complexities of IP. With our customers, we have
discussed, planned, pondered and solved various problems and futures for the
development and reuse of design data and modular design flows. Consequently, we
have observed that there is much design data that is reused, but only after significant
effort. Often this is because the module was not successfully designed with reuse in
mind. I suspect that many designers lacked resources and references broad enough to
be useful on the topic of design for reuse.
Ben has created a pragmatic and useful book on design for reuse. It is useful because it
brings lots of practical information and experience in one place. Useful because he
dares to go beyond just the implementation phases of design, (which is more frequently
addressed), and takes on the procedures from conception to specification and planning.
PLEASE DON'T DISMISS THESE SECTIONS! Too many projects get into too
much trouble down the line due to incomplete, ambiguous, or "undocumented"
specifications and inadequate planning. It seems obvious, yet so many designers think
of it as overhead that impedes progress.
Component Design by Example will be useful to any designer or design team. It may
improve efficiency and improve products, or create disagreement in approach. My
hope is it will stimulate discussion. I expect it will be the foundation for a future filled
with IP. Read this before your next project. Then reread it afterward. You will
benefit both times.
Andrew R. Dauman
Vice-President of Corporate Applications
September 28, 2000