Rating: 
Summary: One of the best books I have read on UML/OOP
Review: A great book not just on UML, but also on OOP. The elevator examples are very informative. I found Chapter 3 (Analysis: Defining the Object Structure) very clear and useful. Highly recomended book.
Rating:
Summary: Yes, OO can help in embedded real-time system design !
Review: As an embedded software in space system developper , i didn't really think OOP could be of any use for me. First because OO didn't show itself much valuable for dynamic systems, second because their usually is no OO language supported by our typical hardware. Then i read Real-Time UML. And i found a very simple, clear way to present and organize my design ideas. Furthermore, UML showed itself very efficient in detecting design error, refining some concepts. Now, each time i have to express my feelings, orientations, solutions, i use one or several of UML's diagrams. This is honnestly a must-read book, where any RT embedded system designer will find a good method to clear and refine things. It also shows itself very didactic in explaining the basics of Object Oriented Design. Impressive !
Rating:
Summary: A must have for all software design projects
Review: Be it Embedded Systems software development or not, this book is, I believe, a must have for any & all software design projects you undertake. I would not hesitate to consider application of the techniques set forth in a client-server or even web enabled internet paradigm. The author renders UML in context very well & allows for all concepts to make sense via formulation of cognitive models. I'll be sure to keep an eye out for future publications made by this author.
Rating:
Summary: A must have for all software design projects
Review: Be it Embedded Systems software development or not, this book is, I believe, a must have for any & all software design projects you undertake. I would not hesitate to consider application of the techniques set forth in a client-server or even web enabled internet paradigm. The author renders UML in context very well & allows for all concepts to make sense via formulation of cognitive models. I'll be sure to keep an eye out for future publications made by this author.
Rating:
Summary: Software Architecture made practical, excellent book!
Review: Before I buy any book, allways read as many readers reviews as possible, I saw this book was reviewed by Grady Booch, then I buy it and am very thankful for the detailed explanations and examples across the development process of real time systems and how apply the UML, from use cases to deployment diagramsI really enjoy the Architectural Design chapter, very few books explains those issues as this one does. Help me to further understand the role and responsibilities of a software architect I really great book. Marco A. Dorantes
Rating:
Summary: Excellent job of combining theory with pragmatics.
Review: Bruce Douglass has written an excellent book. I like how he introduces the problems of development and design that are unique to real time systems, and then demonstrates how, with the UML, one goes about modeling solutions to these problems. The discussion on patterns relative to real time systems is what really sets this book apart. Most of the current patterns work does not reach into this domain, and Bruce has done an excellent job of combining theory (in the world of patterns) with pragmatics (in the world of real time systems). Grady Booch, Chief Scientist, Rational Software Corporation
Rating: 
Summary: My thoughts on Real-Time UML
Review: I am gratified by the positive response for this book by the embedded and real-time community. I've been developing safety-critical real-time and embedded (RT&E) systems for almost 20 years, and have often thought that a book that integrated modeling concepts with the more commonly discussed real-time problems was needed. I strongly believe that object technology is not only mature enough to be used in RT&E systems, but that the growing complexity of these systems requires better ways of dealing with that complexity than traditional structured methods allow. The UML is a leap forward, unifying the best practices in object methodologies. Many of the companies to which I consult are using UML to effectively construct RT&E systems ranging from small 8-bit sized systems up to very large distributed systems with potentially hundreds of processors. This book is meant to be a gentle introduction to the UML and focus on the aspects of UML that are of particular concern to RT&E developers, such as how to identify objects, how to effectively use statecharts and state machines, and a process for using the elements of the UML to construct systems effectively. I hope you find the book helpful. Feel free to send me your comments and success stories.
Rating:
Summary: Great book for embedded developers seeking intro. to OT!
Review: I found this book to be very rewarding for us "real-timers". Easy reading, starting with simple concepts and then building to more complex ones... The author explains OO concepts using non-GUI examples which makes this book a "stand-out" for embedded software engineers. I especially enjoyed the cardiac pacemaker example. B. Douglass also does a fine job regarding his discussion of architectural, mechanistic, and detailed design utilizing UML diagrams and notation.
Rating:
Summary: Great book for embedded developers seeking intro. to OT!
Review: I found this book to be very rewarding for us "real-timers". Easy reading, starting with simple concepts and then building to more complex ones... The author explains OO concepts using non-GUI examples which makes this book a "stand-out" for embedded software engineers. I especially enjoyed the cardiac pacemaker example. B. Douglass also does a fine job regarding his discussion of architectural, mechanistic, and detailed design utilizing UML diagrams and notation.
Rating: 
Summary: Some parts excelent, some poor
Review: I have mixed feelings for this book. Parts of the book are awful, other parts are really excellent. The overall impression is still that this is a book worth reading, and keeping in a bookshelf not too far away from your workplace for real time work. The explanations about state diagrams is really good. In general the treatment of state is the strong side of the book. The book explains state machines and how they can, and cannot, be used in a good way. The book also describes two patterns for state machine design. Most parts of the book are well written and easy to read. The design patterns described in the book are not rocket science, but they are (unlike many pattern descriptions) described in a way that is easy to read and understand. The first chapter is awful (skip it, or read on: it will get better). The language in this chapter is dry and hard to read. There is no useful information here. The author declares that real-time design/programming is harder than desktop program design. He also declares that object-oriented programming is generally better than block-structured. The readers already knows this, or otherwise we would not be reading this book. The remarks about C++ in the book are about 50 % accurate and 50 % false. The author seems to have missed a lot of the C++ programming paradigms that have become common during the last five years. I had the expectation that this book would include some insight that you couldn't combine yourself from experience in desktop focused UML and traditional (block-structured, functional) real-time design. The book did not live up to this expectation. (But I guess that expectation was unrealistic.)
| 
