|
| Login | Sign up | My Wish List |
![]() | Real-Time Systems Design and Analysis: An Engineer's Handbook by Philip A. Laplante, Phillip A. Laplante ISBN-10: 9780780334007 ISBN-10: 0-7803-3400-0 ISBN-13: 9780780334007 ISBN-13: 978-0-7803-3400-7 Hardcover 1996-12-16 John Wiley & Sons Find Lowest Price | |
Editorials | ||
Book Description "IEEE Press is pleased to bring you this Second Edition of Phillip A. Laplante's best-selling and widely-acclaimed practical guide to building real-time systems. This book is essential for improved system designs, faster computation, better insights, and ultimate cost savings. Unlike any other book in the field, REAL-TIME SYSTEMS DESIGN AND ANALYSIS provides a holistic, systems-based approach that is devised to help engineers write problem-solving software. Laplante's no-nonsense guide to real-time system design features practical coverage of:
| ||
Reviews | ||
Excellent primer The preface to this book says it is suitable for a college student or an engineer trying to get up to speed with real time systems. An excellent overview. | ||
Too cursory except as a text book The preface to this book says it is suitable for a college student or an engineer trying to get up to speed with real time systems. The latter is nonsense. It may work for a college course where a skilled instructor is adding material but it is far too cursory to apply. The first 6 chapters are basic material for any curriculum on programming. The chapters that follow mention difficulties but give no techniques that can be applied. Nothing in this would enable a person, previous unprepared to do so, to write a real time system. This book says it eschews mathematical formalism for practical utility. What it lacks is both a formal foundation and practical utility. The exercises (completely without sample answers) are terribly thought out. The description of difficulties of real time job scheduling are a list of known problems and some references to other papers. Sample code included is too specific to be general, and too general to be directly applicable. | ||
Worthless book-- don't buy it I am VERY VERY disappointed that IEEE publishes this book. IEEE usually has very high standard in publishing books under its name. However, it does not happen in this book. I have no clue why IEEE decides to publish this book. This book has a collection of VERY superficial knowledge that you can find from all entry level undergraduate books. It does not help engineers AT ALL as the book title claims. It misses LOTS of important real-time theories. Some theories mentioned in the book are either too superficial or even incorrect. As another reviewer states, the most important and widely used real-time scheduling theory, the rate-monotonic, is mentioned in the book by ONE single sentence. Can you believe this book is a real-time system book? Again, I am very disappointed this book get published. All my classmates believed this book is terribly BAD and we told our instructor. Don't spend your money on this expensive and useless book. If you want to know the practical aspect of real-time systems, check Mr. Simon's book "An Embedded Software Primer". All my classmates love this book. If you want to know the theory aspect of real-time systems, check Dr. Jane Liu's "Real-Time Systems" book published in 2000. | ||
Excellent book, not certain it is worth the price I think that this is an excellent introductory book that covers a broad range of items related to Real Time Systems. Unfortunately, I am not sure that it warrants the steep price. | ||
Expensive and Cursory but Readable There's not enough material to warrant the price. The book is easy to read, but the author repeats himself far too much. As justus@acm.org notes, the book is full of of filler sentences, paragraphs, and chapters. The title of the book seems incorrect, since the real-time portion of the book is skimpy. Rate-monotonic analysis, synonomous with real-time in academia, is only given a sentence. Ada, "the" real-time programming language, is barely mentioned. While Ada's pros and cons can be debated, it is almost completely skipped. On the other hand, software engineering practices, design methodologies, and testing have their own chapters. I didn't hate the book, but felt cheated after paying [the money]. | ||