What Every Programmer Should Know about Object-oriented Design

What Every Programmer Should Know about Object-oriented Design

by Meilir Page-Jones

370 pages· 1995· ISBN 9780932633316
About
Introduction: What does it mean to be object-oriented, anyway? Object-orientation - Who ordered that? Object-oriented design notation. The basic notation for classes em methods. Inheritance and aggregation diagrams. The object-communication diagram. State-transition diagrams. Additional OODN diagrams. The principles of object-oriented design: Encapsulation and connascence. Domains, encumbrance, and cohesion. Properties of classes and subclasses. The perils of inheritance and polymorphism. Class interfaces. Appendix A: Checklist for an object-oriented design walkthrough. Appendix B: The Object-oriented design owner's manual. Appendix C: Blitz guide to object-oriented terminology.

Discuss What Every Programmer Should Know about Object-oriented Design with other readers

Join or start a book club for What Every Programmer Should Know about Object-oriented Design on Readfeed. Live chat, shared reading progress, and AI discussion questions — free to get started.

Frequently asked questions

How do I join a book club for What Every Programmer Should Know about Object-oriented Design?

Sign up free on Readfeed, then browse public clubs or start your own club with What Every Programmer Should Know about Object-oriented Design as the current read. Invite friends with a share link and discuss together with live chat and AI discussion questions.

Can I discuss What Every Programmer Should Know about Object-oriented Design with other readers online?

Yes. Readfeed book clubs let you chat live, share progress, and join discussions about What Every Programmer Should Know about Object-oriented Design with readers worldwide — whether your club is virtual, in-person, or hybrid.

Is Readfeed free?

Yes. Creating an account and joining book clubs is free. Sign up to find readers who love the same books and start discussing today.