What every programmer should know about object-oriented design
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
7 pages matching Larry Constantine in this book
Results 1-3 of 7
What people are saying - Write a review
Review: What Every Programmer Should Know about Object-Oriented DesignUser Review - Ivan Soto - Goodreads
If you want an academic understanding of object-oriented design, this book will give it to you. For in-depth understanding of object oriented design you still have to start fully mastering the object ... Read full review
LibraryThing ReviewUser Review - LibraryThing
I love this book! The idea of connascence reminds me of the notion of dependencies that Robert C Martin talks about.
ObjectOrientationWho Ordered That?
ObjectOriented Design Notation
13 other sections not shown