What Every Engineer Should Know About Developing Real-Time Embedded ProductsYou 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, |
Contents
| 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 |
Other editions - View all
What Every Engineer Should Know About Developing Real-Time Embedded Products Kim R. Fowler No preview available - 2007 |
What Every Engineer Should Know about Developing Real-Time Embedded Products Kim R. Fowler No preview available - 2018 |
Common terms and phrases
Agar Corporation analysis appliances architecture assembly batteries Boeing Support Systems buttons cable circuit boards code reviews commercial complete components concept concerns configuration cost COTS critical design custom design design phase design review design team development processes display documents electrical electronic embedded system enclosure Engineer Should Know example fabrication failure fault tolerance Figure flowmeters FMEA FPGAs functionality IEEE implantable medical device input integration interface Keithley Instruments Kim Fowler laboratory maintenance manufacturing mechanical medical devices microcontrollers mission-critical and safety-critical modules O-Level operation parameters Patton perform problems processor programmer prototype real-time real-time operating system reliability repair requirements rights reserved risk safety schedule sensors SET carrier simulators single-board computers software development software engineers Space instrument spacecraft specific standards Stepper motor support equipment Table technicians thermal trade-offs types ü ü ü Underwriters Laboratory unit V-model vibration
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 59 - Risk management is the systematic application of management policies, procedures, and practices to the tasks of identifying, analyzing, controlling. and monitoring risk.
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 56 - Design output means the results of a design effort at each design phase and at the end of the total design effort. The finished design output is the basis for the device master record. The total finished design output consists of the device, its packaging and labeling, and the device master record.
Page 77 - Safety is the probability that a system will either perform its functions correctly or will discontinue its functions in a manner that does not disrupt the operation of other systems or compromise the safety of any people associated with the system.
Page ii - Vol. 1 What Every Engineer Should Know About Patents, William G. Konold, Bruce Tittel, Donald F. Frei, and David S. Stallard Vol.