The Object-Oriented Thought Process (Developer's Library), 5th Edition

Object-oriented programming (OOP) is the foundation of modern programming languages, including C++, Java, C#, Visual Basic .NET, Ruby, Objective-C, and Swift. Objects also form the basis for many web technologies such as JavaScript, Python, and PHP. It is of vital importance to learn the fundamental concepts of object orientation before starting to use object-oriented development environments. OOP promotes good design practices, code portability, and reuse–but it requires a shift in thinking to be fully understood. Programmers new to OOP should resist the temptation to jump directly into a particular programming language or a modeling language, and instead first take the time to learn what author Matt Weisfeld calls “the object-oriented thought process.” Written by a developer for developers who want to improve their understanding of object-oriented technologies, The Object-Oriented Thought Process provides a solutions-oriented approach to object-oriented programming. Readers will learn to understand the proper uses of inheritance and composition, the difference between aggregation and association, and the important distinction between interfaces and implementations. While programming technologies have been changing and evolving over the years, object-oriented concepts remain a constant–no matter what the platform. This revised edition focuses on the OOP technologies that have survived the past 20 years and remain at its core, with new and expanded coverage of design patterns, avoiding dependencies, and the SOLID principles to help make software designs understandable, flexible, and maintainable. Cover Half Title Title Page Copyright Page Dedication Contents at a Glance Table of Contents Introduction This Book’s Scope What’s New in the Fifth Edition The Intended Audience The Book’s Approach Source Code Used in This Book 1 Introduction to Object-Oriented Concepts The Fundamental Concepts Objects and Legacy Systems Procedural Versus OO Programming Moving from Procedural to Object-Oriented Development Procedural Programming OO Programming What Exactly Is an Object? Object Data Object Behaviors What Exactly Is a Class? Creating Objects Attributes Methods Messages Using Class Diagrams as a Visual Tool Encapsulation and Data Hiding Interfaces Implementations A Real-World Example of the Interface/Implementation Paradigm A Model of the Interface/Implementation Paradigm Inheritance Superclasses and Subclasses Abstraction Is-a Relationships Polymorphism Composition Abstraction Has-a Relationships Conclusion 2 How to Think in Terms of Objects Knowing the Difference Between the Interface and the Implementation The Interface The Implementation An Interface/Implementation Example Using Abstract Thinking When Designing Interfaces Providing the Absolute Minimal User Interface Possible Determining the Users Object Behavior Environmental Constraints Identifying the Public Interfaces Identifying the Implementation Conclusion References 3 More Object-Oriented Concepts Constructors When Is a Constructor Called? What’s Inside a Constructor? The Default Constructor Using Multiple Constructors The Design of Constructors Error Handling Ignoring the Problem Checking for Problems and Aborting the Application Checking for Problems and Attempting to Recover Throwing an Exception The Importance of Scope Local Attributes Object Attributes Class Attributes Operator Overloading Multiple Inheritance Object Operations Conclusion References 4 The Anatomy of a Class The Name of the Class Comments Attributes Constructors Accessors Public Interface Methods Private Implementation Methods Conclusion References 5 Class Design Guidelines Modeling Real-World Systems Identifying the Public Interfaces The Minimum Public Interface Hiding the Implementation Designing Robust Constructors (and Perhaps Destructors) Designing Error Handling into a Class Documenting a Class and Using Comments Building Objects with the Intent to Cooperate Designing with Reuse in Mind Designing with Extensibility in Mind Making Names Descriptive Abstracting Out Nonportable Code Providing a Way to Copy and Compare Objects Keeping the Scope as Small as Possible Designing with Maintainability in Mind Using Iteration in the Development Process Testing the Interface Using Object Persistence Serializing and Marshaling Objects Conclusion References 6 Designing with Objects Design Guidelines Performing the Proper Analysis Developing a Statement of Work Gathering the Requirements Developing a System Prototype Identifying the Classes Determining the Responsibilities of Each Class Determining How the Classes Collaborate with Each Other Creating a Class Model to Describe the System Prototyping the User Interface in Code Object Wrappers Structured Code Wrapping Structured Code Wrapping Nonportable Code Wrapping Existing Classes Conclusion References 7 Mastering Inheritance and Composition Reusing Objects Inheritance Generalization and Specialization Design Decisions Composition Representing Composition with UML Why Encapsulation Is Fundamental to OO How Inheritance Weakens Encapsulation A Detailed Example of Polymorphism Object Responsibility Abstract Classes, Virtual Methods, and Protocols Conclusion References 8 Frameworks and Reuse: Designing with Interfaces and Abstract Classes Code: To Reuse or Not to Reuse? What Is a Framework? What Is a Contract? Abstract Classes Interfaces Tying It All Together The Compiler Proof Making a Contract System Plug-in Points An E-Business Example An E-Business Problem The Non-Reuse Approach An E-Business Solution The UML Object Model Conclusion References 9 Building Objects and Object-Oriented Design Composition Relationships Building in Phases Types of Composition Aggregations Associations Using Associations and Aggregations Together Avoiding Dependencies Cardinality Multiple Object Associations Optional Associations Tying It All Together: An Example Conclusion References 10 Design Patterns Why Design Patterns? Smalltalk’s Model/View/Controller Types of Design Patterns Creational Patterns Structural Patterns Behavioral Patterns Antipatterns Conclusion References 11 Avoiding Dependencies and Highly Coupled Classes Composition versus Inheritance and Dependency Injection 1) Inheritance 2) Composition Dependency Injection Conclusion References 12 The SOLID Principles of Object-Oriented Design The SOLID Principles of Object-Oriented Design 1) SRP: Single Responsibility Principle 2) OCP: Open/Close Principle 3) LSP: Liskov Substitution Principle 4) IPS: Interface Segregation Principle 5) DIP: Dependency Inversion Principle Conclusion References Index A B C D E F G H I J K L M N O P Q-R S T U V W-X-Y-Z While programming technologies have been changing and evolving over the years, object-oriented concepts remain a constant--no matter what the platform. Written by a developer for developers who want to make the leap to object-oriented technologies, this book provides a solutions-oriented approach to object-oriented programming. Readers will learn to understand the proper uses of inheritance and composition, the difference between aggregation and association, and the important distinction between interfaces and implementations. This revised edition focuses on interoperability across programming technologies, whether you are using objects in traditional application design, in XML-based data transactions, in Web page development, in mobile apps, or in any modern programming environment.--From publisher description A concise and readable primer, The Object-Oriented Thought Process lays the foundation in object-oriented concepts and then explains how various object technologies are used. Early chapters introduce object-oriented concepts, then cover abstraction, public and private classes, reusing code, and developing frameworks. Later chapters cover building objects that work with databases and distributed systems. Written by a developer for developers who want to make the leap to object-oriented technologies, The Object-Oriented Thought Process provides a solutions-oriented approach to object-oriented programming. Readers will learn to understand the proper uses of inheritance and composition, the difference between aggregation and association, and the important distinction between interfaces and implementations. 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.