Product Description

Art of Designing Embedded Systems is apart primer and part reference, aimed at practicing embedded engineers, whether working on the code or the hardware design. Embedded systems suffer from a chaotic, ad hoc development process. This books lays out a very simple seven-step plan to get firmware development under control. There are no formal methodologies to master; the ideas are immediately useful. Most designers are unaware that code complexity grows faster than code size. This book shows a number of ways to linearize the complexity/size curve and get products out faster. Ganssle shows ways to get better code and hardware designs by integrating hardware and software design. He also covers troubleshooting, real time and performance issues, relations with bosses and coworkers, and tips for building an environment for creative work.

Get better systems out faster, using the practical ideas discussed in Art of Designing Embedded Systems. Whether you're working with hardware or software, this book offers a unique philosophy of development guaranteed to keep you interested and learning.

* Practical advice from a well-respected author
* Common-sense approach to better, faster design
* Integrated hardware/software

Product Details

• Amazon Sales Rank: #377650 in Books
• Published on: 1999-11-10
• Original language: English
• Number of items: 1
• Binding: Hardcover
• 256 pages

Review
Ganssle takes a direction that I find refreshing. Rather than presenting a one-size-fits-all methodology-a Ganssle Unified Process-he shares anecdote after anecdote, suggestion after suggestion. He's not telling design teams to change their strategies. He just refines them, and throws in a few more tactics along the way, with a conversational style that makes you think you're chatting away at a conference, rather than reading a book about electronics.
-Software Development Times

This book is equally valuable for someone looking for a higher-level understanding of the process of building reliable embedded systems, and the steps that can be taken to deliver them on time and on budget. -Software Development Times

...shows readers how to get better, more integrated code and hardware designs and how to troubleshoot the inevitable bugs. This book presents a philosophy of development, instead of a cookbook of directions. -Poptronics -- Review

Review
Ganssle takes a direction that I find refreshing. Rather than presenting a one-size-fits-all methodology-a Ganssle Unified Process-he shares anecdote after anecdote, suggestion after suggestion. He's not telling design teams to change their strategies. He just refines them, and throws in a few more tactics along the way, with a conversational style that makes you think you're chatting away at a conference, rather than reading a book about electronics.
-Software Development Times

This book is equally valuable for someone looking for a higher-level understanding of the process of building reliable embedded systems, and the steps that can be taken to deliver them on time and on budget. -Software Development Times

...shows readers how to get better, more integrated code and hardware designs and how to troubleshoot the inevitable bugs. This book presents a philosophy of development, instead of a cookbook of directions. -Poptronics

From the Publisher
Get better systems out faster, using the practical ideas discussed in Art of Designing Embedded Systems. Whether you're working with hardware or software, this book offers a unique philosophy of development guaranteed to keep you interested and learning.

Customer Reviews

Good Experience From One Who Has Been There
In Mr. Ganssle's book he states, "Engineers are notoriously poor communicators..." and some of that truth shows in his book. The chapters, sections, and appendices are well organized but the content in them is not. The writing style has a tendency to ramble like a friendly conversation, sometimes deviating into tangential material. However, the experience and wisdom held in the book's content (even the tangential parts) are its greatest prize. As an embedded developer with seven years of experience, I found myself frequently relating to the author's own experience. When I read the sentence, "We've got to avoid quoting a long, arbitrary time impact as a knee-jerk reaction to any change request." I actually laughed out loud. Mr. Ganssle does a good job of contrasting a disciplined, well-documented development process versus a panicked, haphazard one and he explains the trade-offs between the two by quoting respectable studies on the subject. The material on writing and debugging good embedded code is all stuff that most folks will, hopefully, learn after few years on the job. But, if you're just starting out, or if you're looking for a better way to do your job, I recommend that you read this book.

Embedded Systems Guru Knowledge Base
This text is obviously a distillation of many years of experience in the field. I have programmed enough ISR's and programmable devices to know that it is very good advise indeed. The book, however, is not for the beginner. His assumed audience are people who are already in the field and would like to take advantage someone with greater experience. The book is loaded with hard learned nuggets of wisdom that are less likely to be found in classroom textbooks. He has something to offer both software and hardware types(I'm software). For example, the advise about software partitioning, ISR development and debugging, and device programming is excellent, and for hardware types the advise on building boards that are both software and hardware debuggable and the myriad tips on finding problems from the common to the obscure will be appreciated. He also provides suggested project management guidelines that help in getting functionality operating as quickly as possible, and, from my point of view, guidance on how to deal with irrational schedules and managements that are reluctant to provide adequate project resources. I appreciated expecially his citing research that quiet private offices provide the single greatest boost to engineering productivity. Probably the only thing I found lacking in the book was a Bibliography of other book references and useful web links.

Hunter S. Thompson has written an Embedded Systems Book!
This is a really poorly written and poorly organized collection of ramblings from an embedded systems "expert." Each topic is covered at a grossly superficial level and most sections consist of short random thoughts. Here's a typical paragraph (from the 2 pages on real time operating systems).

"Improvements to these tools come almost daily. Keep on top of the field to avoid the fate of the dinosaurs."

Speaking of dinosaurs, the author's favorite tool for debugging and performance analysis seems to be the oscilloscope.

I get the feeling that the author "wrote" this book by talking into a tape recorder while in an LSD haze on the way to Las Vegas.

BTW, the page count is 243 and not 352 claimed in the advertising for this book. Thankfully, the editors saw fit to trash at least a portion of this book.

My only regret in writing this review is that the Amazon rating service doesn't offer the option of giving 0 stars.