Journal articles: 'Groupware systems'

1

Gray, Paul. "Expert Systems and Groupware." Journal of Information Systems Management 6, no. 2 (January 1989): 90–92. http://dx.doi.org/10.1080/07399018908960150.

Full text

APA, Harvard, Vancouver, ISO, and other styles

2

Kline, Theresa J. B. "The Groupware Adoption Scale: a measure of employee acceptance." Human Systems Management 20, no. 1 (April 24, 2001): 59–62. http://dx.doi.org/10.3233/hsm-2001-20108.

Full text

Abstract:

The Groupware Adoption Scale was designed to assess the why users of groupware systems are committed to using their systems and why they are not. Six subscales cover the aspects of user acceptance that need to be addressed by any organization wanting to adopt a new groupware system. These six are: Ease of Use, Training, Technical Support, Consultation, Work Needs Met, and System Capabilities. The psychometric properties of the Groupware Adoption Scale were assessed and found to be very good. This scale should be of use to both researchers and practitioners working in the groupware field.

APA, Harvard, Vancouver, ISO, and other styles

3

Ellis, C. A., and S. J. Gibbs. "Concurrency control in groupware systems." ACM SIGMOD Record 18, no. 2 (June 1989): 399–407. http://dx.doi.org/10.1145/66926.66963.

Full text

APA, Harvard, Vancouver, ISO, and other styles

4

Bibbo, Luis Mariano, Claudia Pons, and Roxana Giandini. "Model-Driven Development of Groupware Systems." International Journal of e-Collaboration 18, no. 1 (January 2022): 1–28. http://dx.doi.org/10.4018/ijec.295151.

Full text

Abstract:

Building Collaborative systems with awareness (or groupware) is a very complex task. This article presents the use of the domain specific language CSSL v2.0 - Collaborative Software System Language -built as an extension of UML, using the metamodeling mechanism. CSSL provides simplicity, expressiveness and precision to model the main concepts of collaborative systems, especially collaborative processes, protocols and awareness.The CSSL concrete syntax is defined via a set of editors through which collaborative systems models are created. According to the MDD methodology, models are independent of the implementation platform and are formally prepared to be transformed. The target of the transformation is a web application that provides a set of basic functions that developers can refine to complete the development of the collaborative system. Finally, evaluation, validation and verification of the language is performed, determining that the CSSL tools allow developers to solve central aspects of collaborative systems implementation in a simple and reasonable way.

APA, Harvard, Vancouver, ISO, and other styles

5

Masui, Hisayuki, Atsushi Tanaka, and Kazuyoshi Miyoshi. "Engineering Office Systems with Groupware Function." IEEJ Transactions on Industry Applications 113, no. 12 (1993): 1423–32. http://dx.doi.org/10.1541/ieejias.113.1423.

Full text

APA, Harvard, Vancouver, ISO, and other styles

6

Talhi, Said, Mahieddine Djoudi ., and Mohamed Batouche . "Authoring Groupware For Intelligent Tutoring Systems." Information Technology Journal 5, no. 5 (August 15, 2006): 860–67. http://dx.doi.org/10.3923/itj.2006.860.867.

Full text

APA, Harvard, Vancouver, ISO, and other styles

7

Montane, L. G., E. I. Benitez, M. C. Mezura, and E. Martinez. "Studying Social Interactions in Groupware Systems." IEEE Latin America Transactions 13, no. 10 (October 2015): 3488–97. http://dx.doi.org/10.1109/tla.2015.7387259.

Full text

APA, Harvard, Vancouver, ISO, and other styles

8

SCHÜMMER, TILL, STEPHAN LUKOSCH, and ROBERT SLAGTER. "USING PATTERNS TO EMPOWER END-USERS — THE OREGON SOFTWARE DEVELOPMENT PROCESS FOR GROUPWARE." International Journal of Cooperative Information Systems 15, no. 02 (June 2006): 259–88. http://dx.doi.org/10.1142/s0218843006001360.

Full text

Abstract:

Fostering interaction between end-users and developers is one of the most important issues when developing groupware. Insufficient interaction leads to groupware systems that do not fulfill the group's requirements and thus to low acceptance. Furthermore, as group processes change dynamically the requirements are not static as well. Groupware system development and use, therefore, have to address users' changing needs. Current design methodologies insufficiently focus on this aspect. Therefore, we propose the Oregon Software Development Process (OSDP) that fosters end-user participation throughout the whole groupware life cycle, structures the interaction between end-users and developers, and emphasizes the use of a shared language between users and developers. We illustrate the application of the process with experiences made in an interdisciplinary development project of a collaborative learning platform.

APA, Harvard, Vancouver, ISO, and other styles

9

CEPERO GARCÍA, MARÍA TERESA, LUIS GERARDO MONTANE JIMENEZ, GUADALUPE TOLEDO TOLEDO, EDGARD IVAN BENITEZ GUERRERO, and CARMEN MEZURA GODOY. "HEURISTICS FOR AWARENESS SUPPORT IN GROUPWARE SYSTEMS." DYNA NEW TECHNOLOGIES 8, no. 1 (March 1, 2021): [11 p.]. http://dx.doi.org/10.6036/nt9980.

Full text

Abstract:

ABSTRACT: Groupware Systems (GS) or collaborative systems are software systems that support the development of activities in which a group of users interacts to combine their skills, abilities, and work to achieve a common goal. In this area, an important concept is awareness, which is the information that helps people be aware of events beyond their current tasks. This information makes smoother the use of a collaborative system, so it is a fundamental element in this kind of software. In the design and construction of these types of systems, heuristics are used as design guidelines that serve as a useful evaluation tool for product designers and usability professionals. The current heuristics and guidelines for the design of awareness support focus on supporting the awareness of the team in the shared workspace, without considering elements to support the information needs of the user's own and individual interaction within the workspace. To address this problem and to facilitate the design and integration of awareness support, we developed 13 heuristics that integrate principles of Human-Computer Interaction and Computer Supported Cooperative Work to help groupware designers meet individual and team awareness needs. For evaluating the validity of the proposed heuristics, a structured and iterative consultation process was carried out with experts in Human-Computer Interaction and Computer-Supported Cooperative Work. The proposed heuristics can help software engineers develop collaborative systems that integrate awareness information and satisfy users' contextual information needs. Keywords: Awareness, virtual groups, collaborative work, heuristics.

APA, Harvard, Vancouver, ISO, and other styles

10

Wulf, Volker, Volkmar Pipek, and Andreas Pfeifer. "Resolving function-based conflicts in groupware systems." AI & Society 15, no. 3 (September 2001): 233–62. http://dx.doi.org/10.1007/bf01208707.

Full text

APA, Harvard, Vancouver, ISO, and other styles

11

ter Beek, Maurice H., Clarence A. Ellis, Jetty Kleijn, and Grzegorz Rozenberg. "Synchronizations in Team Automata for Groupware Systems." Computer Supported Cooperative Work (CSCW) 12, no. 1 (February 2003): 21–69. http://dx.doi.org/10.1023/a:1022407907596.

Full text

APA, Harvard, Vancouver, ISO, and other styles

12

Kock, Ned, and Robert Mcqueen. "A Field Study of the Effects of Asynchronous Groupware Support on Process Improvement Groups." Journal of Information Technology 12, no. 4 (December 1997): 245–59. http://dx.doi.org/10.1177/026839629701200402.

Full text

Abstract:

Process improvement (PI) groups have been among the main change instruments of widely adopted and publicized organizational development approaches such as total quality management and business process re-engineering. Asynchronous groupware tools, such as electronic messaging systems, have found widespread use in organizations yet very little field research exists on how PI groups are affected by such tools. We try to fill this gap with a field study of the effects of asynchronous groupware support on seven PI groups in two New Zealand organizations. Our study indicates that, while not having perceived negative effects on group effectiveness, asynchronous groupware support was perceived as increasing process adoption, hierarchy suppression, departmental heterogeneity and contribution length and decreasing discussion duration, cost and interaction in PI groups. We argue that, based on these findings, the use of asynchronous groupware tools is likely to be beneficial in PI projects, particularly where a large number of PI groups proposing incremental process changes is conducted.

APA, Harvard, Vancouver, ISO, and other styles

13

STAHL, GERRY. "ANALYZING AND DESIGNING THE GROUP COGNITION EXPERIENCE." International Journal of Cooperative Information Systems 15, no. 02 (June 2006): 157–78. http://dx.doi.org/10.1142/s0218843006001323.

Full text

Abstract:

More than we realize it, knowledge is often constructed through interactions among people in small groups. The Internet, by allowing people to communicate globally in limitless combinations, has opened enormous opportunities for the creation of knowledge and understanding. A major barrier today is the poverty of adequate groupware. To design more powerful software that can facilitate the building of collaborative knowledge, we need to better understand the nature of group cognition — the processes whereby ideas are developed by small groups. We need to analyze interaction at both the individual and the group unit of analysis in order to understand the variety of processes that groupware should be supporting. This paper will look closely at an empirical example of an online group problem-solving experience and suggest implications for groupware design.

APA, Harvard, Vancouver, ISO, and other styles

14

FASOLI, N., and A. MESSINA. "EMCORE – EMOTIONAL COOPERATIVE GROUPWARE: A GROUPWARE TOOL FOR COLLABORATIVE WORK." International Journal of Modern Physics C 12, no. 04 (May 2001): 589–600. http://dx.doi.org/10.1142/s0129183101002607.

Full text

Abstract:

In the last years considerable effort has been spent to develop groupware applications. Despite this, no general consenus has been met by groupware applications in computer field. Interdisciplinary approach could prove very useful to overcome these difficulties. A workgroup is not simply a set of people gathered together, working for a common goal. It can also be thought as a strong, hard mental reality. Actually, sociological and psychological definitions of group differ considerably. At sociological level a group is generally described in the view of the activities and events occurring inside the group itself. On the other hand, the psychological group approach considers not only the actions occurring inside the group, but also all the mental activities originated by belonging to the group, be they emotional or rational nature. Since early '60 simple work group (i.e. discussion group) has been analyzed in his psychological behavior. EMCORE is a prototype which aims to support computer science methods with psychological approach. The tool has been developed for a discussion group supported by heterogeneous distributed systems and has been implemented according to the CORBA abstraction augmented by the machine independent JAVA language. The tool allows all the common activities of a discussion group: discussion by voice or by chatting board if multimedia device are not present; discussion and elaboration of a shared document by text and/or graphic editor. At the same time, tools are provided for the psychoanalytic approach, according to a specific methodology.

APA, Harvard, Vancouver, ISO, and other styles

15

Greenes, Robert A. "Technology Transfer in Medical Information Systems: The Potential for “groupware” and its Implications." International Journal of Technology Assessment in Health Care 9, no. 3 (1993): 324–34. http://dx.doi.org/10.1017/s0266462300004591.

Full text

Abstract:

AbstractThe practice of medicine is intrinsically a cooperative activity, involving not only a number of individuals but requiring access to a wide variety of types of data, produced and maintained by different people. Achieving seamless, integrated access to these data requires a new infrastructure of information systems that supports the construction of applications designed to incorporate and use external information resources. The term groupware may be used to connote this collective set of information resources and tools for access to them. Groupware will generate a variety of new kinds of products and services with implications for medical libraries, electronic publishing, and academic and professional collaboration.

APA, Harvard, Vancouver, ISO, and other styles

16

Pinheiro, Manuele Kirsch, and Carine Souveyet. "Is Group-Awareness Context-Awareness?" International Journal of e-Collaboration 15, no. 3 (July 2019): 1–19. http://dx.doi.org/10.4018/ijec.2019070101.

Full text

Abstract:

This article discusses the interest of emerging a unified view for group awareness and context information on groupware and context-aware systems. Group awareness corresponds to an important concept on Groupware applications, allowing individual users to be kept aware of group's activities and status. Context is defined by ubiquitous computing as any relevant information that can be used to characterize the situation of an entity. We assume that group awareness information should be considered as context information and handled as such. Group awareness information is often employed for decision making, contributing to users' activities and decisions, but it gives also an important clue about user's context, characterizing individual's actions regarding the group. As such, group awareness may be used for adaptation purposes, adapting the system behavior, the supplied content or its services. Besides, architectural concerns adopted on context-aware system should also be considered when developing new groupware applications that are more and more designed as context-aware systems.

APA, Harvard, Vancouver, ISO, and other styles

17

King, William R. "Strategic Issues In Groupware." Information Systems Management 13, no. 2 (January 1996): 73–75. http://dx.doi.org/10.1080/10580539608906990.

Full text

APA, Harvard, Vancouver, ISO, and other styles

18

Poulovassilis, Alex, Fatos Xhafa, and Thomas O’Hagan. "Event-Based Awareness Services for P2P Groupware Systems." Informatica 26, no. 1 (January 1, 2015): 135–57. http://dx.doi.org/10.15388/informatica.2015.42.

Full text

APA, Harvard, Vancouver, ISO, and other styles

19

Kirsch-Pinheiro, Manuele, José Valdeni de Lima, and Marcos R. S. Borges. "A framework for awareness support in groupware systems." Computers in Industry 52, no. 1 (September 2003): 47–57. http://dx.doi.org/10.1016/s0166-3615(03)00068-x.

Full text

APA, Harvard, Vancouver, ISO, and other styles

20

Wheeler, Bradley C., Alan R. Dennis, and Laurence I. Press. "Groupware comes to the Internet." ACM SIGMIS Database: the DATABASE for Advances in Information Systems 30, no. 3-4 (September 1999): 8–21. http://dx.doi.org/10.1145/344241.344242.

Full text

APA, Harvard, Vancouver, ISO, and other styles

21

Wood, Charles Cresson. "Principles of secure information systems design with groupware examples." Computers & Security 12, no. 7 (November 1993): 663–78. http://dx.doi.org/10.1016/0167-4048(93)90084-i.

Full text

APA, Harvard, Vancouver, ISO, and other styles

22

FUKS, HUGO, ALBERTO B. RAPOSO, MARCO A. GEROSA, and CARLOS J. P. LUCENA. "APPLYING THE 3C MODEL TO GROUPWARE DEVELOPMENT." International Journal of Cooperative Information Systems 14, no. 02n03 (June 2005): 299–328. http://dx.doi.org/10.1142/s0218843005001171.

Full text

Abstract:

This paper introduces an approach based on the 3C (communication, coordination and cooperation) collaboration model to the development of collaborative systems. The 3C model is studied by means of a detailed analysis of each of its three elements, followed by a case study of a learningware application and the methodology of a web-based course, both designed based on this model. Moreover, this paper describes a component-based system architecture following this 3C approach.

APA, Harvard, Vancouver, ISO, and other styles

23

Cremers, Armin B., Helge Kahler, Andreas Pfeifer, Oliver Stiemerling, and Volker Wulf. "PoliTeam - Kokonstruktive und evolutionäre Entwicklung einer Groupware." Informatik-Spektrum 21, no. 4 (August 13, 1998): 194–202. http://dx.doi.org/10.1007/s002870050099.

Full text

APA, Harvard, Vancouver, ISO, and other styles

24

Kock, Nereu F., and Robert J. McQueen. "Using Groupware in Quality Management Programs." Information Systems Management 14, no. 2 (January 1997): 56–62. http://dx.doi.org/10.1080/10580539708907046.

Full text

APA, Harvard, Vancouver, ISO, and other styles

25

CEPERO GARCÍA, MARÍA TERESA, LUIS GERARDO MONTANE JIMENEZ, GUADALUPE TOLEDO TOLEDO, EDGARD IVAN BENITEZ GUERRERO, and CARMEN MEZURA GODOY. "HEURISTICS FOR COLLABORATIVE SOFTWARE DESIGN." DYNA 96, no. 4 (July 1, 2021): 346. http://dx.doi.org/10.6036/10172.

Full text

Abstract:

Collaborative software (groupware) provides the means for a group of people to develop team activities. These systems provide information that helps people understand events beyond their current tasks, e.g., understanding who is participating, where they are, what they are saying, and what they are doing.

APA, Harvard, Vancouver, ISO, and other styles

26

Nyerges, Timothy, T. J. Moore, Robb Montejano, and Marcie Compton. "Developing and Using Interaction Coding Systems for Studying Groupware Use." Human–Computer Interaction 13, no. 2 (June 1998): 127–65. http://dx.doi.org/10.1207/s15327051hci1302_2.

Full text

APA, Harvard, Vancouver, ISO, and other styles

27

Hendriks, Paul. "Envisioning knowledge-based systems impacts: a groupware facilitated simulation approach." Expert Systems with Applications 15, no. 2 (August 1998): 143–54. http://dx.doi.org/10.1016/s0957-4174(98)00019-0.

Full text

APA, Harvard, Vancouver, ISO, and other styles

28

Prakash, Atul, and Michael J. Knister. "Design considerations in choosing operations for building groupware systems (abstract)." ACM SIGOIS Bulletin 13, no. 4 (April 1993): 9. http://dx.doi.org/10.1145/152716.152721.

Full text

APA, Harvard, Vancouver, ISO, and other styles

29

Luna, Huizilopoztli, Ricardo Mendoza, Miguel Vargas, Jaime Munoz, Francisco J. Alvarez, and Laura C. Rodriguez. "Using Design Patterns as Usability Heuristics for Mobile Groupware Systems." IEEE Latin America Transactions 13, no. 12 (December 2015): 4004–10. http://dx.doi.org/10.1109/tla.2015.7404939.

Full text

APA, Harvard, Vancouver, ISO, and other styles

30

Penichet, Victor M. R., Maria D. Lozano, José A. Gallud, and Ricardo Tesoriero. "Requirement-based approach for groupware environments design." Journal of Systems and Software 83, no. 8 (August 2010): 1478–88. http://dx.doi.org/10.1016/j.jss.2010.03.029.

Full text

APA, Harvard, Vancouver, ISO, and other styles

31

GOTTHELF, PABLO, ALEJANDRO ZUNINO, and MARCELO CAMPO. "A PEER-TO-PEER COMMUNICATION INFRASTRUCTURE FOR GROUPWARE APPLICATIONS." International Journal of Cooperative Information Systems 17, no. 04 (December 2008): 523–54. http://dx.doi.org/10.1142/s0218843008001920.

Full text

Abstract:

Many advances have been done to allow groups of people to work together and collaborate in the Internet. Collaborative systems are characterized by the way participants interact. In many cases, equal standing members should cooperate in a non-authoritative environment, where no entity or authority is or should be in charge of regulating the group. Therefore, decentralized communication infrastructures have been hailed as promising alternatives. Recently, decentralized infrastructures based on P2P approaches have drawn the attention of the research community because of their benefits in terms of scalability, robustness, availability and potentials for leveraging computational resources distributed across the Internet. In this paper, a scalable peer-to-peer (P2P) communication Infrastructure for groupware applications is presented. It enables a large number of people to join and cooperate in a robust, decentralized and easy deployable way, without requiring high capacity servers or any other special network infrastructure. The communication infrastructure is based on a binary tree as overlay structure, which implements all groupware communication functionality, including membership management and packet forwarding, at application level, making it an inexpensive and fast deployable solution for equal standing members, such as home users with a domestic connection to the Internet. Two applications, one for synchronous groupware and the other for asynchronous collaboration, have been developed to validate the approach. Comparisons with other communication infrastructures in aspects such as end-to-end propagation delay, group latency, throughput, protocol overhead, failure recovery and link stress, show that our approach is a scalable and robust alternative.

APA, Harvard, Vancouver, ISO, and other styles

32

Downing, Charles E., and Andrew S. Clark. "Groupware in Practice: Expected and Realized Benefits." Information Systems Management 16, no. 2 (March 1999): 25–31. http://dx.doi.org/10.1201/1078/43188.16.2.19990301/31173.5.

Full text

APA, Harvard, Vancouver, ISO, and other styles

33

Bordetsky, Alex, and Gloria Mark. "Memory-Based Feedback Controls to Support Groupware Coordination." Information Systems Research 11, no. 4 (December 2000): 366–85. http://dx.doi.org/10.1287/isre.11.4.366.11871.

Full text

APA, Harvard, Vancouver, ISO, and other styles

34

Xhafa, Fatos, Alina-Diana Potlog, Evjola Spaho, Florin Pop, Valentin Cristea, and Leonard Barolli. "Evaluation of intra-group optimistic data replication in P2P groupware systems." Concurrency and Computation: Practice and Experience 27, no. 4 (April 2, 2012): 870–81. http://dx.doi.org/10.1002/cpe.2836.

Full text

APA, Harvard, Vancouver, ISO, and other styles

35

Wallace, James R., Stacey D. Scott, Taryn Stutz, Tricia Enns, and Kori Inkpen. "Investigating teamwork and taskwork in single- and multi-display groupware systems." Personal and Ubiquitous Computing 13, no. 8 (June 25, 2009): 569–81. http://dx.doi.org/10.1007/s00779-009-0241-8.

Full text

APA, Harvard, Vancouver, ISO, and other styles

36

Duque, Rafael, Manuel Noguera, Crescencio Bravo, José Luis Garrido, and María Luisa Rodríguez. "Construction of interaction observation systems for collaboration analysis in groupware applications." Advances in Engineering Software 40, no. 12 (December 2009): 1242–50. http://dx.doi.org/10.1016/j.advengsoft.2009.01.028.

Full text

APA, Harvard, Vancouver, ISO, and other styles

37

Decouchant, Dominique, Sonia Mendoza, Gabriela Sánchez, and José Rodríguez. "Adapting groupware systems to changes in the collaborator’s context of use." Expert Systems with Applications 40, no. 11 (September 2013): 4446–62. http://dx.doi.org/10.1016/j.eswa.2013.01.043.

Full text

APA, Harvard, Vancouver, ISO, and other styles

38

Defranco-tommarello, Joanna, and Fadi P. Deek. "Collaborative Problem Solving and Groupware for Software Development." Information Systems Management 21, no. 1 (December 2004): 67–80. http://dx.doi.org/10.1201/1078/43877.21.1.20041201/78987.7.

Full text

APA, Harvard, Vancouver, ISO, and other styles

39

Marks, Eric A. "Manufacturing Execution Systems: Enablers for Operational Excellence and the Groupware for Manufacturing." Information Strategy: The Executive's Journal 13, no. 3 (March 1997): 23–29. http://dx.doi.org/10.1080/07438613.1997.10744565.

Full text

APA, Harvard, Vancouver, ISO, and other styles

40

Mostaeen, Golam, Banani Roy, Chanchal Roy, and Kevin Schneider. "Designing for Real-Time Groupware Systems to Support Complex Scientific Data Analysis." Proceedings of the ACM on Human-Computer Interaction 3, EICS (June 13, 2019): 1–28. http://dx.doi.org/10.1145/3331151.

Full text

APA, Harvard, Vancouver, ISO, and other styles

41

Brans, J. P., and M. Despontin. "Decision Support Systems, Groupware, Multimedia and Electronic Commerce: Seventh Mini Euro Conference." European Journal of Operational Research 109, no. 2 (September 1998): 243–47. http://dx.doi.org/10.1016/s0377-2217(98)00053-8.

Full text

APA, Harvard, Vancouver, ISO, and other styles

42

Lee, Heejin. "Your time and my time: a temporal approach to groupware calendar systems." Information & Management 40, no. 3 (January 2003): 159–64. http://dx.doi.org/10.1016/s0378-7206(01)00140-9.

Full text

APA, Harvard, Vancouver, ISO, and other styles

43

Duque, Rafael, Crescencio Bravo, and Manuel Ortega. "An ontological approach to automating collaboration and interaction analysis in groupware systems." Knowledge-Based Systems 37 (January 2013): 211–29. http://dx.doi.org/10.1016/j.knosys.2012.08.005.

Full text

APA, Harvard, Vancouver, ISO, and other styles

44

BERZTISS, ALFS T. "REVERSE ENGINEERING, REENGINEERING, AND CONCURRENT ENGINEERING OF SOFTWARE." International Journal of Software Engineering and Knowledge Engineering 05, no. 02 (June 1995): 299–324. http://dx.doi.org/10.1142/s0218194095000150.

Full text

Abstract:

This survey reviews four classes of reengineering of software systems: code restructuring and translation of code into a new language, design recovery for corrective maintenance, design recovery for software enhancement, and software reengineering as part of radical business process reengineering. Special attention is given to the reengineering of data bases and user interfaces. We also consider concurrent software engineering, its place in the software reengineering process, and groupware in support of this process.

APA, Harvard, Vancouver, ISO, and other styles

45

PREGUIÇA, NUNO, J. LEGATHEAUX MARTINS, HENRIQUE JOÃO DOMINGOS, and SÉRGIO DUARTE. "SUPPORTING MULTI-SYNCHRONOUS GROUPWARE: DATA MANAGEMENT PROBLEMS AND A SOLUTION." International Journal of Cooperative Information Systems 15, no. 02 (June 2006): 229–58. http://dx.doi.org/10.1142/s0218843006001359.

Full text

Abstract:

It is common that, in a long-term asynchronous collaborative activity, groups of users engage in occasional synchronous sessions. In this paper, we analyze the data management requirements for supporting this common work practice in typical collaborative activities and applications. We call the applications that support such work practice multi-synchronous applications. This analysis shows that, as users interact in different ways in each setting, some applications have different requirements and need to rely on different data sharing techniques in synchronous and asynchronous settings. We present a data management system that allows to integrate a synchronous session in the context of a long-term asynchronous interaction, using the suitable data sharing techniques in each setting and an automatic mechanism to convert the long sequence of small updates produced in a synchronous session into a large asynchronous contribution. We exemplify the use of our approach with two multi-synchronous applications.

APA, Harvard, Vancouver, ISO, and other styles

46

Ackermann, Fran, Joseph St John Bate, and Nathan Travell. "Groupware: Business Success with Computer Supported Cooperative Working." Journal of the Operational Research Society 47, no. 4 (April 1996): 591. http://dx.doi.org/10.2307/3010734.

Full text

APA, Harvard, Vancouver, ISO, and other styles

47

Ackermann, Fran. "Groupware: Business Success with Computer Supported Cooperative Working." Journal of the Operational Research Society 47, no. 4 (April 1996): 591–92. http://dx.doi.org/10.1057/jors.1996.64.

Full text

APA, Harvard, Vancouver, ISO, and other styles

48

Gao, Liping, Tun Lu, and Ning Gu. "CLAF: Solving intention violation of step-wise operations in CAD groupware." Advanced Engineering Informatics 24, no. 2 (April 2010): 121–37. http://dx.doi.org/10.1016/j.aei.2009.07.003.

Full text

APA, Harvard, Vancouver, ISO, and other styles

49

Havlíček, Z., and J. Vaněk. "ICT and cooperative work." Agricultural Economics (Zemědělská ekonomika) 51, No. 10 (February 21, 2012): 469–74. http://dx.doi.org/10.17221/5139-agricecon.

Full text

Abstract:

This article deals with the possibilities of making usage of ICT (Information and communication technology) to support cooperation among teams. There are two main approaches: systems based on the www technologies (intranets), and specialised systems, which are dedicated to cooperation (these systems are designated as groupware). Web technologies are the main element of the Internet. They are becoming the most important technology in the presentation layer of current business information systems. The web environment penetrates into all currently used applications. Its integration with all existing systems makes the users locally independent and enables them to use a variety of hardware and software platforms, as well as the advantages of mobile communications. The results of the issues discussed in the article are outlined in specific examples.

APA, Harvard, Vancouver, ISO, and other styles

50

Salo, Ahti, and Timo K. Kakola. "Groupware Support for Requirements Management in New Product Development." Journal of Organizational Computing and Electronic Commerce 15, no. 4 (January 2005): 253–84. http://dx.doi.org/10.1207/s15327744joce1504_1.

Full text

APA, Harvard, Vancouver, ISO, and other styles

Journal articles on the topic 'Groupware systems'

Create a spot-on reference in APA, MLA, Chicago, Harvard, and other styles