Home > Articles > Software Development & Management > Object Technology

  • Print
  • + Share This
This chapter is from the book

CRC Models

Ward Cunningham and Kent Beck developed the CRC technique.4 The technique consists of using a small index card (see Figure 8.6) that contains the name of the class, the responsibilities of the class, and the names of other classes with which the class collaborates.

Figure 8.6Figure 8.6 Beck-Cunningham CRC card.

A short description of the purpose of the class may be written on the reverse of the card. The technique was developed to allow the designers and users of the system to quickly describe the classes in the system. The resulting index cards can be placed on a table and arranged spatially to interactively develop a model of the system. A variation on the technique, which I have found to be very useful, is to assign the class cards to the people who are involved in the design project. Each person "becomes the class" by playing that class's role in a typical scenario. It is important that the designers think in terms of the service responsibilities of the class instead of the data responsibilities of the class. As a rule of thumb, each class should have only about two to three responsibilities. These responsibilities will be implemented in approximately 10 to 12 operations of each class. Each operation will eventually be programmed in approximately 4 to 30 lines of code.

The whole group can quickly verify communication paths, test the completeness of the design, uncover hidden design assumptions, develop a glossary, and so on. I have found it useful to pass a ball or other object among the team members that represents the system's thread of control. The person passing the ball attaches a message that requires a service from the recipient of the ball. The person who receives the message keeps the message and then either sends requests for service from other objects (the object's collaborators) or returns the requested response back to the requester. At the end of the exercise, each person will have a collection of messages that will represent the operations of the objects that they are responsible for developing. During the design phase of the project, the policies, rules, directives, and algorithms that will be required to implement these operations will be identified and eventually programmed.

The final step of the CRC role-playing exercise is for all of the players to arrange their CRC cards on a tabletop so that the name of their classes are as physically close as possible to the where their class names appear in the collaborator section of the other players' CRC cards. This will produce, in 2 or 3 minutes, a class diagram for the project.

David Taylor has modified the CRC approach (see Figure 8.7) by adding super class and component categories to the card. The super class is the name of the more general class of objects that this class is a member of. For example, the class Sales Order is a member of the more general class called Order. The components are the names of classes that are combined to form the class. For example, the class Sales Order is made up of the combination of Products, Pricing, and Customer classes.

Figure 8.7Figure 8.7 Taylor CRC card.

Ian Graham has modified the CRC card (see Figure 8.8) to include super classes, parts, attributes and associations, operations, servers-messages, and rule sets. His super class and parts are similar to Taylor's super class and components. Attributes indicate if the class is a primitive data item or a user-defined class. They also indicate initial and default values, whether values can change over the class's lifetime, security levels, ownership, the possibility of null values, and valid range constraints. Associations show the cardinality of the relationships the class has with other classes. Operations are the procedures that the class can perform. Servers-messages indicate the messages that the class can receive. Rule sets show the constraints and business rules that apply to this class. Changes in state of the class may be recorded on the backs of the cards during role-playing or walk-through exercises.

Figure 8.8Figure 8.8 Graham class card.

Ian Graham's extensions to the use case and the CRC card techniques are designed to provide additional details to the people who will actually have to implement the model. I agree with his additions, but I am very much in favor of including formal design contracts into the use case and the CRC cards. Graham's extensions are intended to assist people who will still be creating code. My extensions are intended to assist people who will be assembling existing classes.

  • + Share This
  • 🔖 Save To Your Account

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information

To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.


Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.


If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information

Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.


This site is not directed to children under the age of 13.


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information

If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information

Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents

California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure

Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact

Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice

We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020