72 •  Design                                                                                                                                                                                     Design  •  73
    Partial Contents                         What Every Programmer Should Know . . .                                   ORIGINAL EDITION
    Chapter 1: What Does It Mean to         “Beautifully written introduction to the fundamental
        Be Object-Oriented, Anyway?         ideas, notation, terminology, criteria, and principles of                                  What Every
        1.1 Encapsulation                   object-oriented design.  Written for every programmer
        1.2 Information/Implementa-         and, indeed, a must-read for every programmer                                           Programmer
           tion Hiding                      involved with object-oriented programming.  A classic
                                            programmer’s text, delightfully brimming with clarity
        1.3 State Retention                 and elegance.”                                                                     Should Know
        1.4 Object Identity                              —Carlene Char, Computer Book Review
        1.5 Messages                                                                                                          About Object-
        1.6 Classes                         “Regardless of your level of expertise, the principles
        1.7 Inheritance                     will undoubtedly spark more than one discovery.                           Oriented Design
        1.8 Polymorphism                    They are Page-Jones’s lasting contribution to our col-
        1.9 Genericity                      lective understanding of object orientation and soft-
                                            ware development in general.                                                                        by Meilir Page-Jones
    Chapter 2: Object-Orientation—              “. . . surprisingly simple, elegant, and revealing . . .                             foreword by Larry L. Constantine               ISBN: 0-932633-31-5    
        Who Ordered That?                   Rest assured that the book’s explanations will make                                                                                     ©1995    392 pages    hardcover    
                                            your job as a designer and programmer easier and                                                                                        $50.95 (incl. $6.00 for UPS in US)
    Chapter 3: The Basic Notation for       more satisfying. 
        Classes and Methods                     “. . . fresh breeze across the object-oriented land-                                       Winner of a Software Development
    Chapter 4: Inheritance and Aggre-       scape.”                                                                                                   Productivity Award
        gation Diagrams                        —Andrew J. Wozniewicz, Windows Tech Journal 
    Chapter 5: The Object-Communica-        “. . . vintage Page-Jones . . . Meilir is a gifted teacher.                        ith exceptional clarity, Page-                he chief concern of the text is
        tion Diagram                        . . . a relentlessly pragmatic focus based on real-world                    WJones teaches the fundamentals                  Tdesign—not notation.  “Some pro-
    Chapter 6: State-Transition Diagrams    experience . . . compact examples to guide the devel-                       of object-oriented design in a lan-              grammers don’t think they’re doing
                                            oper, whether novice or old hand, toward better                             guage-independent way.  Tech-                    design when they program,” the
    Chapter 7: Additional OODN Diagrams     object-oriented software solutions . . .                                    niques for designing and building                author comments, “but whenever
                                                “. . . Who could ask for more?”                                         with objects are illustrated with                you write code, you’re always doing
    Chapter 8: Encapsulation and Con-                    —Larry L. Constantine, from the foreword                       abundant examples, elaborated with               design. . . .”
        nascence                                                                                                        do’s and don’ts discussions, and                   f you haven’t joined the UML
    Chapter 9: Domains, Encumbrance,        “Some programmers don’t think they’re doing design                          reinforced with meaningful exercises             Ibandwagon—or if you’re ready to
        and Cohesion                        when they program, but whenever you write code,                             and answers.                                     jump off!—explore this experienced
                                            you’re always doing design, either explicitly or implic-                         evised for UML in a second edi-             teacher’s lessons on object-oriented
    Chapter 10: Properties of Classes       itly.  One of the aims of this book is to make program-                     Rtion—entitled Fundamentals of                   design with this highly acclaimed,
        and Subclasses                      mers explicitly aware of the design patterns that                           Object-Oriented Design in UML—this               readable text.
    Chapter 11: The Perils of Inheri-       they’re creating in their code.”                                            award-winning first edition remains                   “illustrates exactly what the criteria are
        tance and Polymorphism                           —Meilir Page-Jones, DHQ,Vol. V, No. 2                          one of the most understandable                        for good objects.  It also reveals that the
                                                                                                                        books on O.O. design.                                criteria are much more relevant than the
    Chapter 12: Class Interfaces            About the Author                                                                rogrammers, designers, and                           coding language, diagramming tech-
    Appendix A: Checklist for an Object-                                                                                Pmanagers who want to learn                           niques, or object methodology for deter-
        Oriented Design Walkthrough                                   eilir Page-Jones is president                     object-oriented design without                        mining system goodness and object suc-
                                                                Mand senior consulting method-                          learning UML will especially find                      cess.  . . . a book for developers who are
    Appendix B: The Object-Oriented                             ologist at Wayland Systems, and has                     this book useful.  The diagrams are                  sure they have already figured out every-
        Design Owner's Manual                                   extensive experience in training, con-                  presented in the author’s OODN                          thing there is to know about objects.”
                                                                sulting, and hands-on system devel-                     notation and the brief code examples                       Roland Racko, Software Development
    Appendix C: Blitz Guide to Object-                          opment.  He is also the author of                       are given in an easily recognizable                     —
        Oriented Terminology                                    Practical Project Management, pub-                      hybrid of C++, Smalltalk, and Eiffel.  
                                                                lished by Dorset House. Visit                                                                                    Read more about this book at 
                                                                www.waysys.com.                                                                             http://www.dorsethouse.com/books/weps.html
           DORSET HOUSE PUBLISHING   353 WEST 12TH STREET   NEW YORK, NEW YORK 10014  USA                                            Order Today! •  (800) 342-6657  •  (212) 620-4053  •  fax (212) 727-1044
                                 info@dorsethouse.com  •  www.dorsethouse.com                                                Phone, fax, or mail with credit card information, check, or money order.   VISA  MC  AMEX