APPLYING THE 3C MODEL TO GROUPWARE DEVELOPMENT
International Journal of Cooperative Information Systems
This paper introduces an approach based on the 3C (communication, coordination and cooperation) collaboration model to the development of collaborative systems. The 3C model is studied by means of a detailed analysis of each of its three elements, followed by a case study of a learningware application and the methodology of a web-based course, both designed based on this model. Moreover, this paper describes a component-based system architecture following this 3C approach. Although the 3C model
... is commonly used for classifying groupware, a few attempts have been made to use it in the context of groupware implementation. A notable example is the Clover design 3 model, which defines three classes of functionalities, namely communication, coordination and production (cooperation in the present paper) [Laurillau & Nigay, 2002] . These three classes of services appear in each functional layer of the model and, during the system design phase, they "must be identified and their access harmoniously combined in the user interface". The Clover model shares the same usefulness of the 3C model in terms of groupware functional specification, because both deal with the three classes of functionalities that a groupware application may support. However, differently from the Clover model, the 3C model is here mapped to a groupware component-system architecture (Section 6). In this paper, we show how the 3C model has been applied to the development of the AulaNet environment and to the dynamics of a course entitled Information Technology Applied to Education (ITAE), currently in its fourteenth edition. In the Section 2 of this paper, AulaNet and the ITAE course are introduced. The following sections detail each aspect of the 3C collaboration model, namely communication (Section 3), coordination (Section 4) and cooperation (Section 5), using AulaNet and the ITAE course as case study. In Section 6, design and implementation issues are discussed by means of the proposal of a component-based architecture. Finally, Section 7 concludes this paper.