Java Modeling in Color with UML: Enterprise Components and Process [With CDROM]

This is an excellent book. It is, however, terse and has taken me a long time to get to grips with its content and language. I have had to read several of the Coad books to 'get it' but it's finally coming together. I would recommend you read it in conjunction with (or maybe after reading) "Streamlined Object Modeling" by Jill Nicola (and would love to see her do a follow-up book). To those that say there is no Java in the title: look at the CD. To be honest I think all the Coad books are good (the "Java Design" book is really good too and was my first contact with Coad's books), some are dated but still stand up. They do take a lot of the guesswork out of modelling.

Though "Java" is in the title, this book is not limited to Java, and, indeed, there are no Java code examples. Usage of UML, however is extensive. The book presents an approach to generalizing business components (modelliing patterns - referred to as archetypes) that really helps one to understand the structure and interaction of business components. I use this book as a regular reference. It includes a near-complete business component model through 12 compound components.

Don't be fooled by the colors and informal communication style. It takes talent to deliver state of the art software development theory in such an easy to understand and practical way. Consider industry thinking on Business Object Component Architecture. Consider IBM's SanFrancisco project with 4 BOCs completed. This book gives us 12! (My copy accordingly has 12 colorful sticky tags.) If someone has seen a more intuitive, comprehesive set of components, please let me know. As Dragan's review says, these guys have done the "heavy lifting." Building on this book's BOCA even the poorest programmers will end with superior software.And anyone who doesn't sense the far reaching implications, as Booch implies, of the colors and the "domain neutral component" either doesn't have the ability to do abstract thinking or just isn't paying attention. I didn't believe it until I added color to my own UML diagram.

Probably one of the best books I've read since the 'Design Patterns'. The FDD design process is quite unique and solid. The book lacks cohesiveness at places, but makes up for it by providing good modelling examples. I would strongly recommend this book.

This book is strange in that I can understand the poor ratings it has got and the good ratings. It is like 3 books in one with the middle book being the meat of it. The first book is one chapter on the color and archetypes. This work is fascinating and takes modeling to a new level. Just being introduced to this idea is worthy of 5 stars. The last book is one chapter on process. The ideas presented here are also fascinating, but like the color chapter, it is one chapter only and requires a few reads for it all to sink in. The material and ideas presented are really deep, but are well worth the effort to understand and then learn. This really feels like breakthrough work. The middle chapters are numerous models for different domains using the color and archetypes from chapter one. This is like reference material.This book is at least 3 books in one. If you are a serious modeler or process person, you must have this book. If you are one of the many who just get by in computing, you'll not understand it and write a very negative review.