Major Features of An EDA Specific Database
An EDA specific database is expected to provide many basic constructs and services. Here is a brief and incomplete list of what is needed:
- Fundamental Features
- The Design (or Cell) as the Basic Unit
- Shapes and Physical Geometry
- Hierarchy
- Connectivity and Hierarchical Connectivity
- General Constructs
- API Forms
- Utility Layer
- Advanced Features
- Parameterized Designs
- Namespaces and Name Mapping
- Place-and-Route Constructs
- Timing and Parasitic Constructs
- Occurrence Models and Logical/Physical Mapping
- Interface to Configuration management
- Extensibility
- Technology Data
- Layer Definitions
- Design Rules
- Generation and extraction rules for simple devices
- Library Data and Structures: Design-Data Management
- Library Organization: From Designs to Disk Files
- Design-Data Management
- Interoperability Models
Read more about this topic: EDA Database
Famous quotes containing the words major, features and/or specific:
“True spoiling is nothing to do with what a child owns or with amount of attention he gets. he can have the major part of your income, living space and attention and not be spoiled, or he can have very little and be spoiled. It is not what he gets that is at issue. It is how and why he gets it. Spoiling is to do with the family balance of power.”
—Penelope Leach (20th century)
““It looks as if
Some pallid thing had squashed its features flat
And its eyes shut with overeagerness
To see what people found so interesting
In one another, and had gone to sleep
Of its own stupid lack of understanding,
Or broken its white neck of mushroom stuff
Short off, and died against the windowpane.””
—Robert Frost (1874–1963)
“I recognize in [my readers] a specific form and individual property, which our predecessors called Pantagruelism, by means of which they never take anything the wrong way that they know to stem from good, honest and loyal hearts.”
—François Rabelais (1494–1553)