Average Reviews:
(More customer reviews)This book was packed with information. The authors call their approach the OO-Method and the first part of 50 pages puts the OO-Method into its historical perspective and in true scholarly fashion gives credit to others where credit is due. If you have been around for a few years you can probably lightly gaze over this section.
The second part of almost 200 pages is called "Conceptual Modelling: About the Problem Space" and documents what you capture to build an object model, dynamic model, functional model and presentation model. It also covered both green-field and legacy systems modeling which I found enlightening.
It seems to be very complete and somehow has the feel of an undergraduate course rather than a book for experienced professionals. While the descriptions are good, I found many of the worked examples trivial and verbose.
The visual style is also a little dense with almost no diagrams in the book, no colour, no fancy fonts (except for the examples which are in italic and thus easily skipped).
The third section of almost 100 pages called "Conceptual Model Compilation: from the Problem Space to the Solution Space" is an interesting discussion on how you delivery a working piece of software once you have captured the problem using the OO-Method and includes mention of their own commercial OLIVANOVA tool as well as a comparison to OMG's MDA approach.
My first read of this book was cover to cover and in general had me nodding rather than scowling. I have been back in with the highlighter to lift the gems and I'm sure I will be reading various chapter again to refresh my memory for upcoming projects.
Thanks guys for an excellent book. Not a casual read but definitely worth the effort.
Click Here to see more reviews about: Model-Driven Architecture in Practice: A Software Production Environment Based on Conceptual Modeling
This book introduces all the relevant information required to understand and put Model Driven Architecture (MDA) into industrial practice. It clearly explains which conceptual primitives should be present in a system specification, how to use UML to properly represent this subset of basic conceptual constructs, how to identify just those diagrams and modeling constructs that are actually required to create a meaningful conceptual schema, and how to accomplish the transformation process between the problem space and the solution space. The approach is fully supported by commercially available tools.
Get 20% OFF
No comments:
Post a Comment