Applying the object-oriented paradigm to the development of software requires individuals and teams to think and act differently than when designing procedural projects. While proponents of the object paradigm often say identifying objects is a simple and intuitive process, experienced developers know that this is not always true. The solution is the CRC (Classes, Responsibilities, Collaboration) Card method, a proven technique for identifying classes and visualizing and testing different class-based models during the design phase.
The CRC Card Book covers the CRC method from start to finish, illustrating its application in three different in-depth case studies which supply tips and pointers drawn from real world experience. The case studies are presented in the engaging style of a novella to demonstrate how personalities and organizational culture come into play when using the CRC technique. C++, Java, and Smalltalk experts provide implementation examples in each language. The CRC Card Book demonstrates how to:
Includes language implementation examples from such noted experts as:
David Bellin is Director of Graduate Studies in the Department of Computer Science at North Carolina A&T State University and consults internationally on object analysis and technical training with organizations such as Macy's, Universidad Nacional Autonomia de Mexico, and the United States government. He has received a Congressional Fulbright Award in computer science and an IBM Corporation University Partnership Award. Susan Suchman Simone is the President of Information Fountain Inc., specializing in technical writing and training. She has taught classes for Yourdon, Inc. and North Carolina State University and has developed training materials for companies across the country including Chase Manhattan Bank, New York Life, and Banamex.
0201895358AB04062001
Product Details
Would you like to update product info or give feedback on images?
|
|
Share your thoughts with other customers:
|
||||||||||||||||||||||
|
Most Helpful Customer Reviews
17 of 18 people found the following review helpful:
5.0 out of 5 stars
Great book for helping do high level OO design.,
By A Customer
This review is from: The CRC Card Book (Paperback)
I have been trying to teach OOD to new graduates for a couple of years. Now I teach through this book first. It has more good information about how to get groups to come up with good designs than any other book I have found. Be warned, it's not about UML or Java. The book is about how to get people to work out a design together.
12 of 13 people found the following review helpful:
5.0 out of 5 stars
Ideal for getting you started on "how to" identify Classes.,
This review is from: The CRC Card Book (Paperback)
You want to know a great way on "how to" identify classes from any type of user requiremnets? Buy this book now!A lot of OOA books like to tell how to design from start to finish. However, some (most) of us are thrown in some obligatory process without consent. CRC will bridge the gap on getting your Classes defined. Also, CRC works well for "Use Cases". I use CRC after a good Use Case session for Class Diagrams. Some prefer to do CRC before Use Cases. That's the beauty, CRC can be injected anywhere you deem fit. And, finally, this book will get you "thinking in objects" fast!
5 of 6 people found the following review helpful:
4.0 out of 5 stars
High-effective but fragile,
By
Amazon Verified Purchase(What's this?)
This review is from: The CRC Card Book (Paperback)
This book encourages better OO design and analysis, shows how to involve the entire team of developers to the design of the whole system. The authors also describe how to gain benefit from involving the user and other parties to the OO design process. I was in OO development for five years and I was thinking about a solution which will improve the efficiency of OO design and help to avoid splitting the program between developers who create their own set of classes they are responsible for. Such splitting leads to integration problems and overall design imbalance. Fred Brooks has described this consequences in his famous book "The Mythical Man-Month", where the modules are being written first and integrated later, and the coordination of interfaces between modules written by each developer requires essential effort and time. The CRC Card Book shows how to have "the interfaces" coordinated in the very beginning. However, the methodology described in this book is "fragile". As soon as it isn't followed by all of the developers, it became useless. But if it is followed, the results are amazing. The book, however, is not very easy to read and lack something which can attract the developers who are "neutral" to improving their way of creating OO programs. But, for the people who already have strong OO background and are seeking the way how to improve their efficiency significant, the book is a must-have.
Share your thoughts with other customers: Create your own review
|
|
Tags Customers Associate with This Product(What's this?)Click on a tag to find related items, discussions, and people.
|
|
This product's forum
Active discussions in related forums
Search Customer Discussions
|
Related forums
|