What Every Engineer Should Know About Developing Real-Time Embedded Products

Front Cover
CRC Press, Oct 24, 2007 - Computers - 496 pages
You can find them in your wristwatch or MP3 player; they perform specific functions in washing machines, traffic lights, and even pacemakers. Embedded systems are pervasive, ubiquitous, and widespread throughout our daily lives. Developing these real-time embedded products requires an understanding of the interactions between different disciplines, such as circuit design, power, cooling, packaging, software, and human interface. This volume provides the knowledge and insight engineers need to make critical design decisions and offers a clear guide for preparing and developing projects in different markets.

The book begins by laying the basic groundwork for effective processes, covering smaller, self-contained devices and subsystems, ranging from handheld devices to appliances. Highly detailed case studies, which include designing instruments for space flight, implanted medical devices, and military support equipment, illustrate industry best practices and managerial issues. Each case study is detailed in terms of concept, market, standards, integration, manufacturing, and phases. With schedule and estimation templates, this highly functional text presents numerous examples of design tradeoffs critical to successful project development.

Offering even coverage and clarification of the entire development process, What Every Engineer Should Know about Developing Real-Time Embedded Products provides engineers and industrial designers with practical tools to make important decisions, from deciding whether to buy or build subsystems to determining the appropriate kinds of field testing.
 

What people are saying - Write a review

We haven't found any reviews in the usual places.

Contents

Chapter 1 Development Processes
1
Chapter 2 Variations on the ThemeConsiderations for MissionCritical Equipment and Medical Devices
53
Chapter 3 Tools of the Trade
97
Chapter 4 Case Study 1Minor Appliances
111
Chapter 5 Case Study 2Telecom Products
123
Chapter 6 Case Study 3Commercial Laboratory Equipment
141
Chapter 7 Case Study 4Automobile Engine Controller
171
Chapter 8 Case Study 5Industrial Flowmeter
189
Chapter 12 Case Study 9Satellite Subsystem
279
Chapter 13 Case Study 10Programmer for Implanted Stimulators
303
Chapter 14 Case Study 11Implanted Medical Devices
333
Chapter 15 Summary Comparisons Across the 11 Case Studies
377
Chapter 16 Some Observations on Architectural TradeOffs in Selected RealTIme Systems
393
Chapter 17 Some Observations about Consumer Appliances
413
Chapter 18 Some Observations about User Interfaces
439
Index
455

Chapter 9 Case Study 6Military Support Equipment
203
Chapter 10 Case Study 7Designing Instruments for Space Flight
221
Chapter 11 Case Study 8Aerospace Video Processor
263
Back cover
469
Copyright

Other editions - View all

Common terms and phrases

Popular passages

Page iv - McKay 26. What Every Engineer Should Know About Quality Control, Thomas Pyzdek 27. What Every Engineer Should Know About Microcomputers: Hardware/Software Design, A Step-by-Step Example. Second Edition, Revised and Expanded, William S. Bennett, Carl F. Evert, and Leslie C. Lander 28. What Every Engineer Should Know About Ceramics, Solomon Musikant 29. What Every Engineer Should Know About Developing Plastics Products, Bruce C. Wendle 30. What Every Engineer Should Know About Reliability and Risk...
Page iii - III 17. What Every Engineer Should Know About Practical CAD/CAM Applications, John Stark 18. What Every Engineer Should Know About Threaded Fasteners: Materials and Design, Alexander Blake 19.
Page iii - Zeldman 12. What Every Engineer Should Know About Microcomputer Systems Design and Debugging, Bill Wray and Bill Crawford 13. What Every Engineer Should Know About Engineering lnformation Resources, Margaret T.
Page iv - Design, A Step-by-Step Example. Second Edition, Revised and Expanded, William S. Bennett, Carl F. Evert, and Leslie C. Lander 28. What Every Engineer Should Know About Ceramics, Solomon Musikant 29. What Every Engineer Should Know About Developing Plastics Products, Bruce C. Wendle 30. What Every Engineer Should Know About Reliability and Risk Analysis, M. Modarres 31. What Every Engineer Should Know About Finite Element Analysis: Second Edition, Revised and Expanded, edited by John R. Brauer 32....
Page iv - What Every Engineer Should Know About Reliability and Risk Analysis, M. Modarres 31. What Every Engineer Should Know About Finite Element Analysis: Second Edition, Revised and Expanded, edited by John R. Brauer 32. What Every Engineer Should Know About Accounting and Finance, Jae K. Shim and Norman Henteleff 33. What Every Engineer Should Know About Project Management: Second Edition, Revised and Expanded, Arnold M. Ruskin and W. Eugene Estes 34. What Every Engineer Should Know About Concurrent Engineering,...
Page ii - What Every Engineer Should Know About Inventing, William H. Middendorf 8. What Every Engineer Should Know About Technology Transfer and Innovation, Louis N. Mogavero and Robert S. Shane 9. What Every Engineer Should Know About Project Management, Arnold M. Ruskin and W. Eugene Estes 10.
Page ii - Vol. 1 What Every Engineer Should Know About Patents, William G. Konold, Bruce Tittel, Donald F. Frei, and David S. Stallard Vol.

Bibliographic information