I'm starting to feel like a relic from a bygone age, because when I talk to younger engineers about the way we used to do things they stare at me in disbelief...
Editor’s Note: I’m starting to feel like a relic from a bygone era, because when I talk to younger engineers about the way we used to do things they stare at me in disbelief. To a very large extent I predate Electronic Design Automation (EDA) as we know it. In fact, if the truth be told, I even predate the term EDA…
The thing is that it really isn’t so long ago that we didn’t have high-level languages and automated synthesis technologies and computer-aided layout tools and so on and so forth. We really did capture and implement our electronic designs by hand.
I personally find the history behind all of this stuff to be really interesting, so I’ve decided to write a series of “How it was” articles that describe different aspects of electronic design capture, debug, verification, implementation, test, and … the list goes on. Each article will be short and focused (well, as focused as I can bring myself to be [grin]) and positively dripping in personal recollections and reminiscences (“Nostalgia isn’t what it used to be,” as they say).
Of course, anything I write will be based on, and colored by, my own experiences, but I am sure that you also have interesting tales to tell. So it would be great if – in addition to commenting on my articles – you took the time to write down short stories of your own. I can help in the copy editing department, so you don’t need to worry about being “word perfect”. All you have to do is to email your offering to me at max@CliveMaxfield.com with “How it was” in the subject line.
I can post your article as “anonymous” if you wish. On the other hand, what would be really cool would be if you wanted to add a few words about yourself – and maybe even provide a couple of “Then and Now” pictures – for example:
On the left we see me as a young sprog – I was still a student at this time, poised on the brink of leaping into my first position at International Computers Limited (ICL). On the right we see me as I am today – a much older and sadder man, beaten down by the pressures of work and bowed by the awesome responsibilities I bear (grin).How it was…
Prior to the 1970s, electronic components and circuits were handcrafted. Circuit diagrams (known as schematics) were drawn using pen, paper, and stencils. Similarly, the copper tracks on a circuit board were drawn using red and blue pencils to represent the top and bottom of the board. Any form of analysis (for example, “What frequency will this oscillator run at if I use this capacitor and this resistor?”
) was performed with pencil, paper, and a slide rule (or a mechanical calculator if you were lucky). Not surprisingly, this style of design was time-consuming, expensive, and prone to error.Computer-Aided Design (CAD)
As electronic designs and devices grew more complex, it became necessary to develop automated techniques to aid in the design process.
In the early 1970s, companies like Calma, ComputerVision, and Applicon created special computer programs that helped personnel in the drafting department capture hand-drawn designs in digital form using large-scale digitizing tables.
Over time, these early computer-aided drafting tools evolved into interactive programs that performed integrated circuit layout; that is, they could be used to describe the locations of the transistors forming the integrated circuit and the connections between them.
Other companies like Racal-Redac, SCI-Cards, and Telesis created equivalent layout programs for printed circuit boards (PCBs). Collectively, these integrated circuit and circuit board layout programs became known as Computer-Aided Design (CAD)
tools.Computer-Aided Engineering (CAE)
Also in the late 1960s and early 1970s, a number of universities and commercial companies started to develop computer programs known as simulators. These programs allowed students and engineers to emulate the operation of an electronic circuit without actually having to build it first.
Perhaps the most famous of the early simulators was the simulation program with integrated circuit emphasis (SPICE). This was developed by the University of California in Berkeley and was made available for widespread use around the beginning of the 1970s. SPICE was designed to simulate the behavior of analog circuits – other programs called logic simulators were developed to simulate the behavior of digital circuits.
Around the beginning of the 1980s, companies like Daisy, Mentor, and Valid spawned computer programs that allowed engineers to capture schematic (circuit) diagrams on the computer screen. These tools could then be used to generate textual representations of the circuits called netlists that described the components to be used and the connections between them. In turn, these netlists could be used to drive analog and digital simulators (and eventually layout tools).
The companies promoting front-end tools for schematic capture and simulation classed them as Computer-Aided Engineering (CAE)
. This was based on the fact that these tools were targeted toward design engineers, and the CAE companies wished to distinguish their products from the CAD tools that were originally used by the drafting department. (With hindsight – the one exact science – it would have made much more sense to use CAD to refer to the front-end design tools and CAL to refer to the downstream layout tools … but it was not to be… Oh well, that’s the way the cookie crumbles…)Designers versus Engineers
If you say things the wrong way when talking to someone in the industry, you immediately brand yourself as an outsider – one of “them” instead of one of “us” (and you certainly don't want to be "one of them" (grin).
For historical reasons that are based on the origins of the terms CAD and CAE, the term layout designer
or simply designer
is typically used to refer to someone who lays out a circuit board (determines the locations of the components and the routes of the tracks connecting them together).
By comparison, the term design engineer
or simply engineer
is typically used to refer to someone who conceives and describes the functionality of an integrated circuit, printed circuit board, or electronic system (what it does and how it does it).Electronic Design Automation (EDA)
Sometime during the 1980s, all of the CAE and CAD tools used to help design electronic components and systems came to be referred to by the “umbrella” name of Electronic Design Automation (EDA), and everyone was happy (apart from the ones who weren’t, but they don’t count [grin]).Click Here
to see other articles in this "How it was..."
If you found this article to be of interest, visit EDA Designline
where – in addition to blogs on all sorts of "stuff" – you will find the latest and greatest design, technology, product, and news articles with regard to all aspects of Electronic Design Automation (EDA).
Also, you can obtain a highlights update delivered directly to your inbox by signing up for the EDA Designline weekly newsletter – just Click Here
to request this newsletter using the Manage Newsletters tab (if you aren't already a member you'll be asked to register, but it's free and painless so don't let that stop you [grin]).