What Every Programmer Should Know about Object-oriented Design

Front Cover
Dorset House Pub., Jan 1, 1995 - Computers - 370 pages
0 Reviews
Partial ContentsChapter 1: What Does It Mean to Be Object-Oriented, Anyway?1.1 Encapsulation1.2 Information/Implementation Hiding1.3 State Retention1.4 Object Identity1.5 Messages1.6 Classes1.7 Inheritance1.8 Polymorphism1.9 GenericityChapter 2: Object-Orientation--Who Ordered That?Chapter 3: The Basic Notation for Classes and MethodsChapter 4: Inheritance and Aggregation DiagramsChapter 5: The Object-Communication DiagramChapter 6: State-Transition DiagramsChapter 7: Additional OODN DiagramsChapter 8: Encapsulation and ConnascenceChapter 9: Domains, Encumbrance, and CohesionChapter 10: Properties of Classes and SubclassesChapter 11: The Perils of Inheritance and PolymorphismChapter 12: Class InterfacesAppendix A: Checklist for an Object-Oriented Design WalkthroughAppendix B: The Object-Oriented Design Owner's ManualAppendix C: Blitz Guide to Object-Oriented Terminology

From inside the book

What people are saying - Write a review

LibraryThing Review

User Review  - dallen - LibraryThing

I love this book! The idea of connascence reminds me of the notion of dependencies that Robert C Martin talks about. Read full review

Contents

Introduction
1
ObjectOrientationWho Ordered That?
51
ObjectOriented Design Notation
71
Copyright

13 other sections not shown

Common terms and phrases

Bibliographic information