Electric (software)
circuit-design system
The Electric VLSI Design System is an EDA tool written in the early 1980s by Steven M. Rubin. Electric is used to construct logic wire schematics and to perform analysis of integrated circuit layout.
It can also handle hardware description languages such as VHDL and Verilog. The system has many analysis and synthesis tools, including design rule checking, simulation, routing, Layout vs. Schematic, logical effort, and more.
Electric is written in Java, and was released as part of the GNU project in 1998 under the GNU General Public License.
In 2017, Electric development ceased, but support and bug fixes continue.
Alternative design style for integrated circuits
Unlike other systems that design integrated circuits (ICs) by manipulating polygons on different layers of the wafer, Electric views IC layout as connected circuitry, similar to the way schematic capture systems work. In Electric, designers place nodes (transistors, contacts, etc.) and connect them with arcs (wires). This has advantages and disadvantages.
“Electric (software)” enters the record as circuit-design system. Crown Archives preserves that source wording while asking what Electric, software and circuit-design can confirm, complicate or overturn.
Why this record matters
“Electric (software)” is worth following because a concise public description often conceals a longer documentary argument. Here, Electric, software and circuit-design provides the most credible route into that argument.
Vocabulary and entity names are the principal evidence signals here, because they determine the precision of every later search. The source revision retrieved here is dated Sep 18, 2026. The linked authority identifier is Q1970665. 1 of 3 selected statements include explicit references; 2 carry qualifiers and 1 use preferred rank. The first chronological checks are 1998 and 2017.
The absence of detail may reflect summary conventions rather than a lack of surviving documentation. The lead is largely declarative, so disagreement and counter-evidence require a deliberate search beyond the opening account. Authority statements aid reconciliation but still require their own references, qualifiers and ranks to be checked.
How to read it
Use the entry as an orientation point, then follow its citations and revision history. Names, dates and institutional relationships should be checked against the original record.
- Subject orientation
- Search vocabulary
- Locating named sources
The closest primary source, responsible institution and strongest cited specialist reference.
Three-step research path
- Establish the record: confirm the title “Electric (software)”, its source revision and the description used here.
- Expand the search: follow Electric (software) primary sources, Electric (software) archive and Electric research across catalogues and specialist indexes.
- Test the account: compare the strongest cited source with the responsible institution’s current record and note any disagreement.
Questions for further research
- Which source most directly establishes the central claim about “Electric (software)”?
- What terminology or title could unlock a more precise catalogue search?
- Which institution is responsible for the underlying evidence?
Search terms from this dossier
This entry incorporates text from “Electric (software)” on English Wikipedia. Contributors are listed in the page history. Text is available under the Creative Commons Attribution-ShareAlike 4.0 License. Selected authority identifiers and statements are retrieved from Wikidata under CC0; their references and qualifiers remain part of the verification path.