Lecture Notes in Computer Science Edited by G. Goos, J. Hartmanis, and J. van Leeuwen
2440
3
Berlin Heidelberg New York Barcelona Hong Kong London Milan Paris Tokyo
Jörg M. Haake José A. Pino (Eds.)
Groupware: Design, Implementation, and Use 8th International Workshop, CRIWG 2002 La Serena, Chile, September 1-4, 2002 Proceedings
13
Series Editors Gerhard Goos, Karlsruhe University, Germany Juris Hartmanis, Cornell University, NY, USA Jan van Leeuwen, Utrecht University, The Netherlands Volume Editors Jörg M. Haake FernUniversität Hagen, Computer Science VI - Distributed Systems Informatikzentrum Universitätsstr. 1, 58084 Hagen, Germany E-mail:
[email protected] José A. Pino Universidad de Chile, Departamento de Ciencias de la Computacion Av. Blanco Encalada 2120, Santiago, Chile E-mail:
[email protected]
Cataloging-in-Publication Data applied for Die Deutsche Bibliothek - CIP-Einheitsaufnahme Groupware : design , implementation , and use. 8th international workshop ; proceedings / CRIWG 2002, La Serena, Chile, September 1 - 4, 2002. Jörg M. Haake ; José A. Pino (ed.). - Berlin ; Heidelberg ; New York ; Barcelona ; Hong Kong ; London ; Milan ; Paris ; Tokyo : Springer, 2002 (Lecture notes in computer science ; Vol. 2440) ISBN 3-540-44112-3
CR Subject Classification (1998): H.5.3, H.5.2, H.5, K.3.1, K.4.3, C.2.4 ISSN 0302-9743 ISBN 3-540-44112-3 Springer-Verlag Berlin Heidelberg New York This work is subject to copyright. All rights are reserved, whether the whole or part of the material is concerned, specifically the rights of translation, reprinting, re-use of illustrations, recitation, broadcasting, reproduction on microfilms or in any other way, and storage in data banks. Duplication of this publication or parts thereof is permitted only under the provisions of the German Copyright Law of September 9, 1965, in its current version, and permission for use must always be obtained from Springer-Verlag. Violations are liable for prosecution under the German Copyright Law. Springer-Verlag Berlin Heidelberg New York, a member of BertelsmannSpringer Science+Business Media GmbH http://www.springer.de © Springer-Verlag Berlin Heidelberg 2002 Printed in Germany Typesetting: Camera-ready by author, data conversion by PTP-Berlin, Stefan Sossna e.K. Printed on acid-free paper SPIN: 10870261 06/3142 543210
Foreword Welcome to the 8th International Workshop on Groupware (CRIWG 2002)! The previous workshops took place in Lisbon, Portugal (1995), Puerto Varas, Chile (1996), El Escorial, Spain (1997), Búzios, Brazil (1998), Cancun, Mexico (1999), Madeira, Portugal (2000), and Darmstadt, Germany (2001). CRIWG workshops follow a simple recipe for success: good papers, a small number of participants, extensive time for lively and constructive discussions, and a high level of cooperation both within and between paper sessions. CRIWG 2002 continued this tradition. CRIWG 2002 attracted 36 submissions from 13 countries, nine of them outside Ibero-America. Each of the 36 articles submitted was reviewed by at least three members of an internationally renowned Program Committee. This year we used a double-blind reviewing process, i.e., the reviewers did not know who the authors of the papers were. In addition, the reviewers were chosen based on their expertise and we also ensured that they came from countries and institutions not related to those of the paper’s authors. This reviewer assignment worked remarkably well, as indicated by the high average confidence value the reviewers gave their own reviews. This means that papers were usually reviewed by experts in the paper’s topic. As a consequence, reviews were usually quite extensive and contained many suggestions for improvements. I would like to thank all the members of the Program Committee for their hard work, which I am sure contributed to improving the quality of the final articles. As a result of this rigorous reviewing process, 18 papers were accepted: nine long papers and nine work-in-progress papers. This year’s program grouped these papers into six sessions on CSCL, meeting support, design and development support, awareness, evaluation and tailoring, and infrastructure. Enjoy! Finally, many thanks to all authors who submitted articles and helped to make CRIWG 2002 a success. I would also like to thank the members of the Organizing Committee, chaired by José A. Pino, for their smooth organization of this workshop. September 2002
Jörg M. Haake
Preface On behalf of the Organizing Committee for this event, I was glad to welcome the participants to CRIWG 2002, the 8th International Workshop on Groupware. I hope they enjoyed the traditional Chilean hospitality. The CRIWG workshops are rooted in the Ibero-American community of researchers, but the latest versions have evolved to become truly open and international forums for researchers working in CSCW, CSCL and their applications. This has occurred thanks to the vision and work of the members of the CRIWG Steering Committee, notably Pedro Antunes, Marcos R. S. Borges, Jesús Favela, Jörg M. Haake, and Ana C. Salgado. The Program Committee prepared a rich scientific schedule of activities. I wish to thank this Committee for its excellent work and especially its Chairman, Jörg Haake, who dedicated many valuable hours to ensure the success of the workshop. We added several social activities to the schedule, opportunities for informal discussion, establishing new research contacts, or simply getting to know new colleagues. Several other people worked in the preparation of the event. I would like to thank Margarita García, Luis Guerrero and Sergio Ochoa for their enthusiastic support and hard work as members of the Organizing Committee. Also, I am grateful to Alejandro Fernández, who organized the Doctoral Consortium. The student volunteers helped with many details. I wish to mention three institutions and a company which helped to make this event possible: The institutions are Conicyt (the Chilean Government Science and Technology Office), the Universidad de Chile (which provided support), and the Universidad de La Serena (which provided local support). The company is Codelco, which sponsored the event. September 2002
José A. Pino
Conference Organization Program Committee Chair Jörg M. Haake, FernUniversität Hagen, Germany Program Committee Members Pedro Antunes, Universidade de Lisboa, Portugal Beatriz Barros Blanco, UNED, Spain Karin Becker, PUCRS, Brazil Marcos Borges, Federal University of Rio de Janeiro, Brazil Dominique Decouchant, LSR-IMAG, France Yannis Dimitriadis, Universidad de Valladolid, Spain Henrique Domingos, Universidade Nova de Lisboa, Portugal Oswald Drobnik, University of Frankfurt, Germany Jesus Favela, CICESE, Mexico Alejandro Fernández, Fraunhofer IPSI, Germany Jutta Fleschutz, Fraunhofer IPSI, Germany Hugo Fuks, PUC/RJ, Brazil Renee Gedge, Monash University, Australia Steve Poltrock, Boeing, USA Luis Guerrero, Universidad de Chile, Chile Jörg M. Haake, FernUniversität Hagen, Germany H. Ulrich Hoppe, University of Duisburg, Germany Marcelo Milrad, Framkom and Växjö University, Sweden Christine M. Neuwirth, CMU, USA Gary Olson, University of Michigan, USA Jose Alberto Pino, Universidad de Chile, Chile Atul Prakash, University of Michigan, USA Wolfgang Prinz, Fraunhofer FIT, Germany Mike Robinson, University of Jyvaskyla, Finland Manuel Romero-Salcedo, Universidad Nacional Autonoma de Mexico Ana Carolina Salgado, Federal University of Pernambuco, Brazil J. Alfredo Sánchez, Universidad de las Américas-Puebla, Mexico Gerry Stahl, Fraunhofer FIT, Germany Ivan Tomek, Acadia University, Canada Gert-Jan de Vreede, Delft University of Technology, The Netherlands Martin Wessner, Fraunhofer IPSI, Germany Weigang Wang, Fraunhofer IPSI, Germany Conference Chair José A. Pino, Universidad de Chile, Chile
X
Organization
Reviewers Pedro Antunes Beatriz Barros Blanco Karin Becker Marcos Borges Dominique Decouchant Yannis Dimitriadis Henrique Domingos Oswald Drobnik Jesus Favela Alejandro Fernández Jutta Fleschutz Hugo Fuks Renee Gedge Steve Poltrock Luis Guerrero Jörg M. Haake H. Ulrich Hoppe Marcelo Milrad Christine M. Neuwirth Sergio F. Ochoa Gary Olson José Alberto Pino Atul Prakash Wolfgang Prinz Timothy Read Mike Robinson Jessica Rubart Manuel Romero-Salcedo Ana Carolina Salgado J. Alfredo Sánchez Gerry Stahl Ivan Tomek Gert-Jan de Vreede Martin Wessner Weigang Wang
Table of Contents
Groupware and Text Technologies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Christine M. Neuwirth
3
Groupware Goes to School . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Gerry Stahl
7
Collaborative Learning in a Web-Accessible Workbench . . . . . . . . . . . . . . . . . 25 J.M. Martins Ferreira, Gustavo R.C. Alves, Ricardo Costa, Nick Hine Document Management in a Computer-Integrated Classroom . . . . . . . . . . . . 35 Nelson Baloian, Alexander Berges, Stephan Buschmann, Katrin Gaßner, Jens Hardings, Heinz Ulrich Hoppe, Wolfram Luther Handheld CSCW in the Meeting Environment . . . . . . . . . . . . . . . . . . . . . . . . . 47 Pedro Antunes, Carlos J. Costa Effect of the Coordination Modes in Supporting Group Multiple Criteria Decision Making in a Distributed and Asynchronous Environment Juan Carlos Leyva L´ opez, Dina Esperanza L´ opez Elizalde
61
A Cooperative Visual Hypermedia Approach to Planning and Conducting Virtual Meetings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70 Weigang Wang, J¨ org M. Haake, Jessica Rubart Towards UML-G: A UML Profile for Modeling Groupware . . . . . . . . . . . . . . 93 Jessica Rubart, Peter Dawabi Designing the Communications Infrastructure of Groupware Systems . . . . . 114 Sergio F. Ochoa, Luis A. Guerrero, David A. Fuller, Oriel Herrera A Component-Based Architecture to Support Collaborative Application Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134 Ana Paula Terra Bacelo Blois, Karin Becker Before Getting There: Potential and Actual Collaboration . . . . . . . . . . . . . . . 147 Alberto L. Mor´ an, Jesus Favela, Ana M. Mart´ınez-Enr´ıquez, Dominique Decouchant Intelligent Awareness in Support of Collaborative Virtual Work Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168 Rosa Alarc´ on, David Fuller The 3-Ontology: A Framework to Place Cooperative Awareness . . . . . . . . . . 189 Edmundo P. Leiva-Lobos, Eliana Covarrubias
XII
Table of Contents
Evaluating Collaborative Learning Processes . . . . . . . . . . . . . . . . . . . . . . . . . . 203 C´esar A. Collazos, Luis A. Guerrero, Jos´e A. Pino, Sergio F. Ochoa The CSCW Lab for Groupware Evaluation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222 Renata Mendes de Araujo, Flavia M. Santoro, Marcos R.S. Borges Tailoring Group Work . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232 Alejandro Fern´ andez, J¨ org M. Haake, Adele Goldberg Building Groupwares over Duplicated Object Systems . . . . . . . . . . . . . . . . . . 245 Hechmi Khlifi, Jocelyn Desbiens, Mohamed Cheriet Adaptive and Transparent Data Distribution Support for Synchronous Groupware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255 Stephan Lukosch COPSE-Web: An Infrastructure for Developing Web-Based Groupware Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275 Jos´e Maria N. David, Marcos R.S. Borges
Author Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285
Groupware and Text Technologies Christine M. Neuwirth Carnegie Mellon University Pittsburgh, PA 15213 USA
[email protected]
Abstract. In this talk, I will outline the history of text technologies and the ways in which they have supported groups working across time and place and changed work practices. I will focus on the rise of annotation practices and its importance to reading and writing processes, and review new technologies that are likely to change the ways in which annotation can enhance and will alter traditional reading and writing practices, both in collaborative writing and in cooperative learning to write. I will raise some directions for future research, including how professionals read and annotate, how readers might make use of annotations produced by others, and how interfaces to annotations are likely to affect communication and collaboration. I will identify outstanding research issues, research methods that are likely to be productive in furthering our theories of workplace and classroom communication, and draw implications for the design of annotation technologies in groupware.
Speaker Biography. Dr, Christine Neuwirth is Professor of English and Human-Computer Interaction at Carnegie Mellon University. In 1986, she received her Ph.D. degree from Carnegie Mellon and, at the same, time, she became a member of its faculty. Her research has focused on designing computer tools for computer-mediated communication as well as conducting empirical research that explores the effects of those tools. Early work focused on building a conceptual framework for understanding collaborative writing, coupled with the development of a "work in preparation" (PREP) Editor to study collaborative writing relationships, especially collaboration at a distance. The PREP Editor implemented an innovative "column" architecture and served as a "proof of concept" for many of the design requirements that were identified from the theoretical and empirical work. Her latest work involves exploring "authorable" visualizations as a way to mitigate or reduce attention and overload problems in electronic mail. Dr. Neuwirth is a member of the Association of Computing Machinery and has served on various advisory panels and conference program committees.
J.M. Haake and J.A. Pino (Eds.): CRIWG 2002, LNCS 2440, p. 3, 2002. © Springer-Verlag Berlin Heidelberg 2002
Groupware Goes to School Gerry Stahl Drexel University (Philadelphia, USA) & Fraunhofer-FIT (Bonn, Germany)
[email protected]
Abstract. Groupware for cooperative work (CSCW) and for collaborative learning (CSCL) have many important commonalities as well as different requirements. By transforming a generic CSCW platform into an environment to support a particular vision of education as collaborative knowledge building, we saw how functionality had to be adopted, transformed and refined to meet the specific educational social setting. By “taking groupware to school,” we discovered the need to extend the original system into a CSCL application that could facilitate collaborative learning, knowledge building, perspective intertwining, knowledge negotiation, portfolio sharing and knowledge artifacts in active, structured virtual learning places. In the paper, we describe the resulting system and reflect on issues of design and implementation that differentiate our CSCL approach from its closely related CSCW basis. Keywords. CSCL, educational groupware, knowledge negotiation, collaborative knowledge building
1 From CSCW to CSCL With widespread use of the Internet, groupware promises to provide the kind of support to networked groups that individual productivity software like word processors and spreadsheets grant individuals. The potential of computer support for groups is perhaps even higher than that for individuals because communication within groups has until now suffered from severe constraints that may be eased by computer support. The question must still be addressed as to what groupware should aim at beyond the reproduction of pre-computer forms of group interaction. We need a vision of how networked computers can facilitate the discussion of all with all that does not require the coordination of a manager or teacher and the collaborative building of knowledge that is not restricted to the skills, memories and efforts of individuals. Perhaps CSCL can provide a model for this. When we take groupware into the schools in a principled and explorative way we may see how computer support can be designed to transform teacher-centric learning into collaborative learning and transcend knowledge management with knowledge building. Academically, the exploration of groupware has historically been split into two separate domains: CSCW and CSCL, which address issues of computer support for cooperative work and collaborative learning, respectively. Each domain has its own conferences, journals and adherents. CRIWG is one of the few places that these come J.M. Haake and J.A. Pino (Eds.): CRIWG 2002, LNCS 2440, pp. 7–24, 2002. © Springer-Verlag Berlin Heidelberg 2002
8
G. Stahl
together. This distinction has not been based on a conceptual analysis that might motivate and justify such a division. Certainly, the two domains have at least sufficient commonalities that they can borrow extensively from one another. Why should CSCW and CSCL be distinguished? There is at least a superficial rationale for this. CSCW is concerned with the world of work, where people must accomplish commercially productive tasks, while CSCL is concerned with the world of schooling, where students must learn basic skills that will in the end allow them to function effectively in the world of work and in adult society generally. These are very different social contexts. Perhaps the clearest lesson of groupware research to date has been the importance of taking into account the social context – the motivations, prevailing practices, political constraints – in which software is to be used. By this criteria, the two domains are indeed distinct and should be treated so. However, it is also true that in today’s “knowledge society” work is often knowledge work that requires constant learning [4, 21]. In the interesting cases, work – whether individual or cooperative – is not the repetitive carrying out of well-known tasks that were learned once and for all in school, but work itself centrally involves various learning tasks. Work may require just-in-time learning, where existing information must be found to solve a current problem. Or it may involve inquiry learning, where solving a wicked, ill-structured or non-routine problem requires the building of new knowledge. Similarly, the learning that is needed to prepare students for an effective role in tomorrow’s knowledge society cannot consist merely of the transfer of existing knowledge into passively receptive minds, but must guide the students to develop personal and social skills that will allow them to find information relevant to unanticipated problems and to engage in inquiry processes. In this sense, the application domains of CSCW and CSCL are closely related; it is not just a matter of both having to support activities of groups. This paper reports on the results of trying to extend a basic CSCW system for a typical CSCL application. We started with BSCW, a well-known and widely used groupware system [1, 2, 8]. Used by over 200,000 people since 1995 when it was developed at the Institute for Applied Information Technology – FIT (previously a GMD Institute, now a Fraunhofer Institute near Bonn, Germany), BSCW provides a system of autonomously managed Web-based workspaces that can be used by members of a workgroup to organize and coordinate their work. These workspaces are central access points for shared documents, including folders for organizing them and a wealth of functionality for knowledge management. Although BSCW has been used in many classrooms, especially at universities in Europe, it is clearly a CSCW application. We wanted to adapt it specifically for the social setting of schools: to see what it would mean to transform it into a CSCL application. We undertook this within a European Union project named ITCOLE (Innovative Technology for Collaborative Learning and Knowledge Building) [10]. With its emphasis on collaborative knowledge building, this project aims primarily at supporting group discourse. It differs from many other educational approaches, that strive to convey information in the form of curriculum content or videotaped lectures, which can perhaps be done with a CSCW system. In ITCOLE, we assume that students can find information on the Internet or in documents uploaded into the system, and that what needs CSCL support is: the collaborative reflection on this information (sharing and annotating), the building of group knowledge (discussion from perspectives) and
Groupware Goes to School
9
the determination of what is to count as produced knowledge artifacts (knowledge negotiation).
The focus of the ITCOLE Project differs from that of BSCW, which is on the archiving and sharing of existing knowledge artifacts. Thus, while we wanted to take advantage of important forms of CSCW support like knowledge sharing and social awareness, we also wanted to go beyond the management of established knowledge to the creation of knowledge that is innovative within a learning community that develops, defines, sanctions and shares its knowledge. This paper reports on how we designed a CSCL system by transforming a CSCW system. It begins with a scenario (section 2), illustrating the vision of how our new system, called Synergeia, might be used to facilitate collaborative knowledge building in a typical collaborative classroom. The system is named Synergeia in recognition that the whole can be much more than the sum of its parts. Thus, the system strives to support the synergistic construction of knowledge at the group level that is quite distinct from what any of the students could produce on their own. The scenario anticipates the pedagogical concepts that are then presented in the next section (section 3). For instance, the “folders” of BSCW are referred to as “virtual learning places” because the metaphor is no longer one of passive storage containers, but of locations within which active knowledge building is supported. The functionality associated with the pedagogical concepts is described with the respective concepts. Other Synergeia functionality for students, teachers, administrators and researchers is then summarized (section 4). Following a brief discussion of the system infrastructure (section 5), reflections on the attempt to adapt CSCW to CSCL are presented (section 6). The Synergeia groupware is already going to school. Teachers and students in Italy, Greece, the Netherlands and Finland have begun to use an initial version within the ITCOLE Project. An additional 50 classrooms in these countries will use the revised version described in this paper during the Fall. The revisions are based on early feedback from pedagogic researchers, teachers and students to the initial version, which was itself based on extensive experience with related systems in both CSCW and CSCL contexts.
2 Scenario of CSCL Support Synergeia is designed to support collaborative knowledge building. However, it must also be flexible enough that teachers in various countries can use it for a broad spectrum of educational approaches. The scenario illustrates what might be called the “default usage” of Synergeia. This means that Synergeia was designed to make it especially easy for teachers to set Synergeia up for structuring knowledge building this way, although other ways of using it are also supported. Meet Carla, a student in a course on The Human Brain. Her teacher has enrolled her in the course and assigned her to a workgroup on the role of Vision. When Carla first logs in, she can see a folder for her course on “The Human Brain.” In addition, there is a “personal knowledge building perspective” for her to jot down her own ideas.
10
G. Stahl
Carla clicks on her course to view its contents. She sees a folder for her project group within that course called “The Vision Team.” She notices in the size column that there are already some items in the group learning place, so she clicks on “Group: The Vision Team” and goes there (see Figure 1). Carla works with the other students in her project team to collect websites and other documents about how vision works as part of the human brain. As they collect new information, the team members discuss what they have found and begin to build theories about vision in the group knowledge building perspective (see Figure 2). This discussion motivates them to do more Web searches and to try to answer questions that they pose to each other. Gradually, they converge on an understanding of their topic and put together a portfolio of what they have learned, to share with the other members of the course. As they begin to explore the physiology of vision, different students come upon different explanations. Some find discussions of vision in terms of light dynamics, lenses and the stimulation of the retinal sensors; others read about chemical reactions in the sensors and nerve connections; while others discover presentations involving electrical charges in neurons. As these different findings come together in the group knowledge building perspective, the concepts and claims in the notes interact. Efforts to question one another and to synthesize multiple notes raise new questions, hypotheses and insights. Carla is a shy girl who does not normally participate much in face-to-face class discussions. She is afraid that her ideas are not very good and she hesitates to share them until she has had time to think about them and to compare them with other ideas or to check them out by collecting more information. So when she sees an interesting idea in the group learning place, she often copies it into her personal perspective and works on it there, where no one else will see it right away. During the week, her
Fig. 1. The Group learning place. Here is where collaboration takes place. Documents, websites and other forms of information are collected, shared, organized, analyzed and critiqued.
Groupware Goes to School
11
Fig. 2. The group knowledge building area. This area provides an overview of the discussion within a group and offers an interface for engaging in the knowledge building process. personal area fills with the results of new web searches, documents she has collected or edited, notes that she has copied from the group area, and ideas she has jotted down in her own knowledge building area. When she is happy with some of her ideas, she copies them and related documents into the group area to see what her team mates will say about it. Now she has some confidence that her ideas are thought through and can stand up to inspection by others. Even if her suggestions are not adopted unchanged in the end, they will be taken into the group discourse as serious contributions. At some point in the collaborative knowledge building process, Carla thinks that the group members have something almost ready to present to the course as a “knowledge artifact” or part of their team “knowledge portfolio.” So she puts this information together in a folder named “Good documents we found about vision” and makes a proposal to share this with the course. Now the group area contains a proposal folder named “The Vision Team’s proposal 1” (see Figure 1). In addition to the folder named “Good documents we found about vision,” this proposal folder contains a voting interface and a knowledge building area for discussing what changes are needed before the group members are ready to agree to send this folder to the course learning place as their “knowledge portfolio.” Once the team has decided to send their portfolio to the course learning area, it can be discussed by everyone in the course and evaluated by the teacher as a product of the group’s knowledge building effort. This might be the end of a curriculum unit, or it might lead to further inquiry and knowledge building. The same groups might continue to work together or the teacher and students might create new groups in new learning places. Our scenario ends here, but the learning continues.
12
G. Stahl
3 Pedagogical Requirements for Synergeia The adaptation of BSCW for school classrooms involves responding to a particular pedagogical vision, and providing support for the particulars of that vision. To understand the difference that the CSCL setting makes to system design, one must understand the pedagogical concepts that drive the adaptation. The central concepts of collaborative knowledge building are presented in the current section, along with a description of the support implemented for them in Synergeia. Note that although Synergeia is most useful and powerful if used to support what is here called “collaborative knowledge building,” the system has been designed to be flexible so that teachers with different curricular goals and pedagogical approaches can adjust it to their needs. The design process tried to incorporate the following influences: Adoption of pedagogical principles of collaborative knowledge building and progressive inquiry. Incorporation of effective functionality from related CSCL and CSCW systems, both commercial and research. Adaptation to the social settings of constructivist European classrooms. Support for social practices involved in collaborative learning such as that described in the preceding scenario. Flexibility for teachers in different countries and pedagogical cultures to adapt the system to their varying approaches. 3.1
Collaborative Knowledge Building
The design of Synergeia is guided by an educational approach that stresses the construction of knowledge within a community of learners, typically including students and more experienced teachers. The idea is that new knowledge will be created through the investigations and discourse of the group. While there are important roles for individual student thinking as well as for teacher guidance, there is also emphasis on sharing, critiquing and building upon each others’ ideas to arrive at deeper knowledge of a topic within a learning community [3, 13]. “Group learning” is to be understood here in an emphatic sense: it is the group that learns, knowledge is constructed by the group itself. Whereas CSCW supports the sharing and archiving of knowledge that is contributed by cooperating individuals, CSCL supports the functioning of a collaborative group so as to build knowledge that is the shared creation and property of the group. Primarily, group knowledge arises in discourse and is preserved in linguistic artifacts, whose meaning is interpreted within group processes [15, 16]. Because knowledge building proceeds largely through discussion, each personal, group and course perspective automatically contains its own knowledge building area in Synergeia. These knowledge building areas have extended the basic threaded discussion facility of BSCW. While threaded discussion support is derived from CSCW, it requires more nuanced and specialized support in CSCL. Notes from one perspective can now be copied to other virtual learning places in other perspectives,
Groupware Goes to School
13
and notes from elsewhere can be pasted here. Notes in these areas are now included in system searches, because they form an important part of the knowledge in the system. The user interface of the threaded discussion areas in Synergeia has been carefully designed to encourage thoughtful, focused, deep knowledge building. Below the current note is a display of all other notes entered in the same knowledge building area. The notes can be displayed as indented threads, indicating which notes reply to which other notes. Alternatively, the notes can be sorted by author, date or thinking type. Sorting by author shows quickly who is contributing the most; by date shows the order in which ideas were written; by thinking type indicates which parts of the knowledge building process have or have not been emphasized so far. In each of the sorted displays, the display of the content of the notes can be toggled on and off so that one can see either just the list of the notes or the full content of the whole discussion. This is useful so that one can quickly get an overview of the structure of complex discussions or see the full content of brief discussions. As seen in Figure 2, the note that is currently being read is at the top of the screen. With it are a number of buttons for building further knowledge, such as adding a “Reply to this Note.” The background color of this part of the display corresponds to the note’s thinking type. The different thinking types are described on a help page reached with the “Thinking Type Descriptions” button; the corresponding background colors can be seen there. 3.2
Thinking Types
It is important for students to reflect upon the role that a note they are entering will play in the knowledge building process. Both note titles and categories should be chosen carefully [5]. Discussion within the knowledge building areas is scaffolded with a set of thinking type categories for the notes. Before someone can enter a note, they have to decide what category of note they want to add to the existing discussion. For instance, do they want to state the problem that is to be pursued, propose a working theory, deepen the knowledge that is already there, or make a meta-comment about the knowledge building process that is taking place? It is possible to have different sets of thinking types for different approaches to knowledge building. For instance, the preceding examples illustrate categories of inquiry learning notes. Other categories are appropriate for brainstorming, debate, design rationale, etc. Thinking types take on a much more important role in Synergeia than in BSCW, where they were limited and rarely used. 3.3
Virtual Learning Places
The most basic function that Synergeia offers is a set of workspaces on the Internet where people can share ideas, documents, web links and other objects. Whether people using Synergeia are in the same room during the same class period or they are in different countries working at different times, they can share their work and collaborate within these virtual learning places. Teachers and students can create new places whenever they want for any special needs they have. Places can be created to store new collections of documents. Synergeia offers several special kinds of learning
14
G. Stahl
places, such as Courses, Groups, Proposals and Knowledge Building areas that have special features. Although these virtual learning places are based upon BSCW folders for storing documents where they can be accessed by other group members, these places are structured to support specific collaborative knowledge building activities like negotiation of group knowledge. The CSCW workspaces are appropriated and specialized to support a variety of CSCL activities. A major advantage of Synergeia over threaded discussion systems in commercial groupware systems is that the discussions in Synergeia are separated into personal, group and course perspectives in different virtual learning places, so that different topics are not mixed together and it is easier to keep up with relevant discussions without being overwhelmed by contributions of many other people who are investigating other issues. The same is true of the documents, web links, etc. that are collected in the various learning places. It is important that the network of learning places be structured in a way that seems natural to the students using them. The basic structure of learning places follows the normal structure of schools, with students in projects within courses. It should be easy to see what is available and relevant, and to navigate to it easily. Therefore, when a student logs in that student’s personal learning place is displayed; the personal place includes a list of the student’s courses and the course learning place includes the student’s groups. It should also be easy to copy documents and ideas from one place to another. At the same time, because these places are generally shared, it is also important to protect the contents so that one person cannot change or delete someone else’s work arbitrarily – as can occur in BSCW. By default, Synergeia defines appropriate connections between places and reasonable access rights to them when people are registered for courses and groups. Each user, group and course automatically has its own knowledge building area – additional areas can be added or the automatic ones can be deleted. Also, plain places that do not have the special characteristics of groups and courses can easily be added. Thus, the structures, navigation paths, access rights and facilities within Synergeia are designed for usage within the social practices prevailing in school settings, with adequate flexibility to allow for broad variations within these settings. 3.4
Perspectives
The approach to building knowledge in Synergeia is based on the idea of intertwining personal and group perspectives [17]. All knowledge involves interpretation from specific perspectives [12, 14]. In collaboration, personal interpretations of what is said in group discourse interact to form shared understandings. [16] The default structure of Synergeia provides a network of virtual learning places that are set up for personal, group and course uses. These perspectives support a range of pedagogical models that are favored in the different countries participating in the ITCOLE Project: Community of learners (Italy). The areas in which work, communication and learning take place are structured to reflect the structure of the community, with its sub-groups and members.
Groupware Goes to School
15
Progressive inquiry (Finland). The inquiry process progresses through collaborative discourse within groups as well as through reflection by individuals. Conceptual change (Greece). Learning is treated as a social process in which the understanding of individuals is affected by and grounded in the discourse of the community. Shared and individual regulation process (Netherlands). The intertwining of shared group and personal individual ideas leads to new understandings at all levels. Thus, there are private personal learning places where only one person can add notes, documents or sub-folders and can come back and look at these, modify them, or copy them to a group place. These are places to develop your personal perspective on a topic without worrying what other people will think about what you are doing. Because your personal ideas and documents are in Synergeia, they can be easily related to ideas in other learning places. Allowing the system for group work to be used for personal reflection as well has two major advantages. First, it encourages system use and familiarity. A major problem with groupware systems can be that they require users to log in every day to see what it new there; if people do not use the system for their normal activities then they tend not to log in frequently enough. Also, if people have to use too many different systems for their work then it is difficult to become proficient in them all. Second, by conducting both personal and group work in the same system, people can easily move ideas and documents back and forth between the two. In particular, Synergeia is designed to allow quick cut and paste of items and sets of items from any visible learning place to any other. Then there are the group learning places where most of the collaboration and knowledge building gets done. Here everything is shared with the other members of the team or work group. Students who are not in the group cannot modify or comment on work in the group until the group decides to share something with the whole course. Knowledge usually emerges from a group perspective [15]. And there are also course learning places, where all the smaller work groups or project teams within the course contribute the knowledge they have built up. For instance, a teacher who has a course with 30 students might divide them into 6 or 7 teams. Perhaps each team would develop a portfolio to present their ideas to the course. Each team might have the same task or they might divide up different aspects of the larger course topic. After they develop their group portfolios, they can share and debate within the whole course perspective. While CSCW systems provide support within a generic group, a CSCL system should support various levels from individual to large group, with fluid navigation and transfer of contents among the levels. 3.5
Negotiating Knowledge Artifact Portfolios
Sometimes it is pedagogically important for groups to negotiate the promotion of knowledge from one perspective to another, such as the decision to make products of a group available to the larger course. A teacher can set up course learning places so that the only way that new documents, maps and folders can be added is by a group developing a knowledge portfolio or knowledge artifact in their group learning place
16
G. Stahl
and then deciding to move this into the course place. Making this kind of group decision is called knowledge negotiation in Synergeia. There is a negotiation mechanism to help a group reach this decision and move the knowledge they have created into the course learning place, where it can be shared and discussed by all members of the course. By specifying the negotiation option for a course, the teacher in effect declares that the only knowledge allowed in this learning place is knowledge created by groups. In CSCW negotiation, such as Herrmann’s or Wulf’s model [7, 17, 20], commenting on one’s voting serves the purpose of expressing one’s supposedly preexisting opinion. In Synergeia, engaging in negotiation of knowledge building is participating in a group reflection on shared knowledge. This can be seen in the thinking types of the notes contributed. In CSCW the note format stresses who the author is and may characterize the notes as a “pro” or “con” opinion (as even in BSCW); in Synergeia the note must first of all be determined to be a particular aspect of the knowledge building process, such as a problem statement, a working theory or a summary statement. Knowledge negotiation is thereby explicitly structured as a collaborative group effort, where notes written by individuals must fit into the group process and are categorized by their function in the group thinking, not the individual. Negotiation in a knowledge building context is essentially different from that in a knowledge management or group decision situation [18]. In other groupware settings, negotiation is conceived of as a straw vote to determine how people’s pre-existing opinions are distributed on alternative options that have been proposed [7, 9, 20]. In a collaborative knowledge building setting, however, it is a matter of further refining the proposed knowledge artifact. Voting serves just to signify that the participants are generally satisfied that the artifact represents their group knowledge, and can it can be shared at the course level as a knowledge portfolio contributed by their group. The important part of the negotiation process is the evolution of the knowledge itself in parallel with the group discourse about it. When members of a group learning place have built a knowledge artifact – such as a collection of websites, a PowerPoint slide presentation, a concept map, or a portfolio of texts and pictures – they can decide to copy it to their course learning space to share with members of other groups in their course. This result of their collaborative work as a group may be a final product that the teacher will evaluate or it may be an intermediate product that they want to share and get feedback on from other people. If a course has been defined to require negotiation, then students in that course must go through a formal negotiation procedure to copy a proposed knowledge artifact portfolio to the course learning space. The purpose of this is to ensure that all or most people in the group agree to have the proposed portfolio represent the knowledge that the group has built together. (If negotiation is not required in the course, anyone can simply copy an item from the group place into the course learning place.) To use the negotiation procedure, a student must select items for their portfolio and execute the “Negotiate” command. This will create a portfolio proposal in the group place. The portfolio proposal interface includes a voting area that allows group members to vote on submitting the portfolio when they are happy with it. Within the portfolio are:
Groupware Goes to School
17
1. 2.
the selected portfolio knowledge artifacts, and a negotiation knowledge building area for discussing changes that should be made to the proposed portfolio. Students use the negotiation knowledge building area to negotiate changes that they think should be made within the portfolio. They make changes in the portfolio that they think will make it acceptable to all or most people in their group. When they like the way the portfolio looks, they vote to approve it. Each person who submits an approval or disapproval vote must enter a statement justifying their vote; this statement is automatically incorporated into the negotiation knowledge building area where it is included in the negotiation discourse and can be discussed. When all or most of the people in the group have voted for the portfolio, it is automatically copied to the course learning place. The negotiation knowledge building area is copied with the portfolio folder so that members of the course can see what was said about the portfolio. Students may want to make summary comments in this area to say what they think is important in the portfolio. If they still have criticisms of the portfolio or if they would like course members to discuss certain ideas about it, they can put that in the area as well. 3.6
Concept Maps
In building knowledge, it is often useful for a group to discuss how the concepts they are using are related to each other. One method for doing that is for the group to construct a concept map which diagrams these relationships. Synergeia provides a whiteboard called MapTool for people to work together simultaneously to sketch a concept map. The whiteboard is accompanied by a chat window to support coordination of this task and interpretation of the symbols in the map. Students and teachers can open the MapTool in course and group learning places and in proposal portfolios. To work with other members of a proposed portfolio, work group or course, they go to the learning place for that portfolio, group or course. At the top of the screen is a list of all members of the place. Those who are currently logged in to Synergeia have their names shown in bold; if they are active in MapTool, their name is in red. This is a form of social awareness which has been added to BSCW; it lets people know who is involved in MapTool in this learning place. Each proposed portfolio, group and course learning place has its own version of MapTool. When a MapTool session is first started, the last map is automatically opened so that work on it can be continued if desired. You can also reset the MapTool to start with a blank whiteboard. When other members join an active MapTool session, they see the current state of the whiteboard and the chat window, so they can catch up on what has already been done in there. At any time, the current state of the work in MapTool can be saved. Then a student can go into the learning space and make a copy of this map. The saved map can be opened as a JPEG graphics file. The student can save this file in a Word document, a PowerPoint slide show, a larger graphic file or simply as a JPEG file in a sub-folder. This way, collaborative work in MapTool can be documented as part of a report or knowledge portfolio.
18
3.7
G. Stahl
Roles and Personalization
Synergeia defines roles for students, teachers, guests, mentors, etc. This gives people in these roles the power to execute certain menu functions, such as to read, edit or delete objects in a learning place. When someone is invited into or registered for a particular learning place (such as a course or group) they are invited or registered as a member with a specific role (such as student). It is possible to change a user’s role, to define new roles and to add new sub-folders where the user has a different role. Whereas roles in BSCW were generic and rarely used, in Synergeia they capture important distinctions between people based on power and knowledge in school settings. These roles must be adapted to different kinds of learning spaces. For youthful users, it is important to make software more fun to use. Personalization and customization facilities allow users to adapt the system to their own preferences and to feel that the systems is “theirs.” Synergeia users can personalize the user interface by including a picture of themselves in the upper lefthand corner of the screen next to their username. This picture will represent them at other places in the Synergeia interface as well, such as when knowledge building notes are sorted by author. There are many functions for customizing the Synergeia interface. A student can: specify which columns to display for details related to sub-folders and documents. change the size of the displayed text. sort the listed sub-folders and documents in different orders. toggle on and off the display of menu shortcut icons below the main menu. toggle the descriptions below the names of sub-folders and documents. toggle the contents below the titles of knowledge building notes. Students can set a variety of details about how the Synergeia system will work for them. They can: change their password. set the location for their picture. enter their email address or home page. set their system preferences. Students are automatically considered “beginners” as users of Synergeia. This means that the menus they see are not full of options that are intended for more experienced users. They can change to “Advanced” or “Expert” status when they feel ready to access more menu items. For younger students in primary school, a new “primary” profile has been defined; it makes the interface simpler by removing many menu items and shortcuts to make student usage simpler.
4 Additional Functionality in Synergeia Section 3 described the pedagogical requirements for Synergeia that distinguish it from related work. Synergeia is focused on the needs of small collaborative groups of students, guided by teachers who structure and facilitate their interactions. By contrast, most commercial systems are oriented to administrative concerns such as
Groupware Goes to School
19
delivering pre-defined content, tracking attendance and test results, handling homework assignments and conducting student evaluation. At best, systems like LearningSpace and WebCT provide basic CSCW functionality for sharing documents and communicating. Because systems like Lotus Notes or Blackboard cater to corporate and professional training applications, they provide generic discussion forums, without specialized thinking types or workgroup perspectives structured in response to classroom cultures. Alternative approaches like Swiki [6] systems also lack the tailoring to classroom needs due to the generality of their functionality. At the other extreme are CSCL systems that are more specialized for particular pedagogies, like the STEP system to support problem-based learning [19]. CISLE/ KnowledgeForum [13] is very similar to Synergeia – because its developers began the tradition in which the ITCOLE Project is firmly planted. Synergeia also incorporated features from FLE [11] and WebGuide [17], research prototypes that led to its conception and prototyped much of the functionality incorporated in it. Synergeia is unique in combining the features of perspectives, multiple thinking type sets and negotiation with threaded discussion to support collaborative knowledge building. It also features a rare integration of synchronous and asynchronous support. In addition to the pedagogically motivated features, Synergeia provides a wealth of functions from BSCW. Some of these have been modified or extended to allow students, teachers, administrators and researchers to take advantage of the core Synergeia functionality. Student actions have been modified to simplify the uploading of the user’s picture; uploading, archiving and versioning of documents, images and websites is already well supported by the inherited BSCW commands. Likewise, the ability to search the Web, review hits, rate URLs and store shared bookmarks was already available. Students can set up new virtual learning places and invite friends to them, as well as starting new knowledge building areas and initiating MapTool sessions. Social awareness is well supported with BSCW’s info, events and history systems. In addition, Synergeia added displays of the names of course and group members, with indications of who is currently active in Synergeia or MapTool. Considerable support for teachers has been added. Teachers can register lists of students in the system and assign them to courses and workgroups easily. Students no longer have to have their own email addresses in order to be registered. Teachers can define course and group learning places, with a number of options for negotiation and access; this gives teachers considerable control in structuring the use of Synergeia. They can, of course, seed a learning place with documents and a knowledge building area with starting questions for discussion. When a new knowledge building area is created, the teacher can select which set of thinking type categories will be used: “knowledge building,” “scientific theory,” “negotiation,” “debate,” “discussion” or “brainstorming.” Teachers can revise the parameters for negotiation, such as the percentage needed for a majority vote. They can also over-ride the voting process to move proposals from group to course places – or even in the opposite direction. Although Synergeia is currently run on a central server in Germany, it can be downloaded to local sites to overcome Internet delays in schools with slow connections. The system administrator registers an initial set of teachers and researchers to use Synergeia. The administrator can also translate all terminology in the interface, including the sets of thinking type categories, as well as re-define the actions associated with various user roles. The entire Synergeia interface has been
20
G. Stahl
translated into Italian, Greek, Dutch and Finnish from the English original. Administrators can modify the translation files. Users select the language they want – by default it corresponds to their browser language setting. In addition, functionality has been added to assist researchers who want to analyze the usage of Synergeia. There are now log files that track all actions in BSCL, the contents of all knowledge building areas and all actions in MapTool. The log files can be analyzed with special tools or copied into a spreadsheet. Knowledge building areas can be printed out in various formats.
5 The Synergeia Architecture The present section briefly indicates how the technological infrastructure of BSCW was extended in response to the needs of the classroom setting. Technically, Synergeia consists of the following three components: BSCW. This is the Basic Support for Cooperative Work system. It is a Web-based system designed to support teams of adult professionals working together and sharing documents. It provides mechanisms for uploading, downloading, versioning and archiving of many kinds of documents. It also supports Web searches, annotations and ranking. BSCW is written in Python as an object-oriented set of cgi scripts. It includes a persistent store for objects. The server runs in Windows or Unix and the client can be displayed in any Web browser. Interestingly, the BSCW technology is literally a technology of extensibility; the cgi scripts extend the functionality of a core webserver like Apache or IIS by means of standard HTTP calls. This makes BSCW an attractive basis for further, open-ended extensions. BSCL. This is the set of functions and interfaces that adapts the BSCW software to collaborative knowledge building in K-12 classrooms. It includes the functions to create personal, group and course learning places and to register users in these with specific roles. It also includes the knowledge building interface, sets of thinking types and support for negotiation. BSCL is implemented as a Python Package that extends BSCW and that interfaces with MapTool. Packages are a flexible technology for modular extensibility in object-oriented languages like Python. BSCL is one of several packages that extend BSCW and it is possible to create new packages that extend BSCL itself. MapTool. This is a collaborative whiteboard that students in a group or course can work on simultaneously (synchronously) to construct concept maps and other simple diagrams. It includes a chat window for coordinating and discussing the drawing. The maps are stored in BSCL learning places. Synchronous support for the MapTool Java applet client is provided by the Ants system, using the Elvin server. The inclusion of MapTool in the Synergeia system is an experiment in extending BSCW with synchronous components, where user information, drawings and chat data must be stored in and retrieved from BSCL’s database by MapTool.
Groupware Goes to School
21
6 What Groupware Can Learn by Going to School Much has already been learned about the differences and similarities of CSCW and CSCL groupware support through the process of designing and implementing Synergeia. The school setting has special characteristics that make certain functionality particularly important and that require specific transformations of other functions. Many such adaptations and extensions have been illustrated in the preceding sections of this paper. One unanticipated technical finding was the importance of mechanisms for setting specific access rights for various kinds of folders. A new version of BSCW (4.0) that was released during the beginning of the ITCOLE Project included mechanisms for defining roles. These mechanisms – which to date have only been explored in the development of Synergeia – proved particularly helpful. From an implementation standpoint, many extensions to BSCW for Synergeia are largely accomplished through the definition of special domain-specific roles, with specific access rights within various kinds of learning places. A straight-forward application of the role mechanism was to define roles for teachers, mentors, students and guests. New users are registered in Synergeia with one of these roles. The role determines what actions the user can undertake within his or her personal learning place. For instance, a user who is registered as a teacher may create courses and groups or redefine negotiation parameters; a student user may upload documents; and a guest may only view contents in Synergeia. A teacher has special powers to delete offensive materials, and so on. A mentor also has many of these powers that students do not have, but does not have the ability to create courses and groups. Users have more control over objects that they created than over other objects, such as the ability to edit or delete them. A user can invite other users to folders and can reset or modify roles, but can never assign abilities that exceed that user’s existing abilities. In addition to the standard roles, special roles were defined for “course mates” and “restricted students.” These are used for special circumstances. For instance, course mates can see in their course learning places what groups exist that they do not belong to. Depending on the option set by the teacher when the group was defined, users who had student roles are re-assigned “course mate” roles, where they are able to see the name of the group listed, or else they are re-assigned the “restricted student” role, where they may enter the group learning place and view or copy – but not add to or modify – the content there. Similarly, in a course where the negotiation option was selected, all student users are re-assigned the role of restricted student. This means that they can see and copy all content, but cannot add or modify anything (except through the group negotiation procedure). This re-assigned role is inherited down into all sub-folders and sub-subfolders, etc. (as is usual for roles). This automatically prevents students in a course from changing the contents of negotiated portfolios from groups, although they can view these contents and copy them elsewhere to work further on them. In a course knowledge building area, the restricted student roles are changed back to normal student roles, so that students can participate in knowledge building discussions within the course perspective. The school setting requires much more complex control over access rights than is instituted in the normal BSCW system. The role mechanism provides a convenient,
22
G. Stahl
flexible and elegant means for defining and instituting the needed sets of access controls. This paper reflects the design of version 2 of Synergeia, which will be released to European elementary and secondary schools within the ITCOLE Project in summer 2002. It has already benefited substantially from informal feedback from the review of version 1 by pedagogic partners in the Project and from the use of version 1 by teachers and students in the winter and spring 2002. The use of version 1 is currently being subjected to extensive evaluation in each of the participating countries. It is expected that this will reveal additional groupware requirements of the school setting. Version 2 of Synergeia will “go to school” in 50 courses in Italy, Greece, the Netherlands and Finland during the fall of 2002. This will again be subjected to formal evaluation using a variety of survey instruments. Data from the log files and classroom observations will be analyzed with a mix of quantitative and qualitative methods. Results of these evaluations should provide important insight into the effectiveness of the Synergeia adaptations and extensions to groupware mechanisms presented in this paper. There are many fundamental commonalities between CSCW and CSCL groupware requirements and the two can build upon each other’s accomplishments. However, the school setting, seen from a specific pedagogical perspective, brings with it considerations that call for particular treatments. In the case of the development of Synergeia within the ITCOLE Project, we have seen that it was necessary to develop a suite of functionality that adapted generic CSCW forms of support to define a unique educational environment. It is likely that as the CSCL extensions mature through testing and usage they will feed back into suggestions for CSCW itself.
Acknowledgements. The ITCOLE Project is a collaboration of many people from universities and schools throughout Europe. The project was conceived largely by people in the Centre for Research in Networked Learning and Knowledge Building at the University of Helsinki and in the Media Lab at the University of Art and Design Helsinki. Much of the Synergeia user interface was designed by the Media Lab group. MapTool was implemented at the University of Murcia. The project manager for ITCOLE at FIT is Wolfgang Appelt. The implementation of most of the features described in this paper was done by the BSCW group at Fraunhofer—FIT, especially by Rudolf Ruland and me. To carry out the adaptation of a complex system like BSCW in a way that takes advantages of the strengths of its design and does not contradict its philosophy would not be possible without detailed guidance from the BSCW development staff, including Thomas Koch, Elke Hinrichs and Gerd Woetzel, in addition to Rudolf. I am grateful to all the people at FIT who made my year there possible, productive and enjoyable. A number of anonymous CRIWG reviewers made suggestions that significantly improved the presentation of this paper.
Groupware Goes to School
23
References 1. 2.
3. 4. 5.
6. 7.
8.
9.
10.
11. 12. 13. 14.
15.
Appelt, W. (1999) WWW-based collaboration with the BSCW system, In: Proceedings of SOFSEM ’99, Springer Lecture Notes in Computer Science 1725, Milovy, Czech Republic, pp. 66–78. Appelt, W. & Klöckner, K. (1999) Flexible workgroup cooperation based on shared workspaces, In: Proceedings of World Multiconference on Systems, Cybernetics and Informatics: SCI ’99 and ISAS ’99 (5th International Conference on Information Systems Analysis and Synthesis), Orlando, FL, pp. 34–39. Bereiter, C. (2002) Education and Mind in the Knowledge Age, Lawrence Erlbaum Associates, Hillsdale, NJ. Brown, J. S. & Duguid, P. (1991) Organizational learning and communities-of-practice: Toward a unified view of working, learning, and innovation, Organization Science, 2 (1), pp. 40–57. Gerosa, M., Fuks, H., & de Lucena, C. (2001) Use of categorization and structuring of messages in order to organize the discussion and reduce information overload in asynchronous textual communication tools, In: Proceedings of CRIWG 2001, Darmstadt, Germany. Guzdial, M. & Turns, J. (2000) Sustaining discussion through a computer-mediated anchored discussion forum, Journal of the Learning Sciences . Herrmann, T., Wulf, V., & Hartmann, A. (1996) Requirements for a human-centered design of groupware. In D. Shapiro, M. Tauber, & R. Traunmüller (Eds.), Design of Computer Supported Cooperative Work and Groupware Systems, Elsevier, Amsterdam, NL. Klöckner, K. (2001) Preparing the next generation of learning: Enhancing learning opportunities by Web-based cooperation, In: Proceedings of 10th European Distance Education Network (EDEN) Anniversary Conference 2001, Stockholm, Sweden, pp. 330– 335. Kraemer, K. & Pinsonneault, A. (1990) Technology and groups: Assessment of the empirical research. In J. Galegher, R. Kraut, & C. Egido (Eds.), Intellectual Teamwork: Social and Technological Foundations of Cooperative Work, Lawrence Erlbaum Associates, Hillsdale, NJ, pp. 375–405. Leinonen, T., Hakkarainen, K., Appelt, W., Dean, P., Gómez-Skarmetav, A., Ligorio, B., Lipponen, L., Merisaari, L., Mielonen, S., Pontecorvo, C., Sligte, H., & Vosniadou, S. (2001) ITCOLE Project: Designing innovative technology for collaborative learning and knowledge building, In: Proceedings of Ed-Media 2001: World Conference on Educational Multimedia, Hypermedia and Telecommunications, Tampere, Finland. Muukkonen, H., Hakkarainen, K., & Leinonen, T. (2000) Introduction to Fle2 Pedagogy, at http://fle2.uiah.fi/pedagogy.html. Nygaard, K. & Sørgaard, P. (1987) The perspective concept in informatics. In G. Bjerknes, P. Ehn, & M. Kyng (Eds.), Computers and Democracy: A Scandinavian Challenge, Avebury, Aldershot, UK, pp. 371–393. Scardamalia, M. & Bereiter, C. (1996) Computer support for knowledge-building communities. In T. Koschmann (Ed.) CSCL: Theory and Practice of an Emerging Paradigm, Lawrence Erlbaum Associates, Hillsdale, NJ, pp. 249–268. Stahl, G. (1993) Supporting situated interpretation, In: Proceedings of Annual Meeting of the Cognitive Science Society (CogSci ’93), Boulder, CO, pp. 965-970. Available at: http://www.cs.colorado.edu/~gerry/publications/conferences/19901997/cogsci93/CogSci.html. Stahl, G. (2002) Contributions to a theoretical framework for CSCL, In: Proceedings of Computer Supported Collaborative Learning (CSCL 2002), Boulder, CO, pp. 62–71. Available at: http://orgwis.gmd.de/~gerry/publications/conferences/2002/cscl2002/cscl2002.pdf.
24
G. Stahl
16. Stahl, G. (2002) [submitted] The complexity of a collaborative interaction, In: Proceedings of ICLS 2002, Seattle, WA. 17. Stahl, G. & Herrmann, T. (1999) Intertwining perspectives and negotiation, In: Proceedings of International Conference on Supporting Group Work (Group ’99), Phoenix, AZ. Available at: http://orgwis.gmd.de/~gerry/publications/conferences/1999/group99/group99.pdf. 18. Stahl, G., Ruland, R., Appelt, W., Hinrichs, E., & Woetzel, G. (2002) [submitted] Negotiating shared knowledge in asynchronous learning networks, In: Proceedings of HICSS 2002, Hawaii, HA. 19. Steinkuehler, C., Derry, S., Woods, D., & Hmelo-Silver, C. (2002) The STEP environment for distributed problem-based learning on the World Wide Web, In: Proceedings of Computer Support for Collaborative Learning (CSCL 2002), Boulder, CO, pp. 217–226. 20. Wulf, V., Pipek, V., & Pfeifer, A. (2001) Resolving function-based conflicts in groupware systems, AI & Society, 15 , pp. 233-262. 21. Zuboff, S. (1988) In the Age of the Smart Machine, Basic Books, Inc., New York, NY.
Collaborative Learning in a Web-Accessible Workbench 1
1
1
J. M.Martins Ferreira , Gustavo R. C. Alves , Ricardo Costa , and Nick Hine 1
2
Faculdade de Engenharia da Universidade do Porto (FEUP / DEEC), R. Dr. Roberto Frias, 4200-465 Porto, Portugal {jmf, galves, rjcosta}@fe.up.pt 2 University of Dundee (Department of Applied Computing, MicroCentre), Park Wynd, Dundee DD1 4HN, United Kingdom
[email protected]
Abstract. Web-based course management and delivery is regarded by many institutions as a key factor in an increasingly competitive education and training world, but the systems currently available are largely unsatisfactory in terms of supporting collaborative work and access to practical science facilities. These limitations are less important in areas where “pen-and-paper” courseware is the mainstream, but become unacceptably restrictive when student assignments require real-time teamwork and access to laboratory equipment. This paper presents a web-accessible workbench for electronics design and test, which was developed in the scope of an European IST project entitled PEARL, with the aim of supporting two main features: full web access and collaborative learning facilities.
1
Introduction
Web-based course management and delivery software packages are widely available on the market and are becoming increasingly popular [1]. Easier access to pedagogical contents and flexible schedules are attractive not only to students but also from the institutional point of view, where a rich catalogue of pedagogical web contents is nowadays of strategic importance [2]. However, and in spite of its fundamental importance for students in practical science domains, effective remote access to laboratory facilities is traditionally ignored in the current generation of webbased education and training frameworks. Moreover, and since teamwork plays an important role in most work assignments, facilities for collaborative learning / work are equally as important and must be able to support real-time communication in the form of audio and video conferencing, besides the traditional text-based chat. The PEARL (Practical Experimentation by Accessible Remote Learning) project was set up with the objective of overcoming these limitations [3:5]. Funded by the European IST (Information Society Technologies) programme, PEARL is a threeyear (2000-2003) project that is being developed to enable practical experimentation for students working together over the Internet or the campus Intranet. The students interact with the remote experiments much as they would in a real teaching laboratory, being able to change parameters and in some cases design experiments. They are also able to observe the results and discuss their actions, using Internetbased collaborative tools embedded in the PEARL system. It is important to stress J.M. Haake and J.A. Pino (Eds.): CRIWG 2002, LNCS 2440, pp. 25–34, 2002. © Springer-Verlag Berlin Heidelberg 2002
26
J. M.Martins Ferreira et al.
that the experiments are real, and as such have an unpredictability that cannot be replicated by simulation. PEARL presents an opportunity to widen access to real experiments that might otherwise only be offered to those able to get to a suitably equipped laboratory. Four types of experiments were selected for validation purposes: – Cellular biology, hosted by the Department of Biochemistry of the University of Dundee (UK), which uses computer controlled electron microscopes to conduct cytology studies – Visual inspection, hosted by the Trinity College at Dublin (Ireland), which is used by engineering undergraduates to carry out image analysis of printed circuit boards – Environmental analysis, hosted by the Open University at Milton Keynes (UK), designed to support a series of experiments at the residential schools for its popular foundation science course – Electronics design and test, hosted by FEUP (Faculdade de Engenharia da Universidade do Porto, Portugal), which provides a web-accessible workbench supporting three main types of experiments: test of digital and mixed-signal circuits (for final year undergraduate and MSc. students), microcontroller-based circuits (second year students) and introductory logic design (first year students) The electronics design and test remote lab was developed in the form of a workbench supporting full access via the web and is the main subject of this paper, where a specific emphasis is placed upon the collaborative learning facilities and their implications over such aspects as system design, information system management, and design of pedagogic experiments. The three types of experiments available share a common look-and-feel interface, which varies only according to experimentspecific control / observation facilities. The access protocol for the microcontroller and the introductory logic design experiments is the same and includes the following steps: i) implementation of the functional specification presented in the lab script (code design or hardware design, according to the type of experiment), which is carried out off-line; ii) design verification by simulation, still off-line; iii) connection to the remote lab server; iv) design upload (code or schematic), remote hardware reset and set up. The third type of remote experiment supported addresses the test of digital and mixed-signal circuits. While sharing the same user interface design and collaborative learning facilities, all the steps are performed on-line (because all test actions are carried out using an interactive application integrated in the user interface). A set of interim trials have already been conducted in relation to this type of experiments, providing a rich volume of data on pedagogical and technical aspects, including the implications of collaborative learning tools over the network traffic and effectiveness of learning. The architecture of the remote lab (hosting the web-accessible workbench that supports the three types of experiments) will be presented in the next section, followed by a description of the digital and mixed-signal test experiments, and a summary of relevant aspects related to experiment access and design. Finally, a summary of the main conclusions that are available so far will be presented, together with the current perspectives for future work.
Collaborative Learning in a Web-Accessible Workbench
2
27
FEUP’s Remote Lab Architecture
All PEARL experiments are based on a remote lab architecture that includes three main components: the web server, the lab server and the laboratory equipment. The web server hosts the course management and delivery software (e.g. WebCT or any other similar package), processes all the actions / requests from the user, and communicates via local area network with the lab server. This second machine interacts with the laboratory equipment, either directly or via a dedicated communication and control bus. In the case of FEUP’s web-accessible workbench, the architecture of the remote lab may be represented as illustrated in Fig. 1. PXI computer (lab server) LAN RS-232
Goepel
4
Function generator
Parallel
4
Digital I/O
RS-232 connection
1
Reset input
Multimeter
Oscilloscope
1
Analog Power -on (+5V) in output
std desktop (web server)
Internet
Analog out
Client
Remote hardware LAB
Fig. 1. The web-accessible workbench in FEUP’s remote lab. The whole infrastructure remains the same for the three types of experiments supported, which differ only in the remote hardware that is made available to the students
The lab server is implemented in the form of a 500 MHz Pentium III embedded controller that is part of a PXI rack interconnecting the various workbench instruments. This computer runs Windows NT and is responsible for controlling the following modules: – A Goepel digital I/O board supporting boundary scan, used to control and observe digital pins, and to interact with IEEE 1149.1 scan chains (for digital and mixed-signal test experiments) – A function generator board, used to provide analog stimulae in mixed-signal test experiments – A multimeter board, made available to support simple measurements of analog and digital waveforms – A two-channel 100 MHz oscilloscope, used to visualize waveforms in predefined pins, as specified in each experiment script LabView was used to build customized interfaces for all the PXI instruments referred above. A commercial tool from Nacimiento (AppletView) was then used to generate the equivalent web interfaces in the form of JAVA-based applets, which the
28
J. M.Martins Ferreira et al.
experiment designers use as building blocks to produce the user interface seen by the students (a given experiment may or may not use all the instruments referred above).
3
Digital and Mixed-Signal Test Experiments
A first set of experiments was developed to support the Design for Testability class offered to final year undergraduate and MSc. students in Electrical and Computer Engineering (ECE). The remote hardware for these experiments consists of demonstration boards containing one or more components compatible with the IEEE standards 1149.1 (standard test access port and boundary scan architecture) [6] and 1149.4 (standard for a mixed-signal test bus) [7]. IEEE std 1149.1 defines an embedded test infrastructure commonly present in VLSI components and was developed to support structural testing of digital printed circuit boards. IEEE 1149.4 is essentially an extension of 1149.1, and supports structural and parametric testing of mixed-signal circuits. These two test standards enable full controllability and observability operations via a small number of access pins (four pins for the test access port – TAP – in the 1149.1 std, and two extra analog test access port – ATAP – pins for the 1149.4 std), making it possible to detect open or short circuit faults without requiring physical access to the nodes under test. The digital and mixed-signal test experiments enable the students to interactively carry out elementary test procedures, using the JAVA-based applets to control the remote instruments, and a simple public domain application to interact with the IEEE 1149.x test access ports. 3.1
User Interface
A user interface integrating control and communication tools was built to support a first set of interim trials, described in the following section. This user interface is illustrated in Fig. 2 and provides the following main resources: – Videoconferencing channels, seen vertically on the left – Text-based chat, seen horizontally on bottom – A two-channel oscilloscope, occupying the central area (channel 0, channel 1, trigger controls, time base and display) – A function generator, seen above the oscilloscope display – Interaction with the IEEE 1149.x test access ports, seen horizontally on top It is particularly important to stress the presence of control and communication resources in the same interface, enabling videoconferencing among the students while the experiment is being carried out. Text-based chat might be considered redundant in this case, but it becomes an effective tool to register actions agreed upon by the team, which may later be printed out by each member as a session log. Notice that the various resources referred are available to the experiment designer as independent building blocks, and as such the user interface might comprise several windows, one for each specific action or PXI instrument.
Collaborative Learning in a Web-Accessible Workbench
29
Fig. 2. User interface used by the final year undergraduates and MSc. ECE students to carry out mixed-signal test experiments
3.2
Interim Validation Trials
A set of interim trials was conducted at FEUP on November and December 2001, providing important feedback concerning the proposed system architecture, usability of the interface and pedagogical effectiveness. An experiment script was previously made available to five groups of two MSc. students, specifying in detail all the actions that should be carried out. The two students in each pair were located in different rooms and could only communicate via videoconferencing and chat. The script specified which procedure was under the responsibility of each student, but they had to communicate frequently in order to agree upon the specific actions required (this was particularly important, since both were able to control the remote PXI instruments). Additionally, a tutor was available in his office to provide support and clarify doubts, who again could only be contacted via videoconferencing or chat. A typical student workplace and the remote web-accessible workbench are shown in Fig. 3. In order to explore the implications for the network operators of the campus infrastructures, measurements were made of the traffic generated during the interim trials. These measurements are a good first indication of the impact that a PEARL system will have on the campus infrastructures, and provide early data for exploitation discussions within and outside the project institutions.
30
J. M.Martins Ferreira et al.
A typical student workplace
Remote lab workbench
Fig. 3. A student workplace and the remote lab workbench during the interim trials of the digital and mixed-signal test experiments. Notice the PXI server and instruments, all contained in the rack at the center of the workbench
3.3
Network Traffic and Collaboration Tools
The EtherPeek network monitoring tool was used to capture the network data packets. This tool is able to capture all packets, or only a filtered set, within a network subnet. Statistics such as packet loss, distribution of packets between network protocols, etc., can then be extracted from the data gathered. Traffic between the lab server and the students’ or tutor’s workstations passes to them via the learning material server (which in the this case was a WebCT server), as may be seen in a detailed analysis of the network traffic logs. The total volume of traffic generated by the experiment was around 650 Kbps, of which around 170 Kbps was between the collaboration server and the various participants’ machines. The traffic between any user’s machine and the rest of the machines is around 160 Kbps. This suggests a requirement for the servers to be on a 100 Mbps LAN segment, and the user / tutor stations to be on 10 Mbps segments with good routing to the servers. The traffic data gathered for the user and tutor machines shows that HTTP traffic represents a higher share than videoconferencing traffic, which confirms the feasibility of using this type of synchronous communication facilities for collaborative work in this context. The collaboration tools chosen for the PEARL project are based on a web-based conferencing system built around a central server and browser-delivered user interfaces. The web-based approach was chosen in order to enable seamless integration with the interfaces of the experiment instruments. As far as the authors are aware, there is currently only one system available that provides these requirements, the CUWeb system marketed by First Virtual Communications. This system is an evolution of the successful CUSeeMe videoconferencing technologies, and uses a software H.323 compatible videoconferencing server. Because this server is standards compliant, a variety of software and hardware clients may be used in a single conference. Application sharing and collaboration tools are supported according to the T.120 standard, but the only viable implementation of that standard is within the NetMeeting
Collaborative Learning in a Web-Accessible Workbench
31
software from Microsoft. NetMeeting was not chosen as the principle client for PEARL however because for two reasons. Firstly, it operates as a client application alongside other applications. This would mean that rather than provide the students with a single seamless interface, the various functions of the experiment and student interactions would be provided through different applications on the students’ machines. The second reason relates to the way that the NetMeeting client generates the packets of data containing the video and audio content. NetMeeting preserves video quality in its default configuration by encoding all content in a given time period in variable length IP packets. The greater the complexity of the video and audio content, the larger the packets. Other software based clients, including the CUSeeMe video and audio engines sacrifice quality by using fixed length packets, and discarding content if it exceeds the capacity of the packets available for the specified operating bandwidth limits. This quality loss is noticeable but does not affect the information conveyed in the PEARL context. This approach ensures that, from a network management point of view, the CUSeeMe clients consume less network capacity and generate predictable network traffic.
4
Experiment Access and Design
This section will exemplify the sequence of actions required to carry out an experiment, including session booking and collaborative learning issues. Additionally, and since collaborative work aspects are a specific script design feature, the final remarks will address this topic.
4.1 Access and Booking Access to the remote lab is done via the entry page shown in Fig. 4 and requires a valid login and password, which may be obtained by filling in a registration form and submitting it to the Lab administrator. Once a valid login and password is granted, the student may then book a session, using the interface shown in Fig. 5. When accessing their own booked sessions, the students are given full control and observation privileges. If a student accesses an ongoing session, i.e. another user has booked it or is currently using the remote lab, he/she is still granted access, but only with observation privileges (i.e. it is possible to watch what the current user is doing, but not to control any of the buttons / switches present in the user interface). When a certain experiment requires collaborative work, the team members have to use the same login and password, which can be requested by any of them. After receiving the registration approval from the Lab administrator, the element that made the request may indicate the group’s login and password to the other group members. 4.2 Collaborative Learning and Script Design The lab script for the experiment on the mixed-signal test infrastructure instructs one student to control / observe the digital part and the other student to control / observe the analogue part, as summarised in table 1. The proposed experiment requires
32
J. M.Martins Ferreira et al.
Fig. 4. Entry page to the remote lab supporting the three types of experiments described
Fig. 5. Weekly schedule displayed to enable a student to book a session
Collaborative Learning in a Web-Accessible Workbench
33
exchange of information within the pair of students, since the required test procedures include coordinated actions in the digital and analogue parts. The collaborative tools are essential in this type of experiment, because they allow the students to exchange ideas and solutions, and also enable the necessary synchronization between their actions (which is facilitated by the fact that each of them sees what action is currently being carried out by the other). The data collected from the interim trials revealed the students mostly use audio and video for exchanging support information, while the tutor used the chat window essentially for answering questions posed by the students (tutor participation via chat had two benefits: it had a low impact on the network traffic and it enabled the students to keep a record of the tutor’s recommendations). Table 1. Summary of the collaborative actions required from each pair of students in the digital and mixed-signal test experiment selected for the interim trials Task
Student A (uses an integrated application to access the digital part)
Initialise test infrastructure and provide the required waveforms to the analogue inputs Check that the test infrastructure is in transparent mode
Select the required access port and initialise the test infrastructure
Place test infrastructure in observability mode (observe the signal present at the analogue output, through one of the analogue test pins)
Verify that the signal applied to the analogue input is present at the analogue output – connected to one of the oscilloscope input channels Set up the digital test infrastructure (ensuring that the analogue switching structures provide the required operating mode)
Student B (uses the function generator and oscilloscope to access the analogue part) Set up the function generator (sine wave, frequency, amplitude, etc.) Set up the oscilloscope (Volt/div, trigger source, time basis, etc.)
Help student A to determine the test vectors that will set up the digital test infrastructure as required
It is important to stress the importance of teamwork towards the effectiveness of the learning process, as became readily evident from the questionnaires filled by the students during the interim trial period. This is a well-known fact in cognitive studies and should be taken into account either in remote experimentation or in simulationbased experiments [8]. However, the introduction of collaborative work features calls for specific pedagogical skills, which frequently go well beyond the technical competence required for the design of (remote) experiments. Script design should therefore be seen as a multidisciplinary activity oriented by technical and pedagogical requirements, particularly when an increasing number of web-based communication and collaboration tools are widely available to improve the outcome of the authoring process.
5
Conclusion
The prototype validation and interim trials work done so far leads us to believe on the effectiveness of providing access to remote experiments in a collaborative context [9].
34
J. M.Martins Ferreira et al.
The trials carried out with five groups of two MSc. students were videotaped and the network traffic was monitored. At the end of the experiment, each student filled in a questionnaire and was personally interviewed by a psychologist. At the time of writing, the PEARL project is at about two thirds of its duration. Besides experiment design and production of tutor support documentation, the work currently under way addresses the preparation of the main validation trials, which are planned for November 2002, when approximately 400 ECE students attending the Microcontroller / Microprocessor class will be available to provide comprehensive information concerning usability, reliability and pedagogical aspects. The effectiveness of remote experimentation as a cognitive tool for learning was not addressed in the interim trials of PEARL, which were essentially concerned with technical and usability information, and not so much an evaluation of pedagogic impact. Moreover, its effectiveness comparatively with other cognitive tools for learning [10] will be an important issue to address in the main validation trials.
References 1.
B. Landon, On-Line Educational Delivery Applications: A Web Tool for Comparative Analysis (http://www.ctt.bc.ca/landonline/). 2. Richards, P.: MIT to make nearly all course materials available free on the World Wide Web (http://web.mit.edu/newsoffice/nr/2001/ocw.html) (April 4, 2000) 3. Cooper M., Scanlon E., Freake, S.: Remote Controlled Teaching Experiments, in Science and Engineering Subjects, Accessible over the World-Wide-Web: the PEARL project, World Conference on Educational Multimedia, Hypermedia & Telecommunications (EdMedia), Montreal, Canada (2000) 4. Cooper M., Santacruz Valencia, L.: User interface approaches for accessibility in complex WWW applications – Examples from the PEARL project, Association for the Advancement of Assistive Technology in Europe Seminar (AAATE), Hatfield, UK (2000) 5. Fidalgo, A., Costa, R., Martins Ferreira, J. M., Alves, G.: Experimenting the 1149.1 and 1149.4 test infrastructures in a Web-accessible remote Lab (without Plug-ins!), XVI Conference on Design of Circuits and Integrated Systems (DCIS’01), Porto, Portugal (2001) 6. Test Technology Standards Committee of the IEEE Computer Society, IEEE Standard Test Access Port and Boundary-Scan Architecture, IEEE Std 1149.1-1990 (includes IEEE Std 1149.1a-1993), ISBN 1-55937-350-4 (1993) 7. Test Technology Standards Committee of the IEEE Computer Society, IEEE Standard for a Mixed Signal Test Bus, IEEE Std 1149.4-1999, ISBN 0-7381-1755-2 (2000) 8. Joolingen, W.R. van: Designing for collaborative discovery learning. In G. Gauthier, C. Frasson, K. VanLehn (eds.) Intelligent Tutoring systems (202–211), Berlin: Springer (2000) 9. Martins Ferreira, J. M., Costa, R., Alves, G., Cooper, M.: The PEARL Digital Electronics Lab: Full Access to the Workbench via the Web, 13th EAEEIE Annual Conference on Innovations in Education (European Association for Education in Electrical and Information Engineering), York, UK (2002) 10. Joolingen, W.R. van: Cognitive tools for discovery learning. International Journal of Artificial Intelligence in Education, 10, pp. 385-397 (1999)
Document Management in a Computer-Integrated Classroom 1
2
2
2
Nelson Baloian , Alexander Berges , Stephan Buschmann , Katrin Gaßner , 2 2 2 Jens Hardings , Heinz Ulrich Hoppe , and Wolfram Luther 1
2
Universidad de Chile, Departamento de Ciencias de la Computacion, Blanco Encalada 2120, Santiago, Chile {NBaloian}@dcc.uchile.cl
University of Duisburg, Institute for Computer Science and Interactive Systems, Lotharstr. 65, 47048 Duisburg, Germany
[email protected], {buschmann, gassner, hardings, hoppe, luther}@collide.info www.collide.info
Abstract. This paper reports on a work in-progress scenario of a computerintegrated classroom (CiC) with a focus on document management and document sharing. Following a brief introduction on the topic of distributed (distance) and non-distributed (face-to-face) learning, the system´s functionalities and architecture are being described, as well as the file structure to be found in the document archive. The system uses a unique type of XML document that can be created and edited by the FreeStyler application. The paper then concludes with a short description about the future work on the project.
1
Introduction
Traditionally, most of the research efforts in Computer Supported cooperative Learning (CSCL) areas have been dedicated to develop distance learning scenarios (for a good covering of this issue see [4]), still most learning activities take place in the traditional classroom, i.e. in a face-to-face learning scenario. It is still an open question if future learning will take place in the more de-personalized way of “virtual learning” or continue in the traditional style. Meanwhile, there are still classrooms, and there are people, namely teachers, whose responsibility it is to organize classroom learning. Accepting this reality, we can still ask what could be gained by using new information and communication technologies in classrooms. Motivated by the fact that innovative hardware and software has made its way to the classroom, some systems supporting in classroom learning scenarios have been developed [5, 9]. In this paper we present a system supporting teacher and student sharing learning documents in a computer-integrated classroom (CiC). The original idea of a computer-integrated face-to-face classroom was exemplified in the COSOFT environment [2,3]. Recently, the CiC idea was adapted to “early learning” in a primary school classroom [10] as well as to academic lecturing [7]. We share the J.M. Haake and J.A. Pino (Eds.): CRIWG 2002, LNCS 2440, pp. 35–44, 2002. © Springer-Verlag Berlin Heidelberg 2002
36
N. Baloian et a1
same principles which are behind the development of systems like Classroom2000 [I] and the electronic classroom used by ITM [13] about ubiquitous computing in the classroom [12]. However, Classroom2000 is oriented to capture the lecture and store it in files and the ITM classroom is oriented to remote lecturing. In our project we address the problem of document management (distribution, collection, sharing) inside (and outside) the classroom. It differs from the traditional courseware creation and managing systems in that it combines traditional face-to-face lecturing with computer supported collaborative learning. In a CiC setup the teacher presents the learning material (multimedia documents) on an electronic blackboard. Every student has a notebook or PDA, while the technical system provides the functionalities of interaction among the multiple computers. A wireless LAN connects the student's computer with the electronic blackboard, and there is a server (outside the local network) which provides and stores learning material. A CiC also includes systems which help teacher and students to recover, manage and share learning material. The CiC combines positive aspects of the classical chalkboard approach, particularly its flexibility in the spontaneous elaboration of ideas, with the potential of modern networked multimedia. The value added lies in the avoidance of discontinuities in representations ("media breaks"). In the CiC approach presented here, re-use and exchange of results, either synchronous or asynchronous, is easily possible. The full spectrum of basic representations, ranging from freehand input to sophisticated simulation and animation is available.
7 MW variolu
Fig. 1. The computer-integrated classroom scenario.
The work presented in this paper was motivated by concrete experience from a lecture about programming in distributed systems held at Duisburg University. Many problems occurred which could have been avoided by having an administration system for the learning material of the course. The same group is now designing and developing the CiC system for this particular case. The work reported here focuses on the teacher's work-plan (in a classroom).
Document Management in a Computer-Integrated Classroom
37
Although the CiC is still work in progress, most functionalities have already been implemented. The next chapter will introduce the use cases, that have been extracted as important needs. Chapter 3 will deal with the implementation of the system presenting its architecture, modules, and implementation of some important functionalities. Chapter 4 will briefly present some characteristics of the documents which are administrated by the system and the tool used to present and manipulate them. Chapter 5 will present some conclusions and future work.
2
The System Functionalities
The basic functional requirements for the envisaged CiC scenario can be broken down into the eight items listed below, each corresponding to a typical “use case”: Registration of teachers, courses, and students. In order to facilitate the document handling and management it is necessary to first register teacher, students and courses to the Document Manager. This module also maintains information about what courses are taught by each teacher, and the students that participate in each course. Login procedures for students and teacher. Teacher and students have to login to start a teaching and learning session. The teacher can establish a classroom session which the students may join. The username and password credentials determine access rights to files and directories within courses’ and students’ files, inside as well as outside the classroom. Distributing/collecting documents. During a classroom session the teacher can distribute and collect documents of any type to and from the students. Documents can be located on the Document Manager or in a local directory, either at the teacher’s electronic blackboard or on the students’ computer. Sharing documents. By sharing a document we understand many people viewing and modifying the same document at the same time. This can be used when the teacher asks a student to present his/her work to the rest of the class. Discussions can be supported by allowing other students or the teacher to use the document being shown, adding notes and drawings to further explain their idea. Monitoring the students’ work. During a classroom session, a teacher can look at student’s work within a document, for example to examine the progress made on an assignment or to verify the correctness of work in progress. A teacher is also able to collect parts of documents from the students, increasing his ability to monitor the work by comparing different approaches. Questions and answers. A module named “Questions and Answers” allows students and teacher to interact in a chat-like manner. The conversation details can be saved for a later analysis of the written interaction inside the classroom.
38
N. Baloian et al.
Working outside the classroom. Users should have the possibility to create and modify learning material wherever they are. For this reason, we have implemented an interface that enables the user to access and edit the learning material via the internet. However, the tool does not include a synchronous remote learning environment via video or audio conferencing, it solely enables users to continue and edit their work started in the classroom environment. Logging the actions during a session. We will provide mechanisms for keeping track of relevant information about the actions taken during the lectures by the teacher and the students for a later analysis. Conclusions can then be drawn about how the lecture was organized. For example, it is important to record which documents were opened during a session, how many times they were opened during the whole course, and how many times they were modified. This can provide us with valuable information about which files need to be replaced, complemented, or deleted.
3
The System Architecture
As a result of our practical experience we assumed the system should consist of at least one classroom local area network (Classroom Environment), desirably secured by a firewall which is again connected to a Document Manager (see 3.1). Adding to this we wanted to present the users the ability of asynchronous and distributed work on their documents, i.e. via an internet connection outside the classroom. The component developed for this purpose is situated in the Home Environment. 3.1
The Modules of the System
The System is organized into different components, placed into three environments: classroom environment, server and home environment. The functionalities of the components shown in Figure 2 and their interaction with each other is described below. Session Control. The first component of the classroom environment is a supervision tool for the teacher: the Session Control. It is to be run by the teacher only, either on the electronic blackboard or on a separate computer. It includes mechanisms for synchronizing the instances of client interfaces in the classroom environment, for giving and taking rights to or from the users, and for logging session information. As the central component for the teacher it also includes file handling functionalities. This enables the teacher to use the Session Control as a stand-alone interface on the blackboard or in combination with the File Handler (run on the blackboard). Not only can any document from the Document Archive or inside the classroom environment be sent to a selection of students, any document that is currently being worked on by any user can also be displayed on a selection of students’ File Handlers.
Document Management in a Computer-Integrated Classroom
39
Fig. 2. System structure and environments.
File Handling. It is used in the classroom environment by the students and the teacher to open, edit, create, transfer and display the user’s files or course files. Adding to this it allows direct communication with the Session Control Interface via a questions and answers dialogue. Remote File Editor. The home environment consists only of the Remote File Editor, that enables the users to view, create, edit and transfer their files located on the Document Archive from a remote location. This is implemented by an internet connection and the document editor FreeStyler. It does not include synchronous collaboration with other users. Document Manager. The Document Manager is part of the server environment and provides authentication to all users in either the classroom or home environment, including the individual’s rights inside the whole CiC system. Adding to this it controls all file transfers from and to the Document Archive and keeps track of new and existing sessions and courses. Document Archive. This repository is the second part of the server environment and stores all documents of the users, courses and sessions, all personal information of the users and all logged information. The Document Archive is controlled by the Document Manager. 3.2
The File Structure at the Document Archive
The Document Archive consists of a hierarchical organization of files containing all the necessary information to administrate the CiC. This includes information about the teachers and their files, the students and their files, the courses and the learning material associated with them, the information about which students are in a certain course, which teacher is responsible for a certain course, as well as the rights for
40
N. Baloian et al.
teachers and students to create, modify, and/or read certain files. The next figure shows the directory structure and the information contained. The root of the repository is divided in three directories: Courses, Teachers and Students, which contain the corresponding home directories. The home directories of Teachers and Students contain personal information, a Logs directory to store the actions history and a Files directory which is the only visible to the clients. The courses have the same structure, but the Files directory has another name as its use is oriented to share documents rather than store personal files. Also, each course may have another directory intended for uploads of e.g. homework prepared by students.
Fig. 3. The file structure at the Document Archive.
3.3
Permissions Management
The access rights are managed on the Document Manager, which assigns some default settings that can be changed later on. By default, each user controls the visible part of the home directory (he/she can perform all the available operations), and can grant or deny “read”, “write” and “delete” access rights within this hierarchy. The enforcement of the rights is done at a lower level, using a custom Java SecurityManager which is automatically invoked before operations like opening files are attempted within the JVM. Using this scheme, it is not necessary to audit every part of the server code, since the code itself is not trusted to perform every action.
Document Management in a Computer-Integrated Classroom
3.4
41
Implementation of Login Procedure
The login procedure consists of several steps, including authentication from the data stored in the Document Archive. To start a new Classroom Environment Session for an existing course, the Session Control sends login parameters to the Document Manager and receives all available course information accessible to the given teacher. When a new session has been created, any File Handler can now access the running session by sending user parameters to the Document Manager, which authenticates the user with information stored on the Document Archive. Only after having received a unique session ID, the File Handler can perform a login to the Session Control (via RMI) and is then signed up to the Classroom Environment.
3.5
Implementation of Document Distribution and Sharing
During a classroom session the teacher can distribute and collect documents or parts of documents to and from the students. Files are first downloaded from the Document Archive (Fig.4, arrow 1) and can then be distributed among the multiple users (Fig.4, arrow 2). For the sharing of content (i.e. part of a document) in the classroom situation, we use a synchronization server called MatchMaker [11], which allows the sharing of objects. This sharing is accomplished by maintaining a copy of the FreeStyler document model on the server, and sending the modifications to all clients that share the specific object being edited. It is important to note that the model exists in distributed copies on each client, so an application or communication failure does not imply loss of data, since the model will be available from any copy. 3.6
State of Implementation
All Modules have been developed and tested in collaboration with each other. Some functionalities are still missing, though, which will have been implemented and tested by the time the paper is being printed. A restructuring of the whole system, including the specification of standard actions evolving in a learning situation and the implementation of these is to be undertaken at that point. At the same time we will work on the strengthening of the interaction between the FreeStyler document editor and the individual CiC tools, which implies that certain actions or user inputs can be implemented in the FreeStyler directly, rather than repetitively in each CiC tool.
42
N. Baloian et al.
Fig. 4. Distribution and sharing of documents displayed in the FreeStyler model.
4
The Documents
For creating, manipulating and viewing the documents, the primary tool will be the FreeStyler [8]. It can be used during multiple working phases as preparation, creative meetings, presentation, postprocessing or wrapping up information Therefore, is serves also as an interface between face-to-face discussions and the documentation process. This is enabled by a cooperative visual language which offers a set of content objects to structure information. A content object combines a symbolic view with predefined interactions. It can be characterized as a template for a special type of information as ideas, concepts, decisions, addresses or internal and external links. Whereas several content objects rather define the category of information, others, i.e. the links, provide additional structural information and interaction features. Together with these content objects users can add handwritten input flexibly. Methods as concept mapping, mind mapping or MetaPlan are easy to perform with the FreeStyler. The external representations both enrich and influence the communication. The documents may include a workflow description about how and when they should be distributed to the students, collected, where they should be stored, etc. This allows the system to offer useful default alternatives to the user, minimizing the input required to perform each task and keeping the focus on the session. FreeStyler files are stored in XML format. Beside the advantages of a standard format in general, XML makes it easy to retrieve information. In order to exchange
Document Management in a Computer-Integrated Classroom
43
the maps an integrated mail functions converts the maps to a picture format and send the content as attachments or the original XML files. FreeStyler-internal filters allow for separating types of information in order to focus on special aspects as decision or ideas. The system will provide an interface to query the XML documents, both in their current state while being edited and off-line in the repository. This way, the teacher can monitor the work of the students over the document as well as grade the work or analyze the result of past sessions. The structure of the documents will help the teacher to look whether certain part of a assignment has been finished by all students, or if some keywords appear in the answers.
5
Conclusions and Future Work
We intend to use and evaluate the system in various scenarios, one of which will be a sample classroom setup in AccessNova at the University of Chile, another will be a comparison of lecturing using this system to the traditional way of teaching at the University of Duisburg. The evaluation of the results will be on the level of system usability (with surveys for teachers and students) and effectiveness (with tests about the issues being learnt/taught for the students and comparing them with results of the same test taken on a control group). The CiC architecture and functionality share certain features with currently available “course management tools” such as Blackboard CourseInfo, WebCT, Luvit or TopClass (for a comparison, cf. Hazari, [6]). The specific issues addressed in our work are: - The services provided have been designed with a primary focus on inclassroom work as opposed to remote scenarios. - The application focus is more on the intra-course perspective with a smaller granularity (although multiple groups and courses are supported), not so much on the administration of courses in a bigger institution. - The system is deeply integrated with the document data model used and comprises a XML-based query interface for teacher supervision as well as for intelligent support and analysis. - The components in our modular architecture can also be used in other contexts or as special purpose services.
References 1. 2. 3.
Abowd, G.: Classroom2000: An Experiment with the Instrumentation of a Living Educational Environment. IBM System Journal, Special issue on Pervasive Computing. Vol. 38, Nr. 4, pp. 508–530, (1999). Baloian, N., Hoppe, H.U., Kling, U.: Structural Authoring and Cooperative use of Instructional Multimedia Material for the Computer integrated Classroom. In: Proceedings of the ED-Media, Graz, Austria (1995). 81–86 Baloian, N., Hoppe, H.U., Pino, J.A.: A Teaching/Learning Approach to CSCL. In: IEEE Comp. Science press, Los Alamitos, CA (USA) 33rd Annual Hawaii International Conference on System Science. Maui, HI (USA). (2000)
44 4. 5. 6. 7.
8.
9.
10. 11. 12. 13.
N. Baloian et al. Berge, Z. & Collins, M. (eds.): Computer-mediated Communication and the Online Classroom, Hampton Press, New Jersey, USA, (1995) Colazzo, L. & Molinari, A.: To see or not to see: tools for teaching with hypertext slides. In: H. Maurer (Ed.): Proceedings of ED-Media 95 (World Conf. on Educational Multimedia and Hypermedia), Graz, Austria (1995) 17–21 Hazari, S.: Evaluation and Selection of Web Course Management Tools. http://sunil.umd.edu/webct/ (1998) Hoppe, H.U., Luther, W., Mühlenbrock, M., Otten, W., Tewissen, F.: Interactive Presentation Support for an Electronic Lecture Hall. In: Cumming, G., Gomez, L., Okamoto, T. (eds.): Advanced Research in Computers and Communications in Education. IOS Press, Amsterdam, The Netherlands (1999) 923–930 Hoppe, H.U., Gaßner, K.: Integrating Collaborative Concept Mapping Tools with Group Memory and Retrieval Functions. In: Stahl, G. (eds.): Computer support for collaborative learning: Foundations for a CSCL Community. Lawrence Erlbaum, Hillsdale, USA (2002) 716–725 Norman, K.: Hypercourseware for assisting teachers in the interactive electronic classroom. In: J. Willis, B. Robin, & D. A. Willis (eds.): Proceedings of Fifth Annual Conference of the Society for Technology and Teacher Education, Washington, D.C., USA, (1994) 473–477 Tewissen, F., Lingnau, A., Hoppe, H.U.: “Today’s Talking Typewriter” – Supporting Early Literacy in a Classroom Environment. In: Gauthier, G., Frasson, C., VanLehn, K. (eds.): Proceedings of Intelligent Tutoring Systems. Montreal, Canada (2000) 252–262 Tewissen, F., Baloian, N., Hoppe, H.U., Reimberg, E.: "MatchMaker" Synchronising Objects in Replicated Software-Architectures. In: Proceedings of 6th International Workshop on Groupware (CRIWG) Madeira, Portugal. IEEE CS Press (2000) Weiser, M.: Some Computer Science Issues in Ubiquitous Computing, Communications of the ACM 36, No. 7, 75–84 (1993). Perez, E., “IT Management Center Project”, http:// itm.dsv.su.se/eng/index.htm
Handheld CSCW in the Meeting Environment 1
Pedro Antunes and Carlos J. Costa 1
2
Department of Informatics, Faculty of Sciences of the University of Lisboa, Bloco C5 – Piso 1 – Campo Grande, 1700 Lisboa, Portugal,
[email protected], www.di.fc.ul.pt/~paa 2 Departamento de Ciências e Tecnologias de Informação, ISCTE, Lisboa, Portugal,
[email protected]
Abstract. This paper discusses the role of PDA in the meeting environment. Three fundamental design issues are raised: PDA as mobile devices, CSCW devices and coordination devices. The research work described in this paper is focused on the coordination facet. The paper proposes three levels of detail to characterize meetings as coordination mechanisms and ascertain the role of PDA in that process. The first level identifies meeting agents and roles, as well as the tangible things necessary to support those roles. The second level describes how the tangible things are organized in meetings, highlighting repetitive patterns in meeting processes. Finally, the third level draws the functional requirements of the PDA support to the tangible things. The paper applies the proposed approach to a specific meeting environment, staff briefings, and uses a small consulting company as test bed. The PDA functionality was specified from analyzing how the test bed organization conducted staff briefings. A prototype was then developed. The test bed organization also produced feedback information on the prototype use. The obtained results indicate a general satisfaction with the functionality and increased enthusiasm with PDA usage in the meeting environment.
1 Introduction PDA play an important role as mobile devices that support personal information [1]. In that context, PDA allow one person to create and manipulate personal information away from the desktop and plug in to remote information sources to upload, download or synchronize specialized information. Several researchers analysed in detail the concept of mobility. Dix et al. [2] consider three levels of mobility: fixed, mobile and autonomous systems. Kistoffersen and Ljungberg [3] [4] define three different modalities for mobile work: travelling, wondering and visiting. Travelling is the process of working while going from one place to another. Wondering is extensive local mobility in a building or local area. Visiting is spending time in one place for a period of time before moving on to another place. The concept of visiting clearly encompasses formal meetings, where people get to-
J.M. Haake and J.A. Pino (Eds.): CRIWG 2002, LNCS 2440, pp. 47–60, 2002. © Springer-Verlag Berlin Heidelberg 2002
48
P. Antunes and C.J. Costa
gether in a conference or office room, while the wondering concept applies to informal meetings held in places such as hallways and cafeterias. Mobility should also be considered in terms of context [5]. Context deals with the situated nature of groups of users and existing work practices and poses significant problems to the design of information devices that allow mobility between different contexts [2]. PDA can also be regarded as CSCW devices, able to manipulate collective artefacts. Luff and Heat [6] illustrate the importance of these artifacts with the example of the medical record, which in many circumstances serves to organize work and mediate the interactions between doctors and patients, as well as other health care personnel. In this perspective PDA must support two fundamental requirements of collective artefacts. One is fluidity between public and private contexts [1]. The other requirement is flexibility. People manage collective artefacts in many subtle ways according to the affordances of the medium, situated nature of work, type of interaction and degree of cooperation (Luff and Heat highlight the importance of what they designate micromobility [6]). Meeting environments represent another instance where fluidity and flexibility are vital. During meetings, people alternate between private and public information in very fast and disorganized ways. Meeting subgroups are dynamically created and reconfigured as well. Moreover, meeting processes are governed by many complex and subtle rules and procedures. Thus, meeting environments challenge the design of adequate PDA support to shared meeting artifacts. PDA can finally be regarded as coordination tools. A critical issue to organizational and team performance is coordination. According to some authors, coordination can be classified in two major categories: impersonal coordination and coordination by feedback [7]. Impersonal coordination is exemplified by the use of plans, schedules and procedures. Coordination by feedback is illustrated by two significant examples: one-to-one communication and group meetings. In everyday activities, people move around personal information, such as calendars and address books – possibly the most widely used PDA tools – creating opportunities to reduce the effort associated to impersonal coordination [8]. However, PDA are as well becoming important tools in the support to coordination by feedback. In this paper we analyze the role of PDA in the meeting environment. Our main scenario is a meeting room where people meet face-to-face, have a desktop computer in the room, possibly linked to a shared whiteboard, and bring their own PDA as well. This scenario emphasizes the importance of the link between personal information and meeting information. The issue then is to understand how can the PDA be used in this environment, considering the design issues of mobility, support to shared artifacts and coordination. In this paper we also describe an implementation of a handheld meeting system in the scenario broadly described above. The system was experimented by an organization, thus drawing some preliminary results also presented in this paper.
Handheld CSCW in the Meeting Environment
49
2 Related Work Several research projects studied the role of PDA in the meeting context. We will overview these projects according to the three major design issues that were previously considered: mobility, support to shared artifacts and coordination. One of these research projects is Pebbles, developed at the Carnegie Mellon University [9] [10] [11] [12]. Pebbles connects PDA devices and desktop computers in real-time. The major concern of Pebbles is to explore different modalities, such has having the PDA controlling a slide show on the desktop. Another area of concern is developing mechanisms to exchange information between PDA and large display devices, which are awkward to write directly. Another project, developed at the University of Calgary, is the SharedNotes prototype [1]. Shared Notes is a meeting system that uses PDA to integrate public and private artifacts. The project addresses the issues of information exchange and presentation, while resolving important design issues such as feedback and awareness. NotePals is a note sharing system designed to take individual notes during meetings and later synchronization and sharing via the web [13]. As such, NotePals is fundamentally concerned with mobility issues, information uploading and post-meeting sharing of information. One example of NotePals usage is the post-production of meeting reports. The RoamWare project intended to support informal face-to-face meetings, such as the ones that people have in hallways and corridors [14]. One research issue addressed by this project is the support to ad-hoc meeting arrangements, where PDA must scan for co-located devices to establish connections. In what concerns shared artifacts, RoamWare pursues the seamless distribution of notes taken during meetings while preserving their context. RoamWare associates meeting notes with the particular group of individuals interacting in a ad-hoc meeting, creating, for instance, e-mail distribution lists and thus facilitating information distribution to the right people. Table 1. Systems and major design goals Systems Peebles
Mobility
Shared Notes Note Pals
RoamWare
Note taking in meetings; Uploading and sharing Ad-hoc meetings
FieldWise MeetingLog, MeetingManager
Shared artifacts Multiple modalities; Information exchange and presentation Information exchange and presentation
Coordination
Seamless integration; Meeting context Knowledge management
Individual recording meeting topics
50
P. Antunes and C.J. Costa
FieldWise addresses the problem of autonomous mobile workers that must coordinate with co-workers to make decisions and accomplish tasks [15]. FieldWise is a mobile knowledge management system. It supports evolving tasks and notifies users of interdependencies. One should note however that FieldWise was basically designed for remote work rather than face-to-face meeting environments. Besides the several systems described above, developed in the research field, we should also mention that several commercial/freeware PDA tools (e.g. MeetingLog and MeetingManager) can be used in meetings for individual recording and tracking of topics, notes, decisions, etc. As summarized in Table 1, the role of PDA in meetings has mainly studied and developed the mobility and shared artifacts facets. The work described in this paper will essentially focus on coordination though.
3 Focusing the Problem Meetings bring together people sharing a common purpose. Meetings combine a series of dimensions in human behavior, such as communication, interaction, decisionmaking, negotiation, conflict resolution or creativity. The major argument in favor of meetings is that they increase creativity, coordination and informed decision-making [16]. In this context, coordination may be defined as managing dependencies between activities [17]. Often, meetings are connected in meeting systems revolving around the same problems over a long period of time and thus serve as a control mechanism by determining whether and when work is performed. Malone et al. [18] [19] conceptualized the types of dependencies between activities and corresponding coordination mechanisms. In this conceptualisation, resources emerge as a fundamental mediator between activities. We will not go into the details of the relations between resources, activities and dependencies. Instead, we will consider two different types of information in these resources: The intangible things – The contribution of the resources to organizational objectives, such as reconcile conflicts, make decisions, solve problems, plan actions, approve activities, etc. The tangible things – Physical testimonials that report and preserve the intangible things that will be consumed or produced during meetings. Examples are meeting minutes, action plans or meeting transcripts (e.g., [20]). Many organizations are even legally required to document this way some particular meetings, such as stakeholder meetings. For us, this distinction is necessary to delimit the type of interventions in the meeting environment that we are considering for PDA. Having PDA supporting the management of intangible things leads necessarily towards the field of workflow and, particularly, flexible workflow and mobile workflow, (e.g. [21]). Ancona, et al. [22] describe such approach in a healthcare system. On the other hand, the PDA support to tangible things deals basically with organizational
Handheld CSCW in the Meeting Environment
51
memory. For instance, Davis et al. [23] developed a note-taking repository that uses PDA. Our work focuses only on the PDA support to the tangible things that turn up in meeting environments. Having in mind these considerations, we will now delineate a conceptual approach to the problem.
4 Conceptual Approach In this section of the paper we characterize in more detail the tangible things that mediate meetings and the other activities in organizations. Our conceptual approach proposes a characterization at three increasing levels of detail [24]. The first level describes the context of the problem, including the main agents and activities. The second level describes the institutionalised communication patterns, categorizing the tangible things consumed and produced by meetings. Finally, the third level is the implementation level, describing what and how tangible things integrate in the organization, and the role of PDA in the process. In the first level we can identify five types of agents (or roles):
Sponsor is the owner of the meeting, who defines the meeting objectives and rules.
Facilitator is the person that plans and manages a meeting.
Participants are those who attend a meeting and contribute by making comments, giving opinions, voting, etc.
Secretary is the agent that produces the meeting report and distributes it to the other agents.
Organisational agents are those agents that affect meetings or find their activities directly affected by meetings.
This first level allows us to identify a set of generic tangible things necessary for accomplishing the above roles: (1) the agenda, produced and managed by the facilitator and approved by the sponsor; (2) issues, produced by organizational agents and related to the topics proposed in the agenda; (3) decisions, taken by the meeting participants and affecting organizational agents; and (4) the meeting report, produced by the secretary to document the other tangible things. The second level of the framework is intended to describe how the different tangible things are organized in a meeting. This organization is not ad-hoc, it is rather ritualized, reflects organizational culture and most times follows a ceremonial order [20]. In fact, the organizational values and rules impose repetitive patterns in meeting processes. One issue to ponder is how to identify these patterns. We adopted an organizational analysis/diagnosis method designated genre analysis [25] [26]. The genre concept was imported from the literature, where its main purpose was to classify literary works, and generalised to the organisational context [27] [28]. A genre of “organisational
52
P. Antunes and C.J. Costa
communication” is an institutionalised template for social action, such as a memo, report, resume, inquiry, letter, meeting, announcement, expense form or training seminar. Genres are primarily characterised by their purpose and form. The purpose is not an individual’s private motive for communicating, but a purpose socially constructed and recognised by the community, and invoked in typical situations. The form refers to observable aspects of the communication, such as medium, structural features and linguistic features, which entail recognition and action by the community. The genre approach gains particular interest considering that organizations utilize many different computational systems to communicate and work, such as e-mail, video conferencing, web chats, workflow, calendaring tools or group editing. Genre analysis captures and categorizes the different “digital genres” used by the organization in terms of communicative purpose and form. Furthermore, the genre analysis also captures how organizations combine different genres in complex communicative patterns designated “genre systems”. These genre systems highlight how organizations structure work and manage interdependencies. Considering the meeting environment, the genre analysis highlights typical patterns in meetings. Orlikowski and Yates [28] consider that meetings can be regarded as a system consisting of four generic genres: logistics, agenda, the meeting itself, and the meeting report. Note that the agenda and meeting report are two tangible things that we already identified at the first level. The genre approach adds logistics to that list, i.e., details on who participates in the meeting, when and where is the meeting taking place, what technology is being used. Most importantly however, the genre approach defines a scheme to classify and characterize different types of recurrent meeting systems in organizations, such as planning meetings, quality circles, staff briefings, formal evaluation meetings, design meetings, task forces, brainstorming meetings, conferences and workshops, ceremonial meetings, etc. These different types of meeting systems include particular types of logistics, agenda, meeting genres and reports, as well as particular types of agents and roles, issues and decisions. This second level of detail thus amalgamates in coherent patterned structures the tangible things that make up meetings. Finally, we will consider the third level of detail. The third level concerns implementation details: how genres and genre systems are materialized and integrated in the organization, how people enact and use genres to accomplish work. How PDA will participate in that process. Considering our previous discussion, we can at this level identify the following functional requirements to the PDA use in the meeting environment: Allow users to produce, distribute and carry to meetings a meeting agenda; Support the production of issues related to the agenda items; Document decisions taken during meetings; Integrate the agenda, issues and decisions into a meeting report that can be distributed to organizational agents; Document the meeting logistics (who, when, where, what); Support concrete meeting patterns;
Handheld CSCW in the Meeting Environment
53
Offer different templates of the agendas, issues, decisions, reports and logistics according to the meeting patterns that are recurrent in the meeting environment. In the next sections we will describe the implementation of our conceptual approach to the particular case of staff briefings.
5 Applying the Approach to Staff Briefings Organizations regard staff briefings as particularly important coordination mechanisms. Usually, staff briefings call for project members to report on the progress of individual or group tasks, allowing management to track and assess the overall project status, identify project risks and apply any corrective actions that may be needed. In order to study in detail the particularities of staff briefings, we observed and analyzed how a small financial consulting and accountancy company conducted weekly staff briefings. Both the type of structure (small, flat) and core business (independent consultancy) of this company stresses the role of briefings as a primary coordination mechanism. The target organization uses, on a daily basis, several coordination technologies, such as web chat, net-meeting and e-mail. Fundamentally, these technologies support one-to-one coordination. The organization relies on meetings to achieve more broad coordination, encompassing the whole senior staff, which includes accountants and consultants. We participated in several meetings and were able to find out that the organization coordinates itself around three recurrent meeting patterns: (1) process definition meetings, dedicated to analyze work processes in an informal way, clarifying and improving the organizational maneuver; (2) planning meetings, which allocate staff to consulting projects and schedule individual tasks; and (3) briefings, where the state of each committed task is analyzed. Briefings, in this organization, have a weekly frequency, occurring in general every Friday. The typical composition includes two senior consultants and one senior accountant. We will now describe how we applied the conceptual approach described in the previous section to derive design goals for PDA support to this company’s staff briefings. Level 1 – Agents, Activities, and Tangible Things
In the target organization, the same person carries out the sponsor and facilitator roles. This person is the top responsible for the organization, although we should note that the power distance is small, considering that the organizational structure is small and flat. The sponsor/facilitator is also a meeting participant. The secretary role is distributed through all participants. The participants write down their own actions committed during the briefing, while the sponsor/facilitator is also informally responsible for tracking the others’ actions.
54
P. Antunes and C.J. Costa
The organizational agents affected by these briefings are the senior consultants and accountants. Thus, the meeting participants are also organizational agents but not all organizational agents participate in a weekly briefing. The sponsor/facilitator manages an agenda consisting of a list of tasks currently in progress. The issues contributed by participants consist of progress reports. The decisions taken during briefings involve approvals of on-scheduled tasks and re-schedules of delayed tasks. Each participant is responsible for taking notes about the decisions made during the briefings. Finally, this organization does not produce a formal report, although the sponsor/facilitator preserves the whole list of tasks that the organizational agents are responsible for. Level 2 – The Briefing Pattern
The sponsor/facilitator brings to the briefing the list of tasks that were previously scheduled in planning meetings and are currently in progress. This list shapes the briefing agenda. During the briefing the sponsor/facilitator goes through this agenda, item by item. The participants may bring their issues already prepared to the briefing, reporting the progress of the tasks that are their responsibility, or produce them during the briefing. Apparently, the consultants and accountants prefer a certain level of informality in their meetings and thus a formal progress report is not required. While going through the agenda, the participants analyze and discuss the issues, considering in detail what was done and what was not done and why. The decisions taken during briefings consist fundamentally in informally approving on-schedule tasks and re-scheduling delayed tasks. Sometimes re-scheduling also requires reassigning tasks to participants and organizational agents. Each participant is responsible for taking notes about the individual tasks that are re-scheduled. The sponsor/facilitator also takes notes about the status of all tasks. This organization uses simple and fixed logistics. The briefings happen in a weekly frequency, occurring every Friday, in the same room, at the same hour, with the available senior consultants and accountants. Level 3 – Functionality
The proposed system functionality is based on the assumption that the sponsor/facilitator has a PDA. The other participants may have PDA as well or use paper and pen to write down the meeting decisions. Furthermore, there must be a desktop computer available in the meeting room, ideally connected to a shared whiteboard. The sponsor/facilitator brings the agenda to the briefing in her PDA. The agenda consists of a “topic list”. The sponsor/facilitator can synchronize the PDA with the desktop computer, thus sharing the agenda with the other participants through the whiteboard. Then, the sponsor/facilitator goes through the topic list to get issues from the participants. The participants may have prepared these issues in their PDA and, in that case, are able to synchronize their PDA with the desktop computer to present an issue to the audience. The desktop computer collects these issues and associates them with
Handheld CSCW in the Meeting Environment
55
the topic list in the agenda. The participants may also insert issues directly on the desktop computer. At any time the sponsor/facilitator may synchronize her PDA with the desktop computer and get a coherent collection of topics and issues. To that collection, the sponsor/facilitator may append the decisions taken in the briefing. The participants can take individual notes on their PDA, documenting the decisions and schedules concerning their individual tasks. These individual notes are collected in “to-do lists”. Such lists can be associated with the collection of topics and issues synchronized with the desktop computer. In the next section we will describe in more detail the implementation of this functionality.
6 Prototype The prototype consists basically of three different components: (1) the sponsor/facilitator’s database; (2) the participants’ database; and (3) the shared whiteboard application. The PDA software implementation used the Jfile database system (www.landj.com) for the Palm Pilot. The sponsor/facilitator’s database has the following elements: topic list, issues, and decisions. The participants’ databases add to-do lists to the above elements. In Figures 1 and 2 we illustrate the structure of these databases, while in Figure 3 we illustrate the Palm user-interface for the to-do list. The shared whiteboard application was implemented using Internet technology (HTML files, CGI and Perl scripts) and a relational database from Microsoft. Users can interact with this application using a web browser, since it runs on the Xitami (imatix.com) web server. Sponsor/ facilitator
maintains >
Topic list
< report
< progress
Decisions
Re-schedules Fig. 1. The sponsor/facilitator’s database
Issues
56
P. Antunes and C.J. Costa
< report
Topic list
Issues
< progress
< approves
Decisions
track >
brings >
Participant maintains >
Re-schedules
To-do list
briefing >
Fig. 2. The participants’ database
Fig. 3. To-do list on a participant’s database
We should mention that this prototype was developed from a previous prototype that we built to integrate PDA with an Internet-based Electronic Meeting System (also built by us). In fact, the prototype described in this paper is the result of removing functionality to the previous one. While experimenting the PDA/EMS integration mechanism, we found out that the added value was resulting from the coordination support provided by PDA rather than integration with EMS. More details on the previous prototype can be found in [29] [30].
Handheld CSCW in the Meeting Environment
57
7 Feedback and Discussion The solution that was developed to integrate PDA in the meeting environment was experimented by several employees of the organization where the study was conducted. Although no formal evaluation was performed, we could obtain some preliminary feedback information about the overall acceptance of the system. The major aspect of the solution that made the users generally satisfied is that it preserves the flexibility of the team. The conceptual approach does not mandate formalized work procedures but, instead, supports the recurrent work practices and types of information exchanged between the meeting participants. All of the users that participated in this project had a PDA (one had a Psion while the others had Palm Pilots). However, at the beginning of the project, they were not very enthusiastic about using PDA in meeting environments, basically because they considered its use very disruptive. By the end of the project, however, there was a rebirth of interest in PDA usage during meetings. Apparently the benefits provided by the system (synchronizing meeting information) surpassed the associated costs (disruptive use). We should also mention that many aspects pertaining to the characterization of the tangible things managed in briefings were oversimplified. For instance, re-scheduling and re-assigning tasks may be a complex procedure, requiring the group to manage project, process and task information. However, the users were satisfied with the level of detail that was implemented. Some users even criticized any attempt to increase functionality. This attitude should be further analyzed in the future, but it hints that this kind of system should be kept simple. We note however that briefings are a particularly simple meeting pattern. Briefings are very ritualized and do not seem to offer much latitude for creativity, discussion and decision-making. Furthermore, the tangible things managed in briefings are also very simple. For instance, people mention projects, processes and tasks but do not seem to analyze or discuss their inner details, rather focusing on status information. Other meeting patterns should thus be more difficult to implement, such as planning meetings or strategic meetings. Future work is necessary to understand if our conceptual approach can be applied to more demanding situations.
8 Conclusion This paper describes how we brought handheld CSCW into the meeting environment. Our major concern was to understand how PDA could improve the role of meetings as fundamental coordination mechanisms. PDA have already an important role in the support to individual information, but its support to team meeting information is still low. The conceptual approach proposed in this paper defines three levels of detail for handling the problem. The first layer highlights the major roles and activities that people assume during meetings, as well as the tangible things necessary to accomplish those roles. Then, the second layer is concerned about how organizations bring to-
58
P. Antunes and C.J. Costa
gether the tangible things into identifiable repetitive patterns in meeting processes. Finally, the third layer is dedicated to identify the functional requirements of the computational system and, particularly, the role of PDA in that system. The paper describes the application of the conceptual approach to a particular type of meetings: the staff briefings. A target organization in the accountancy field was selected to help us identify the major roles and activities, tangible things and patterns associated to briefings. The implementation work was accomplished with the cooperation of several employees of the organization. The employees had also the opportunity to experiment the developed prototype and provided us with some feedback about their satisfaction with the whole system functionality. The prototype was considered adequate to support briefings and also seemed to increased users’ enthusiasm towards PDA usage.
Acknowledgments. This paper was partially supported by the Portuguese Foundation for Science and technology, Project POSI/SRI/34392/99.
References 1.
Greenberg S, Boyle M, Laberge J (1999) PDAs and Shared Public Displays: Making Personal Information Public, and Public Information Personal. Personal Technologies, March. 2. Dix A, Rodden T, Davies N, Trevor J, Friday A, Palfreyman K (2000) Exploiting Space and Location as a Design Framework for Interactive Mobile Systems. ACM Transactions on CHI 7 (3), September. 3. Kristoffersen S, Ljungberg F (1998) Your mobile computer is a stationary computer. CSCW’98 Handheld CSCW Workshop. Seattle, November. 4. Kristoffersen S, Ljungberg F (1999) Mobile Informatics. In: Planet Internet. Studentlitterature, lund. 5. Urray J (2000) Sociology beyond societies: Mobilities for the twenty-first century. Routledge, London. 6. Luff P, Heath C (1998) Mobility in Collaboration. Proceedings of ACM CSCW’98 Conference on Computer-Supported Cooperative Work. Seattle, Washington. 7. Van de Ven A, Delbecq A (1976) Determinants of Coordination Modes Within Organizations. American Sociological Review (41):322-338. 8. Lewis B (1997) Personal digital assistants could sneak into the office and become the next PCs. InfoWorld 19 (49), December:138. 9. Myers B (2001) Using handhelds and PCs together. Communications of the ACM 44 (11), November:34-41. 10. Myers B (2000) The Pebbles Project: Using PCs and Hand-held Computers Together; Demonstration Extended Abstract. Adjunct Proceedings CHI’2000: Human Factors in Computing Systems. ACM Press, The Hague, The Netherlands, pp 14-15. 11. Myers B, Miller R, Bostwick B, Evankovich C (2000) Extending the Windows Desktop Interface With Connected Handheld Computers. 4th USENIX Windows Systems Symposium. Seattle, pp 79-88.
Handheld CSCW in the Meeting Environment
59
12. Myers B, Lie K, Yang B (2000) Two-Handed Input Using a PDA and a Mouse. Proceedings CHI’2000: Human Factors in Computing Systems. ACM Press, The Hague, The Netherlands, pp 41-48. 13. Davis R, Landay J, Chen V, et al (1999) NotePals: Lightweight note sharing by the group, for the group. Proceedings of the CHI 99 Conference on Human Factors in Computing Systems. ACM Press, Pittsburg, pp 338-345. 14. Wiberg M (2001) RoamWare: An integrated architecture for seamless interaction in between mobile meetings. Proceedings of the 2001 International ACM SIGGROUP Conference on Supporting Group Work. ACM Press, Boulder, Colorado, pp 288-297. 15. Fagrell H, Forsberg K, Sanneblad J (2000) FieldWise: A Mobile Knowledge Management Architecture ACM Press (ed.). Proceeding of the ACM 2000 Conference on Computer supported cooperative work. Philadelphia, pp 211-220. 16. Romano N, Nunamaker J (2001) Meeting analysis: Findings from research and practice. Proceeding of the 34th Hawaii International Conference on Systems Science - HICSS 2001. Hawaii. 17. Malone T, Crowston K (1994) The Interdisciplinary Study of Coordination. ACM Computing Surveys 26 (1), March:87-119. 18. Malone T, Crowston K, Lee J, et al (1997) Tools for inventing organizations: Toward a handbook of organizational processes. Center for Coordination Science, Massachusetts Institute of Technology. 19. Malone T, Crowston K, Lee J, Pentland B (1993) Tools for inventing organizations: Toward a handbook of organizational processes. Proceedings of the 2nd IEEE Workshop on Enabling Technologies Infrastructure for Collaborative Enterprises. Morgantown, WV. 20. The 3M Meeting Management Team (1994) Mastering Meetings. McGraw-Hill, Inc., New York. 21. Carlsen S, Gjersvik R (1997) Organizational metaphors as lenses for analyzing workflow technology. In: Proceedings of the international ACM SIGGROUP conference on Supporting group work : the integration challenge. ACM Press, Phoenix, Arizona, pp 261-270. 22. Ancona M, Dodero G, Minuto F, Guida M, Gianuzzi V (2000) Mobile computing in a hospital. Proceedings of the 2000 ACM symposium on Applied computing 2000. ACM Press, Como, Italy. 23. Davis R, Lin J, Brotherton J, Landay J, Price M, Schilit B (1998) A framework for sharing handwritten notes. ACM Press, San Francisco, California. 24. Costa C, Antunes P, Dias J (2001) A model for organizational integration of meeting outcomes. In: Maung K. Sein, Bjørn-Erik Munkvold, Tore U. Ørvik, et al (eds.) Contemporary Trends in Systems Development. Kluwer Plenum. Papers from the Ninth International Conference on Information Systems Development, ISD 2000. ISBN: 0-306-46608-2. 25. Antunes P, Costa C, Dias J (2001) Applying genre analysis to EMS design: The example of a small accounting firm. Seventh International Workshop on Groupware, CRIWG 2001. IEEE CS Press, Darmstadt, Germany, pp 74-81. ISBN: 0-7695-1351-4. 26. Costa C, Antunes P (2001) Meetings as genre systems: Some consequences for EMS design. In: F Ackermann, G Vreede (eds.) Proceedings of Group Decision & Negotiation 2001. Faculty of Technology, Policy and Management, Delft University of Technology, La Rochelle, France, pp 261-263. ISBN: 90-5638-078-8. 27. Orlikowski W, Yates J (1994) Genre repertoire: The structuring of communicative practice in organizations. Administrative Science Quarterly 39:547-574. 28. Orlikowski W, Yates J (1998) Genre systems: Structuring interaction through communicative norms, CCS WP 205. Sloan MIT WP 4030.
60
P. Antunes and C.J. Costa
29. Costa C, Antunes P, Dias J (2002) Integrating two organisational systems through communication genres. Fifth International Conference on Coordination Models and Languages (Coordination 2002). Lecture Notes in Computer Science, Springer-Verlag, York, UK. 30. Costa C, Antunes P, Dias J (2000) Supporting the meeting report process. Proceedings of the 23rd Information Systems Research Seminar in Scandinavia, IRIS 23. Laboratorium for Interaction Technology, University of Trollahattan Uddevalla, Uddevalla, Sweden, pp 1141-1150. ISSN: 0359-9470.
Effect of the Coordination Modes in Supporting Group Multiple Criteria Decision Making in a Distributed and Asynchronous Environment Juan Carlos Leyva López and Dina Esperanza López Elizalde Universidad de Occidente Carr. a Culiacancito, Km. 1.5 Culiacán, Sinaloa, México Tel. +52-667-7540495
[email protected] [email protected]
Abstract. To solve a multiple criteria decision problem by a collaborative group is necessary to have an adequate coordination process. This paper discusses an on-going research project, which aims to develop an internet-based Multiple Criteria Group Decision Support System (MCGDSS) – which will support to collaborative group decision makers in reaching a consensus when they try to solve a ranking problem – and to further investigate the impacts of such a system on group multiple criteria decision aid (MCDA) process performed in parallel and sequential coordination modes. Features of the MCGDSS prototype and design of a follow-up laboratory experiment are described in this paper. Keywords. Group Decision Support Systems, Multiple Criteria Decision Aid, Ranking Problem, Coordination Modes, ELECTRE Methods.
1 Introduction Group decision making is one of the most frequent and important processes inside of organizations in the public or private sector. Most of the problems about real decision making involve multiples decision makers [34]. The comprehension, analysis, and support of the decision making process can be extremely difficult for three reasons: 1) the basic problem is badly structured, 2) the dynamic environment in which the decision making process develops, 3) the presence of multiple decision makers, each of them with their own points of view about the way the problem has to be managed and what decisions have to be adopted [15]. The strongest obstacle to resolving a group decision problem is that each individual has his/her own perception about problem. Consequently, he/she has his/her own belief about what should be the result or the correct decision to make. Therefore, in such an environment, it is logical and common to find conflicts between the opinions and desires of the group members. These conflicts arise due to the several factors present such as different values and
J.M. Haake and J.A. Pino (Eds.): CRIWG 2002, LNCS 2440, pp. 61–69, 2002. © Springer-Verlag Berlin Heidelberg 2002
62
J.C. Leyva López and D.E. López Elizalde
objectives, different criteria and preference relations, lack of communication support between group members, etc. [30] encapsulates the diverse factors in conflict under the term “distinct value systems.” This paper presents a research projects that aims to develop an Internet-based Multiple Criteria Group Decision Support System (MCGDSS) prototype built around Multiple Criteria Decision Aid (MCDA) models, which provides support for group decision making processes in asynchronous and distributed environments. The project intends to investigate whether the parallel and sequential coordination modes influence the outcomes of the group MCDA processes. In this paper we briefly discuss the research method and design in our study. The MCGDSS prototype and a lab experiment design are also presented in this paper.
2 Group MCDA Process A coordination mode refers to a series of procedures and aggregation methods, which incorporate the group and individual members activities and facilitate them to reach agreement of a high quality group decision [3]. In such an environment, each participant can sometime work individually and/or collaborate with the rest of the group at other time. These two different processes result from two coordination modes, which has named by Cao and Burstein [3] as sequential and parallel modes respectively. The influence of coordination modes on outcomes of group decision making process, however, has not attracted much attention in previous synchronous GDSS studies. Previous research indicated that the different procedure and aggregation methods might bring about different decision outcomes when using MCDM models [33]. In a distributed and asynchronous setting, these coordination modes may have an important influence on outcomes of group decision making. Therefore, such research is necessary and it may help to find out appropriate coordination modes that will bring the individual decision making process into synchronization with the group process, without restricting the achievement of satisfactory decision performance. Cao and Burstein [3] claim that in a distributed and asynchronous setting, these coordination modes have an important influence on outcomes of group decision making, our interest in this research is validate the hypotheses proposed by Cao and Burstein under different conditions: different multiple criteria modeling approach (MCDM vs. MCDA), different platform (Domino-Lotus vs. Groove), different problem solving (selection problem vs. ranking problem) and different method (Simple Additive Weighting (SAW) vs. ELECTRE).
3 Related Works There are a few GDSS that have used multiple criteria analysis techniques to support a group decision. Most of them have focused on communication elements, the structure of ideas, the generation of alternatives and the voting procedures. For instance, the GDSS of Conklin and Begeman [6], Cesar and Wainer [4], Lee [17] are
Effect of the Coordination Modes
63
focused on distributed and asynchronous meeting support, via an interconnected computer network. In these systems, the elements of a debate can be documented, reviewed or used again in any phase of the process, although, in contrast, they do not have structured techniques to solve problems of group decision making. MCGDSS have emerged just in the 80’s, almost twenty years after the introduction of the field of MCDA. These methodologies were identified in Iz [13], Iz and Gardiner [14], and Hwang and Lin [12]. In the early years, Bui [2] presented Co-oP, a co-operative multiple criteria group decision making system. The PLEXSYS system [8] and its descendant GroupSystems [26] contain, among others, a Alternative Evaluator tool which provide multiple criteria decision making support. After appears the Expert Choice system for group decision support based on the AHP method [31]. Also after Barzilai and Lootsma [1], [25] describe some other interesting methods of multiple criteria group decision making support. Hamlainen and Mustajoki [10] present the web-HIPRE system, which, in part, is based on the AHP. In [22] and [7] we can find another studies on MCGDSS. A similar approach to PROMETHEE MCGDSS developed by Macharis et al. [21] we can find in Leyva [18], which is based on the ELECTRE method [30]. By the way, research on the coordination modes in distributed group decision support systems has recently focused on the issue of system restrictiveness, which refers to the degree that a system limits its users decision making processes to a subset of all possible processes [32]. Another research topic has been the flexibility of coordination structure, and its influence on group decision outcomes and performances [24]. The conclusions reached in this area have been inconsistent. In studies on synchronous groups support systems, Chidambaram and Jones [5] reported that a GDSS with a high degree of system restrictiveness had negative impact on group performance. It seems that an imposed coordination structure can be overly restrictive due to the limited bandwidth of the interaction medium. Research regularly indicates that the individuals come to the group with a predetermined preference over others decision alternative and they seem relatively inflexible to following a particular decision making strategy [28]. It is also suggested that less restrictive coordination structures are more appropriate to support asynchronously interacting distributed groups [16]. Therefore, distributed GDSS should be flexible enough to allow the individual freedom to concentrate on aspects of the problems to which he or she can best contribute [35]. On the other hand, Dickson, Partridge, and Robinson’s [9] research indicated that GDSS should be designed with some degree of restrictiveness. Too much freedom in group interaction decreases group cohesiveness. Such loss of cohesion increases the decision cost either by generating a lower quality decision or taking more time to make a decision. Therefore, a coordination structure in distributed GDSS should impose some restrictions on interaction to maintain a certain level of group cohesiveness. The varying outcomes may results from applying different degree of system restrictiveness [11]. So far very little is known about what objectively determines the perceived degree of system restrictiveness. Previous studies have not explicitly shown the use of MCDA to support the group decision making processes. In our study, system restrictiveness is manipulated by applying certain procedures and aggregation methods (particularly ELECTRE methods) to the GDSS process. By manipulating these procedures and aggregation methods in group MCDA we try observe the impacts of different coordination modes on group decision outcomes and performance.
64
J.C. Leyva López and D.E. López Elizalde
4 Group MCDA Processes with Two Coordination Modes As stated above, in this study, we considered two coordination modes: parallel and sequential. We believe these two modes mostly cover the possible ways that people can go through a MCDA process. Guided by these two coordination modes imposed to the decision making process, group may reach a right decision at a right time. 4.1 Parallel Coordination
Parallel coordination means everyone in a group works independently throughout most steps during the decision making process. The procedure and respective aggregation methods are described step by step as following: Preliminary stage structuring the decision problem The preliminary stage is a phase of knowledge acquisition and problem structuring. A facilitator has first to be appointed. On one hand, the facilitator has to be familiar with the GDSS-ELECTRE methodology and, on the other hand, he needs to have a reasonable knowledge of the actual group decision problem and its context. The following steps can be considered potentially. Step 1. First contact Facilitator – Decision Makers. Each decision maker is encouraged to express his own opinions in order to progressively enrich the maturity of the facilitator with respect to the decision process. Step 2. Problem description. The decision makers meet in the MCGDSS. The facilitator comments the available infrastructure and gives an overall description of the problem. Step 3. Alternative generation. This is a “computer” phase during which the decision makers work alone. Step 4. Choose a stable set of alternatives. Step 5. Comments on the alternatives. Step 6. Define the possible evaluation criteria. This step ends the preliminary stage and the next evaluation stages can start. Individual evaluation stage Step 7. The proposed alternatives are evaluated by each criterion Step 8. Define weights and thresholds of the criteria Step 9. The individual ELECTRE analysis The ELECTRE III method [29] is applied to construct a fuzzy outranking relation and next a genetic algorithm [19] is applied to exploit it and as a result it recommends a complete ranking of the alternatives from the best to the worst ones. During the first stage, each decision maker works individually, with the possible assistance of the facilitator. At the end of this stage, everybody has a good personal view of the decision problem. Everybody has ideas on how to decide. More precisely, each decision maker has a ranking of the alternatives in decreasing order of preference. Group evaluation stage. The purpose is now to focus on group decision support in order to take into account the specific points by view of the different decision makers.
Effect of the Coordination Modes
65
Step 10. Global evaluation At the end of the individual evaluation stage, the facilitator collects the rankings an fuzzy preference relations coming from the decision makers and with these information the ELECTRE GD method [20] is applied to construct a fuzzy outranking relation and again the genetic algorithm is applied to exploit it and as a result it recommend a complete ranking of the alternatives from the best to the worst ones. At the end of the step 10, a global evaluation is obtained for the group. The (ELECTRE GD-genetic algorithm) method proposes a best compromise. If the group is agreeing upon the results of the global analysis, the best compromise can be adopted and the GDSS-ELECTRE session can be closed. On the other hand, if for some reasons some decision makers don’t agree on this compromise, the conflicts have to be faced. 4.2 Sequential Coordination
In a nut shell, we can say that sequential coordination implies that consensus would be sought throughout some stages of decision making process, from problem formulation to ranking determination. The consensus may be reached by applying aggregation methods at any appropriate stage. A procedure with sequential coordination mode and ELECTRE III method is: The group is asked to agree on the alternatives, criteria, weights, and thresholds before the model provides a ranking. The group discussion focuses on what actions and criteria should be considered, what weights and other necessary parameters are appropriate. Once the discussion is closed and all the individual information has been gathered, a technique is used for obtaining values of these model parameters, which should represent the collective opinion. With this information, the (ELECTRE IIIgenetic algorithm) method gives us the group ranking. It needs to be noticed that this procedure is iterative rather than simply sequential. If the group is unsatisfied with the result at any stage, it may go back to any step and redo it.
5 Research Design The research question in our study is stated as: “ Which coordination mode between the parallel and sequential ones is more appropriate for a group multiple criteria decision aid process in the asynchronous and distributed environment?” 5.1 Research Framework
The research adopts Nunamaker et al. [27] general GDSS research model. Revised version that conforms to our research design is present in Figure 1. From this “inputprocess-output” system standpoint, coordination mode is an independent variable in our study. McGrath and Hollingshead [23] developed a framework that consists of four primary factors: input, organization concepts, process variables, and outcomes. Their framework stresses the interactive relations between the variables. One of the
66
J.C. Leyva López and D.E. López Elizalde
most interesting points is that the process variables can be regarded as independent or dependent variables depending on the intended purpose. Process quality
Small Group
Process outcome
meta tasks
Satisfaction w ith process Participation
Process
Satisfaction w ith decision Decision outcome
Context
Decision quality Asynchronuous GDSS prototype
Coordination mode: Paralle l and sequential
Confidence in decision
Fig 1. Research framework for adapted MCGDSS [27]
In order to answer the research question, we need to implement a GDSS, which provides appropriate procedures and tools to support the group MCDA process. It should be tailored to suit for our further investigation of the research question. Once the GDSS prototype is implemented, a lab experiment will be organized to further investigate the research question. Two kinds of subject groups will be asked to use the system prototype going through a predefined MCDA process coordinated by the parallel and sequential modes. By observing the MCDA process outcomes, which are measured by the decision outcome and the process outcome, we may find out how significant these two coordination modes might influence the process outcomes. 5.2 GDSS Prototype System Development Environment. The prototype will be developed in Groove by using C++ and Visual Basic languages. Groove is a new groupware technology and consists of a combination of both software and services to transform the Internet into a personal medium for directing communication and interaction between some users. The Groove platform provides services and abilities of development in a wide variety for applications peer to peer. The users directly interact with each other in a real-time environment and share in an asynchronous or synchronous manner. This component has a 40% of advance. System Architecture. The Functional architecture will incorporate the following features: The ELECTRE III model to aggregate multiple criteria individual preferences, the ELECTRE GD model to aggregate the multiple criteria group preferences, a genetic algorithm to exploit a fuzzy outranking relation, the Delphi technique to stimulate and to generate ideas, use of a facilitator tool for optimization
Effect of the Coordination Modes
67
the meetings coordination of the group members, use of a Graphic interface, use of a Database Management subsystem to allow efficient and secure information access, a Norm subsystem, a Discussion subsystem and a Multiple Criteria Decision Analysis subsystem. This component has a 60% of advance. System Features. The prototype provides support for group MCDA process at three levels: a) Individual activity support, b) Group activity support and c) Facilitation support.
6 Laboratory Experiment Design The objective of the experiment is to examine how the use of parallel and sequential coordination modes with the internet-based MCGDSS affects group performance in an asynchronous and distributed environment. A series of experimental sessions will be conducted with a two-group between-subjects design. These experiments based on simulated business environment are being used to evaluate the group performance affected by parallel and sequential coordination modes. The effect of each group configuration will be assessed experimentally on six dependent variables: users’ satisfaction with process, users’ satisfaction with decision outcomes, users’ confidence in decision outcomes, quality of final decision, participation, and quality of decision process. 6.1 Subjects and Decision Task
The experimental subjects in the study will be undergraduate and postgraduate students enrolled in information systems courses. The decision task for this study will be either a case study of solving MCDA problems selected from textbook or familiar MCDA problem, which have been done previously by subjects. A pilot study will be conducted before the main study to test reliability of the prototype and complexity of the decision task, and to fine-tune both of the experimental procedure and the instrument. 6.2 Independent Variable
Coordination mode is the independent variable in the study. It has two levels: parallel and sequential 6.3 Dependent Variables and Hypotheses
Two classes of dependent variables, process outcome and decision outcome, are evaluated as the outcomes of group MCDA processes affected by two coordination modes.
68
J.C. Leyva López and D.E. López Elizalde
6.4 Experimental Procedure and Instrument
The appropriate instruments will be used to collect qualitative and quantitative data for measurement of dependent variables. The response sheets and questionnaire are being prepared for collection of data on both subjective and objective measurements. Two types of groups are being created with two levels of independent variables. In parallel coordination mode (“parallel groups”), subjects will work through decision procedure individually, except agreeing on alternatives in advance, and final group selection through asynchronous on–line discussion. “Sequential” groups will works through one stage of the procedure at a time. Groups will need to reach agreement or aggregate individual results into a group one before moving onto the next stage of decision process. A facilitator will help monitor and collaborate the overall group process.
References 1. 2. 3. 4. 5. 6. 7. 8. 9. 10. 11.
12. 13. 14.
Barzilai, J., Lootsma, F.A.: Power relations and group aggregation in the multiplicative AHP and SMART. Journal of multi-criteria decision analysis 6 (1997) 155-165 Bui, T.X.: Co-oP: A group decision support system for cooperative multiple criteria group decision making. Lecture Notes in Computer Science, Vol. 290. Springer, Berlin (1987) Cao, P. P., Burstein, F.V.: An empirical study of influences of the coordination modes in supporting Group Multiple – Criteria Decision – Making. Australian Conference in Information Systems (ACIS’2000), Brisbane (CD ROM) (2000) Cesar F.L., Wainer, J.: vIBIS: A discusión and voting system. Journal of Brazilian Computer Society 2 (1) (1994) 36-43 Chidambaram, L., Jones, B.:Impact of communication medium and computer support on group perceptions and performance: A comparison of face-to-face and dispersed meetings. MIS Quarterly 17 (4) (1993) 465-491 Conklin, J., Begeman, M.L.: gIBIS: A hipertext tool for exploratory policy discussion. ACM Transactions on Office Information Systems 6 (1998) 303-331 Davey, A., Olson, and D.: Multiple criteria decision making models in group decision support. Group Decision and Negotiation 7 (1998) 55-75 Dennis, A.R., George, J.F., Jessup, L.M., Nunamaker, J.F., Vogel, D.:Information technology to support electronic meetings. MIS Quarterly 12 (4) (1998) 591-624 Dickson, G., Partridge, J. L., Robinson, L.: Exploring modes of facilitative support for GDSS technology. MIS Quarterly 17 (2) (1993) 173-194 Hamalainen, R. P., Mustajoki, J.: Web-HIPRE-Java-applet for value tree and AHP analysis, computer software, http://www.hipre.hut.fi, Systems Analysis Laboratory, Helsinki University of Technology. (1998) Hiltz, S. R., Dufner, D., Fjermestad, J., Kim, Y., Ocker, R., Rana, A., Turoff, M.: Distributed group support systems: Theory development and experimentation. In: Olsen, G. M., Smith, J.B., Malone, T. W. (Eds.): Coordination Theory and Collaboration Technology. Hillsdale NJ: Lawrence Erlbaum Associates (2000) Hwang, C. L., Lin, M.J.: Group Decision Making under Multiple Criteria: Methods and Applications, Vol 281. Heidelberg, Germany: Springer-Verlag (1987) Iz, P.H.: Two multiple criteria group decision support systems based on mathematical programming and ranking methods. European Journal of Operational Research 61 (1992) 245-263 Iz, P.H., Gardiner, R.L.: Analysis of Multiple criteria decision support systems for cooperative groups. Group Decision and Negotiation 2 (1) (1993) 61-79
Effect of the Coordination Modes
69
15. Jelassi, M.T., Kersten, G, Zionts, S.: An introduction to group decision and negotiation support. In: Bana e Costa C. A. (Ed.): Readings in Multiple Criteria Decision Aid. Springer Berlin (1990) 16. Kim, Y., Hiltz, S., Turoff, M.: Coordination structure and system restrictiveness in distributed group support systems: An experiment on coordination mode and leadership. st In: Proceedings of the 31 Annual HICSS Hawaii. IEEE Computer Society. (1998) 145153 rd 17. Lee, J.: SIBYL: A tool for managing group decision rationale. 3 Conference ComputerSupported Cooperative Work 10 (1990) 72-92 18. Leyva López J. C.: A genetic algorithm application for individual and group multicriteria decision making: PhD Thesis Abstract. Computación y Sistemas IV-2 (2000) 183-188. 19. Leyva López, J.C., Fernández González E.: A Genetic Algorithm for deriving final ranking from a Fuzzy Outranking Relation. Foundations of Computing and Decision Sciences 24/1 (1999) 33-47 20. Leyva López J.C., Fernández González E.: A New Method for Group Decision Support Based on ELECTRE-III Methodology. Accepted in: European Journal of Operational Research. January 2002 21. Macharis C., Brans J.P., Mareschal B.: The GDSS PROMETHEE Procedure. Journal of Decision Systems 7 (1998) 22. Matsatsinis N.F., Samaras A. P.: MCDA and preference disaggregation in group decision support systems. European Journal of Operational Research 130 (2001) 414-429 23. McGrath, J. E., Hollingshead, A.B.: Groups interacting with technology: ideas, evidence, issues, and an agenda. Vol. 194. Sage Publications. Thousand Oaks, CA (1994) 24. McLeod, P., Liker, J.: Electronic meeting systems: Evidence from a low structure environment. Information Systems Research 3 (3) (1992) 195-223 25. Miettinen, K., Salminen, P., Hokkanen, J.: Acceptability analysis for multicriteria problems with multiple decision maker. Report 2/1997, University of Jyvaskyla, Department of mathematics, laboratory of scientific computing, Jyvaskyla (1997) 26. Nunamaker, J.F., Dennis, A.R., Valecich, J.S., Vogel, D. R., George, J.F.: Electronic meeting systems to support group work. Communications of the ACM. 34 (7) (1991) 4060 27. Nunamaker, J.F., Dennis, A. R., Valacich, J.S., Vogel, D.R., George, J.F.: Group support systems research: Experience from the Lab and Field. In: Jessup L.M., Valacich J.S. (Eds.): Group Support Systems: New perspective. Macmillan Publishing Company. (1993) 125-145 28. Putnam, L.L.: Procedural messages and small groups’ work climates: A lag sequential analysis. Communication Yearbook 5 (1982) 331-350 29. Roy, B.: The outranking approach and the foundations of ELECTRE methods. In: Bana e Costa, C.A., (ed.) Reading in multiple criteria decision aid. Springer-Verlag, Berlin. (1990) 155-183 30. Roy, B.: Multicriteria methodology for decision aiding. Nonconvex Optimization and its applications, Vol 12. Kluwer Academic Publishers, the Netherlands (1996) 31. Saaty, T.: The Analytic Hierarchy Process. McGraw Hill, New York (1980) 32. Silver, M.S.: Decision support systems: Directed and nondirected change. ISR 1(1) (1990) 47-70 33. Tung, Y.A.: Time complexity and consistency issues in using the AHP for making group decisions. Journal of Multi-Criteria Analysis 7(3) (1998) 144-154 34. Turban, E.: Decision Support Systems and Expert Systems: Managerial Perspectives. Macmillan, New York. (1988) 35. Turoff, M., Hiltz, S.R., Bahgat, A., Rana, A.: Distributed group support systems. MISQ Vol 17 (4), (1993) 399-417
A Cooperative Visual Hypermedia Approach to Planning and Conducting Virtual Meetings Weigang Wang1, Jörg M. Haake2, and Jessica Rubart1,3 1Fraunhofer
Institute for Integrated Publication and Information Systems (IPSI) Dolivostr. 15, 64293 Darmstadt, Germany {wwang, rubart}@ipsi.fhg.de 2 FernUniversitaet Hagen, Computer Science VI Informatikzentrum, Universitaetsstr. 1 D-58084 Hagen, Germany
[email protected] ³go4teams GmbH Julius-Reiber-Strasse 15a, 64293 Darmstadt, Germany
Abstract. Most distributed meeting support systems focus on meeting management and audio/video communication mechanisms. They provide little support for a flexible meeting process and a shared information space with structure-rich visual artifacts. In this work, a cooperative visual hypermedia system is developed to provide visual hypermedia artifacts for team members to manipulate in a distributed meeting. The visual hypermedia system is a hypermedia-based drawing system that integrates visual hypermedia artifacts and structures found in multiple hypertext domains. In addition, the visual hypermedia is integrated with process support for flexible meeting control and for easy setup of audio/video and application sharing communication channels. A use cases is presented, which shows that using the cooperative visual hypermedia, distributed teams can perform many kinds of meetings, in the meantime, enjoying dedicated support for the planning, control, information management, and follow-up activities of a distributed meeting. Keywords. Cooperative hypermedia, visual hypermedia, process support, distributed meeting support.
1 Introduction The trend towards globalization of business activities requires business teams to carry out their projects in a distributed environment. While face-to-face project meetings have always been central to effective teamwork, distributed meetings are used more and more often to reduce traveling costs and time, and to couple with emerging issues on short notice.
J.M. Haake and J.A. Pino (Eds.): CRIWG 2002, LNCS 2440, pp. 70–89, 2002. © Springer-Verlag Berlin Heidelberg 2002
A Cooperative Visual Hypermedia Approach
71
Traditional meeting support systems focus on augment co-located face-to-face meetings. In recent years, many distributed meeting support systems have been developed to provide audio/video communication channels, meeting management services, and some simple floor control mechanisms. However, these systems lack support for a well-planned flexible meeting process, lack a common information space with structure-rich visual artifacts, and lack the support for document handling. Our approach to tackle the problems is to develop a cooperative visual hypermedia for providing a common information space with structure-rich visual artifacts, flexible meeting process modeling and control, integrated document management, and session-based meeting management and easy setup of communication and application sharing channels for a meeting session. The remainder of the paper is organized as follows: section 2 provides a problem analysis on meetings, distributed meetings and distributed meeting support systems. Section 3 introduces the cooperative visual hypermedia concept and provides detailed descriptions of our approach to addressing the found problems. Section 4 describes hypermedia related implementation techniques that make our approach possible. Section 5 presents use cases of our system. Section 6 presents related work and section 7 concludes the paper with a summary, contribution highlights, and plans for further work.
2 Problem Analysis Meetings are social or business events when a number of persons come together at a certain time and place for certain purposes, such as discussion and decision-making. Good meetings can create a dynamic interaction between participants to achieve more then one could achieve alone. Meetings are an important part of any business. There are many kinds of business meetings, such as, project work sessions, strategic planning, management team meetings, customer problem solving sessions, project reviews, staff meetings, and team building meetings. 2.1 What Makes a Meeting Successful Working together does not always guarantee efficiency. Unnecessary or bad meetings could be just a costly interruption and a waste of time. A good meeting needs to have [8]
72
W. Wang, J.M. Haake, and J. Rubart
A strategically designed agenda with commonly understood goals and objectives. A clear, agreed upon process for reaching those goals and running the meeting. An awareness that people come with their personal preoccupations and feelings, as well as an interest in the subject at hand. A sense of involvement and empowerment; A skilled facilitator. To make a meeting effective, five meeting specific roles need to be taken by meeting organizers and participants [11]:
Chairman: who is responsible for meeting pre-coordination, setup, operation, and follow up; who decides the "why/what," "when," "where," and "who" of the meeting; and organizes and publishes a meeting agenda.
Presenter: who finds out how much time the presentation is allowed to take, and provides information clearly and concisely. Recorder: who condenses information into key points, documents decisions, actions, and pertinent information, and produces meeting minutes ASAP after the meeting. Timekeeper: who helps maintain the pace of the meeting by reminding people of time used, and Participants: who shows up on time and prepared for discussion, and remains attentive, alert, and focused throughout the meeting. The chairperson of a meeting needs to plan for support of each of these roles. It is possible to play more than two roles during a given meeting, but that is not wise in most meetings. Because it may not be possible for one to pay enough attention to the task at hand when one attempts to do this. Therefore, to make a meeting successful, the following meeting support services should be provided: meeting planning for preparing a well-designed meeting process (or agenda) with a clear purpose in a business context. A meeting process or agenda specifies the sequence of meeting activities, the roles of participants, and the resources allocation to the activities. meeting management for setting up meeting facilities and for participants to take part in the right meeting sessions they are intend to, a common information space for information presentation and manipulation, leadership to run a meeting in an efficient and flexible way, and document handling for documents prepared before a meeting, presented and manipulated in a meeting, and stored for follow-up activities. Based on their roles, meeting participants may have different access rights to the meeting support services. The common information space should not only provide tools for information presentation, but also allow meeting participants to annotate and modify the information presented (e.g. to modify an agenda). For supporting discussion and exploitation, widely used visual artifacts and tools should be provided.
A Cooperative Visual Hypermedia Approach
73
2.2 Distributed Meetings (Virtual Meetings) Distributed meetings are Virtual Meetings that denote the situation where meeting participants from different locations and organizational units meet in a "virtual" meeting place. In such a distributed virtual setting, meeting planning, coordination and communication become even more crucial. The meeting process as one fundamental component of collaboration needs to be viewed and supported as a part of the overall business processes taking place in the organizational and social context. Audio/video channels have to be easy to setup and use. It should also be easy for meeting participants to find the virtual place and join their part of the meeting, or be on-line at the right time for meeting organizers to bring them into the right meeting sessions. Before or during the meeting, the participants may have a need to import pre-existing documents into a common workspace, jointly view and manipulate the workspace in the meeting, and export documents to a shared organizational repository. As a discussion aid, synchronous manipulation and structuring of visual artifacts including writings and drawings are also very important. 2.3 Distributed Meeting Support Systems Efficient and effective technology support for distributed meetings is a key to virtual organization effectiveness through (1) saving of cost and time required for communication and collaboration in distributed teams. This will enable the user organization to better cope with dynamics of the market. (2) better reaction on short notice will be possible. This leads to greater flexibility. (3) establishing/strengthening business relationships (not only to partners, but also to suppliers and customers) due to better communication and collaboration facilities. (4) reduction of media breaks due to integrated document management, collaborative work and conferencing facilities. However, so far, attempts of technological support for distributed meetings (e.g., video conference studios for meetings, Internet-based and Web-based text or audio chatting, white boarding, application sharing tools) have been disappointing. Insufficient progress – or even failure – of most current meeting support systems are caused by their lack of support for shared document handling, by missing support for a rich set of information structures and visual artifacts, and by their insufficient integration with asynchronous modes of co-operation and related applications (e.g., workflow management systems). Most importantly, the current generation of tools for distributed meetings lacks a comprehensive model of such meetings in a business context. A model that integrates the meetings into the overall business processes is necessary to guide the construction of effective virtual meeting facilities. Because of all these deficits, the current generation of facilities remains of marginal value to businesses.
74
W. Wang, J.M. Haake, and J. Rubart
3 The Cooperative Visual Hypermedia Approach Our approach to tackle the above mentioned problems is to develop a cooperative visual hypermedia for providing a common information space with structure-rich visual artifacts, flexible meeting process modeling and control, integrated document management, and session-based meeting management and easy setup of communication and application sharing channels for a meeting session. In this work, we extended our component-based cooperative hypermedia system XCHIPS [7] with visual hypertext artifacts and above mentioned meeting support services. The key points of our approach are presented in the following subsections. 3.1 Visual Hypermedia: A Hypermedia-Based Drawing System with Structure-Rich Visual Artifacts The visual artifacts and tools that people widely use in face-to-face meetings include blank sheets or whiteboards, on which people can write and draw using colored lines, shapes, and sticky tags or pin cards. Sticky tags or pin cards allow people to post them in one way and then to organize or classify them in different ways. It is also very common to see people to draw arrow lines between cards or group of cards to indicate their relationship. Cooperative electronic whiteboards are tools provided in many distributed meeting support systems for such purpose. But these whiteboarding tools lack the flexible structuring support, such as the composing and decomposing capabilities that many object-oriented drawing systems have and the reorganizing and classification, nesting, and linking that supported by many spatial [12] and graphical navigational [17] hypermedia systems. Spatial hypertext uses spatial layout and some visual characteristics to represent relationship. For instances, similar information objects are placed near to each other. Navigational hypertext is the classical hypertext that is normally presented to users as a content page with highlighted embedded links (e.g. a Web page). Navigational hypertext structures may also be presented visually as hypertext maps, in which labeled square or icons represented nodes and arrow lines between them represent links. Our approach to providing structure-rich visual artifacts is to combine the features found in spatial and graphical navigational hypermedia systems as well as those found in drawing tools into a visual hypermedia system. Such a system can make use of various visual properties found in drawing systems for the expressing relationship among various visual artifacts. These visual properties include the (foreground and background) colors, patterns, images, the label text, the size, the orientation, the position, the shape, and the Z-ordering of the visual components. In the mean time, it makes all these visual components into hypermedia objects that can be re-organized into different sets or nested structures, be linked to or referred to each other, and linked to external documents.
A Cooperative Visual Hypermedia Approach
75
For instance, while explicit link representations (e.g. as arrow lines) are good for expressing the precedence relationship between tasks, color-coding is better for indicating the state of the tasks (e.g. yellow means ready and green means on-going). Such visual hypermedia can be used to create and manipulate both the meeting process structures (see section 3.3 and section 5) and the visual contents (see section 5) that used in various sessions of the meeting . The user interface (i.e. the XCHIPS browser) for the visual hypermedia (see Figure 1) resembles that of a drawing tool: it has two visual object palettes providing predefined visual hypermedia object types and general types that can used to derive new types. In Figure 1, on the top toolbar, there are buttons to activate a textual chatting tool and the MS NetMeeting tool. On the right-hand side palette, there is a list of visual object types for process modeling. On the left-hand side palette, there are object types for creating information objects, among which there a general node type (the button with a blue “i” icon) and a general link object type (the button a link icon) for users to create new node and link types on selected hypermedia model objects (such as “folder” or “href”, see section 4.1 and 4.2). The appearance of new visual types can be defined by using menu operations on the newly created general types, for instance, to change its foreground and background colors or patterns, the label text, the size, the orientation, the shape, and the Z-ordering of the visual component, or to load an image. These visual properties correspond to the visualization design dimensions that a good visual design should consider [16]. Any visual objects in the content pane can be used as a prototype for creating new instances of the same type with the same appearance (by copying). A view copy mechanism can be used to create multiple views of the same model object (see section 4.1). The whole nested structures rooted from a composite node can be used as a template for cloning the whole hypermedia structure in one operation. 3.2 Session-Based Meeting Management and A/V Setup A meeting is normally organized into one or more sessions A session is also a meeting, which may involve all or part of meeting participants. Sessions may happen in parallel or one after another. Each session takes a period of time used for a particular purpose or activity and happens normally in one meeting room. To simplify meeting management for distributed meetings, we do not make a difference between a meeting and a session. In our approach, a session is made up of a collection of people, groupware components, and shared objects. To provide a sense of virtual place, each session is visualized as a separated session window. Under the menu bar of the window lists all the names (uids) of the on-line participants of the meeting (see Figure 2). Groupware tools used in the session will be opened in the session window. All participants of a session will have a synchronous instance of the session window. Working with the XCHIPS browser component in a session, other groupware components invoked from the browser user interface or from the shared objects in its content pane can be activated using menu operations on the (closed) views of the shared objects. Options of
76
W. Wang, J.M. Haake, and J. Rubart
the menu operations are provided for users to open them in either in the same session window (thus becoming accessible to all users within this session) or in a new session window (providing a simple transition to individual work or a subgroup meeting in a new session). If a meeting takes a long time and needs multiple sessions, we use a meeting process structure to organize it (see next section) and to divide sessions by opening composite objects for different session activities in different session windows. Meeting organizers can invite other users to join their working session by activating the Invite user button at the upper right corner of the session window (see Figure 2). Users can also use a query tool to search for all the active meeting sessions and request to join selected sessions. With the XCHIPS browser, it is very easy to set up a NetMeeting session for audio/video communication and application sharing for all the on-line participants (see the section 4.4 for detail). Users can also activate a Chat groupware component for all the session participants by clicking on the Chat tool button on the user interface. 3.3 Process-Based Meeting Control and Document Handling A process structure can be described as a directed graph consisting of a coordination structure among the steps. Such a graph can be modeled as a typed hypermedia structure (see also [23]). In XCHIPS, the process structure is represented by a set of predefined hypermedia object types: Task nodes, which may carry a description of the task and other information objects (such as embedded links to external documents) as its contents, and which can be related to other resources via specific explicit links, such as a “assign” link from a role (or position). When a task node contains other task nodes connected with process links, it becomes a composite task node that presents a process or a sub process. Thus, processes can be nested and may form a layered graph. This nesting allows for representing the decomposition of work procedures into smaller parts. Task nodes have process-specific attributes, such as state and time, and have process-specific behaviors, such as state transitions and activation of certain actions, Process links, which represent precedence relationship between task nodes. Process links have control flow and data flow behaviors. For example, instances of the process link type “precede" can be used to link tasks and processes into sequences or parallel structures, where each precede link specifies under which condition the successor node can be activated and which documents will then flow from the predecessor node to the successor node, Role (or position) nodes, which specify the responsibility in a process or an organization, Person nodes, placeholders that present actual individuals, Assignment links, which assign a role to a task. Filled-by links, which specify which Roles are assumed by which Persons, and
A Cooperative Visual Hypermedia Approach
77
Any other nodes or links for additional information, such as information about the goals and objectives of the work process, background information, and resources. Thus, in such a typed hypermedia environment, a process can be represented as graphs consisting of typed hypermedia objects, together with additional information related to the process. For a clear overview of the state of a process, the state information of task nodes is color-coded in their views (white for inactive, yellow for enabled, green for active and brown for completed). Tasks can be performed by menu operations activated on the task nodes. Selecting "enable" and then "activate" menu operations on the root composite task node of a process structure can start the process execution. When a composite task node is "activated", the starting tasks of the process structure nested in the composite task node are "enabled". They can then "activate" their tasks. When the work of a task is finished, its actor can select the "complete" menu operation on the task node, such that its following tasks (or nested starting tasks if it is a composite task node) are "enabled". A process is completed when all its subtasks are completed.
Using such a process-enable hypermedia structure, a meeting process can be created: A meeting process can be modeled using a root task node, which contains other task nodes for meeting sessions and agenda items (meeting activities). Information objects (see section 4.1-4.3) presented and manipulated for each meeting activities can be placed into the task nodes represent the meeting activities before the meeting takes place.
Meeting specific roles, such as Chairman, Recorder, Presenter, Timekeeper, and Participant can be modeled using Role nodes.
Meeting participants can be modeled using the Person nodes. The meeting roles can be assigned to meeting activities by the assignment relationship. The meeting role and participant relationship can be specified using filled-by links. The document handling capabilities are integrated into several types of embedded links that can be placed in folders or tasks in a process model (see section 4.12-4.3). The meeting process structure can be modified at the beginning of a meeting or modified on the fly during the meeting. The execution of a meeting process (i.e. the transition from one meeting activity to another) can be manually controlled by the Chairman. Presenter can open documents in his or her task node when the task is enabled. For annotation, or discussion and exploitation activities (tasks), visual artifacts can be used together with the audio or textual chatting communication between meeting participants.
78
W. Wang, J.M. Haake, and J. Rubart
4 Implementation Details The cooperative visual hypermedia as described in previous section has been implemented and supported with a cooperative visual hypermedia browser in our component-based XCHIPS system, which is an extension of the CHIPS system [22-24]. This section focuses on the cooperative visual hypermedia related implementation issues.
4.1 Visualization and Behaviors of Hypermedia Objects A graphical view of a hypertext is a view of its underlying model (instance). It is composed of the views of the objects (nodes) and relationships (links, containment, and visual indications) in the model. If a node has content or if it is a reference to another object, the node will have at least two views: one for its closed view and the other for its opened view (for its content or the referred object). A node that refers to another object or external document (URL) can be seen as an embedded link. In this case, node opening is equivalent to (reference) link following. Each node or link object may have more than one view. In this case, all of them are kept consistently up-to-date with the model of the node or the link. The view and controller object for a closed view has an instance variable pointing to its model object, while the model object has no direct (instance variable) reference to its view object. The changes to a model object are propagated to its view objects by means of an event subscription mechanism. The controlling operations to the hypermedia object can be triggered using the menu available from the view objects. Menu operations available from a link view or a closed node view object include operations collected from both the view object and its underlying model object. We use Groupware Component to implement the opened view of a node. The binding between the model object and the view object for its opened view is resolved at run-time through a model-task-component triple object that is published on the view component object class (see [7] for details). In addition to the explicit links, the layout (e.g. positions and visual properties) of the nodes can also indicate relationships. For instance, for a composite node presenting the structure of an organization, the contained views of nodes and links can be laid out as an organization chart – a top down hierarchical structure whose links are lines with rectangular corners. The content view of a composite node can be provided with a layout manager to automatically layout its components. For manually handled free layout, the positions, bounds and other visual properties are persistently stored so as to assure a stable spatial and visual relationship representation.
A Cooperative Visual Hypermedia Approach
79
4.2 Text, Hand Writing or Drawings, Lines, Shapes, and Images as Hypermedia Objects By default, these view objects are created together with a simple model object, which has a type label and a name attributes. The model object can be changed to other predefined model object types. The pre-defined types include composite model objects types (such as “folder” and “task”) which can contain other node and link objects, an xref model object that can refer to another shared object (see [7]), a href model object that can refer to a read-only external document (see below), or a Webdec model object which can refer to an editable external document (see below). 4.3 Shared Objects as Embedded Links to Shared Documents For integrating document handling into the common information space, two types of shared objects are developed as embedded (cooperative) links to documents on the Web. href is an embedded link for a read-only access to documents on the Web (such as HTML pages and other document types that can be handled by plug-ins of a standard Web browser). The pages or documents are fetched and displayed by the standard Web browser or its plus-in applications. This embedded link is presented as a labeled icon. The behavior of the link is encapsulated in the href object type. Users can activate a menu upon the labeled icon to - set a label, - set a URL, - open a page or document for oneself, or - open it for all the active users in the meeting session. Such a link that opens an external document (or a page) for more than one person (on a number of dynamically selected machines) can be considered as a kind of computed cooperative link. Both the 'open for one' and the 'open for all' methods can also be considered as process links (see the HB/SP series [29] on links and anchors as processes), as they both activate a method (or methods) of a COM object on a local machine (through a Java-COM bridge). The difference between them is that the 'open for all' method sets the 'showForAll' attribute of the href object; while the 'open for one' method not. After the invocation of the 'open for all' method, the changed attribute 'slot' is replicated to all the local proxies of the href object for its distributed users. This value change (i.e. from false to true) in turn triggers a local call to COM APIs. In this case, it is an href method calling for the FollowHyperlink(url) and close() methods of a Word.Document COM Object. The open for all option can be used to do a Web-based presentation using a standard Web browser. For doing so, user can create a sequence of href embedded links pointing to each of the Web pages, and then activate them in a sequel in his or her presentation.
80
W. Wang, J.M. Haake, and J. Rubart
Webdec is an embedded link for a read-write access to documents on the Web (such as HTML pages and other document types). The pages or documents are fetched and displayed by the Web browser for HTML pages and MS Office tools for MS office documents. This embedded link is presented as a labeled icon view. As the underlying data object of the view is a shared object, many attributes can be defined for the object and be reflected on the view for group awareness purpose. The behavior of the link is encapsulated in the webdoc object type. Among many operations on the object, users can activate a menu upon the labeled icon to - set a label, - set a URL, - check-out and edit (i.e. lock, download, and open) a document from an organizational shared document repository, which can be any Web server that supports the http get and put protocols, and - check-in (i.e. upload and unlock if locked) a document to the shared repository. When a document is checked out for editing, it is locked and a name label appears on the graphical view of the embedded link. The name label provides a kind of group awareness information on who is editing the document. If another person tries to invoke any of the above menu operations, he or she will get a warning message. This message tells him or her that the document is locked and he or she can contact the person for releasing the lock or for setting up a NetMeeting session to share the MS Office application for the document (see next section). The locking is implemented with a locking-service that is a simple implementation derived from the naming service of the XCHIPS system. The upload and download methods used by the check-in and check-out menu operations are implemented initially using the common http get and put methods, and then in a later version using a WebDav [3] based Java package from one of our project partners. The open document method used in the Check-out menu operation is implemented using a COM API, i.e. an open() method of a Word.Document COM object.
4.4 Mobile Groupware Components as Embedded Links to Distributed Applications We use Microsoft NetMeeting for audio/video communication channels and for application sharing (e.g. to share a PowerPoint presentation or to jointly edit a Word document). Because NetMeeting uses a point-to-point network connection, to setup a NetMeeting session for a group of people, the meeting host has to inform all the participants the host machine’s IP address and let them call this address using a NetMeeting client. This is a cumbersome manual process. To make this simple, we develop another type of embedded link, with which the NetMeeting connection for a group of people can be setup easily. Again, here we used a shared object as a wrapper of the NetMeeting COM APIs. Because in this case, we want to allow all the meeting participants to initiate, join or
A Cooperative Visual Hypermedia Approach
81
leave a NetMeeting session, we need to provide them with a user interface to invoke the corresponding COM APIs. For this reason, the shared object has two views: a closed view (shown as an icon) and an opened view, which presented in a separate window (i.e. an Internal Frame within the session window). The closed view is used to invoke the opened view, while the opened view in the separated window provides the graphical user interface for users to setup and control a NetMeeting session. The groupware component can be considered as a computed multi-source process link to the NetMeeting COM objects on the distributed machines of the meeting participants. When one of the participants activates the embedded link and then push the ’host a meeting’ button on the opened view, the user’s machine becomes the NetMeeting host (i.e. the destination of the NetMeeting link). Then he or she can push the 'start a meeting' button to let the NetMeeting client on each all participants’ machine to connect to host automatically (see Figure 2). In this connection process, the link sources (i.e. the NetMeeting clients represented as the IP addresses of all the participants are found from the active user list of the session object that is accessible from the shared object. This is possible as the User object of the system has an IP attribute whose value is automatically assigned when the user is logged on the system. The NetMeeting connection call (through an NetMeeting COM application programming interface with the host IP address as its parameter) is invoked on the local instance of the groupware component (see [7] for detail). When each client invocation is done from each participant’s machine, the NetMeeting host participant gets a dialogue box asking him or her to accept the NetMeeting connection from the client. After that the original NetMeeting control window appears on all the participant’s desktop and the NetMeeting setup is done. Participants can talk to each other and they can also use this control panel to initiate application sharing, passing control to shared application. Using the same techniques, an embedded link (and a groupware component) can be created for doing a PowerPoint presentation for the meeting participants. In this case, the embedded link is a multi-target link; its groupware control panel will has buttons to navigate forth and back in a slide show. This can be used together with conference phone or chat tools in situations when a NetMeeting connection is prevented by firewalls at participants' sites.
5 Sample Use Cases and User Experience EXTERNAL is an IST project on technology support for virtual enterprises. There are five partner organizations distributed in Germany, Norway, and Greece. XCHIPS is one of the tools developed in the project for providing 3C (coordination, cooperation, and communication) and cooperative work management services. The support for distributed meeting is one of its most important services. For testing our own ap-
82
W. Wang, J.M. Haake, and J. Rubart
proach, the XCHIPS system along with other tools developed in the project have been deployed and used in three use cases, one of which is for the joint planning and management of the project. After a period of testing, the first deployment of the XCHIPS system for use cases was in last June, and then a series of revised versions were issued based on the feedback from its use.
Fig. 1. A meeting process description
The following is a description of a distributed meeting use case using the XCHIPS system by the EXTERNAL project management team for distributed project management meetings. The project management team consists of the project coordinator, the work package managers and the site managers of the project. The following use case describes one of the project management meetings. The purpose of the management meeting is to review progress, discuss use case designs, and perform a crisis analysis for identifying important issues that have to be addressed for a successful project. Before the meeting, the organizer (Chairman) of the meeting creates a meeting agenda (in the form of a meeting process structure in a composite task node, which is part of the overall process model for the joint planning and management of the project). The meeting process model includes the status report, user case design, and crisis analysis as its major activities (see Figure 1). Then the Chairman sends an email message to all the participants to inform them the time, the topics, and the (virtual) location of the meeting (i.e. the URL of the meeting process model). Based on the plan, the Presenter of the meeting prepares and then checks-in a PowerPoint file into the “User case design” activity that is assigned to him.
A Cooperative Visual Hypermedia Approach
83
When the meeting time comes, the participants are all logged on to the system, and then are invited into the meeting session by the Chairman. Then one of the meeting participants sets up the NetMeeting tool for all the participants (see Figure 2 for the groupware control panel). As the first meeting activity, the Chairman tries to see if there is any request to adjust the meeting agenda. Then each work package manager reports the status of his or her work package using the audio communication channel.
Fig. 2. A groupware component for NetMeeting
After that the Presenter activates his PowerPoint presentation by selecting the “check-out” menu operation upon a Webdoc embedded link in side of the “Use case design” task. The Presenter shares it with others using the NetMeeting control panel on his desktop. After the presentation and a brief discussion, the Chairman starts the “Crisis analysis” task and opens the task node in the same session for all the meeting participants. Coordinated by the informal audio channel, each participant first posts the issues he or she thinks to be important (see Figure 3), and then they move the vis-
Fig. 3. Collecting important issues
84
W. Wang, J.M. Haake, and J. Rubart
ual cards into several clusters and using explicit links to indicate the relationship among the clusters (see Figure 4). Finally, together with all the participants, the Chairman makes an action list to be carried out after the meeting. During the whole meeting process, the Recorder makes minutes individually using text, scribbles, or other visual components in the content pane of each activity. After the meeting, the Recorder collects his or her notes into a minute (accessible in the Minutes task node) and informs all the participants to see if there are any questions on it. Based on the decisions and action list made in the meeting, the project manager can monitor the execution of the follow-up actions.
Fig. 4. Clustering and linking ideas
From over a year testing and half a year use of the system in the EXTERNAL project, we got numerous comments and feedback from the users. They liked the colorcoding of the meeting agenda items (i.e. the task nodes) and the minute recorded within or accessible from the task node for each meeting activity. As this allows them to see (particularly for the late comers of a meeting) what has been performed, what is on going, and what are the next to come. Other team members who are not able to attend the meeting can navigate the meeting process structure to learn what happened in the meeting and to find and understand the decisions made in its original meeting context. They also liked the ability to write, scribble, post-visual artifacts, and to reorganize them for on-line discussions. The handling of MS documents and its integration into a process structure were considered a useful and practical solution, as all the user organizations of the use case partners of the project have MS Office suite and Windows operating system used in their daily working environment.
A Cooperative Visual Hypermedia Approach
85
Users have also experienced many problems on using the system. As both the XCHIPS and the NetMeeting require the user organizations to open certain ports for inbound TCP/IP communications. One of the problems is with the firewalls. We resorted to the help of the system administrators and even the management of the organizations for opening the port or to deploy machines in a de-military zone of their Intranet settings. But still we have got one user organization refused to do so. For these reasons, in many situations, we have to use conference phone instead of NetMeeting for voice communication. This also motivates us to develop Web-based presentation tools (as mentioned in section 4.3-4.4) that do not have a firewall problem. Another experience we got is that even a NetMeeting session can be setup, participants still prefer to use conference phone for voice communication, as it provides a better sound quality. In these cases, the common workspace provided by XCHIPS was considered by most meeting participants a good aid for presentation and discussion. Our experience suggests that the system is better suited for short distributed meetings of a small group of people. We still have a long way to go before we can use such systems to replace long lasting (i.e. over one day) face-to-face project meetings of a large group of people.
6 Related Work The hypertext technology most closely related to our cooperative visual hypermedia is spatial hypertext, such as the spatial and visual hypertexts supported by Aquanet, Viki [12], VKB [5] and CAOS [18]. Our cooperative visual hypermedia supports a kind of mixture of multi-domain visual hypertext structures, including spatial, set-based, navigational, automaton-based, and cooperative hypertexts. This kind of hypertext extends spatial hypertext with a set of ready-made visual hypermedia objects that is not only visual, but also has pre-defined computational semantics (i.e. each view object has an application specific model object behind it). It also provides ad hot visual hypermedia objects (text, hand drawings, filled or unfilled shapes, images) created-on-the-fly in a shared information space. It supports multiple views (i.e. view objects) on the same model objects. These view objects can form multiple classifications or groupings (i.e. alternative views) on the same set of hypermedia objects. In addition, it includes explicit links that are missing in set-based spatial hypertext. These explicit links can enrich the explicit relationship expressiveness and the computational semantics (as demonstrated by the process links) of spatial hypertext. Other enhancement to existing spatial hypertext is the cooperative manipulation of visual artifacts and the cooperative document handling upon Web-based repositories. Among meeting support systems, the one nearest to ours is the Dolphin system from our group a few years back [14]. Dolphin addressed a much wider range of meeting support issues, such as user interaction on large display in a meeting room and support meetings held in multiple meeting rooms. Dolphin also provides a hypermedia-based whiteboard as a common information space. While XCHIPS focuses on desktop based virtual meeting support for distributed teams. What XCHIPS adds to
86
W. Wang, J.M. Haake, and J. Rubart
Dolphin and other cooperative hypermedia systems developed in our group ([22-23, 7]) are the integrated process support, document handling, meeting management, and a rich set of visual artifacts for supporting distributed meetings. Nest, in the sequel, we discuss several areas of meeting support systems in relation to our approach and our XCHIPS system: Desktop Teleconferencing: In addition to available desktop-teleconferencing functionality as provided by NetMeeting and WebEx, our approach also provides meeting oriented conference control as well as meeting specific functionality (e.g., agenda or meeting process planning). Video-conferencing rooms (e.g., media spaces [10]): XCHIPS may also be used in electronic meeting rooms with large displays and at the same time it can integrate well remote desktops for participants no available in the rooms. Shared documents (e.g., asynchronous shared workspace systems BSCW [2] and WebDav [3]; cooperative hypermedia systems KMS, rIBIS; meeting room systems Group Systems [15], CoLab [20]; Shared editing tools of GROVE [4], ShrEdit [13]; and shared drawing tools of GroupSketch [6] and CaveDraw [9]: Whereas shared document systems enable shared viewing or shared editing of isolated documents, XCHIPS exploits CSCW and hypermedia technology to facilitate rich information structures and seamless process support through the provision of shared workspaces, including traditional linear documents and hypermedia structures as well as support of transitions between different meeting phases. Further more, the use of multimedia functionality inherent in hypermedia will support the integration of different pieces of information without introducing media breaks. Asynchronous collaboration support (e.g., bulletin boards, e-mail or workflow management systems): In contrast to asynchronous collaboration tools, which can only support the exchange of information or describe schematic, well-structured processes, XCHIPS bridges the technology gap and integrate schematic workflow with unstructured phases of the business process, where flexible ways of problem solving, coordination and collaboration support are required.
7 Conclusions Business processes of today are characterized by a change from individual work to teamwork as well as by a shift from single, independently acting corporations to virtual organizations operating as dynamic networks. To realize the benefits of globalization and business networking, we have to find a way for teams of knowledge workers effectively work together across distances and time zones. Efficient and effective technology support for distributed meetings is a key to virtual organization effectiveness. However, current distributed meeting support systems lack support for a wellplanned flexible meeting process, lack a common information space with structurerich visual artifacts, and lack the support for document handling.
A Cooperative Visual Hypermedia Approach
87
Our approach to tackle the problems is to develop a cooperative visual hypermedia for providing a common information space with structure-rich visual artifacts, flexible meeting process modeling and control, integrated document management, and cooperative session-based meeting management and easy setup of communication and application sharing channels for a meeting session. Two use cases are presented, which show that using the cooperative visual hypermedia, distributed teams can perform many kinds of meetings, in the meantime, enjoying dedicated support for the planning, control, information management, and follow-up activities of a distributed meeting. In terms of hypertext technology and its application to distributed meeting support, our approach has a number of innovation aspects: The cooperative visual hypermedia integrates many visual and interaction features found in multiple hypertext domains including cooperative hypermedia, spatial hypermedia, navigational hypermedia, and automaton-based workflow hypermedia [21–23]. It demonstrates the possibility and usefulness of the co-existence of multi-domain visual hypermedia structures for supporting distributed meetings. It provides flexible meeting process support and a common information space for meeting planning, flexible meeting process modification and execution, and follow-up activities (to be carried out in either synchronous or asynchronous cooperation). I.e. it provides a seamless transition between synchronous cooperation and asynchronous cooperation. It integrates document handling into the meeting process structures. More importantly, it can connect and integrate multiple meeting processes into the whole organizational business (process) context. The cooperative embedded links for opening external documents for multiple distributed users and the cooperative embedded links for controlling external applications cooperatively are new to existing hypertext linking mechanisms. To be successful in providing virtual meeting support, we must integrate people, processes, and technology. Our cooperative visual hypermedia approach have used explicitly (visually) represented knowledge about the task at hand, the domain of discourse, and the set of participants involved to improve meeting process. It allows more flexibly move between and integrates different kinds of meetings or a series of meetings into a large business context. It makes contextual information persistently available when moving between different meeting processes. This makes it easier to integrate such environment with the enterprise-wide knowledge and project management systems as well as with the personal work environments of individual knowledge workers. This contrasts sharply with the currently available teleconferencing systems, which are stand-alone generic facilities with very limited capabilities.
88
W. Wang, J.M. Haake, and J. Rubart
Distributed meeting support involves a wide range of technical and social issues, and may use a wide range of communication and groupware technologies. In this work, we made a focus on distributed desktop-based meeting support for small group meetings. From our experience with the Dolphin system, this system can also be used for co-located meetings and the meetings with a mixture of co-located and distributed team members. For this potential, many useful features of the Dolphin system [25] could be re-established. We are also interested in the integration of mobile devices for remote meeting participants. As the current NetMeeting system has difficulties with firewalls, we are looking for alternative audio communication and application-sharing solutions that support http tunneling so as to have a better Web-based integration of our cooperative hypermedia based solutions. Currently one of our EXTERNAL project partners is performing evaluation on the XCHIPS system and other EXTERNAL tools, and we are cooperating with them for both feedback and findings.
Acknowledgments. We would like to thank our EXTERNAL project partners for feedback and discussions on the usage of the tools reported in the paper.
References 1.
2.
3. 4. 5.
6.
7.
8. 9.
Akscyn, R. M., D. L. McCracken and E. A. Yoder, "KMS: A Distributed Hypermedia System for Managing Knowledge in Organizations,"Communications of the ACM, v. 31, no. 7, July 1988, pp. 820-835. Bentley, R., Horstmann, T., Sikkel, K., and Trevor J. Supporting Collaborative Information Sharing with the World Wide Web: The BSCW Shared Workspace System. In Proceedings of the 4th International WWW Conference, Issue 1, O’Reilly, Dec. 1995, pp. 6374. E. James Whitehead, Jr. WebDav, in Proceedings of ACM Hypertext’01, pp. 259, Aug. 1418, 2001. Ellis, C.A., Gibbs, S.J., and Rein, G.L. Groupware: Some issues and experiences. Communications of the ACM 34, 1 (Jan. 1991), 38-58. Frank M. Shipman III, Haowei Hsieh, Preetam Maloor, J. Michael Moore, The Visual Knowledge Builder: A Second Generation Spatial Hypertext, in Proceedings of ACM Hypertext’01, pp 113-122, Aug. 14-18, 2001. Greenberg, S., and Bohnet, R. Group Sketch: A multi–user sketchpad for geographically distributed small groups. In Proceedings of Graphics lnte@aces'91 (June 5-7, Alberta, Canada), 1991, pp. 207-215. Jessica Rubart, Joerg M. Haake, Daniel A. Tietze, Weigang Wang "Organizing shared enterprise workspaces using component-based cooperative hypermedia", in Proceedings of ACM Hypertext2001, pp 73-82, Aug. 14-18, 2001. Kevin Wolf., "The Makings of a Good Meeting", 1994, available at http://www.dcn.davis.ca.us/go/kjwolf/manual.html Lu, I., and Mantei, M. Idea management in a shared drawing tool. In Proceedings of the European Conference on Computer-Supported Cooperative Work (EC-CSCW '91). (Sept. 24-27, Amsterdam), 1991, pp. 97-112.
A Cooperative Visual Hypermedia Approach
89
10. Mantei, M., Baecker, R., Sellen, A., Buxton, W., Milligan, T., and Wellman, B. Experiences in the use of a media space. In Proceedings of the CHI ’91Conference (New Orleans, Louisiana), 1991. 11. Marilyn Manning, "Meetings Bloody Meetings", available at http://www.mmanning.com/Articles/MeetingsBloodyMeetings.html, Reprinted from March 1998 issue of Channel Magazine 12. Marshal, Catherine C and Shipman III, Frank M.: Spatial Hypertext and the Practice of Information Triage. In proc. of ACM Hypertext’97, pp : 124-133 13. McGuffln, L., and Olson, G. M. ShrEdit: A Shared Electronic Workspace. Technical Report No. 45, University of Michigan, Cognitive Sciences and Machine Intelligence Laboratory, 1992. 14. N.A. Streitz, Joerg Geissler, Joerg M. Haake, J. Hol DOLPHIN: Integrated Meeting Support across LiveBoards, Local and Remote Desktop Environments. In: Proceedings of the 1994 ACM CSCW’94, pp. 345-358, N.C., October 22-26, 1994 15. Nunarnaker, J .F., et al. Electronic meeting systems to support group work. Communications of the ACM 34,7 (July 1991), 40-61. 16. Paul Kahn, Information Architecture: a New Discipline for Organizing Hypertext, Opening keynote speech at Hypertext’01, in Proceedings of ACM Hypertext’01, pp. 1, Aug. 1418, 2001. 17. Rein, G. L., Ellis, C. A., rIBIS : a real-time group hypertext system, International Journal of Man-Machine Studies, 1991, volume 34, pages 349-367. 18. Reinert, O., Bucka-Lassen, D., Pederson, C.A., Nuernberg, P.J. CAOS: A Collaborative and Open Spatial Structure Service Component with Incremental Spatial Parsing. In Proceedings of Hypertext’97, ACM Press, Southamton, U.K., pp. 49-50 19. Roseman, M., and Greenberg, S. TeamRooms: Network Places for Collaboration. In Proceedings of CSCW’96, ACM Press, Cambridge, MA, 1996. 20. Stefii, M., et al. Beyond the chalkboard: Computer support for collaboration and problem solving in meetings. Communications of the ACM 30, 1 (Jan. 1987), 32-47.27. 21. Stotts,P.D.and Furuta, R. 1989. Programmable browsing semantics in trellis. In Proceedings Hypertext ’89. Pp 27-42. 22. Weigang Wang "Team-and-Role-based Organizational Context and Access Control for Cooperative Hypermedia Environments", in Proceedings of ACM Hypertext’99, pp 37-46, Feb 23-25, 1999 23. Weigang Wang and Joerg M. Haake, "Flexible Coordination with Cooperative Hypermedia", Proceedings of ACM Hypertext’98, pp. 245-255, June, 1998
Towards UML-G: A UML Profile for Modeling Groupware Jessica Rubart1, 2 and Peter Dawabi1 1 Fraunhofer
Institute for Integrated Publication and Information Systems (IPSI), Dolivostrasse 15, 64293 Darmstadt, Germany 2 go4teams GmbH, Julius-Reiber-Strasse 15a, 64293 Darmstadt, Germany {rubart, dawabi}@ipsi.fhg.de
Abstract. Groupware is explicitly designed to support the cooperation among group members. The implementation of cooperation-aware groupware is supported by several object-oriented toolkits and frameworks, but there is no unified way to model applications built on top of these. We propose UML-G as an extensible UML profile for modeling groupware and want the community to contribute to it. We identify groupware specific modeling needs related to shared data modeling. Since these needs are not addressed by standard UML, we define UML-G’s shared data modeling part. Usage scenarios demonstrate how UML-G can be used to assist groupware modeling. UML-G supports explicit modeling of groupware related needs. Moreover, a shared understanding between developers is backed, which abstracts from the implementation. In addition, CASE tool support for UML-G strengthens its practical relevance.
1
Introduction
Groupware, such as Computer-Supported Cooperative Work (CSCW) and Learning (CSCL) applications, are explicitly designed to support the cooperation among group members [10]. This might be in a distributed or co-located setting. In addition, it might be synchronous or asynchronous. Synchronous cooperation means cooperation happening at the same time with typically fine-grained notifications giving immediate feedback about the activities of other users, whereas asynchronous cooperation can happen at different times with usually no notifications of other users’ actions [14]. The implementation of cooperation-aware groupware is supported by several object-oriented toolkits and frameworks, but there is no unified way to model applications built on top of these. The Unified Modeling Language (UML) [17, 22] is the standard notation for modeling object-oriented software. A UML Profile specializes the UML for a specific domain. We propose such a profile for groupware (UML-G) in order to assist developers in explicit modeling of groupware related needs, such as shared information.
J.M. Haake and J.A. Pino (Eds.): CRIWG 2002, LNCS 2440, pp. 93–113, 2002. © Springer-Verlag Berlin Heidelberg 2002
94
J. Rubart and P. Dawabi
There are several groupware tools available, such as e-mail systems, shared repositories, shared workspace systems, e.g. BSCW (Basic Support for Cooperative Work) [2], audio/video-conferencing, shared whiteboards or sharing support for single user applications. Sometimes it is sufficient for groupware developers to select a single-user tool, such as an office suite’s word processor, and combine it with a shared repository in order to support asynchronous editing of documents. To support synchronous editing, sometimes it is sufficient to combine the word processor and the shared repository with an application-sharing tool, such as Microsoft’s NetMeeting [27]. But there are also obvious restrictions, e.g. by using an application-sharing tool only strict WYSIWIS (What You See Is What I See) functionality can be supported. Moreover, no workspace awareness (if there is any workspace) can be given - in the sense of an up-to-the-moment understanding of another person’s interaction [12]. That’s why application-sharing tools belong to the cooperation-transparent class of groupware. To develop new cooperation-aware applications, object-oriented toolkits and framework, e.g. DistView [19], GroupKit [20], COAST [23], JSDT [3], Habanero [4] and DyCE [29] have become available. All these toolkits and frameworks have their special way of using them. There is no unified way to model applications built on top of these. In this paper, we identify groupware specific modeling needs related to shared data modeling. We propose a modeling language, UML-G, supporting groupware specific modeling needs and designed as an extensible UML profile. With this language, groupware developers are supported in modeling their cooperative applications independent from the latter implementation. This supports explicit modeling of groupware related needs, and a shared understanding between developers, which is independent of and thus abstracts from the latter implementation. The remainder of this paper is organized as follows: The next section deals with a problem description related to shared data modeling, which leads to a list of requirements UML-G has to fulfill. Then, UML extensions are defined for UML-G, which address the identified requirements. Afterwards, usage scenarios are presented that utilize UML-G’s current shared data modeling part. Next, we talk about CASE (Computer Aided Software Engineering) tool support for UML-G in order to strengthen its practical relevance. Afterwards, related work is presented. The paper ends with conclusions and plans for future work.
2
Requirements: A Problem Description Related to Shared Data Modeling
This section identifies core requirements for modeling groupware. First of all, both, asynchronous and synchronous cooperation – in a distributed as well as co-located setting, work on shared information – either at the same time or at different points in time. Therefore, this is our first requirement: R1. A modeling element marking shared information is needed.
Towards UML-G: A UML Profile for Modeling Groupware
95
Asynchronous cooperation requires persistent data; otherwise different persons at different points in time can’t continue work. In addition, if synchronous work needs to be continued later or at least the results need to stay available, persistence is also required for synchronous cooperation: R2. Shared information requires the option to be modeled as persistent. Synchronous cooperation requires notifications of other users’ interactions since it is explicitly designed to support simultaneous work. These notifications are also important for the provision of awareness. Hence, changes of shared information may need to be propagated: R3. Notifications on shared information need to be supported. Since several users access shared information, access control might be necessary. Therefore, there is a need for modeling access-controllable shared information: R4. Shared information requires the option to be marked as accesscontrollable. Groupware toolkits and frameworks usually provide concurrency control mechanisms so that shared data is kept consistent though multiple users access it simultaneously. But it might be necessary due to some semantics of the cooperative application that shared information should be explicitly locked, e.g. when using floor control mechanisms. Floor control can be used to moderate the cooperation. Only one person at one point in time is in charge of the floor and hence able to change some shared information. Locking is independent from the users who access the shared data so that it differs from access control (note that this requirement does not address the usage of concurrency control techniques, such as optimistic and pessimistic concurrency control – see future work): R5. Shared information requires the option to be marked as lockable. Users of cooperative applications need a model of themselves so that for instance access control mechanisms can be applied to them. In addition, users can be interested in information about other users or awareness regarding users can be necessary. In general, we are talking about actors, such as users, teams or even system parts, which are designed as user representatives. Actors need a model of themselves. Moreover, actors can fill roles. This leads to our last core requirement we have identified: R6. Shared models of groupware actors and roles need to exist. The following table summarizes the identified requirements: Table 1. Summary of Requirements for Modeling Groupware related to Shared Data Modeling
R1 R2 R3 R4 R5 R6
Shared information Persistent shared information Notifications on shared information Access control on shared information Lockable shared information Shared models of groupware actors and roles
96
3
J. Rubart and P. Dawabi
Towards UML-G
Based on the identified requirements we have designed a shared data modeling part of UML-G by using the extension mechanisms of UML. The shared data modeling part itself is designed in an extensible manner, too. 3.1
Extension Mechanisms of UML
UML provides three mechanisms for extension: stereotypes, tagged values and constraints. Stereotypes classify other UML elements and thus represent variations of them with the same structure, but a different intent, respectively. In general, a stereotype represents a usage distinction. Tagged values are (Tag, Value) pairs attaching information to a model element and thus representing properties. Constraints allow the specification of new semantics (a condition or restriction) for a model element linguistically in some textual language. For details see [17]. A UML profile is a predefined set of stereotypes, tagged values, constraints, and notation icons, which tailor the UML for a specific domain. Such a profile does not extend the metamodel of the UML (that defines classes, attributes, stereotypes etc.), but it provides modeling elements for specializing standard UML to a particular domain. This has the advantage that CASE tools supporting the UML extension mechanisms can be configured to support modeling with the profile (see section 5). Since the UML specification does not provide a formal approach for defining the semantics of new stereotypes, tagged values and constraints, we describe the semantics of UML-G informally. 3.2
Syntax and Semantics of UML-G’s Current Shared Data Modeling Part
According to the requirements we have one basic model element that is shared information (R1). This model element can be further specified by e.g. lockable or persistent. Therefore, we have introduced the stereotype <<shared>> and decided to define constraints or tagged values on it to extend its semantics. The stereotype <<shared>> applies to the UML baseclass Element, which is the class in the UML metamodel at the very top of the inheritance tree. Thus, the stereotype <<shared>> can be applied to any UML model element. Instances of elements marked as <<shared>> are potentially accessible from all users. This is meant completely independent from the latter implementation – whether it will be realized by e.g. using a replicated architecture, one-to-many communication channels or remote objects. A shared element can be further specified by the Boolean tagged value {lockable} in case it is used in a scenario where for example floor control needs to be supported (R5). We have chosen a Boolean tagged value in order to indicate whether locking needs to be supported or not. If the cooperative application developer wants to specify the locking in more detail, she can use standard UML model elements, such as associations and OCL (Object Constraint Language) constraints [31]. We haven’t yet identified specific OCL constraints,
Towards UML-G: A UML Profile for Modeling Groupware
97
which need to be predefined in the profile. Note that you can leave out the value of a Boolean tag, if it is set to TRUE. Similarly, we have designed the extensions {access-controllable} and {observable} (R4, R3). A shared model element can be marked as {access-controllable}, which means that during runtime access control mechanisms can be applied. It can be marked as {observable} to express that notifications about changes are possible. This is important to support synchronous cooperation, which usually needs fine-grained notifications. We have chosen the term observable in order to use a more active term. And again, by using e.g. associations and OCL constraints from standard UML more details on the semantics can be expressed by the groupware developer. A persistence Boolean tagged value (R2) is already available in standard UML and is defined on the model elements association, attribute and classifier (which is a supertype of e.g. class). Hence, it can be easily combined with UML-G. If we need this tag on other UML model elements as well, we need to define it. For now, the existing tag is sufficient. In order to model roles and actors of cooperative applications (R6), we have introduced the stereotypes <<sharedRole>> and <<sharedActor>>. We have defined them as subtypes of <<shared>> (see Fig. 1) so that the Boolean tags {accesscontrollable}, {lockable} and {observable} can also be applied to them. <<stereotype>> shared
<<stereotype>> sharedRole
<<stereotype>> sharedActor
Fig. 1. Stereotype-Framework
This is important since according to the requirements, models of groupware users are also shared information, on which e.g. notifications regarding changes need to be possible. For example, it need to be notified whether a user is online or offline. In addition, <<sharedRole>> and <<sharedActor>> are separate stereotypes in order to mark their special meaning. With <<sharedRole>> roles in cooperative sessions are marked and with <<sharedActor>> actors in cooperative sessions are marked that can take several roles. Adding new sub-stereotypes in order to make explicit special shared information can extend this “stereotype-framework”. These sub-stereotypes inherit the possibility to apply the Boolean tags {access-controllable}, {lockable} and {observable} to them. Moreover, additional tagged values or special constraints can be defined on the general stereotype <<shared>> or on special sub-stereotypes. Furthermore, a sub-stereotype can specialize the baseclass to which it applies by naming a subclass of the parent-stereotype’s baseclass. We defined for instance that the stereotypes <<sharedRole>> and <<sharedActor>> apply to classes, rather than to any model element. For the super-stereotype <<shared>> it is important to apply to other model elements than classes as well. In the following, some examples are given: The stereotype
98
J. Rubart and P. Dawabi
<<shared>> applied to attributes is needed in order to support higher granularity. It can be that a groupware developer wants to model some attributes as shared, but not the whole class. If the whole class is marked as <<shared>>, this is synonymous with marking each attribute as <<shared>>. In addition, if a shared class is marked with tags, these tags apply to each attribute since all of them are shared. The stereotype <<shared>> applied to events is important for state and activity diagrams in order to express shared events, e.g. if a user does something special on the user interface, then for other users having the same view this is done automatically. A shared event can be locked for example in order to disallow a special activity on the user interface until a special constraint is fulfilled. The stereotype <<shared>> applied to messages is important for sequence and collaboration diagrams to express shared messages. If a user sends a shared message to an object, then for other users accessing the same object this message should be sent, too. A shared message can be observable for example in order to express explicitly that other users are notified about sending this message. The stereotype <<shared>> on associations expresses potentially accessible associations for all users so that all users can e.g. navigate via this association to related object(s) in case the association is not hidden due to for example access control mechanisms. Table 2 summarizes the defined UML-G elements and briefly describes their semantics (we do not include icons for the different stereotypes yet). Table 2. Summary of UML-G’s current Shared Data Modeling Part Name <<shared>>
Type Stereotype
Applies to Element
<<sharedRole>>
Stereotype
Class
<<sharedActor>>
Stereotype
Class
{access-controllable}
Boolean Tag
{lockable}
Boolean Tag
{observable}
Boolean Tag
Stereotype <<shared>> Stereotype <<shared>> Stereotype <<shared>>
3.3
Description Instances are potentially accessible from all users. Subtype of <<shared>>; marks roles in cooperative sessions Subtype of <<shared>>; marks actors in cooperative sessions Access control mechanisms can be applied to instances. It is possible to lock instances. Notifications about changes of instances are possible.
Telepointer Example
This subsection gives a brief example on how to use the defined UML extensions. A telepointer appears exactly at the same position on every participant’s screen. Often it is visualized as an arrow. Users can move telepointers to point to some part of a shared document.
Towards UML-G: A UML Profile for Modeling Groupware
99
An example telepointer class is detailed in the class-diagram of Fig. 2. It is associated with the roles Tutor and Learner, instances of which represent roles participating in cooperative sessions. That’s why both classes – Tutor and Learner – are marked with the stereotype <<sharedRole>>. Both associations are named move because the actors filling the roles are allowed to move the telepointer, i.e. to change the Xpos and Ypos attributes. For this reason, the Telepointer class is marked as <<shared>>. The semantics of the stereotype is extended by the Boolean tagged value {lockable} because in this example a tutor needs to have the functionality to lock the access to the Telepointer, i.e. by using it exclusively. Additional OCL constraints assigned to the association(s) can be used to detail the locking. <<shared>> Telepointer {lockable, observable, access-controllable}
1
Xpos: Integer Ypos: Integer 1
getXpos(): Integer getYpos(): Integer setXpos(Integer) setYpos(Integer)
<<shared>> 0..n move
<<share d>> move
0..m
<<sharedRole>> Tutor
<<sharedRole>> Learner
Fig. 2. Telepointer Example
The tag {observable}, applied to the whole class, indicates that notifications on changes regarding all attributes need to be supported. This is because learners and tutors are able to observe the movements of a telepointer visualization. The tag {access-controllable} indicates access control to the telepointer. In this example, tutors need to be able to control the access. Additional OCL constraints assigned to the associations can be used to detail the access control. Both associations are marked as <<shared>> since it is visible who at one point in time accesses the telepointer. Note that a coupling degree, i.e. how many users use the same telepointer, can be specified by cardinalities of the associations. 3.4
Relations to Design Patterns
To simplify Fig. 2, the presented class diagram focuses on data modeling and not on the visualization. Note that also visualization classes or only attributes of them can be marked as <<shared>> of course. UML-G does not enforce any design pattern. A pattern names a design structure as a solution to a problem in a particular context and thus increases our vocabulary [9]. It’s like a template that one can apply in different situations. UML-G can help writing down object-oriented design patterns for groupware in a framework-independent way. Fig. 3 shows for example a groupware pattern, which we call shared state.
100
J. Rubart and P. Dawabi
It defines a many-to-one relationship between an object and its shared state so that a flexible coupling degree (i.e. which objects share the same state) is supported. UMLG helps to mark the SharedState class as shared information without going into any framework-dependent details.
Object
n
1
<<shared>> SharedState
Fig. 3. Shared State Groupware OO Pattern
In addition, UML-G can be extended to include any groupware pattern explicitly, e.g. a Boolean tagged value {sharedState} can be introduced in order to specify that the pattern needs to be applied on a given class without specifying the details of it. Additional patterns for groupware, which can be reflected in an object-oriented pattern, can be found in [11]. Moreover, a CASE tool can be tailored to perform an automatic transformation to the pattern. The pattern in turn can be taken into account by the CASE tool in order to generate code for a special framework or toolkit (see section 5).
4
Usage Scenarios
This section presents two usage scenarios in order to illustrate the applicability of UML-G in two of our projects. It demonstrates the practical relevance of UML-G for modeling groupware. The first example is related to a cooperative laboratory environment and focuses on group members and access to shared artifacts. The second scenario is concerned with cooperative hypermedia and complements the first one by combining UML-G with the persistence Boolean tag from standard UML, a UML constraint as well as object and state diagrams. 4.1
CoopLab
This usage scenario origins from an internal project named CoopLab, which is cur3 rently embedded in the L project [32]. In CoopLab we develop a Java-based virtual learning environment for biotech and other kind of experiments [5, 6]. One project goal of CoopLab is the development of a software framework with the aim to simplify the implementation of cooperative virtual laboratories. The framework is called CoopLab because an important aspect of the framework is to enable cooperative learning in virtual labs. Each virtual scenario consists of several workbenches, whereby each one provides a scenario for a special part of an experiment (see Fig. 4). The framework itself is designed according to a Model-View-Controller approach. A corresponding model, view and a controller class implement each lab device or tool.
Towards UML-G: A UML Profile for Modeling Groupware
101
While the controller and the view classes are responsible for user interaction and visualization, the model class implements the internal behavior and functionality of a virtual device or tool. An icepot in a (real world) biotech lab for example has the function to cool down devices like reaction tubes. The icepot, which is implemented in our virtual lab, can carry up to three tubes in different orders (see Fig. 4) and has an analogous function in the virtual lab. The tools and devices, which are in usage by a tutor or student, are visually marked by [Tutor: GM
] and [Student: GM<m>] to identify the corresponding group members.
Fig. 4. A Shared Virtual Lab
As a small usage scenario we show the classes IcePot and Tube from the internal model of the framework application and combine it with the classes Tutor and Student in a class diagram by using our shared data modeling extension of UML-G (see Fig. 5). The classes Tutor and Student model the different roles a user can adopt in a virtual lab scenario. The class Tutor implements the role of a Tutor in the virtual lab. Analogous to the real world a tutor has the task to supervise and assist the other users during a virtual experiment. Dealing with an icepot in a cooperative lab scenario, we need a tutor who directs one or more students with inserting one or more reaction tubes into the icepot in order to keep them cooled (virtually), when the experiment protocol requires it. The tutor of such a shared experiment uses the icepot in the virtual lab mainly as a demonstration platform and less for the purpose of fulfilling the next step of the experiment. Re-
102
J. Rubart and P. Dawabi
garding cooperation in a virtual lab it is important for the participating students to be able to observe the actions of the tutor. Vice versa the system should provide the functionality that the students can be observed while doing a working step in the virtual lab. <<shared>> IcePot {lockable, observable} maxNumberOfContainers: Integer containerPos1: Container {access-controllable} containerPos2: Container {access-controllable} containerPos3: Container {access-controllable} fillContainerPos1(Container) fillContainerPos2(Container) fillContainerPos3(Container) addContainer(Container) removeContainer(Container) <<shared>> uses 1 {access-controllable} 1
1
>> ed ar s h s e << us
1
*
directs
1
<<sharedRole>> Tutor
<< s co hare nta d> ins >
0.. 3
<<shared>> uses 1{access-controllable} *
<<shared>> Tube {lockable, observable} *
1
<<sharedRole>> Student
1
<<shared>> uses
Fig. 5. The Class IcePot and some of its Associated Classes
A typical cooperative situation is that a tutor demonstrates a task (for example: “Insert tube A into the icepot”) and the students are able to watch and repeat it. In analogy to real world experiments the tutor needs to be able to observe the actions of the students, whenever he likes to do it. But in contrast, the students only have the possibility to watch the tutor, when they have got the permission. In Fig. 5 you see the class diagram of the class IcePot and the corresponding classes Student and Tutor, which are marked with the stereotype <<sharedRole>>. The associations between Tutor and Icepot as well as Student and IcePot are named uses. Furthermore, both associations are stereotyped <<shared>>. This stereotype for associations means that the associations are shared with respect to visibility and changeability. A Tutor needs to recognize at any time, which objects a student is dealing with at the moment. Besides, he needs to be able to restrict the visibility of his own associations – in this case his interactions – with objects of the virtual lab. For this reason the association between Tutor and Icepot is in addition marked as {accesscontrollable}. The association named directs between the classes Tutor and Student
Towards UML-G: A UML Profile for Modeling Groupware
103
shows the connection between the roles. This association is not stereotyped <<shared>> because it is not supposed to be visible between the users. The class Tube, which is aggregated by IcePot is stereotyped <<shared>> in order to indicate that it needs to be visible for all users, how many tubes are aggregated by an instance of IcePot. The associations between the class Tutor and Tube as well as Student and Tube are also stereotyped <<shared>> so that they are shared with respect to visibility and changeability. In addition, the association between Tutor and Tube is access controlled (compare associations to IcePot). Both, the IcePot and the Tube, are marked as {lockable}. This is due to the fact that a tutor can lock the usage of a virtual tube. This is needed when the tutor demonstrates something and does not want to be interrupted by a student who wants to handle the same shared tube in the virtual lab synchronously. Another tagged value {observable} is attached to the classes Icepot and Tube to indicate that all elements of the classes are observable by all other classes. As a precondition the classes themselves are stereotyped as <<shared>>. In Fig. 5 you can see that the tagged value {access-controllable} is also applied to special attributes. It indicates that these attributes are access controlled. In this case, an instance of the class Tutor is able to restrict the usage. This can be further specified by e.g. OCL constraints. 4.2
XCHIPS
This usage scenario is related to the European project EXTERNAL (“EXTended Enterprise Resources, Network Architecture and Learning) [7]. There, we use shared hypermedia workspaces for supporting dynamic networked organizations in developing and performing joint business processes. For this we have developed the cooperative tool XCHIPS (“eXtensible Cooperative Hypermedia with Process Support”) (21, 30). With XCHIPS, users can cooperatively model and execute business processes. Fig. 6 shows three users working in an XCHIPS session. They have modeled a process with the steps Initial planning, Negotiation, and Approval, surrounded by Start and Finish. In addition, they have assigned responsibilities to the different tasks. XCHIPS shows awareness information regarding who has currently opened which tasks. The Initial planning task for example is currently being worked on by rubart and dawabi. The underlying data model of XCHIPS is a shared hypermedia model. Fig. 7 gives a basic overview over this model and makes use of UML-G. A basic hypermedia model is characterized by a node-link paradigm [16]. Nodes are connected by links. Composites allow nested hypermedia structures. In XCHIPS, we have a special composite Task and a special link Flow to model workflow. A process is represented as a set of shared hypermedia tasks connected by
104
J. Rubart and P. Dawabi
Fig. 6. XCHIPS Browser
shared hypermedia flows. Such a hypermedia-based process representation can contain associated materials because the shared hypermedia structure is not limited to tasks and flows. In this way, process support is combined with information management. All instances of these types are shared. That’s why the general hypermedia class (HMObject) is marked as <<shared>>. <<shared>> HMObject {observable, persistence}
Node
Composite
Link
Task
Flow
Fig. 7. Cooperative Hypermedia Model with UML-G
The subclasses inherit the <<shared>> stereotype. In addition, all instances of HMObject stay persistent. This is important because all processes and related information serve as experiences, which need to be accessible from members of later joint projects so that they can learn from and reuse the experiences. They could for example clone a successful business process and adapt it to the requirements of the new project. In standard UML, a persistence Boolean tag is already defined, which also applies to classes so that it can easily be combined with the UML-G extensions in Fig. 7. In
Towards UML-G: A UML Profile for Modeling Groupware
105
addition to the persistence Boolean tag, we have used the observable Boolean tag on order to express that all changes on instances of HMObject need to be propagated. Combination of a UML Constraint and UML-G 4.2.1 Fig. 6 shows awareness information on the task Initial planning, which means that the referring users have currently opened the task. Fig. 8 shows our Task class with its inherited stereotype and tagged values. Instances of it may be associated with a number of rectangles (boxes) visualizing tasks in XCHIPS browsers. <<shared>> Task {observable, persistence} isOpenedBy: Vector getIsOpenedBy(): String
TaskRectangle
assign to {box.getBottomText() = task.getIsOpenedBy()}
1 task
* box
bottomText: String getBottomText(): String setBottomText(text: String)
Fig. 8. The Tagged Value {observable} Detailed by a Constraint
Each task has an attribute isOpenedBy indicating who has currently opened the task. The {observable} tag models explicitly that changes need to be notified. This includes the information on who has opened the task. To detail this, Fig. 8 uses a constraint, expressing that the bottom text of a task rectangle needs to equal the names of the users who have currently opened the task. Object and State Diagrams Using UML-G 4.2.2 An object or interaction diagram is a collaboration diagram or a sequence diagram. Both focus on messages between objects in special contexts. A sequence diagram points out the temporal order of messages (a message asks an object to execute an operation. Operations are implemented by methods). A collaboration diagram explicitly shows the object relationships. Fig. 9 shows a sequence diagram using UML-G. It presents that a user can create a task. After a task exists, a user may open it. This open message to a task is modeled with <<shared>> in order to express that all users participating in the XCHIPS session share opening a task. This means that, if one user opens the task, it gets opened for the others, too. The {observable} tag makes explicit that the other users are notified about this message. The close message is modeled similarly. Analogously, UML-G can be used on messages in collaboration diagrams. A state diagram shows a sequence of states, which an object can take in its life. In addition, it presents state changes, events that trigger state changes and activities. An activity diagram is a special state diagram that focuses on activities. In these diagrams UML-G can be used on events. A task for example can be in an opened or
106
J. Rubart and P. Dawabi
a user create a task open <<shared>> {observable}
close <<shared>> {observable}
Fig. 9. Sequence Diagram Modeled with UML-G
closed state. Instead of an open message like in the sequence diagram in Fig. 9 an open event could be modeled that is shared by all users accessing the task.
5
CASE Tool Support
UML-G allows high level, implementation-independent modeling of groupwarespecific elements and empowers CASE tools to partially automate the development activities. For this, existing CASE tools, supporting the UML extension mechanisms, can be configured to support modeling with UML-G. If they provide suitable configuration mechanisms or APIs, they can be adapted to generate special code. For groupware development, usually a groupware toolkit or framework is used. After integrating a selected one into an appropriate CASE tool and using the CASE tool’s configuration mechanisms or APIs to adapt the code generation accordingly, code for the used toolkit or framework can be generated from the UML-G models. Commercially available UML CASE tools, such as Rational Rose1, Together2, ojectiF3, Objecteering4 or Visual UML5 (to mention a few), usually provide support for the extension mechanisms of UML. Differences can be found regarding the completeness of this support and with reference to semantic support, whether it is for ex-
1
Rational Software, http://www.rational.com/products/rose/ TogetherSoft, http://www.togethersoft.com/ 3 microTOOL, http://www.microtool.de/ 4 Softeam, http://www.softeam.fr/us/produits.htm 5 Visual Object Modelers, http://www.visualobject.com/ 2
Towards UML-G: A UML Profile for Modeling Groupware
107
ample possible to define a stereotype hierarchy, a reusable set of extensions or whether OCL constraint expressions are verified against the model. For our purposes we have chosen ArgoUML6 since it is an open source UML CASE tool written in Java. This enables us promising future work because we can adapt and extend it in any direction. It also has support for adding to-do comments at certain points in models. Fig. 10 shows the telepointer example from section 3.3 modeled with ArgoUML. On the top left part you can see a hierarchical view of our Examples project. On the upper right part you can see the telepointer class diagram. The bottom right part shows the details of the selected object in the class diagram. Currently, the telepointer class is selected and its tagged values are shown in the details part.
Fig. 10. The Telepointer Example Modeled with ArgoUML
5.1
Code Generation
UML CASE tools usually provide code generation support for different objectoriented programming languages. In addition, some CASE tools allow the adaptation of generating code by providing suitable configuration mechanisms via for example scripts or by providing APIs. This enables special handling of particular UML extensions. For generating code we have selected the Java-based groupware framework DyCE (Dynamic Collaboration Environment) [29] since it is used in our institute. Since DyCE offers an object-oriented interface to modeling shared information, the code 6
Tigris.org community, http://www.argouml.org/
108
J. Rubart and P. Dawabi
generation is quite straightforward. We have adapted and extended the responsible code generation classes of ArgoUML. Fig. 11 shows the generated code for the telepointer class. The telepointer class is generated as a subclass of DyCE’s shared object model. Its shared attributes are generated as DyCE’s shared attributes with get- and set-methods. Note that the way shared attributes are generated and thus the get- and set-methods for them are specific DyCE-code. For the tagged value {lockable} a shared attribute LockedBy is generated that can point to the user who has currently locked the telepointer. Regarding the tagged value {access-controllable} a shared attribute AccessRight is generated pointing to an AccessRight object that encapsulates respective information. And again get- and setmethods are created. With reference to {observable} nothing special is generated for the telepointer class since it is intended to use the observer mechanisms already provided by DyCE’s shared object model. Please note that this is only one way of generating code for one specific underlying framework and programming language. UML-G does not enforce a special implementation.
6
Related Work
Basically, there are two areas of research related to work presented in this paper: Groupware and UML extensions. 6.1
Groupware
Toolkits and frameworks for building groupware, such as in [3, 4, 19, 20, 23, 29], do not provide support for modeling groupware in a manner, which is independent of the toolkit or framework. Typically, some usage examples are provided. However, these examples are implementation related and focus on programming rather than modeling. Sometimes user’s guides include modeling hints, but they are written using the language of the framework or toolkit. Hence, only very low level modeling support is provided there. Modeling support for groupware developers, such as in [24], applies a design pattern from the area of single-user application development [28] to groupware. This design pattern focuses on the separation of application and domain model, whereby the application model is related to user interface elements. UML-G in contrast does not enforce any special design patterns. It provides groupware-specific modeling elements, which can be used in any UML diagram. Moreover, UML-G can help writing down design patterns for groupware in a way that is independent of any framework and toolkit. In addition, it can be extended to include any groupware pattern explicitly (see section 3.4). In [15] a modeling approach is taken for shared information spaces in order to ease their management and support knowledge sharing within the enterprise. A metamodel
Towards UML-G: A UML Profile for Modeling Groupware
109
Fig. 11. Example Code
is proposed that defines the conceptual building blocks of an information space. This modeling approach focuses on organizing information spaces rather than on developing groupware.
110
6.2
J. Rubart and P. Dawabi
UML Extensions
With UML-F [8], working with object-oriented frameworks is supported. It allows the explicit representation of framework variation points. Hence, it is very useful for documenting a concrete framework. By using UML-F, framework developers can make explicit which parts of the system need to be adapted in order to create a valid framework instance. Therefore, application developers (users of a framework) are assisted in framework implementation and instantiation. In contrast to UML-F, UMLG does not model framework variation points. It is not intended to support framework developers in documenting their framework so that it is easier to use for application developers. It directly supports application developers in modeling cooperative applications independent of any framework. Synchronous groupware is related to real-time systems in the sense of fast propagation of other users’ interactions in order to provide workspace awareness [12]. A real-time system must respond to events in real time. The architectural design usually involves organizing the system as a set of interacting, concurrent processes [26]. There are UML extensions supporting real-time systems, part of UML-RT [13, 25]. Such an extension is useful for modeling a toolkit or framework supporting groupware development, such as in [3, 4, 19, 20, 23, 29]. These usually care for concurrency control, network latency and so forth. UML-G in contrast is not intended to support modeling of real-time systems. It is intended to support application developers in modeling their cooperative applications on a semantically high level. Typically, application developers use a toolkit or framework supporting groupware development, but not build one. UML extensions for agent-based systems, which are addressed by Agent UML (AUML), as described in e.g. [1] mainly support different ways of modeling the communication protocols between agents. In contrast, UML-G does not aim at such protocols, but at groupware-specific modeling elements. UMLi [18] is a UML extension for modeling interactive applications (in the sense of human-computer interaction). It explicitly addresses interaction issues in activity and use-case diagrams. In addition, a user interface diagram is introduced for modeling abstract user interface presentations. These presentations can be related to domain objects in UMLi activity diagrams. Since cooperative applications usually are interactive UMLi is nicely combinable with UML-G. Note that you are free to combine different UML extensions in your UML models, if this is meaningful.
7
Conclusions and Future Work
We have proposed a UML profile, called UML-G, for specializing the UML to the domain of groupware development. Standard UML and other related work do not support the explicit modeling of groupware-specific elements from an application developer’s point of view. We have identified core requirements for modeling groupware with reference to shared data modeling. Our proposed extensions address the identified requirements by explicitly representing shared information and roles and
Towards UML-G: A UML Profile for Modeling Groupware
111
actors in cooperative sessions as well as providing further semantics on shared information with the Boolean tagged values {access-controllable}, {lockable} and {observable}. UML-G supports groupware developers in modeling their cooperative applications by making groupware design explicit and therefore, easier to understand. The described usage scenarios, in which we indeed have used UML-G, validate the applicability of UML-G. Our experience shows that UML-G allows to model groupware independently from any concrete architecture of a framework or toolkit. A shared understanding between developers is supported, which abstracts from the latter implementation. UML-G can help writing down object-oriented design patterns for groupware in a way that is independent from any toolkit or framework. In turn, UML-G can be extended to include any groupware pattern explicitly. UML-G allows high level, implementation-independent modeling of groupware-specific elements and enables CASE tools to partially automate the development activities for special groupware toolkits and frameworks. In our future work, we will complement UML-G. As an example, a new part of UML-G addressing the usage of concurrency control can include tagged values, such as {optimistic} and {pessimistic}. For this, we want the community to contribute to it. In order to make this efficient we are in the process of setting up and host community support (http://www.uml-g.org/). Moreover, we will build cooperative tools providing synchronous as well as asynchronous modeling support for UML-G. For this, we will either continue using ArgoUML and create suitable shared data models with DyCE or extend the cooperative modeling tool XCHIPS to support a UML-G template. In addition, we will increase the code generation support.
3
Acknowledgements. This work was partially supported by the L project (funded by the German Ministry of Education and Research under the grant 21B8196B) as well as the EU project EXTERNAL, which is funded by the CEC (IST 1999-10091). Thanks also go to the anonymous reviewers for their detailed comments.
References 1.
2.
Bauer, B., Müller, J.P., and Odell, J.: Agent UML: A Formalism for Specifying Multiagent Interaction. In Agent-Oriented Software Engineering, Ciancarini, P., and Wooldridge, M., eds., Springer-Verlag, Berlin, 2001 (held at ISCE'00, Limerick, Ireland, 2000) 91-103 Bentley, R., Horstmann, T., Sikkel, K., and Trevor J.: Supporting Collaborative Information Sharing with the World Wide Web: The BSCW Shared Workspace System. In: The th World Wide Web Journal: Proceedings of the 4 International WWW Conference, Issue 1, O’Reilly (1995) 63-74
112 3. 4. 5.
6. 7.
8. 9. 10. 11. 12. 13.
14. 15. 16. 17. 18.
19. 20. 21.
22. 23.
24.
J. Rubart and P. Dawabi Burridge, R.: Java Shared Data Toolkit User Guide. User Guide, Sun Microsystems Inc. (1998) Chabert, A., Grossmann, E., Jackson, L., Pietrowicz, S. and Seguin, C.: Java Object-Sharing in Habanero, Communications of the ACM pp. 69-76, Vol. 41, No.6. (1998) Dawabi, P., and Rubart, J.: CoopLab: A Framework for Web-Based Virtual Labs. In: Proceedings of the Workshop Multimedia Computing on the WWW, VL2000, Seattle (2000) Dawabi, P., and Wessner, M.: Combining Instructionist and Constructionist Learning in a Virtual Biotech Lab. In: Proceedings of ED-Media 2001 Tampere, Finnland (2001) EXTERNAL – Extended Enterprise Resources, Network Architectures And Learning, EU Project, IST-1999-10091, New Methods of Work and Electronic Commerce, Dynamic Networked Organisations, http://research.dnv.com/external/ (2000-2002) Fontoura, M., Pree, W., and Rumpe, B.: UML-F: A Modeling Language for ObjectOriented Frameworks. In: Proceedings of ECOOP’00, Cannes, France (2000) Gamma, E., Helm, R., Johnson, R., and Vlissides, J. Design Patterns: Elements of Reusable Object-Oriented Software. Addison-Wesley (1995) Greenberg, S.: Computer-Supported Cooperative Work and Groupware, Academic Press, London (1991) The Groupware Patterns Project, available at: http://swiki.ipsi.fhg.de/gw-patterns/ (2001) Gutwin, C., and Greenberg, S. Workspace Awareness for Groupware. In: Proceedings of CHI’96, Vancouver (1996) 208-209 Herzberg, D.: UML-RT as a Candidate for Modeling Embedded Real-Time Systems in the Telecommunication Domain. In: Proceedings of <>, Fort Collins, CO, USA, Oct. 28-30 (1999) Keith Edwards, W., and Mynatt, E.D.: Timewarp: Techniques for Autonomous Collaboration. In: Proceedings of CHI’97, ACM Press, Atlanta, GA (1997) Natvig, M.K., and Ohren, O.: Modeling Shared Information Spaces (SIS). In Proceedings of Group'99, Phoenix, Arizona, USA, ACM Press, (1999) 199-208 Nielsen, J. Hypertext and Hypermedia. Academic Press, Inc., San Diego (1990) OMG: OMG Unified Modeling Language Specification V1.3, http://www.rational.com/uml/ (1999) Pinheiro da Silva, P., and Paton, N.W.: UMLi: The Unified Modeling Language for Interactive Applications. In Proceedings of UML 2000, York, UK, A. Evans, S. Kent and B. Selic (Eds.). LNCS Vol. 1939 (2000) 117-132 Prakash, A., and Shim, H.S.: DistView: Support for Building Efficient Collaborative Applications using Replicated Objects. In: Proceedings of CSCW’94 (1994) Roseman, M., and Greenberg, S.: Building Real-Time Groupware with GroupKit, a Groupware Toolkit. In: Transactions on Human-Computer Interaction, 3(1) (1996) 66-106 Rubart, J., Haake, J.M., Tietze, D.A. and Wang, W. Organizing Shared Enterprise Workspaces Using Component-Based Cooperative Hypermedia. In Proceedings of Hypertext’01, ACM Press, Århus, Denmark (2001) 73-82 Rumbaugh, J., Jacobson, I., and Booch, G. The Unified Modeling Language Reference Manual. Addison-Wesley (1999) Schuckmann, C., Kirchner, L., Schümmer, J., and Haake, J.M.: Designing object-oriented synchronous groupware with COAST. In: Proceedings of CSCW’96, ACM Press (1996) 30-38 Schuckmann, C., Schümmer, J., and Seitz, P.: Modeling Collaboration using Shared Objects. In: Proceedings of Group’99, ACM Press, Phoenix, Arizona (1999)
Towards UML-G: A UML Profile for Modeling Groupware
113
25. Selic, B., and Rumbaugh, J.: Using UML for Modeling Complex Real-Time Systems. White paper available at http://www.objectime.com/otl/technical/umlrt.html (1998) th 26. Sommerville, I.: Software Engineering, 6 Edition, Addison-Wesley (2001) 27. Summers, R.: Official Microsoft© NetMeeting™ Book. Microsoft Press (1998) 28. Szekely, P., Luo, P., and Neches, R.: Facilitating the Exploration of Interface Design Alternatives: The HUMANOID Model of Interface Design. In: Proceedings of CHI’92 (1992) 507-515 29. Tietze, D.A. A Framework for Developing Component-based Co-operative Applications. GMD Research Series No. 7/2001, ISBN: 3-88457-390-X (2001) 30. Wang, W., Haake, J.M., Rubart, J., and Tietze, D.A.: Hypermedia-Based Support for Cooperative Learning of Process Knowledge. In: Journal of Network and Computer Applications (2001) 31. Warmer, J.B., Kleppe, A.G.: The Object Constraint Language: Precise Modeling with UML, Addison-Wesley, Reading, Mass. (1999) 3 32. Wessner, M., Dawabi, P., and Haake, J.M.: L – An Infrastructure for Collaborative Learnflow. In: Gerry Stahl (Ed.): Proceedings of the CSCL 2002 (2002) 698-699
Designing the Communications Infrastructure of Groupware Systems Sergio F. Ochoa1, Luis A. Guerrero1, David A. Fuller2, and Oriel Herrera3 1 Department
of Computer Science, Universidad de Chile. Blanco Encalada 2120, Santiago, Chile {sochoa, luguerre}@dcc.uchile.cl
2 Computer Science Department, Pontificia Universidad Católica de Chile. V. Mackenna 4860, Santiago, Chile. [email protected] 3 Informatics School, Universidad Católica de Temuco. Manuel Montt 56 Temuco, Chile. [email protected]
Abstract. In the development of groupware systems a well designed communications infrastructure is required, due to the high complexity of the communication scenario. Also, the design and implementation of coordination and collaboration mechanisms depends on the communications infrastructure. Actually there are no well known guidelines to design this infrastructure. Therefore, this paper proposes an architectural pattern that helps carry out the design of this communications infrastructure. The proposed pattern supports all the groupware systems communication scenarios, taking in account their particularities. This pattern has been used in the design of several groupware applications and a groupware framework with very good results.
1 Introduction A collaborative application or groupware system supports the work performed by a group of collaborators who pursue a common goal. For the attainment of this goal, the groupware system must provide support in three essential aspects: coordination, collaboration, and communication, better known as the three groupware Cs [4]. Communication is the base for reaching coordination and collaboration. Unlike distributed systems, collaborative applications share a common goal, which has to be reached by the collaborators through the coordination of their individual contributions and activities. Due to the existence of this common goal, communication becomes a way of supporting the coordination and collaboration mechanism that permits the group work. Therefore, the design of the communications infrastructure is very important, since there are many other design aspects that depend on it [14]. These are, for example, awareness, sessions and user administration, floor control, and notifications. Considering the essential aspects that have been defined by Ellis, et al. [4], the groupware systems should be designed using a layered architecture [2] (see Figure 1). The reason is that each layer uses services from lower layers to do its work. This is J.M. Haake and J.A. Pino (Eds.): CRIWG 2002, LNCS 2440, pp. 114–133, 2002. © Springer-Verlag Berlin Heidelberg 2002
Designing the Communications Infrastructure of Groupware Systems
115
similar to what happens with the data communication protocols or with operating systems. In this scenario, each layer carries out a specific function and communicates with the other layers through well-defined interfaces. In groupware systems the communication layer should be in charge of providing the communication among the applications. The coordination layer should generate a shared vision of the group work. It coordinates the actions that are carried out individually, and generates a consistent vision of the group activities. Finally, the two superior layers correspond to the definition and the use of the elements that permit collaborative work, from the user viewpoint. Stratified architectures have many advantages, which have been widely discussed [2].
Fig. 1. Layers of a typical groupware system
Typically, in groupware systems, each component of the layers two and three should be designed and implemented over the defined communications infrastructure (or communication layer). Therefore, the implementation, extension or modification capacities of these components depend greatly on: (a) the services provided by the communications infrastructure and (b) the quality of they. Therefore, the infrastructure must be well designed, and isolated from the rest of the collaborative work support media. In this way, it is always possible to add new services to the communication interface, incorporate new communication technologies, and maintain and improve the existing infrastructure, without