Advances in Petri nets 1986, part I on Petri nets: central models and their properties
An object-oriented datamodel for the VLSI design system PLAYOUT
DAC '89 Proceedings of the 26th ACM/IEEE Design Automation Conference
Toward a unified framework for version modeling in engineering databases
ACM Computing Surveys (CSUR)
Meta data management in the NELSIS CAD framework
DAC '90 Proceedings of the 27th ACM/IEEE Design Automation Conference
Design version management in the GARDEN framework
DAC '91 Proceedings of the 28th ACM/IEEE Design Automation Conference
Electronic CAD frameworks
On modeling integrated design environments
EURO-DAC '92 Proceedings of the conference on European design automation
Representing the hardware design process by a common data schema
EURO-DAC '92 Proceedings of the conference on European design automation
On modeling top-down VLSI design
ICCAD '94 Proceedings of the 1994 IEEE/ACM international conference on Computer-aided design
Generating ECAD framework code from abstract models
DAC '95 Proceedings of the 32nd annual ACM/IEEE Design Automation Conference
A design utility manager: the ADAM planning engine
DAC '86 Proceedings of the 23rd ACM/IEEE Design Automation Conference
VLSI CAD tool integration using the Ulysses environment
DAC '86 Proceedings of the 23rd ACM/IEEE Design Automation Conference
On the architecture of a CAD framework: the NELSIS approach
EURO-DAC '90 Proceedings of the conference on European design automation
Toward Quality EDA Tools and Tool Flows Through High-Performance Computing
ISQED '05 Proceedings of the 6th International Symposium on Quality of Electronic Design
| Hi-index | 0.00 |
The important step towards a comprehensiveCAD framework is the development of a suitable, completedesign model on which the design system's components arebased. To date, we generally find "island" solutions for differentaspects as data and process management, but in future, weneed more and more integrated solutions. Only the integrationgives us the traceability we need for design planning, to generateparts of the design toolýs code automatically, etc.This paper describes how a suitable Design Task Model canbe used to link the Product and Flow Models which are currentlyseparated in most frameworks. Using the PLAYOUTDesign Model as an example, we show how the Product, theTask, and the Flow Models may fit together, and we describe amodeling environment that guarantees the development ofconsistent, integrated models.