reviews
Feb 01, 2011
Right on the cover, Martin Fowler says Larman's book is his unreserved recommendation for learning OOD. Circa 2006-2010, that's an incredibly huge endorsement and says more than any amateur review could.
This is a big, college-text-style book. It's dense. I've read it twice through, and that was probably a mistake because it feels like I've failed to really soak it all up. Hence it's back on my to-read list. It might better use the book more as a school text - read a couple chapt More...
This is a big, college-text-style book. It's dense. I've read it twice through, and that was probably a mistake because it feels like I've failed to really soak it all up. Hence it's back on my to-read list. It might better use the book more as a school text - read a couple chapt More...
Mar 27, 2009
This was one of the trail-blazing books into both Design Patterns and agile methodologies. However, the art has passed this by and it is showing its age.
Dec 25, 2011
Read this book as part of an analysis and design class I recently took at the University of St. Thomas, Saint Paul. I have had the previous edition of this book, but it took taking a class to actually get me to read it entirely. Enough good things have already been said about this book by others, and I don't have a different opinion here either. What I especially enjoyed when reading this book is it's description and demonstration using effective UML diagrams of simple examples and case studie
More...
Oct 25, 2009
This is one of the two books I require in my Software Analysis & Design class. This is the standard text in OOA/OOD because of its breadth of coverage and its approach. It is written in a spiral style, meaning it doesn't dump everything on you at once, but addresses topics at increasingly deep levels as the text progresses. Two running examples help anchor the ideas. It is Java-based as well. It does cover a fair amount of iterative process material, which might be a benefit to some, but is
More...
Nov 24, 2007
It does say quite much about UML if you read through it all (I guess). But to just get the information you're interested in (which UML is much about for me; combine and use the parts that suit your current project), it's quite bad. Hard to use as a reference book. So I didn't like it. It does probably have most information you need though, just not for me.
Nov 21, 2007
One of those long ones you have to read from cover to cover. Almost impossible to use as a reference book; design patterns and UML information are spread all over the place. Good if you want to learn by following a couple of toy projects, almost useless otherwise.
Mar 08, 2008
This is a good read for introductory learning of OOA/D. Covers a lot of basic ground and takes an iterative approach to RUP. Is rather dry and hard to get through (be forewarned).
May 09, 2008
I have learned all about UML from this book. And I recomend it to all programmers. It's a perfect start in UML. It would be better to buy it and idolize)
Mar 08, 2010
This book taught me that I never want to work in a software development organization that relies upon Unified Modeling Language.
Feb 11, 2012
Feb 10, 2012
Feb 02, 2012
Feb 02, 2012
Feb 02, 2012
Feb 01, 2012
Jan 31, 2012
Jan 23, 2012
Jan 21, 2012
Jan 19, 2012
Jan 08, 2012
Jan 06, 2012
Jan 05, 2012
Jan 05, 2012
Jan 05, 2012
Jan 04, 2012
Dec 28, 2011
Dec 28, 2011
