Customer Reviews

Systems Analysis and Design with UML Version 2.0: An Object-Oriented Approach

5 star:		(5)
4 star:		(3)
3 star:		(1)
2 star:		(5)
1 star:		(2)

 

 

I have looked at over twenty books on UML and its updates over the past few years, and this book is a gem.

It is concise, and provides a clear picture of the entire systems design process

It shows how UML 2.0 can be used to support system requirements capture, specification, analysis, and design.

It clearly says what is important and what is not, and what is not covered in the book.

Very pleasing to look at visually, with nice pictures and colors, and very good use of footnotes.

I would recommend this highly to all university faculty considering creating or teaching a course in system design using UML. Excellent job by the authors in exceeding the goals and expectations set by this book.

The above views are my personal views, and don't reflect those of any other institution.

I am using parts of it at a graduate course I teach at Georgia Tech.

The book offers a very pragmatic approach to the subject of system analysis and design. It also has the advantage of not being dispersive, so the reader does never loose the focus. Repetition occurs only occasionally, for concepts that may be more hostile to digest.

The only thing that I reckon is missing is a support with some templates that is possible to use (e.g. a CD-ROM with examples of analysis and design).

Overall, I would say is a very good deal! Definitely worth having it!

After reading a couple of 'classic' system analysis texts I felt I needed to read about system analysis and UML. This title had some good reviews so I purchased a copy.

This book did cover both system analysis and UML, but I felt that it did not cover either well. I had a hard time engaging with the content and linking it with my existing knowledge of UML and systems analysis.

If you are interested in UML and systems analysis I would recommend reading "Modern Structured Analysis" (Yourdon Press Computing Series) by Edward Yourdon, and finding a good UML 2 text (I'm lookging for one now).

For the price, I was expecting a much better book.

The UML writing style of this book is very easy to follow, and a great way to gradually introduce the whole concept of object-oriented analysis and design methodologies to the readers, especially the beginners. The authors did a great job illustrating the entire system development life cycle with a coherent and realistic example using the latest UML notations, practical methodologies, and various analytical artifacts. The only criticism I have is that sometimes the description of a particular topic spans over multiple pages without sub-leveling or sub-topics or highlights, making it very difficult for user to go back and perhaps mine certain important concepts embedded in the discussion. Perhaps more generalization relationship and diagrams can be helpful. Overall, it is a very good source of reference for object-oriented design in layman's term. I will strongly recommend it to my colleagues.

This might sound petty, but I found the authors' frequent, and usually incorrect, use of "as such" incredibly grating:

----
p. 243-4:
However, at this point in the representation of a system, we are still trying to completely understand the problem. As such, [as what?] this process of creating instance-specific sequence diagrams for each scenario instead of creating a single generic sequence diagram for the entire use case will enable the developers to attain a more complete understanding of the problem being addressed. Furthermore, each instance-specific sequence diagram is fairly simple to interpret, whereas a generic sequence diagram can be very complex. As such, [again, huh?] the testing of a specific use case is accomplished in a much easier manner by validating and verifying the completeness of the set of instance-specific sequence diagrams instead of trying to work through a single complex generic sequence diagram.
----

I am a student who was forced to wince my way through this text for a course. AS SUCH, [i.e. as a student who was forced to wince her way through this text for a course], I would encourage my prof to select a different book next year.

If you need to learn UML this is a good place to start. Its easy to read and well written and most improtantly pretty comprehensive of an introduction. It is however an introduction, you will need get another book to take it to the next level of doing it in the real world.

The organization is bad, really bad. The structure of the chapters is confusing, and I really have no idea who told my professor to get this book. It ocvers the material, but the way they present it is horrific!

This book is about UML. Since you are considering purchasing this book I assume that you are somewhat computer savvy. If your professor is not going to be using the questions from the text book (mine did not) then you can get by without it and use free internet resources. I purchased a few iPhone UML apps because this was such a boring textbook to read... not that any textbook is fun to read but this was dreadfully boring.

The examples in the book where not typical business situations that you will ever be in.

This product came well packaged and very timely, Great value compared to University Book Stores. Solid buy with no complaints or criticisms.

The book is serivicable...professor loved certain sections but hated others. There is no perfect textbook on this topic.