 |
GetTextbooks.co.uk
Compare Prices & Save up to 90% |
|
|
|
| Login | Sign up | My Wish List |
 | | Use Cases Combined With Booch/Omt/Uml: Process and Products by Putnam P. Texel, Charles B. Williams ISBN-10: 9780137274055 ISBN-10: 0-13-727405-X ISBN-13: 9780137274055 ISBN-13: 978-0-13-727405-5 Hardcover 1997-06 Prentice Hall Find Lowest Price |
Editorials | ||
Amazon.com Review The Unified Modeling Language (UML) gives you a chance to create a wide variety of software-engineering documents, but what are the steps required to build successful, even military-quality, software? Use Cases Combined with BOOCH/OMT/UML provides a "cookbook," or design guide, to creating software based on use cases, while stressing software requirements and testing. This text begins with a discussion of its software methodology (which is based on Ivar Jacobson's Use Case methodology). The authors stress software requirements and a "requirements traceability matrix." This is the list of user requirements that will furnish a blueprint for design, implementation, and testing. Based on this requirements list, the authors discuss the use cases, which show how actors interact with software and hardware. The chosen single case study here is certainly idiosyncratic: a "habitat control center" for monitoring the air pressure, temperature, and oxygen level for 48 living quarters in a sealed environment. The chosen case study highlights the authors' belief that critical and reliable software can be created using their process. Further steps in the design add classes (and groups of classes, called categories) to this requirements matrix. Along the way, this text provides project tracking and testing steps for validating software. All the major UML diagram types are introduced, including class, collaboration, statechart, and activity diagrams. The authors also pay attention to actual coding (or implementation) of their design. (Finished versions of their designs are provided in C++, Java, and Ada95 on the accompanying CD-ROM.) In all, Use Cases Combined with BOOCH/OMT/UML shows that UML can work within a powerful software process that would seem to have a lot of potential to deliver on-time, highly robust software systems. It's up to readers to decide for themselves, but this software process seems to offer some real advantages. --Richard Dragan | ||
Reviews | ||
I lived it I worked for a company where Putnam Texel was an OO process consultant just prior ro her writing this book. What a horror. We were getting all focused on producing these idiotic design artifacts but never actually were gaining any real understanding of the system we were trying to design. She was all process but never really conveyed the real methods of thinking that are essential to OO analysis and design. Don't even waste you time with this book. | ||
Waste of money This is quite the worst OO book that I have come across. The presentation of OO principles is very confused, and even wrong in some key areas. The approach to use cases clearly comes from a distant planet - "It's a use case Jim, but not as we know it!". The title of the book is extremely misleading. As for the software engineering process presented herein - NOOOOOO! You CAN'T be serious! The process is just byzantine in it's complexity! A friend of mine sent his copy of this book back to the publishers and got a refund. I wish I had! | ||
Apt for Intermediate OO designers Definitely not for novice developers, this book presents a respectable starting point for OOAD practices. Though some text/techniques did look dated; the approach, deliverables, phases were well covered and can definitely be used for mid-sized OO projects. The phases are well-explained alongwith important elements like pragmatic issues, entry-exit criteria. For those attempting to bring more structure to their development process, this book's utility can be enhanced with knowledge of design patterns, and previous OOAD experience. One can certainly modify / improve the various deliverables covered in the book to their own needs. I do wish for a better title and singular focus on UML, now that it is a standard. The code listings can surely be reduced and made more up-to-date. Some basic Java dev guidelines (like package names in lowercase) have been ignored. | ||
Save your time and money Well I guess a title like this helps sales but it's a pity there is so little content to support it. Anyone looking for some great use-case technologies will be sorely disappointed. And the process and project management content is stifling, cumbersombe and dated. There are many far more exciting, modern and lightweight alternatives than this mess. | ||
difficult to rate This book is to difficult for OO-novices and too easy for advanced OO-practicioners. It has 450 pages approx. but most of it are just programming listings which are of no use to anybody | ||