A unified design representation can work

Authors:
P. Kollaritsch;S. Lusky;D. Matzke;D. Smith;P. Stanford
Affiliations:
Texas Instruments, P.O. Box 655621, MS 369, Dallas, TX;Texas Instruments, P.O. Box 655621, MS 369, Dallas, TX;Texas Instruments, P.O. Box 655621, MS 369, Dallas, TX;Texas Instruments, P.O. Box 655621, MS 369, Dallas, TX;Texas Instruments, P.O. Box 655621, MS 369, Dallas, TX
Venue:
DAC '89 Proceedings of the 26th ACM/IEEE Design Automation Conference
Year:
1989

Citing 4
Cited 4

Object-oriented programming: Themes and variations

AI Magazine
ZEITGEIST: Database support for object-oriented programming

Lecture notes in computer science on Advances in object-oriented database systems
DOSS: a storage system for design data

DAC '86 Proceedings of the 23rd ACM/IEEE Design Automation Conference
A database approach for managing VLSI design data

DAC '82 Proceedings of the 19th Design Automation Conference

The case for a read barrier

ASPLOS IV Proceedings of the fourth international conference on Architectural support for programming languages and operating systems
Requirements-based design evaluation

DAC '95 Proceedings of the 32nd annual ACM/IEEE Design Automation Conference
Transistor reordering for power minimization under delay constraint

ACM Transactions on Design Automation of Electronic Systems (TODAES)
High level test generation using data flow descriptions

EURO-DAC '90 Proceedings of the conference on European design automation

Quantified Score

Hi-index	0.00

Visualization

Abstract

A unified design representation can work. This has always been considered impractical due to major problems of run time, space, tool interdependencies, and multiple representations. We have addressed these problems and found them tractable. We present our solutions to these problems, gained through the experience of developing the Droid design system.