Developing Applications with Visual Basic and UML The Addison-Wesley Object Technology Series)

Author: Paul R. Reed List Price: $39.95 Our Price: Click to see the latest and low price ISBN: 0201615797 Publisher: Addison-Wesley Pub Co (04 November, 1999) Edition: Paperback Sales Rank: 46,811 Average Customer Rating: 4.5 out of 5

Buy now directly from Amazon.com -

Customer Reviews

Developing Applications with Visual Basic and UML breaks ground in an area where I've seen no other book yet do a good job, applying UML to VB. UML is a complex design notation that works best with object oriented design and programming tools, but VB 6 is at best object-based. Reading most generic UML books requires, at the very least, an advanced degree in computer science, keeping it to the intellectual elite of the software world. The author has bridged this gap effectively, relating the various diagrams and tools in UML to VB applications, demonstrating how you can apply them to real applications. And relating terms and concepts in VB to those in UML is a big help as well.

This is a complex, in-depth book, and it would be easy to get lost in the conceptual discussions and sample project. But between the clearly marked process diagram used consistently throughout, goals and checkpoints that start and finish each chapter, and constant relating of new concepts to those covered before, the author helps the reader stay clearly focused on the big picture and which part is being discussed.

Rational Rose is used as the sample design tool throughout the book. This might annoy readers using other tools, but the Rose-specific discussions were light enough that you should be able learn the technique well enough to apply it with other tools. The author sometimes gets bogged down in a few too many step by step listings to accomplish a given task in VB. Anyone picking up this book had better have a pretty good feel for VB already, or will become quickly lost.

The one thing that mildly annoyed me is that the author introduces yet another design process methodology, his Synergy system. Synergy seems reasonable enough-I haven't yet given it a work out-but I'm not sure that the world needs another methodology.

I'm not sure that you could sit down, read this book, and emerge an effective design engineer for enterprise applications using VB. But if you have a good feel for what it takes to build robust applications, have some familiarity with software engineering concepts, and have struggled applying them to VB projects, the book provides an excellent bridge between VB and UML. Certainly the best I've seen so far, and applying the techniques are sure to improve your development projects.

The other major problem with the book is that the middle part reads like a user's guide for Rational Rose, a tool most programmers cannot afford. Visio would have been far more relevant, although if it could have been made tool-agnostic with regards to modelling applications, that would have been even better.

Overall, I found the book to be worth the money it cost, since the first part of the book really helped me understand how UML works, the time I wasted with the last part really wasn't worth it. Due yourself a favor, if you are a VB programmer who wants to learn UML - buy the book, and rip out everything from around the middle of the book onward.

There is a problem with Paul's approach. Because of the amount of detail, I found it easy to get lost. What issues are balanced in ending up with Paul's choices? Paul tries to tell me, but the issues are so closely tied to the Remulak Productions example of a musical instrument company that extraction of the idea from this particular example can be a headache that takes you back and forth through a lot of code and a lot of chapters. In the end, you will know far more than you ever wanted about Remulak Productions.

I find the issues and the art much more lucidly presented in Ivar Jacobson's "Object-oriented Software Engineering".

Bottom Line: If you want to know semantics: Quatrani, if you want to know management: Cantor, if you want a lot of detail, particularly how code is generated: Reed, if you want perspective: Jacobson.

Similar Products