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:
“I have not had major experience of talking with people once pronounced brain-dead, but I think we could be safe in saying he did not have great zip.”
—Sir Howard Smith (b. 1919)
“These, then, will be some of the features of democracy ... it will be, in all likelihood, an agreeable, lawless, particolored commonwealth, dealing with all alike on a footing of equality, whether they be really equal or not.”
—Plato (c. 427–347 B.C.)
“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)