A laboratory for teaching object oriented thinking
OOPSLA '89 Conference proceedings on Object-oriented programming systems, languages and applications
Designing object-oriented software
Designing object-oriented software
CRC: finding objects the easy way
Object Magazine
Object-oriented analysis and design with applications (2nd ed.)
Object-oriented analysis and design with applications (2nd ed.)
Using CRC cards: an informal approach to object-oriented development
Using CRC cards: an informal approach to object-oriented development
The CRC card book
The Unified Modeling Language user guide
The Unified Modeling Language user guide
Object-Oriented Design Heuristics
Object-Oriented Design Heuristics
Role playing in an object-oriented world
SIGCSE '02 Proceedings of the 33rd SIGCSE technical symposium on Computer science education
Reflections on CRC cards and OO design
CRPIT '02 Proceedings of the Fortieth International Conference on Tools Pacific: Objects for internet, mobile and embedded applications
Object Design: Roles, Responsibilities, and Collaborations
Object Design: Roles, Responsibilities, and Collaborations
CRC cards for product modelling
Computers in Industry
Object Thinking
Improving CRC-card role-play with role-play diagrams
OOPSLA '05 Companion to the 20th annual ACM SIGPLAN conference on Object-oriented programming, systems, languages, and applications
3-step knowledge transition: a case study on architecture evaluation
Proceedings of the 30th international conference on Software engineering
Hi-index | 0.00 |
CRC-cards are a common lightweight approach to collaborative object-oriented analysis and design. They have been adopted by many educators and trainers to teach object-oriented modelling. In our experience, we have noticed many subtle problems and issues that have largely gone unnoticed in the literature. Two of the major issues are related to the CRC-card role-play as described in the literature. Although CRC-cards are representing classes, they are also utilized as substitutes for the actual objects during the scenario role-play. Furthermore, it is quite difficult to document or trace the scenario role-play. We propose using Role-Play Diagrams (RPDs) to overcome these problems. Our experience so far is quite positive. Novices have fewer problems with roleplay activities when using these diagrams. Teaching and learning the new type of diagram adds only little overhead to the overall CRC-approach. Although our improvements specifically target the teaching and learning of object-oriented modelling, we believe that RPDs can be successfully applied in professional software development.