Object-Oriented Thought Process, The (2nd Edition) [Paperback]

Matt Weisfeld (Author)

Book Description

ISBN-10: 0672326116 | ISBN-13: 978-0672326110 | Publication Date: December 22, 2003 | Edition: 2

The Object-Oriented Thought Process, Second Edition will lay the foundation in object-oriented concepts and then explain how various object technologies are used. Author Matt Weisfeld introduces object-oriented concepts, then covers abstraction, public and private classes, reusing code, and devloping frameworks. Later chapters cover building objects that work with XML, databases, and distributed systems (including EJBs, .NET, Web Services and more).Throughout the book Matt uses UML, the standard language for modeling objects, to provide illustration and examples of each concept.

Editorial Reviews

From the Back Cover

The Object-Oriented Thought Process is a concise and readable primer. Matt Weisfeld's years of programming, teaching, and writing have given him a flair for presenting highly technical topics in a clear and interesting manner. He is able to blend abstract concepts with ingenious examples and clear illustrations to quickly teach powerful OOP techniques. The code examples are written in Java and UML but are designed in such a way that a reader with no previous experience will still understand them. The Object-Oriented Thought Process is a clear and accessible alternative to the often dry and overly dense books available on the market today. --This text refers to an alternate Paperback edition.

About the Author

Matt Weisfeld is an assistant professor at Cuyahoga Community College (Tri-C) in Cleveland, Ohio. Matt is a member of the information technology faculty, teaching programming languages such as C++, Java, and C# .NET. Prior to joining Tri-C, Matt spent 20 years in the information technology industry gaining experience in software development, project management, business development, corporate training, and part-time teaching. Matt holds an M.S. in computer science and an MBA in project management. Besides the first edition of The Object-Oriented Thought Process, Matt has published two other computer books, and more than a dozen articles in magazines and journals such as Dr. Dobb's Journal, The C/C++ Users Journal, Software Development Magazine, Java Report, and the international journal Project Management. Matt has presented at conferences throughout the United States and Canada.

See all Editorial Reviews

Product Details

• Paperback: 288 pages
• Publisher: Sams; 2 edition (December 22, 2003)
• Language: English
• ISBN-10: 0672326116
• ISBN-13: 978-0672326110
• Product Dimensions: 8.9 x 6.8 x 0.7 inches
• Shipping Weight: 14.4 ounces
• Average Customer Review: 4.1 out of 5 stars  See all reviews (56 customer reviews)
• Amazon Best Sellers Rank: #1,057,057 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

56 of 58 people found the following review helpful:

4.0 out of 5 stars Good introduction for OO newcomers, May 22, 2000

By 

A.M. - See all my reviews

This review is from: The Object-Oriented Thought Process (Paperback)

A good introduction to fundamental concepts of OO. At around 200 pages, it is concise and can be read relatively quickly (compared to the 2,000 page monster-books that are common-place).

Introduces ideas of classes, objects, messages, methods, attributes, inheritance, encapsulation, polymorphism, public interfaces/private implementations, abstract methods/classes, aggregation/association, constructors/destructors, exceptions, overloading, accessor methods, and Interfaces (amongst others).

Moderately experienced OO developers (i.e. you understand the OO terms given above) will probably prefer a more advanced book than this one - this is an introductory text aimed at people just getting started with OO.

Also provides some (basic) guidelines on class design and software development, giving a worked example to illustrate. OO Concepts are illustrated using Java code samples, basic UML, and a quick introduction to CRC cards (this is NOT a Java/UML/CRC tutorial though - rather it is an OO CONCEPTS tutorial).

I found the numerous references to specific pages in other OO books rather irksome, but others may find these useful pointers to more advanced material. I would have preferred a single "Further Reading" appendix instead.

Overall, a good introduction to fundamental OO concepts that all OO developers must know.

35 of 35 people found the following review helpful:

5.0 out of 5 stars Thank God, Finally I Get OOP, May 19, 2003

By A Customer

This review is from: The Object-Oriented Thought Process (Paperback)

I can program in C, Assembler, Motorola 68HC11 assembly language and have never been able to shift my thinking from procedural to object oriented programming. I've bought 8 books on Java and C++, trying to understand OOP (Object Oriented Programming) and never got the hang of it. I also couldn't get a straight answer from any supposed C++/Java programmers as to what OOP was. Finally, after reading this book it's cleard up my issues with OOP. With my other books by Deitel, Schlidt, and SAMS, I've lost interest in trying to figure out their meaning of OOP. This book I've shifted my thought process in two hours. This is by far the most useful book I've ever read on any aspect of programming. I reccomend this book to anyone starting out programming or trying to shift from procedural to an OOP language. I wouldn't worry that it has Java examples if you're trying to learn C++, he teachs a thought process and different view point. All I can say is "Thank God this finally makes sense to me!"

37 of 39 people found the following review helpful:

5.0 out of 5 stars Undoes bad habits, September 11, 2001

By 

Linda Zarate "IT Ops Consultant" (Azusa, CA United States) - See all my reviews

This review is from: The Object-Oriented Thought Process (Paperback)

After reading this book I realized why so many development projects that use object-oriented tools and techniques fail - they are staffed by developers who think in the traditional terms of procedures and functions. In retrospect it dawned on me that there is a high probability that developers who started out with procedural languages view objects as functions.

This book provides a compass that will point developers in the right direction by breaking mental paradigms. It does so by getting them to think in terms of states instead of functions, and objects as components, independent of the application being developed, with well-defined interfaces and properties that can be used to create services.

I personally learned a lot about object-orientation, which I can apply to analysis. This book is a quick and easy read, and packs a lot of information and concepts between its covers. I highly recommend it and give it five stars for clarity and content.