It has the requirements specification document, and taking as a starting point, it is desired to create a representation of responsibilities and collaborations for each existing class.
It has a structure of the total set of classes in the system, assigning responsibilities for each class.
It is desired to create a representation of how a software system works from the user's perspective. The graphical representation will be using a unified modeling language icons, defining the meaning of each class by responsibilities and collaborations. It aims to understand the behavior of each class at a high level.
- System Type: It applies to all types of systems.
- Characteristics of organizations: This pattern can be used in existing projects in any company.
- Type of system to be developed: This product can be used in projects in which user requirements are changing.
- Type of Customer: It must exist or be achieved, the target area development business being involved in achieving it.
- Programming Paradigm: OO (Object Oriented).
- Utility: CRC cards can be used to simulate scenarios, distributing a CRC card for each team member.
- Brainstorming is a good practice to suggest how to fill the cards.
- Generally classes are self-sufficient and self-contained, so there may be a liability without a collaboration partner.
- Definition of software requirements (functional and non-functional).
- Intermediate knowledge of UML.
- Know how to obtain data on how it really work.
- Accustomed to using a particular paradigm.
- OO system representation
- Fowler, M. (2004). UML distilled: a brief guide to the standard object modelling language.' Addison-Wesley.
- Artículo original sobre Tarjetas Crc (Beck y Cunningham 1989) en la Web