Object-Oriented Analysis and Design [Paperback]

Andrew Haigh (Author)

Book Description

Publication Date: July 30, 2001 | Series: Application Development

This volume provides an exploration of the four stages of software development: analysis, design, implementation, and troubleshooting. Appropriate for programmers of all levels, it contains both working examples and design concepts using non-technical language.

Editorial Reviews

From the Back Cover

"Comprehensive introduction to OOAD principles using UML v1.4, along with tried and trusted techniques for building real-world applications." --Dilhar Desilva, Member of the UML Core Team, member of the UML v1.1 Semantics Task Force, and member of the UML RTF

Develop essential analysis and design skills using UML v1.4

Uncover effective methods of designing fully functional object-oriented software. From analyzing needs to designing applications to implementing the final product, Object Oriented Analysis and Design contains the techniques used by professionals worldwide. Inside, you'll find comprehensive instructions to UML v1.4 notation for analyzing design strength. Also included are strategies for debugging software using three major debugging tools (DBX, GDB and JDB) as well as for porting to other operating systems, languages, and platforms. In addition, you'll get utilities for maintaining source code and methods of recording error reports, enhancement requests, and regression tests. Loaded with examples, this comprehensive book provides the expertise needed to oversee all aspects of successful design.

• Learn the fundamentals of object-orientation, including identifying objects, their classes, attributes, and methods
• Explore information-gathering techniques to determine high level system requirements
• Learn how to use analysis documents defined by the UML v1.4 standard
• Master advanced design principles and understand what makes for good design
• Identify and avoid inappropriate design schemes
• Implement advanced design constructs, such as API and threading
• Develop an efficient testing system
• Understand the differences between stress and scalability testing
• Follow examples of debugging using three widely used tools (DBX, GDB, and JDB)
• Add valuable flexibility needed when porting across operating systems, platforms, and languages

About the Author

Andrew Haigh (East Setauket, NY) is the Development Manager for Computer Associates' object-oriented database Jasmine. He is responsible for teaching object-oriented programming to engineers at Computer Associates.

Product Details

• Paperback: 454 pages
• Publisher: McGraw-Hill/Osborne Media (July 30, 2001)
• Language: English
• ISBN-10: 0072133147
• ISBN-13: 978-0072133141
• Product Dimensions: 9.2 x 7.5 x 1.2 inches
• Shipping Weight: 2.2 pounds
• Average Customer Review: 2.4 out of 5 stars  See all reviews (7 customer reviews)
• Amazon Best Sellers Rank: #3,950,820 in Books (See Top 100 in Books)

More About the Author

Discover books, learn about writers, read author blogs, and more.

Customer Reviews

Most Helpful Customer Reviews

9 of 11 people found the following review helpful:

1.0 out of 5 stars Horribly Organized, April 15, 2002

By A Customer

This review is from: Object-Oriented Analysis and Design (Paperback)

I ordered this book in hopes of gaining an understanding of the "analysis documents defined by the UML 1.4 standard." However, because this book is so poorly organized and written, I had no confidence after a couple of chapters that I would gain anything from it.

As a person in the technical training realm, this book has little in the way of educational value. Why? Well, its examples are not practical or "usable" in any sense. They are poorly explained and and often do not provide enough information to relate them to the discussion leading up to the example. For example, what is the <<include>> tag in the use cases in the first case study? Good luck finding it. I had hoped the case-study at the end of the book would help. However, the case-study jumps right into use cases without a decent explanation of the problem. Another gripe, which is all too common with books written by technical, but non educational, people is that topics will be introduced with some sort of a list (like the project requirements in the first case study) and then the following sub-headings that are meant to drill down into each item in the list don't match up with the items in the list. Overall, if you are looking for a book with good practical UML/OOAD information, look elsewhere.

3 of 4 people found the following review helpful:

3.0 out of 5 stars Strayed from OOAD, December 11, 2003

By A Customer

This review is from: Object-Oriented Analysis and Design (Paperback)

Previous reviewers must have failed Mr Haigh's course, because it is tough. Yes the book strays from OOAD. However in the context of his course Software Engineering, it fits. The book covers topics never taught to us in other courses, but it has become an invaluable reference since graduating. I believe that since my graduating Mr Haigh's course has become compulsory, which I believe says it all.

2 of 3 people found the following review helpful:

1.0 out of 5 stars Perhaps the worst of its kind, October 27, 2003

By A Customer

This review is from: Object-Oriented Analysis and Design (Paperback)

With such great people writing books in this topic, such as Craig Larman, Martin Fowler, Ward Cunningham, Robert C. Martin and Alistair Cockburn, why would anyone buy this book? Students who are forced to take Mr. Haigh class, that's who. Even they report that no one actually reads it (Mr Haigh teaches a Software Engineering course, which is not as bad as his book, at CUNY). "I use it to hold my monitor up and it only cost me 50 cents" one student told me.

Here are some reasons why you should stay away from this horrendous book:

- Every book out there on OOAD is better than this one. (see Craig Larman's book)
- There are just too many errors.
- Disorganized
- Nothing is explained well enough to make good use to if
- It appears the author does not know much UML (He is a typical programmer but he is no engineer)
- Many of the UML examples are wrong. (perhaps he should read more on the subject)
- Irrelevant topics are discussed. (One chapter talks about how to use make, another on how to use a debugger, and another on porting C++ applications. Furthermore, none of these chapters are actually good. A book on OOAD I don't think so)
- Does not even touch the tip of the iceberg that is OOAD
- The case studies are pathetic.
- It is clear that Mr haigh is just an average programmer who borrowed a couple of notes from Cockburn, Gamma and others (It clearly shows) for his 2nd, 3rd, 4th, 5th chapter and in the other chapters he just put a couple of man pages, then came up with some awful examples, put all the material together and called it Object-Oriented Analysis and Design. (First chapters seem to be just notes stapled together from different sources)
- No patterns, principles, and not much OOAD. (some patterns are discussed but they are not mentioned as such. He mentions them more as, "hey here's a neat trick I read, use it at your own risk since I don't really understand it myself")
- The only people who gave this book more than a star was Mr. Haigh himself. He even used two accounts (the second was probably his wife's who edited the book I believe) in order to put up 2 reviews in his favor. He put 5 stars twice boosting his rating. Now there's a professional.

Reasons you should buy this book:

- Its only 50 cents, used that is. I wouldn't pay anything more than that for a new copy.
- You want to see an example of a really bad book.
That's it.