|
| Login | Sign up | My Wish List |
![]() | Object-Oriented Software Construction (Book/CD-ROM) (2nd Edition) (Prentice-Hall International Series in Computer Science) by Bertrand Meyer ISBN-10: 0136291554 ISBN-10: 0-13-629155-4 ISBN-13: 9780136291558 ISBN-13: 978-0-13-629155-8 Paperback 2000-03-21 Prentice Hall PTR Find Lowest Price | |
Editorials | ||
Amazon.com The developer of the acclaimed Eiffel programming language comes through with one of the clearest and most informative books about computers ever committed to paper. Object-Oriented Software Construction is the gospel of object-oriented technology and it deserves to be spread everywhere. Meyer opens with coverage of the need for an object-oriented approach to software development, citing improved quality and development speed as key advantages of the approach. He then explains all the key criteria that define an object- oriented approach to a problem. Meyer pays attention to techniques, such as classes, objects, memory management, and more, returning to each technique and polishing his readers' knowledge of it as he explains how to employ it "well." In a section on advanced topics, Meyer explores interesting and relevant topics, such as persistent objects stored in a database. He also offers a sort of "Do and Don't" section in which he enumerates common mistakes and ways to avoid them. Management information isn't the main point of Object-Oriented Software Construction, but you'll find some in its pages. Meyer concludes his tour de force with comparisons of all the key object-oriented languages, including Java. He also covers the potential of simulating object technology in non-object-oriented languages, such as Pascal and Fortran. The companion CD-ROM includes the full text of this book in hypertext form, as well as some tools for designing object-oriented systems. If you program computers, you need to read this book. | ||
Book Description Recipient of the 1997 Jolt Award. The developer of the acclaimed Eiffel programming language comes through with one of the clearest and most informative books about computers ever committed to paper. Object-Oriented Software Construction is the gospel of object-oriented technology and it deserves to be spread everywhere. Meyer opens with coverage of the need for an object-oriented approach to software development, citing improved quality and development speed as key advantages of the approach. He then explains all the key criteria that define an object- oriented approach to a problem. Meyer pays attention to techniques, such as classes, objects, memory management, and more, returning to each technique and polishing his readers' knowledge of it as he explains how to employ it "well." In a section on advanced topics, Meyer explores interesting and relevant topics, such as persistent objects stored in a database. He also offers a sort of "Do and Don't" section in which he enumerates common mistakes and ways to avoid them. Management information isn't the main point of Object-Oriented Software Construction, but you'll find some in its pages. Meyer concludes his tour de force with comparisons of all the key object-oriented languages, including Java. He also covers the potential of simulating object technology in non-object-oriented languages, such as Pascal and Fortran. The companion CD-ROM includes the full text of this book in hypertext form, as well as some tools for designing object-oriented systems. If you program computers, you need to read this book. | ||
Reviews | ||
The better book you can get about OO There's no way someone can get to know about objects without reading meyer's book. It's huge but worth | ||
highly recommended as a first introduction to OOP When writing a treatise on computer programming one has to strike a balance between providing a book that is both useful (which usually means writing within the context of a compilable programming language), but general enough so as not to oversimplify or truncate parts of the theory because it is not represented by the chosen language. In OOSC2 Meyer does just this, by providing a sound and general introduction to object-oriented programming, while using the Eiffel language for purposes of notation and practical programming examples. Meyer has a very engaging writing style: very clear, with lots of good (and humorous : ) examples. And the Eiffel language itself seems quite simple, readable (it was obviously influenced by ADA) and brilliantly designed (think of Java, but with multiple inheritance, generics, and without the run-time inefficiency of the java virtual machine). But whether you program in Eiffel, Java, C#, or C++, OOPSC2 has alot to offer in terms of OO software design, and a good understanding of the issues behind inheritance, polymorphism, the importance of static typing, and dynamic binding. For example, I program in C++, and this book has helped me clearly understand the object-oriented features of the language, because in clearly explaining the principles, it helped me understand the intentions of the C++ language designers. May be my only complaint, at perhaps half a star, is the fact that Meyer often weighs in heavily against other languages for their shortcomings, while going easy on his own Eiffel language. For example, he failed to give an objective analysis regarding the run-time costs of garbage collection. Indeed, the chapter on garbage collection seemed more of handwaving defense of the fact that Eiffel uses this technology. A presentation of run-time empirical studies for various applications would have been much more welcomed. However I believe that the benefits of this book far outweigh the occasional partisanship shown towards Eiffel. I truely believe that Meyer favors Eiffel because he believes in it more on the basis of principle than on profit (he does own a software company that supports Eiffel development tools). | ||
very good, but not the holy grail of software engineering In this book Bertrand Meyer did an excelllent job in explaining object oriented software design in a rigourous way. Too often authors of OO books were not formal and rigorous enough, leading to a lot of confusion in the OO world. This book gives a very formal and exact treatment of Object orienteation. As a consequence this book is a must read for every OO expert. That the book focusses on eiffel should not be seen as a drawback : you can apply most of the explained techniques in other OO languages. Also this book does not focus much on UML. However, to my opinion, this is not a drawback neither since the power of UML is strongly overhyped. Though there are some minor drawbacks in this book : Finally some remarks : please do not overestimate the power of software reuse : in reality it has limited usage since in order to create reusable software and reuse it, each teammember has to know quite well what the other teams are doing in order to reuse some part of their work. In reality, for big projects, this is often impractical. | ||
A must have book for professionals in OO Unfortunately, the majority of books in computing science area suffers a lack of precise definition and clarity of terms and concepts. In my personal opinion, the commercial aspects that strongly affect this area, comparing to other technological ones, contributes to open the computing book market for authors of highly questionable experience and a quite shalow knowledge about the matter they're treating. For example, it is not unusual to see the same author (or group of authors) writing books about Java, .NET, JSP, ASP, Perl, OO, C/C++ and so on. Bertrand Meyer's OO book is an exception in this tendency. The subjects treated are logically distributed and the concepts are clearly and precisely defined. Then, the reader gets an intuitive and deep understanding of OO theoretical aspects, independent of OO language specifics. All the concepts are perfectly prioritized and sequenced: software quality before OO, ADT before classes, features before functions, DBC before exception handling. Every single concept bases the following ones. I must say, however, that the author should be more concise: he writes too much to explain a single concept. He reveals his large academic literate background inserting unnecessary large comments in the text. The book could have a quite less number of pages without any loss in learning the main concepts. I sincerely do not see any problem about the relation between the OO concepts presented and their practical implementation: EIFFEL language. At least, the author shows concretely that the concepts treated in the book are implementable. If there were not any language to complete and support the theoretical aspects, we could say : "Ok, all the concepts in the book are perfect and beautiful, but the closest programming language to these concepts we can use is JAVA, for example." | ||
How can you say enough to reward excellence? I have two 3M notpad leafs stuck at the periphery of pages 3 to 278. They are labeled Curious and Enlightened, respectively of course. People that walk into the office asking about what OO design is about, get the tattered Meyer paperback and the instruction to come back when they have read these pages. For practical example, they are steered to the rest and works of others. This a special tag on the page about Polymorphism, which is the kind of ambigous term that begs to be forgotten. However, Meyer's lucid brevity makes the meaning stick. The feature I find most special is the pull down menu style outline quality of these pages. Abandon your highlighters with this book. Meyer has already digested and illuminated the key concepts for you. Fortunately, this does nothing to diminish the surrounding text. High marks for editing quality and concept density in a book which clearly pays for itself a third of the way through. | ||