AnyBook4Less.com	Find the Best Price on the Web Order from a Major Online Bookstore
Home  |  Store List  |  FAQ  |  Contact Us  |
Ultimate Book Price Comparison Engine Save Your Time And Money Keyword AuthorISBN

Title: Object-Oriented Development Process, The: Developing and Managing A Robust Process for Object-Oriented Development by Tom W. Rowlett ISBN: 0-13-030621-5 Publisher: Prentice Hall PTR Pub. Date: 20 December, 2000 Format: Hardcover Volumes: 1 List Price(USD): $54.99

Your Country USA Canada United Kingdom Australia Austria Belgium France Germany Italy Netherlands Switzerland Currency AutoUSD CAD GBP EUR AUD CHF Delivery Only cheapest delivery All delivery options Include Used Books Are you a club member of: Barnes and Noble Books A Million Chapters.Indigo.ca

Average Customer Rating: 3.67 (3 reviews)

Rating: 4
Summary: A book worth buying if you have patience
Comment: First of all, this book is good if you are a very patient reader. The book is not about pure Object Oriented Technology. Rather, the author tries to bring together a process which is much more practical and makes sense. It is a fast paced book, so you might have to go back and read couple of chapters more then once to get the concepts straight.

The book uses UML for all diagrams. It explores different options that the software architect can choose from depending on the type of project and the comfortability level. For eg., the author explains the usage of state machines, decision tables and sequence diagrams during the Analysis phase of a system. Any of these processes can be used by the reader. It explains the logic behind constructing class diagrams from use cases, how to establish relation between classes and deriving the database table structures from classes. It lays emphasis on testing the finished product and how to go cover different test cases .

The book does include some case studies which many readers might find helpful and use them as "templates" in tackling their projects.

I have done two projects using this book and have been able to bang in the time estimates. Also it has helped me in the actual coding much easier.

In a nutshell, I would give a good rating to this book since it has really helped me to get into the Object Oriented world of programming and develop into a much better and efficient programmer.

Rating: 3
Summary: Not for developers (designers & programmers)
Comment: You might like this book, I didn't. As a developer I found it way too light on design, and missing a key part of design. This looks like a book that is not for developers. Maybe requirements people or managers will like it. The design artifact of greatest use to a programmer goes by different names: object interaction diagram, interaction diagram, collaboration diagram, and so on. A sequence diagram is similar. This book mentions sequence diagrams very briefly, but this most useful concept is largely missing. As a software developer, I prefer this new book: "UML and the Unified Process" by Jim Arlow and Ila Neustadt. Don't buy this without first looking at a real copy. You might love this book, but you really need to look it over first.

Rating: 4
Summary: Good book to start out if shifting from mainframe
Comment: The book is very detailed and gives numerous examples of the deliverables created in the process. It starts out overviewing process models (waterfall, iterative, incremental) and talks about the criteria for a robust process (complete, consistent, verifiable,traceable, incremental and testable). The author recommends using an incremental process with use cases. To me this is the best way to start out since your requirements, analysis and design are established and your team can progress without change issues. Change management and control are documented and implemented in future releases.

The book has chapters on requirements definition, analysis, use case design, class design, persistence,implementation, testing, user interface, maintenance, project management and over 100 pages dedicated to a case study with 4 increments (very detailed and helpful).

The book uses UML diagrams as examples and touches upon subjects such as the importance of correctness, of having a data dictionary, planning, and it has a good summary and glossary at the end. It even gives an example on how to build an estimating model spreadsheet using metrics and statistical correlation.

One topic that is missing is security and how it fits into applications. Also, the chapter on requirements definition is a little weak since it blends into use cases right away and does not give the reader a clear message on how to reduce ambiguity, what a requirements specification should contain, etc. But there are good books on requirements that can be bought.

Overall a really good book that can help any manager or developer with getting started using OO concepts.