Object-Oriented Methods: A Foundation, UML Edition (2nd Edition) (Hardcover)

~ James Martin (Author), James J. Odell (Author)

Editorial Reviews

Product Description

Make sense of object-oriented philosphy--and use it in both information systems development and business process reengineering. Completely revised and updated to comply with UML notation, this book gives techniques for serial, concurrent, and synchronized processing specification.

From the Publisher

This book presents those concepts and techniques that support almost any system development approach--whether it involves computers, people, or machines. It considers object structure, object behavior and more advanced concepts such as composition, structural constraints, rules, using rules and diagrams, meta-modeling, and power types. Shows how to represent OOA constructs--modeling object structure, modeling object behavior, modeling state transitions and event diagrams, scenarios. Outlines considerations for design, discusses object-oriented programming, and considers object-oriented design and "instant" CASE. --This text refers to an out of print or unavailable edition of this title.

See all Editorial Reviews

Product Details

• Hardcover: 408 pages
• Publisher: Prentice Hall PTR; 2nd edition (December 4, 1997)
• Language: English
• ISBN-10: 0139055975
• ISBN-13: 978-0139055973
• Product Dimensions: 9.6 x 7.2 x 0.8 inches
• Shipping Weight: 1.7 pounds
• Average Customer Review: 4.4 out of 5 stars  See all reviews (7 customer reviews)
• Amazon.com Sales Rank: #1,427,810 in Books (See Bestsellers in Books)

Customer Reviews

Most Helpful Customer Reviews

5 of 5 people found the following review helpful:

4.0 out of 5 stars Develops framework / terminology for OO analysis & design, April 22, 1999

By	Anurag Gupta "platform guru" (Bangalore, India) - See all my reviews (REAL NAME)

Has useful techniques for defining a problem domain unambigously. This helps ensure that teams working on the project share a common understanding of the problem analysis. Techniques help discussion of mapping conceptual model to physical design and evaluating tradeoffs. Techniques were used to develop effective communication mechanisms between database designers, application developers, and performance engineers.

4 of 5 people found the following review helpful:

5.0 out of 5 stars A Must Read, July 28, 2002

By	Tobias Hust "TobInMuc" (München) - See all my reviews (REAL NAME)

This review is from: Object-Oriented Methods: Pragmatic Considerations (Hardcover)

Martin and Odell - an experienced team demonstrates object oriented concepts to the theoretically educated audience.
Without the enlightning read of 'The OO Foundation' (Martin, Odell) the buyer might encounter difficulties to follow the discussions.
As the title clearly states, the authors discuss the applications, mostly pragmatic, of oo concepts and methods. This includes the realization of oo concepts in programming languages, their limitations, best practices.
The book is structured as a cook-book with powerfull how-tos not only for the application design but also for tasks of a software development process.
Please note that this book does not define any methods nor does it specify a software development process. It gives you a pragmatic view based on the rich experience of the authors - even today, six years after the book was first published.

A must read for every serious software developer.

3 of 4 people found the following review helpful:

5.0 out of 5 stars Excellent explanation and easy to read, December 16, 2001

By	Alexey - See all my reviews

I recommend it to people wishing to strongly become familiar with OO. In comparison with "UML Users Guide", "OO Analysis and Design with C++ examples", "Applying patterns with UML ", "UML Distilled" this book explains OO at the good fundamental level and explanation is very sequential. You will understand OO approach step by step. However, this book is not for novice. Some experience is necessary. If you want just to get few basic concepts and start programming, then this book is not for you too. System Analysts, Architects and Team Leaders must read it.