Electronic CAD Frameworks

1. Front Matter

   Pages i-xvii

   PDF

2. Introduction

   • Timothy J. Barnes, David Harrison, A. Richard Newton, Rick L. Spickelmier

   Pages 1-15

3. Major Components of an Engineering Framework

   • Timothy J. Barnes, David Harrison, A. Richard Newton, Rick L. Spickelmier

   Pages 17-27

4. Data Representation

   • Timothy J. Barnes, David Harrison, A. Richard Newton, Rick L. Spickelmier

   Pages 29-50

5. Data Management

   • Timothy J. Barnes, David Harrison, A. Richard Newton, Rick L. Spickelmier

   Pages 51-75

6. Tool Management

   • Timothy J. Barnes, David Harrison, A. Richard Newton, Rick L. Spickelmier

   Pages 77-86

7. Design Flow Management

   • Timothy J. Barnes, David Harrison, A. Richard Newton, Rick L. Spickelmier

   Pages 87-100

8. User Interfaces

   • Timothy J. Barnes, David Harrison, A. Richard Newton, Rick L. Spickelmier

   Pages 101-120

9. Extension Languages

   • Timothy J. Barnes, David Harrison, A. Richard Newton, Rick L. Spickelmier

   Pages 121-137

10. Implementing a CAD Framework

    • Timothy J. Barnes, David Harrison, A. Richard Newton, Rick L. Spickelmier

    Pages 139-145

11. The CAD Framework Initiative

    • Timothy J. Barnes, David Harrison, A. Richard Newton, Rick L. Spickelmier

    Pages 147-162

12. Summary

    • Timothy J. Barnes, David Harrison, A. Richard Newton, Rick L. Spickelmier

    Pages 163-165

13. Back Matter

    Pages 167-195

    PDF

When it comes to frameworks, the familiar story of the elephant and the six blind philosophers seems to apply. As each philoso­ pher encountered a separate part of the elephant, each pronounced his considered, but flawed judgement. One blind philosopher felt a leg and thought it a tree. Another felt the tail and thought he held a rope. Another felt the elephant's flank and thought he stood before a wall. We're supposed to learn about snap judgements from this alle­ gory, but its author might well have been describing design automation frameworks. For in the reality of today's product development requirements, a framework must be many things to many people. xiv CAD Frameworks: Integration Technology for CAD As the authors of this book note, framework design is an optimi­ zation problem. Somehow, it has to be both a superior rope for one and a tremendous tree for another. Somehow it needs to provide a standard environment for exploiting the full potential of computer-aided engineering tools. And, somehow, it has to make real such abstractions as interoperability and interchangeability. For years, we've talked about a framework as something that provides application-oriented services, just as an operating system provides system-level support. And for years, that simple statement has hid the tremendous complexity of actually providing those services.

• Software
• Standard
• computer-aided design (CAD)
• development
• integrated circuit

• Cadence Design Systems, USA

  Timothy J. Barnes

• University of California, Berkeley, USA

  David Harrison, A. Richard Newton, Rick L. Spickelmier

Policies and ethics