The CRC card book / David Bellin and Susan Suchman Simone.

By: Bellin, David, 1951-.

Contributor(s): Simone, Susan Suchman, 1948-.

Material type: materialTypeLabel

BookSeries: Addison-Wesley series in object-oriented software engineering.Publisher: Reading, Mass. : Addison-Wesley, 1997Description: xxiii, 290 p. : ill ; 24 cm. + pbk0.ISBN: 0201895358 .Subject(s): Object-oriented programming (Computer science)

| Application software -- Development

DDC classification: 005.117

Contents:

CRC: A Problem-Solving Technique -- OO Concepts and Vocabulary -- Getting started with CRC -- Selecting the Core Classes -- A Case study in stocks and bonds -- CRC Role Play: Living the system -- Fashion Pro: Role-Playing Core Classes -- Managing Object Analysis -- Case study 3: Traffic Control -- Implementing CRC in Smalltalk -- Implementing CRC in C++ and JAVA -- Transition to Methodologies.

Holdings
Item type	Current library	Call number	Copy number	Status	Date due	Barcode	Item holds
General Lending	MTU Bishopstown Library Lending	005.117 (Browse shelf(Opens below))	1	Available		00069933

Total holds: 0

Enhanced descriptions from Syndetics:

CRC cards are a useful development tool in helping developers facilitate brainstorming or acting out the running of an application just as if it were a working system. This text addresses the actual details involved with using CRC cards, including coverage of program code (Java, C++, and Smalltalk) derived from the use of the CRC card method.

Bibliography: (pages 279-280) and index.

Table of contents provided by Syndetics

About the Authors
Figure List
Foreword
Preface
Acknowledgments
1 CRC: A Problem-Solving Technique
The CRC Card
CRC Is Fun!
Problem Solving and Insight
A Parable of Insight
CRC Cards as a Metacognitive Process
The Challenge of Finding Classes
Making CRC Work: Project Management Guidelines
Summary
2 OO Concepts and Vocabulary
Thinking About the World as Objects
Encapsulation
Instantiation: Classes and Objects
Inheritance: Classes, Super-classes and Sub-classes
Abstract Classes
Polymorphism
Frameworks and Patterns
A Case in Point
Summary
3 Getting Started with CRC
Who Writes CRC Cards?
Two Is Only Company; Ten Is a Crowd
Reading the CRC Card
Brainstorming: A Discovery Technique
Description of Brainstorming Principles
Using Brainstorming to Find Classes
The Candidate Class List: Where Do Classes Come From?
Read Over All Requirements Documents
Look Carefully at Reports
Conduct Interviews
Examine Documentation and Files
Summary
4 Selecting the Core Classes
Identify Critical Classes
Clarify System Scope
Take Advantage of Hot Spots, Frameworks, and Patterns
Phantoms and Ghosts, Surrogates and Aliases
Distinguish Attributes from Classes
The Annotated Candidate Class List
Questions to Ask of a "Good Class"
Writing Classes on the CRC Cards
Assigning Responsibilities
"What And Not How"
Responsibility for Behavior
Responsibility for Knowledge
Responsibility Detection Pointers
Assigning Collaborators
Identifying Hierarchies
Summary
5 A Case Study in Stocks and Bonds
Saver, Soone, & Eayrne's Cyber-Trading System
Selecting the CRC Team
Warming Up the Team
Brainstorming Candidate Classes
Selecting Core Classes
Assigning Responsibilities
Assigning Collaborators
Identifying Hierarchies
Summary
6 CRC Role Play: Living the System
The Theory Behind the Practice
The Problem of Shared Meaning
Beware the Limits of Working Alone
Active Learning: The Rationale for Interactive Review
How CRC Role Play Works
Developing the Role-Play Scenarios
The Theory of "Aha!"
The Psychological Model
Confusion is Rarely Permanent
Role Play: Performing the System Simulation
Timing the CRC Role-Play Session
The Warm-Up
Enactment
Assessment
Summary
7 Fashion Pro: Role-Playing Core Classes
Fashion Pro: A New Idea in Garment Creation
The Fashion Pro Analysis Team
Recapping the Core Classes
Sketching Scenarios
Reusing Analysis Frameworks
Continuing the Scenario List
Role-Play Enactment
Assessment
Summary
8 Managing Object Analysis
Object-Oriented Development Changes the SDLC
The Waterfall SDLC
The Spiral SDLC
The Incremental and Iterative SDLC
Using the OO SDLC to Manage Project

Excerpt provided by Syndetics

Applying the object-oriented paradigm in the development of software applications requires the individual developer and the application team to think and act quite differently than one would in approaching a procedures based project. Object-oriented projects follow a new software development life cycle, one that is both iterative and incremental, a cyclic spiral of analysis, design, and deployment. In this new application-development process, determining and defining properly the classes that are central to the desired system at the beginning of the life cycle is critical. Thorough analysis of the problem and good design up front saves time, and money and helps ensure a successful end result. Although proponents of the object paradigm often say that identifying objects is a simple and intuitive process, a number of noted experts admit that this is not always true! Particularly with larger-scale applications, omitting a formal analysis of the base classes necessary to the application and the related analysis of their responsibilities and collaboration is certain to lead to missed schedules, blown budgets, and frayed nerves. The solution is to use the CRC process to determine the classes necessary to the system as part of the design process for the application. CRC (classes, responsibility, and collaboration) cards can be used to visualize and test different class-based models during the design phase. It is a proven technique used and advocated by leading methodologists. The CRC Card Book demonstrates the use of the CRC methodology in a realistic team setting, covering the full range this methodology from initial identification of classes to the production of code based on these classes. At this writing, there are two other books on or incorporating coverage of CRC. Rebecca Wirfs-Brock wrote Designing Object-Oriented Software many years ago. It remains the classic definition of responsibility-driven design, but does not discuss the application of the technique in the team-oriented setting in which large-scale applications are developed. Nancy Wilkinson's book, Using CRC Cards , focuses specifically on the C++ programming community and likewise does not include any illustration of the team approach to class discovery. The approach of The CRC Card Book is to cover the CRC method from start to finish, demonstrating its application in three different, detailed case-study examples while supplying tips and pointers throughout. The book demonstrates how real teams can use the CRC technique to accomplish a variety of tasks, including: Initially discovering classes Selecting the core classes Acting out class relationships and scenarios Refining the project requirements Furthering project management Serving as a guide to the design of code (in C++, Java, and Smalltalk) This book is a useful tool for those applying the CRC technique. The tips, tricks, and pointers included are drawn from real-world experience, and all the various tables and lists presented in the text, are collected together in an appendix. The case studies are provided to help you visualize how the guidelines developed in the descriptive chapters might be applied in a real-life situation. All three case studies are based on real systems and are presented in a dramatized style to help you understand how to use the method better. Also included are two examples of how our third case study, the control of automobile traffic intersections, might look when in Smalltalk, C++, and Java. The source code from these chapters is available from Addison-Wesley at http://www.awl.com/cp/bellin-simone.html. The CRC Card Book is organized as follows: Brainstorming We place special emphasis on the dynamics of team work, and how these dynamics are applied to the successful use of CRC. The first team strategy we suggest is brainstorming. We show how this applies to the task of finding classes and listing scenarios. Role Plays The second team strategy we recommend is role play. CRC cards provide a uniquely dynamic way of testing out your conception of the system and evaluating potential paths of collaboration. Role plays get everyone involved and invested in the system. Case Studies Three case studies are provided to help you visualize how the guidelines developed in the descriptive chapters might be applied in a real-life situation. All three case studies are based on real systems. They are presented in a dramatic, novella style to demonstrate more clearly how personalities and organizational culture come into play when a group is using the CRC technique. This is especially important in the context of brainstorming and role play. We hope that this approach not only will clarify the use of the method, but will provide a little entertainment along the way! Implementations in Code We also provide two examples of how our third case study, the control of automobile traffic intersections, might look when a programmer uses CRC cards as the basis for coding in Smalltalk, C++, and JAVA. Three experts in each language community joined with us to write this unique material. Managing Object Analysis Following the examination of role playing in the CRC method, we discuss the overall demands of managing an object-oriented project, along with suggestions as to useful metrics for monitoring the process, and for including legacy software in OO systems. We also provide some ideas for the transition from informal modeling with CRC cards to the use of a full-blown, formal methodology such as Schlaer-Mellor or the Unified Modeling Language. The final case study in the book provides additional insight into the application of these techniques. Transition to Methodologies In this concluding chapter we discuss the limitations of CRC cards and examine several popular and more comprehensive object-oriented analysis and design methodologies. CRC Roadmap Every chapter is full of useful tips, tricks, and pointers drawn from the real world. In addition to the various tables and lists in the text, we've collected these together in an appendix with pointers back into the book, so you can find things quickly when you need them. Get to Work! In The CRC Card Book , we have tried to distill a wide range of experiences and training tips for the use of CRC. We hope that some of it applies to all of you, and that all of it applies to some of you. Above all, remember, let CRC make your team work fun! 0201895358P04062001 Excerpted from The CRC Card Book by David Bellin, Susan S. Simone All rights reserved by the original copyright owners. Excerpts are provided for display purposes only and may not be reproduced, reprinted or distributed without the written permission of the publisher.

Author notes provided by Syndetics

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