Search in Book Reviews

Until now that has been a tough one. Most of us lack the time to read weighty tomes on subjects that might be of interest, and we frequently lack the background to make sense of the standard works even if we are willing to put in time in study.

The purpose of this book is to address such readers. The author tries (but not always as successfully as he thinks) to make few assumptions about the background of the reader. I think you do need to have some understanding of programming fundamentals and at least an implicit understanding of object oriented design. The later does not need to be in depth but some is essential else you will continually be wondering what all this is for.

I think the ideal reader of this book is the person who has 'done a bit of programming' but does not program professionally (well, unfortunately many people who only do a 'bit' get paid for the results and think of themselves as professional programmers).

I found this to be an informative tidily written book. Those with less technical background will have to take their time gently digesting the information because there is a deceptively high density of information per page. The expert might not notice it, but those who the author describes on the back cover as non-technical professionals who need to understand software development activities in the workplace will find that the simple language and low word count per page hides a substantial demand on their attention and intellect.

Reading this book will not make you a competent user of UML, but it will help you understand what UML means and why good software developers use it.