Order from a Major Online Bookstore
Ultimate Book Price Comparison Engine
Save Your Time And Money
| AnyBook4Less.com | Order from a Major Online Bookstore |
|
| Home | Store List | FAQ | Contact Us | | ||
| Ultimate Book Price Comparison Engine Save Your Time And Money |
||
 |
Title: Real-Time Object-Oriented Modeling by Bran Selic, Garth Gullekson, Paul T. Ward ISBN: 0-471-59917-4 Publisher: Wiley Pub. Date: 22 April, 1994 Format: Hardcover Volumes: 1 List Price(USD): $64.99 |
Average Customer Rating: 4.22 (9 reviews)
Rating: 4
Summary: Useful, but mostly as a historical document
Comment: First, remember that this book was published in 1994 - it was probably written in the 1992-3 era. The OO design world was still in the "warring states" period before unification under UML. The company that created ROOM tools, if I understand correctly, was absorbed by another company that was absorbed by another company - I'm not sure how much of ROOM in its pure form is still left.
That doesn't matter. In its time, ROOM was wild, innovative, and a topic of heated debate. It created a visual, highly abstracted language (back then, a questionable novelty) around an intensely parallelized model of computing (also a questionable novelty), at a time when "real-time" often meant lots of assembly programming in command-line environments. I was doing embedded development back about then - based on the mind-set of the time, I'm surprised that ROOM had the success and influence that it did.
Surprised but pleased. Lots of the ROOM techniques and notations survive in UML and other development tools. Modern component programming environments, JavaBeans included, show many signs of direct descent from the ROOM techniques. Still, there's a long way to go. ROOM may have been way ahead of its time, and languages still haven't caught up fully to its models of communication and parallelism.
As impressive an achievement as ROOM was (and is), I have some reservations about it. It relies pretty heavily of state machines for modelling the interacting components. State machines are a good tool, but quite unfamiliar to most software developers these days. I'm not sure whether that's a fault of the methodology or of today's programmers. I also have reservations about any methodology that requires me to buy someone's tools. The authors state that the design methodology can be used without their tools - based on ROOM's complexity, I doubt it. Also, I have a serious distrust of any programming environment that takes over so much of the process. Such tool sets tend to leave me feeling cramped, with little way to express my ideas in different terms. Finally, I'm sure it does all it says it does. Even so, the moment always comes when the tool-generated subsystems need to be opened up for debugging, or when the system has to be open to interaction with other development tools. Real-time and embedded systems tend to be so idiosyncratic and demanding that both kinds of openness in an IDE are compulsory. I just don't see the way out of the closed ROOM.
My present interest is not so much in the ROOM methodology itself, although I'm interested in methodology in general. Instead, I'm studying the visual notation it developed for expressing complex computations. Whatever ROOM's faults and whatever its later history, it's still worth attention.
Rating: 4
Summary: Concepts are incredibly valid and useful
Comment: The eminently practical, usable, powerful, elegant and - once understood - simple concepts behind ROOM deserve the broadest audience amongst real-time and even non-real-time developers. It has been a couple of years since I cracked the cover and I recall the reading being dry. Nonetheless, if you are considering a move to Rational Rose RealTime as a development tool (into which ObjecTime evolved), then this book is truly helpful as a reference for the modeling concepts. The example used throughout is simple enough that it is easy to grasp allowing you to dedicate your time to conceptual understanding rather than getting your head around some obtuse example. At the same time, the example is a natural vehicle for the inclusion of advanced concepts as each is intoduced.
The concepts of ROOM are finding/have found their way into the UML and the "it's not UML" darts of years ago are a little tired at this juncture.
ROOM is brilliant.
(from a former ObjecTime/Rational type though with no association for a few years)
Rating: 1
Summary: Too old
Comment: This book doesn't even mention UML. It may be good if you want to use author's modeling.
 |
Title: Designing Concurrent, Distributed, and Real-Time Applications with UML by Hassan Gomaa ISBN: 0201657937 Publisher: Addison-Wesley Professional Pub. Date: 15 January, 2000 List Price(USD): $59.99 |
 |
Title: Real-Time UML: Developing Efficient Objects for Embedded Systems (2nd Edition) by Bruce Powel Douglass ISBN: 0201657848 Publisher: Addison-Wesley Professional Pub. Date: 27 October, 1999 List Price(USD): $44.99 |
 |
Title: Real-Time Concepts for Embedded Systems by Qing Li, Caroline Yao ISBN: 1578201241 Publisher: CMP Books Pub. Date: July, 2003 List Price(USD): $44.95 |
 |
Title: Real-Time Design Patterns: Robust Scalable Architecture for Real-Time Systems by Bruce Powel Douglass ISBN: 0201699567 Publisher: Addison-Wesley Professional Pub. Date: 23 September, 2002 List Price(USD): $54.99 |
 |
Title: Practical Statecharts in C/C++: Quantum Programming for Embedded Systems with CDROM by Miro Samek ISBN: 1578201101 Publisher: CMP Books Pub. Date: July, 2002 List Price(USD): $44.95 |
Thank you for visiting www.AnyBook4Less.com and enjoy your savings!
Copyright� 2001-2021 Send your comments
