Only 5 left in stock (more on the way).
Ships from and sold by Gift-wrap available.
Fundamentals of Object-Or... has been added to your Cart
+ CDN$ 6.49 shipping
Used: Good | Details
Sold by wobcanada
Condition: Used: Good
Comment: The book has been read but remains in clean condition. All pages are intact and the cover is intact. Some minor wear to the spine.
Have one to sell?
Flip to back Flip to front
Listen Playing... Paused   You're listening to a sample of the Audible audio edition.
Learn more
See all 2 images

Fundamentals of Object-Oriented Design in UML Paperback – Nov 3 1999

4.5 out of 5 stars 21 customer reviews

See all formats and editions Hide other formats and editions
Amazon Price
New from Used from
"Please retry"
CDN$ 50.66
CDN$ 44.16 CDN$ 3.27

Harry Potter and the Cursed Child
click to open popover

Special Offers and Product Promotions

  • You'll save an extra 5% on Books purchased from, now through July 29th. No code necessary, discount applied at checkout. Here's how (restrictions apply)

No Kindle device required. Download one of the Free Kindle apps to start reading Kindle books on your smartphone, tablet, and computer.
Getting the download link through email is temporarily not available. Please check back later.

  • Apple
  • Android
  • Windows Phone
  • Android

To get the free app, enter your mobile phone number.

Product Details

  • Paperback: 480 pages
  • Publisher: Addison-Wesley Professional; 1 edition (Nov. 3 1999)
  • Language: English
  • ISBN-10: 020169946X
  • ISBN-13: 978-0201699463
  • Product Dimensions: 18.5 x 2.8 x 23.1 cm
  • Shipping Weight: 839 g
  • Average Customer Review: 4.5 out of 5 stars 21 customer reviews
  • Amazon Bestsellers Rank: #640,317 in Books (See Top 100 in Books)
  •  Would you like to update product info, give feedback on images, or tell us about a lower price?

  • See Complete Table of Contents

Product Description

From the Inside Flap

"You say you want some evolution. Well, you know, I'm just doing what I can."
-- Charles Darwin, On the Origin of Species

People who reviewed this book in its draft form had several questions for me, questions that perhaps you share. Let me address some of them.

I'm a programmer. Why should I care about design?

Everyone who writes code also designs code -- either well or badly, either consciously or unconsciously. My goal in writing this book is to encourage people working in OO -- and their number increases annually - to create good object-oriented designs consciously and prior to coding. To this end, I introduce notation, principles and terminology that you and your colleagues can use to evaluate your designs and to discuss them meaningfully with one another.

I'm not yet an OO programmer. Will this book teach me an OO programming language?

No. Although I occasionally swoop down close to code, this isn't a book on object-oriented programming.

But if I'm learning an object-oriented language, will this book help?

Yes, it will. If you don't currently know an object-oriented programming language, you can begin your object-oriented knowledge with Chapter 1. Knowing the key concepts of object orientation will speed your learning an object-oriented language and, I hope, boost your morale as you move into unfamiliar territory. The later chapters of the book, on sound design, will also help you in getting your early programs to work successfully. On the other hand, if you're already an experienced object-oriented programmer, you can use Parts II and III of the book to enhance the design skills that are vital to your being a rounded, professional software designer or programmer.

Why aren't the code examples in this book in C++?

I've written the code in this book in a language of my own devising, which is a blend of four popular languages: C++, Eiffel, Java and Smalltalk. I did this because there are two kinds of programmers: those who are fluent in C++ and those who aren't. If you're a C++ aficionado, then you'll find the code a breeze to translate into C++. If you're not familiar with C++, then you might have found the language's arcane syntax getting in the way of the examples. I'd like you to feel welcome in this book whatever your programming language might be.

However, there is a fragment of Java in this book. I used Java because it's more accessible to a non-Java programmer than C++ is to a non-C++ programmer. Why isn't this book devoted to the design of windows, icons and menus? There are two reasons: First, I don't believe that object orientation is useful only for the design of graphical user interfaces. Second, there are many books on the market devoted solely to the topic of object-oriented window design. I want this book to cover topics that are not well covered by the other object-oriented books on the market. However, in Chapter 7 I offer some notation for window-navigation design.

Is this book about a methodology?

No. As you know, a development methodology contains much more than design. For example, there's requirements analysis, library management and so on. Also, a true methodology needs to explain how the various development activities fit together. A lot of stuff!

So, instead of turning out a book as diffuse as many other books on object orientation, I decided to focus on a single topic: object-oriented design.

You've said a lot about what this book isn't about. What is it about?

It's about the fundamental ideas, notation, terminology, criteria and principles of object-oriented software design. Object-oriented software is software that comprises objects and the classes to which they belong. An object is a component in which methods (which are like functions or procedures) are organized around a set of variables (which are like data). A class implements a type defining the group of objects that belong to that class. The above modest sentences hold some surprising implications for software designers and programmers, implications that arise from the design concepts of inheritance, polymorphism and second-order design. But, since you asked a specific question, let me give you a specific answer.

Part I of the book (Chapters 1-2) provides an introduction to object orientation. Chapter 1 summarizes the key concepts and demystifies "polymorphism," "genericity," and all the other OO jargon. Chapter 2 sets object orientation into the framework of previous developments in software. If you're already familiar with object orientation (perhaps by having programmed in an object-oriented language), then you can skip or skim Part I.

Part II (Chapters 3-7) covers the Unified Modeling Language (UML), which has become the de facto standard notation for depicting object-oriented design. In passing, Part II also illustrates many of the structures that you find in object-oriented systems. Chapter 3 introduces the UML for depicting classes, along with their attributes and operations. Chapter 4 covers UML for hierarchies of subclasses and superclasses, associations, and aggregate and composite objects. Chapter 5 sets out UML for messages (both sequential and asynchronous), while Chapter 6 covers UML for state diagrams. Chapter 7 reviews UML for system architecture and the windows that form a human interface.

Part III (Chapters 8-14) covers object-oriented design principles in some depth. Chapter 8 sets the scene with the crucial notions of connascence and level-2 encapsulation. Chapter 9 explores the various domains that "classes come from" and describes different degrees of class cohesion. Chapters 10 and 11 form the central pillar of Part III, using the concepts of state-space and behavior to assess when a class hierarchy is both sound and extendible. Chapter 12 offers some light relief, as it examines designs taken from real projects, including both the subtle and the absurd. (Chapter 12 is really about the dangers of abusing inheritance and polymorphism.) Chapter 13 looks at some ways of organizing operations within a given class, and explains design techniques such as mix-in classes and operation rings that will improve class reusability and maintainability. Chapter 14 rounds off the book by taking a stab at the old question: "What makes a good class?" In answering this question, Chapter 14 describes the various kinds of class interface, ranging from the horrid to the sublime. A class with an exemplary interface will be a worthy implementation of an abstract data-type. If the class also obeys the fundamental principles laid out in earlier chapters, then it will be as robust, reliable, extensible, reusable and maintainable as a class can ever be.

Chapter 15 traces the development of an object-oriented component for a business application. In following the component's construction, I recall some of the object-oriented principles of the previous chapters. Although I've added plenty of examples, diagrams and exercises to reinforce what I say in the main text, I must admit that the material in Part III gets tough at times. Nevertheless, I decided not to trivialize or dilute important issues. Some aspects of object-oriented design are difficult and to suggest otherwise would be to patronize you. Anyway, I know you can take it!

Does this book cover everything in object-oriented design?

I very much doubt it. Each day, I learn more about object orientation, and I'm sure you do too. Indeed, it would be a dull world if a single book could tell us everything about object-oriented design and leave us with nothing more to learn. And everything in this book may not be completely true! I certainly changed my mind about one or two things after I wrote my previous books, as I became older and wiser -- well older, anyway.

So, although I think that I've covered many important design principles in this book, if you're serious about object orientation you should continue to read as much as you can and always challenge what you read.

Do you offer courses on object-oriented design?

Yes, we offer several courses on object-oriented topics.

Bottom-line, as they say: Is this book for me?

What kind of question is that? You expect me to say "No!"? But seriously, folks, this book's for you if you are -- or are about to become -- a programmer, designer, systems engineer or technical manager on a project using object-oriented techniques. Even if you're a beginner to object orientation, you can glean a lot from this book by reading Part I, practicing some object-oriented programming and then returning to Parts II and III.

You should also read this book if you're a university student or professional programmer who has mastered the techniques of standard procedural programming and is looking for wider horizons. Much of the book's material is suitable for a final-year computer-science or software-engineering course in object orientation.

But, whatever your role in life, I hope that you enjoy this book and find it useful. Good luck!

Meilir Page-Jones
Bellevue, Washington
July 1999


From the Back Cover

Object technology is increasingly recognized as a valuable tool in application development, but what is not yet recognized is the importance of design in the construction of robust and adaptable object-oriented (OO) applications. With the recent introduction and widespread adoption of the Unified Modeling Language (UML), programmers are now equipped with a powerful tool for expressing software designs. Fundamentals of Object-Oriented Design in UML shows aspiring and experienced programmers alike how to apply design concepts, the UML, and the best practices in OO development to improve both their code and their success rates with object-based projects.

In the first two chapters, best-selling author Meilir Page-Jones introduces novices to key concepts and terminology, demystifying the jargon, and providing a context in which to view object orientation. Part II is a practical and well-illustrated guide to UML notation and to building the most useful UML diagrams. Part III grapples with advanced topics in the testing and improvement of design quality, including connascence, level-2 encapsulation, and the use of state-space and behavior to assess class hierarchies. These design principles are explained and demonstrated without reference to any one design methodology so that they are easily accessible and applicable in a variety of contexts. Programmers and designers learn how to assess and enhance their work as the author walks them through the evaluation of designs taken from actual projects and the realistic example that ends the book.

Readers will come away with a better understanding of object-oriented concepts and of how to design and develop the high-quality software their clients need.


See all Product Description

Customer Reviews

4.5 out of 5 stars
Share your thoughts with other customers

Top Customer Reviews

Format: Paperback
After going through a lot of books on subjects, this is one I like to return to. It is excellent book on Object Orientation. Books has a load of fun examples that are as paractical as can be in a book. It also has examples of a bad design, errors etc. The UML part is good, but what makes this book different is OO part, I wish that part was longer. You will find out why coupling is bad, why classes should belong to single domain, how to compare different designs, what are the most common errors in inheritance... Highly recomended!
One person found this helpful. Was this review helpful to you? Yes No Sending feedback...
Thank you for your feedback.
Sorry, we failed to record your vote. Please try again.
Report abuse
Format: Paperback
The author uses his own dialect of UML in too many places, Skips Use-Cases all together. The examples are too simplified. It is not fundamental OO because he doesn't define OO terminology as it is in the standards. He gives his oppinion on everything and this colors his explanations and examples.
If you are looking for a beginners UML or OO forget about this book. If you like to read another angle on some parts of the OO or some UML diagrams then this is your book.
One person found this helpful. Was this review helpful to you? Yes No Sending feedback...
Thank you for your feedback.
Sorry, we failed to record your vote. Please try again.
Report abuse
Format: Paperback
Object-orientation is often criticized for lacking a theoretical foundation. While patterns proliferate, principles remain elusive. But the pursuit is on, and Mr. Page-Jones leads the hunt with this fine work.
He catalogs attributes of object-oriented design by which we may intelligently discuss their quality: connascence, encumbrance, cohesion, type conformance, contravariance, covariance, closed behavior, ideal states, ideal behavior, and others. Patterns and anti-patterns are also exhibited, but the distinctive feature is the presentation of principles that all patterns must obey.
Each chapter begins with an overview and ends with a summary followed by exercises with answers. Be sure to read them all. The exercises are interesting, and the "summaries" sometimes (Chapters 5 and 6, for example) introduce new concepts.
The glossary is excellent. The bibliography is unfortunately not annotated. Some passages are over-peppered with footnotes, especially when their point is merely humorous. Overall the footnotes are valuable and the humor is appreciated.
The text takes care to reference backward and forward to related topics, helping readers to trace their own threads.
Some readers want more details about UML. Part II clearly describes a basic subset of UML probably sufficient for 90% of business scenarios, but many of the fine points are omitted.
Part III treats the reader to a series of thought-provoking discussions of the qualities of good software design. Some of the thoughts provoked involve differences of opinion that this reader would like to describe below. Before doing so, however, he must emphasize first just how valuable he found the time spent considering the ideas of Mr.
Read more ›
Was this review helpful to you? Yes No Sending feedback...
Thank you for your feedback.
Sorry, we failed to record your vote. Please try again.
Report abuse
Format: Paperback
This is a book more about object-oriented design then UML. The first section covers the absolute basics of what OOD is. The middle portion teaches the reader how to use UML to depict their designs. The final section is a set of instructive essays, warning the reader of the problems and pitfalls that often occur in OOD, and how to avoid them.
Page-Jones has an excellent sense of humour, and his engaging style makes this an incredibly enjoyable book to read. You won't even notice that you're actually learning something! I also like the fact that he doesn't use a single programming language for his examples, instead trying to be generic, or alternatively, giving examples from C++, Java, Eiffel, and Smalltalk in turn. This makes the book accessible for all OO designers.
I wouldn't recommend this book to an experienced OO designer who wishes to learn UML. That's not the intended audience. For a new comer, who wishes to learn good design techniques from the start, this is the book for you.
Was this review helpful to you? Yes No Sending feedback...
Thank you for your feedback.
Sorry, we failed to record your vote. Please try again.
Report abuse
Format: Paperback
Fundamentals of Object-Oriented Design in UML is a friendly book. I enjoyed it. Meilir Page-Jones maintains a wry sense of humor while threading through the intricacies of OO development in a clear, instructive fashion. The book really does have something for new and experienced programmers alike.
The first two sections of the book are most accessible to those with little programming experience. These sections introduce object orientation and provide a review of the most useful Unified Modeling Language notations while illustrating their use in software design work. But throughout the book the author examines critical principles in such a way that the most experienced software designers will be challenged to reconsider assumptions and habits and to look more critically at their work. The third section of the book is not completely accessible to readers without substantial development experience but even so has enough to offer that it should not be skipped by the newcomer to coding.
In my opinion this book is more about design than UML. If you want an introduction to UML it might make more sense to read Sams Teach Yourself UML in 24 Hours. The introduction to UML in Page-Jones' book is good enough to be your first look at UML but it is not comprehensive and it is oriented to illustrating design principles. This is an excellent book to start with and I would recommend reading it before anything else on UML. And I cannot imagine a better book for introducing object-oriented design. The author has a long track record in structured design and he frequently relates OO to SD concepts. The book is language independent but weighted toward C++. I only speak Java and had a little trouble with the concept of parameterized classes because they don't exist in my frame of reference but this was a very minor problem.
Was this review helpful to you? Yes No Sending feedback...
Thank you for your feedback.
Sorry, we failed to record your vote. Please try again.
Report abuse

Most recent customer reviews