A group decision support system for idea generation and issue analysis in organization planning

Applegate, Lynda M.; Konsynski, Benn R.; Nunamaker, Jay F.

doi:10.1145/637069.637073

Cited by 61 publications

(17 citation statements)

References 27 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…The goal is to improve the productivity of decision-making meetings, either by speeding up the decision-making process or by improving the quality of the resulting decisions [51]. There are GDSS aids for decision structuring, such as alternative ranking and voting tools, and for idea generation [2] or issue analysis [ 11 ].…”

Section: Group Decision Support Systeln8 and Electl~ml¢ Meeting Rooms;mentioning

confidence: 99%

See 1 more Smart Citation

Groupware: some issues and experiences

Ellis¹,

Gibbs²,

Rein³

1991

Commun. ACM

1,983

716

View full text Add to dashboard Cite

Section: Group Decision Support Systeln8 and Electl~ml¢ Meeting Rooms;mentioning

confidence: 99%

“…A well-known example is the PlexCenter Planning and Decision Support Laboratory at the University of Arizona [2]. The facility provides a large U-shaped c)nference The computer serves as a communications medium in a variety of ways.…”

Section: Group Decision Support Systeln8 and Electl~ml¢ Meeting Rooms;mentioning

confidence: 99%

Groupware: some issues and experiences

Ellis¹,

Gibbs²,

Rein³

1991

Commun. ACM

1,983

716

View full text Add to dashboard Cite

“…An early concept of collaboration by Applegate et al (1986), explored the effect of the technology on idea generation and collaborative processes to facilitate problem solving for groups, using computer-mediated communication. Design and implementation strategies for group decision support systems were used in actual planning sessions at the MIS Planning and Decision Laboratory (Applegate, Konsynski, and Nunamaker, 1986).…”

Section: Collaborationmentioning

confidence: 99%

“…Design and implementation strategies for group decision support systems were used in actual planning sessions at the MIS Planning and Decision Laboratory (Applegate, Konsynski, and Nunamaker, 1986). In this context, the use of the computer significantly stimulated task-oriented behavior.…”

Section: Collaborationmentioning

confidence: 99%

Campus Information Model: A Participatory Design Tool to Support Qualitative Decision Making

Zamora

Grimes²,

Swarts³

2014

Proceedings of the XVIII Conference of the Iberoamerican Society of Digital Graphics - SIGraDi: Design in Freedom

View full text Add to dashboard Cite

This paper presents our Campus Information Model from a participatory perspective. The primary goal of our Campus Information Model (CIM) is to gather several disciplinary goals into a single model as the platform for collaboration. This intermediate-scale model integrates information and expert knowledge about a university campus design, including landscape planning and building design, allowing users to obtain quantitative feedback in real time to support design facilitating their specific goals. This paper describes first, the concept of collaboration; second, the collaborative system CIM; and third, the strategies to bring quantitative and qualitative goals to the same design environment.

show abstract

“…Since large software system development is a procedure under high economic pressure, the quality of communication among developers determines the progress in development as well as the quality of the final product [3][4][5][6]. It has turned out that, for conceptual design, where several views as well as individual design proposals have to be integrated, there is a lack of adequate support for successful, i.e., collaborative communication.…”

Section: Introductionmentioning

confidence: 99%

Modeling collaboration for large-scale software system integration by formal communication models

Stary

1992

Journal of Systems Integration

View full text Add to dashboard Cite

Abstract. In the development of large software systems, several synchronization points have to be passed successfully in order to achieve high-end user acceptance of the final system. In particular, the integration of conceptual design entities has turned out to be the most crucial step in software development. At this point, an explicit representation of the organizational knowledge, namely how the integration can be performed, is required. The overall organization of the integration of design entities is a set of knowledge, action (including communication), and time. The knowledge part comprises the integration procedure itself as well as the design entities. Actions are performed by the members of the project team (project leaders, developers). Each integration step has to be performed synchronized, so that each member of the development team knows concurrently the status of the integration procedure. All other individual design activities are usually performed asynchronously. According to the need for an explicit representation of the organizational knowledge for large software system design, this paper attempts to understand the nature of large software system integration and formally describes the coordination of a dispersed set of software developers. The organizational knowledge is represented by processes that occur in an asynchronous development environment. The design knowledge is assigned to logical formulas that are processed as exchanged messages among developers. Hence, the activities for integraiton are based on the transmission of messages. Time-critical events, such as the integration of a particular design entity into the final conceptual design of the software system, have to become common knowledge concurrently for all developers. This organizational constraint has been formalized in the communication model. Not only can the proposed flamework be adapted to organizational changes in a flexible way, it can also be applied to any specific development strategy for the integration of conceptual design entities. Thus, such kind of formal communication models may provide a sound basis for cooperative CASE (computer-aided software engineering) tools.

show abstract

A group decision support system for idea generation and issue analysis in organization planning

Cited by 61 publications

References 27 publications

Groupware: some issues and experiences

Groupware: some issues and experiences

Campus Information Model: A Participatory Design Tool to Support Qualitative Decision Making

Modeling collaboration for large-scale software system integration by formal communication models

Contact Info

Product

Resources

About