Top critical review
7 people found this helpful
Examples were rather weak and did not provide solutions
on 1 May 2011
There is one rather dense chapter (#2) perhaps worth reading explaining the nature of the object as used in the religion of OO programming. Although, it does not point out that this is not the only way to program and that often you should do things differently, for example EAV or functional programming. Then there are some really weak chapters giving an example of the use. At no point did it actually show you how using UML would explain and analyse a system in a better way than just going to build a system naively. The concept idea of the book is fine, but this is not a good rendition.
Why can't they get a good case study from a medium sized enterprise in a developed economy to show how some complex business model is systematically scoped, streamlined and improved inside a new business system? - Surely this is what most business analysts do.
UML is only going to be interesting on its own if you are autistic. You may get autistic programmers, but you are unlikely to get autistic business analysts. The cases and documents described are so facile, that frankly if I was sent this stuff by a business analyst I would wonder what he/she was being paid for. The most important part of business analysis is identifying change opportunities through improved system design that makes the money. The thing a business analyst should avoid is excessive verbage and obscure acronyms; this book is very jargon heavy and this stuff is not going to be very helpful in the real world.