| ||||||||||||||||||||||||
|
Shop the new tech.book(store)
New! Introducing the tech.book(store), a hub for Software Developers and Architects, Networking Administrators, TPMs, and other technology professionals to find highly-rated and highly-relevant career resources. Shop books on programming and big data, or read this week's blog posts by authors and thought-leaders in the tech industry. > Shop now |
|
There is a newer edition of this item:
|
Product Details
Would you like to update product info or give feedback on images? |
Looking at the examples, one finds that the examples in each model's section are totally unrelated to the examples in the other two model's sections. Essentially, the authors have fabricated example systems for each section that are easy to describe using that particular model, but have failed to show the other two models for those systems. This book would have been far better if the same set of examples were carried through the three types of models, showing how they interrelate.
The primary problem with the book, however, seems to be that it's about OMT. OMT has many serious flaws. OMT's object model notation is reasonable. The functional model notation is satisfactory. The dynamic model is incomplete. And the three models are not related to eachother in any clear way by this book. Without fixing the flaws inherent in OMT, any book on OMT is going to be mostly useless.