Rating: 
Summary: Clarifying the "What, When, Why and How" of OO Development
Review: I probably purchased somewhere upwards of twenty books on the topics of the UML and object-oriented development before buying The Object Primer, 2nd Edition. Yeah, it probably would have been nice to have read this one first, but on the other hand, it may have been just the right book at the right time in terms of my learning process. As a result of my previous efforts, I was getting overwhelmed and confused by the sheer volume of concepts, notations, diagrams, development processes, and tools associated with becoming proficient with UML modeling and object-oriented development. While I had learned lots of important terminology and techniques from the previous books, I found The Object Primer to be enormously practical and useful in terms of putting it all together and breaking through to a working level of proficiency. Among the aspects of the book that I appreciated are it's easy-to-read style, effective use of diagrams and visual examples, and the "techniques" sections with clear directives about what to do, and what not to do, in specific areas. I was able to use the technique lists in somewhat of a cookbook style as I applied what I was learning to some of my own work. So far, in my growing library of OO development books, this one provides the "biggest bang for the buck".
Rating: 
Summary: The Book To Read Before Your First OO Course
Review: I wrote The Object Primer so that people who are learning object-oriented development concepts for the first time, perhaps experienced structured developers or college students, had something to read that they could actually understand. I highly suggest reading The Object Primer before taking your first OO development course as it will give you a firm grasp of the fundamentals. This book is currently being used as an introductory textbook in several colleges. Visit http://www.ambysoft.com/theObjectPrimer.html for more details
Rating:
Summary: A Developer's Look at Real-World Software Development
Review: I wrote this book to share with you the techniques that I have found to work on the development of real-world business applications. The book covers the development lifecycle from end-to-end, covering requirements, analysis, design, implementation, and testing from the point of view of a developer. It covers the Unified Modeling Language (UML), focusing on the 20% that you actually apply in practice, and goes beyond the UML so you actually have a collection of techniques that will work for you in the real world. For example, do you develop applications with user interfaces and databases? Of course you do, yet the UML has nothing to say about user interface modeling or data modeling does it? How about business rules or future requirements (change cases)? I cover these techniques and more because they are what you need to be successful. You're not limited to just applying the techniques of the UML so why should books that describe how to develop software be limited in that manner? Techniques and topics that I cover in the book include: Business rules, Change cases, Class responsibility collaborator (CRC) models, Constraints, Essential use case models, Essential user interface prototypes, Persistence/data models, mapping objects to relational databases, Technical requirements, UML activity diagrams, UML class models, UML collaboration diagrams , UML component diagrams, UML deployment diagrams, UML sequence diagrams, UML state chart diagrams, UML use case models, User interface (UI) flow diagrams, UI design tips and techniques, and UI prototypes.
Rating: 
Summary: Good, but not simple to follow
Review: It is a good book to teach you about OO concept. The author generalizes the CRC card methodology in OO design. It is an excellent idea. However the examples are not in details. Moreover the explanation is not writing in simple English. You need to read several times to understand the idea. I hope in next edition, the author can provide more examples and use one case to explain the idea in step by step. Summarize tables can provides will be much better.
Rating:
Summary: This guy is good! The OO comes before the UML.
Review: OO came first and then came UML to model it! This book is all about the principles of object-oriented requirements, analysis, and design first and secondly about the UML tools for modeling these steps in project development. That's as it should be since OO is the thing most to be admired, and UML is (just) a popular and very useful language for modeling OO development. Too many UML books are so intent on UML that the fundamentals of OO are ignored. The first edition of this book was published in 1995 just before UML was born. Its author, Scott Ambler, is a prolific and renowned writer and developer. The book has many detailed UML diagrams and is clearly written in a pleasant, professional style. The book is not about implementation. Look elsewhere for sample code, including some of Ambler's fine other publications. Don't be lislead by the word "Primer" in the title. It's for the serious reader and would make a good text, but for a junior or senior level CS course. If you are a professional and could have just two references in your library for your first OO project, this 523-page book together with a good programming reference (Java, C++, C#, or VB.NET) would be a good choice.
Rating: 
Summary: Worth Buying Book and Useful Book for Object-Oriented Design
Review: This book is very useful for me. As a JAVA Programmer i was always confused with the notations used by various authors. I found the notations used in this book to draw various design diagrams are simple and understandable. I thank author for producing such an excellent book for Object-Oriented programmers and designers.
Rating:
Summary: This book rocks
Review: This has to be the first book that has gotten object-oriented development right. Ambler really does tell it like it is in an easy to read manner. This is a great book for novices because it provides an introduction to the actual techiques you need to know about to develop software and is good for people like me who have been working in Java for a few years now because it fills in the missing blanks. Every Java and C++ programmer needs to read this book. The thing that I like most about the book is that he colors outside of the UML lines, I wish more authors had the nerve to do that. This book is what the UML User Guide by the Three Amigos should have been. This book, in combination with UML Distilled, is the only thing that you need to know how to model object-oriented business applications.
Rating:
Summary: This book rocks
Review: This has to be the first book that has gotten object-oriented development right. Ambler really does tell it like it is in an easy to read manner. This is a great book for novices because it provides an introduction to the actual techiques you need to know about to develop software and is good for people like me who have been working in Java for a few years now because it fills in the missing blanks. Every Java and C++ programmer needs to read this book. The thing that I like most about the book is that he colors outside of the UML lines, I wish more authors had the nerve to do that. This book is what the UML User Guide by the Three Amigos should have been. This book, in combination with UML Distilled, is the only thing that you need to know how to model object-oriented business applications.
Rating:
Summary: Actually much more than just an object primer!
Review: This is a great book! Not that it's perfect, but nothing is. This book is not only a very clear, extremely well-organized approach to learning and/or becoming expert in "Object Orientation and the UML," as the the cover says, but he presents this together with a development methodology that makes a *lot* of sense. For example, for those of you who have read Karl Wiegers' excellent "Software Requirements," did you notice that at the end of the book you knew exactly what good requirements are but not how to get there? Me too! But Ambler takes you on a whirlwind tour, with each page absolutely *packed* with value, that instead leaves you saying "hey, now I know not only what good object oriented designs are, but how to get there from here!" This is a strange thing to say, but this book actually gave me the requirements engineering methodology I needed to get from point A to B -- having requirements that Karl Wiegers would be proud of!
Rating:
Summary: Actually much more than just an object primer!
Review: This is a great book! Not that it's perfect, but nothing is. This book is not only a very clear, extremely well-organized approach to learning and/or becoming expert in "Object Orientation and the UML," as the the cover says, but he presents this together with a development methodology that makes a *lot* of sense. For example, for those of you who have read Karl Wiegers' excellent "Software Requirements," did you notice that at the end of the book you knew exactly what good requirements are but not how to get there? Me too! But Ambler takes you on a whirlwind tour, with each page absolutely *packed* with value, that instead leaves you saying "hey, now I know not only what good object oriented designs are, but how to get there from here!" This is a strange thing to say, but this book actually gave me the requirements engineering methodology I needed to get from point A to B -- having requirements that Karl Wiegers would be proud of!
|
