Integrating groupware applications into shared workspaces

Abstract

A key aspect in groupware applications is to provide support for quality collaboration in workgroups. Consequently, some non-functional requirements that are traditionally associated with single-user applications are also becoming demanded for this kind of software. Due to the use of a wide range of ad-hoc methods and development techniques, as well as differences in underlying communication technologies and conceptualization of the applications themselves, there are some important pitfalls in terms of applying methods and techniques to systematically handle non-functional requirements in groupware applications. In this paper, we present an analysis of non functional requirements and specific functional requirements for groupware applications, and propose a framework that serves as a basis for the satisfaction of relevant non-functional requirements in groupware applications: interoperability, integration, usability, extensibility and reusability. The framework consists of a set of mechanisms to support group awareness about the manipulation of multi-user interfaces, a communication and coordination middleware, and a shared workspace encompassing first class concepts present in the system (users, roles, applications, documents, etc.), and their relationships. A case study shows how several groupware applications may be integrated and may interoperate under this approach.

An Integrative Approach to Diagram-based Collaborative Brainstorming: A Case Study

“…To achieve such a collaborative environment we have been concerned with awareness that as claimed by [12] is defined as an understanding of others activities, which provides a context for your own activity. According to [13] group awareness information includes knowledge about who is on the collaborative environment, where they are working, what are they doing and their furthermore intentions [3]. Furthermore, the techniques and diagram types that could be used to support collaborative diagramming efforts were taken into consideration, and how the features and functions of a single-user differ from a multi-user diagramming tool in order to optimize the values that groups can create through collaborative diagramming.…”

“…In the above scenario, we have to support collaboration engineers in designing collaborative processes (R1), such as strategy building, root cause analysis, and design suitable collaboration support (R2). For that the GSS needs to support the integration of components that support collaborative processes (R3), by allowing re-using of existing components [3] Furthermore, it must be able to share and exchange data efficiently (interoperability) between components (R4) [3], [16], [17], in order to reuse the data gathered for example from the first activity (text-based brainstorming) into the second activity (diagram-based brainstorming). Additionally, we do not know all the support that is needed so that the set of components must be extensible (R5) [3]) by software developers and an API (R6) to support them [18] should be provided.…”

“…Action Center does not address all requirements needed for Collaborative Diagramming. For that purpose, we implemented our (R7) CLSD Component that consists of an XML wrapper and an implementation in JavaScript with Ext JS 2 and an extended library called Joint JS 3 . The JointJS library is used for to create diagrams that can be fully interactive for both implementing a diagramming tool (as our CLSD Component) as well as simply for publishing diagrams (R7.1, R7.2 and R7.3) [11].…”

“…According to [3] there are GSS systems addressing some of the requirements described above, however for our approach we have chosen ActionCenters because it addresses all of the requirements and it fits with our purpose. Two parts form Action Centers: a CACE editor and a Process Support System (PSS).…”

“…Groups can become even more productive when supported by Group Support Systems (GSS). It is decisive that GSS adopt techniques for the development of groupware applications that meet non-functional requirements (quality attributes) such as interoperability, integration, reliability and usability [3]. Collaborative graphical systems support a group of people concurrently editing graphical processes over the network.…”