Pub Date : 1995-04-20DOI: 10.1109/ENABL.1995.484559
Karim Hussein, F. Peña-Mora, Ram D. Sriram
Conference management is a critical component of a collaborative engineering effort. This paper describes, CAIRO (Collaborative Agent Interaction and synchROnization system), a system for managing participants in a distributed conference. We have drawn from various models of group interaction and social communications theory in order to develop CAIRO. While most conference systems have focused on the technical issues of communicating information between computers, we have also emphasized the role of the computer as a mediator and conference control mechanism. CAIRO provides both media synchronization, i.e. insuring that all information conveyed from one participant to another is synchronized, and agent synchronization, i.e. ensuring effective structuring and control of a distributed conference.
会议管理是协作工程工作的关键组成部分。本文介绍了一个分布式会议参与者管理系统CAIRO (Collaborative Agent Interaction and synchROnization system)。为了开发CAIRO，我们借鉴了群体互动和社会传播理论的各种模型。虽然大多数会议系统都集中在计算机之间通信信息的技术问题上，但我们也强调了计算机作为调解人和会议控制机制的作用。CAIRO既提供媒体同步，即确保从一个参与者传递给另一个参与者的所有信息都是同步的，也提供代理同步，即确保有效地组织和控制分布式会议。
{"title":"CAIRO: a system for facilitating communication in a distributed collaborative engineering environment","authors":"Karim Hussein, F. Peña-Mora, Ram D. Sriram","doi":"10.1109/ENABL.1995.484559","DOIUrl":"https://doi.org/10.1109/ENABL.1995.484559","url":null,"abstract":"Conference management is a critical component of a collaborative engineering effort. This paper describes, CAIRO (Collaborative Agent Interaction and synchROnization system), a system for managing participants in a distributed conference. We have drawn from various models of group interaction and social communications theory in order to develop CAIRO. While most conference systems have focused on the technical issues of communicating information between computers, we have also emphasized the role of the computer as a mediator and conference control mechanism. CAIRO provides both media synchronization, i.e. insuring that all information conveyed from one participant to another is synchronized, and agent synchronization, i.e. ensuring effective structuring and control of a distributed conference.","PeriodicalId":275450,"journal":{"name":"Proceedings 4th IEEE Workshop on Enabling Technologies: Infrastructure for Collaborative Enterprises (WET ICE '95)","volume":"40 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1995-04-20","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"122129702","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Pub Date : 1995-04-20DOI: 10.1109/ENABL.1995.484541
Carleton A. Moore
The authors discuss: 1. Three scenarios that represent different situations for collaboration, 2. A framework that can be used to describe collaborative tools and, 3. Some concerns, issues, and holes we found.
{"title":"WET ICE tools working group report","authors":"Carleton A. Moore","doi":"10.1109/ENABL.1995.484541","DOIUrl":"https://doi.org/10.1109/ENABL.1995.484541","url":null,"abstract":"The authors discuss: 1. Three scenarios that represent different situations for collaboration, 2. A framework that can be used to describe collaborative tools and, 3. Some concerns, issues, and holes we found.","PeriodicalId":275450,"journal":{"name":"Proceedings 4th IEEE Workshop on Enabling Technologies: Infrastructure for Collaborative Enterprises (WET ICE '95)","volume":"25 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1995-04-20","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"116882445","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Pub Date : 1995-04-20DOI: 10.1109/ENABL.1995.484561
A. Schill, B. Bellmann, Wito Böhmak, Sascha Kümmel
With the widespread use of distributed systems on one hand and the rapid deployment of mobile computing and communication infrastructure on the other, it becomes important to link both technologies together. This paper first outlines new problems arising from distributed mobile computing and then presents a software support architecture and system for mobile applications. We then discuss a system model for structuring mobile applications, a station software infrastructure for managing resource access in dynamic mobile environments, and a description technique for specifying behavioural aspects of mobile applications. The implementation is based on the remote procedure call of the OSF Distributed Computing Environment and on Microsoft RPC. First experiences with our prototype are reported and directions for future development are outlined.
{"title":"Infrastructure support for cooperative mobile environments","authors":"A. Schill, B. Bellmann, Wito Böhmak, Sascha Kümmel","doi":"10.1109/ENABL.1995.484561","DOIUrl":"https://doi.org/10.1109/ENABL.1995.484561","url":null,"abstract":"With the widespread use of distributed systems on one hand and the rapid deployment of mobile computing and communication infrastructure on the other, it becomes important to link both technologies together. This paper first outlines new problems arising from distributed mobile computing and then presents a software support architecture and system for mobile applications. We then discuss a system model for structuring mobile applications, a station software infrastructure for managing resource access in dynamic mobile environments, and a description technique for specifying behavioural aspects of mobile applications. The implementation is based on the remote procedure call of the OSF Distributed Computing Environment and on Microsoft RPC. First experiences with our prototype are reported and directions for future development are outlined.","PeriodicalId":275450,"journal":{"name":"Proceedings 4th IEEE Workshop on Enabling Technologies: Infrastructure for Collaborative Enterprises (WET ICE '95)","volume":"1 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1995-04-20","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"129720247","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Pub Date : 1995-04-20DOI: 10.1109/ENABL.1995.484548
K. Alho, C. Lassenius, R. Sulonen
This paper proposes a conceptual framework and supporting architecture for general-purpose process modeling and enactment. The framework includes abstractions of all critical entities and their relationships needed to model complex tasks in a distributed environment. We are able to support multi-paradigm process descriptions, since the support system only sees process execution as operations executed by agents. We do, however support division and delegation of activities. The supporting architecture is based on industry-standard communication and distribution mechanisms (CORBA) in order to make the services available to a wide variety of computers, operating systems, and communication protocols. We propose a way to integrate process modelling and enaction with existing configuration management systems and other repositories responsible for the storage and management of the artifacts handled by the processes. Possible application areas for the proposed system include software engineering, other design processes, logistics control, office automation, and enhanced electronic communication.
{"title":"Process enactment support in a distributed environment","authors":"K. Alho, C. Lassenius, R. Sulonen","doi":"10.1109/ENABL.1995.484548","DOIUrl":"https://doi.org/10.1109/ENABL.1995.484548","url":null,"abstract":"This paper proposes a conceptual framework and supporting architecture for general-purpose process modeling and enactment. The framework includes abstractions of all critical entities and their relationships needed to model complex tasks in a distributed environment. We are able to support multi-paradigm process descriptions, since the support system only sees process execution as operations executed by agents. We do, however support division and delegation of activities. The supporting architecture is based on industry-standard communication and distribution mechanisms (CORBA) in order to make the services available to a wide variety of computers, operating systems, and communication protocols. We propose a way to integrate process modelling and enaction with existing configuration management systems and other repositories responsible for the storage and management of the artifacts handled by the processes. Possible application areas for the proposed system include software engineering, other design processes, logistics control, office automation, and enhanced electronic communication.","PeriodicalId":275450,"journal":{"name":"Proceedings 4th IEEE Workshop on Enabling Technologies: Infrastructure for Collaborative Enterprises (WET ICE '95)","volume":"143 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1995-04-20","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"122463082","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Pub Date : 1995-04-20DOI: 10.1109/ENABL.1995.484549
D. Irving
The "Virtual Corporation", as a better way of working, is supported by such visionaries as Tom Peters and Robert J. Kriegel. Organisations making a move to this configuration often suffer culture shock from having to change management style to cope with project management. More significantly, if an organisation is moving towards performing all of its functions using a project structure, it must learn to manage a portfolio of projects. The new corporate structure will have the majority of the workforce divided into project teams. If these neglect to adopt project planning and management procedures many projects will fail. However, if senior management neglect these in managing the entire portfolio of projects, the consequences are potentially catastrophic for the organisation. If an organisation gets it right, "Organisation by Project" is an efficient and highly motivating method of working in which project teams often achieve results that can surpass even the highest expectations.
{"title":"Managing the resources of a portfolio of projects","authors":"D. Irving","doi":"10.1109/ENABL.1995.484549","DOIUrl":"https://doi.org/10.1109/ENABL.1995.484549","url":null,"abstract":"The \"Virtual Corporation\", as a better way of working, is supported by such visionaries as Tom Peters and Robert J. Kriegel. Organisations making a move to this configuration often suffer culture shock from having to change management style to cope with project management. More significantly, if an organisation is moving towards performing all of its functions using a project structure, it must learn to manage a portfolio of projects. The new corporate structure will have the majority of the workforce divided into project teams. If these neglect to adopt project planning and management procedures many projects will fail. However, if senior management neglect these in managing the entire portfolio of projects, the consequences are potentially catastrophic for the organisation. If an organisation gets it right, \"Organisation by Project\" is an efficient and highly motivating method of working in which project teams often achieve results that can surpass even the highest expectations.","PeriodicalId":275450,"journal":{"name":"Proceedings 4th IEEE Workshop on Enabling Technologies: Infrastructure for Collaborative Enterprises (WET ICE '95)","volume":"2 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1995-04-20","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"134249807","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Pub Date : 1995-04-20DOI: 10.1109/ENABL.1995.484545
Elliot A. Shefrin, James M. Purtilo
Prototyping is a means by which requirements for software projects can be defined and refined before they are committed to firm specifications for the finished software product. By this process, costly and time-consuming errors in specification can be avoided or minimized. Reconfiguration is the concept of altering the program code, bindings between program modules, or logical or physical distribution of software components while allowing the continuing execution of the software being changed. Combining these two notions suggests the potential for a development environment where requirements can be quickly and dynamically evolved. This paper discusses reconfiguration-based prototyping (RBP), that is, the simultaneous consideration of requirements, software behavior and user feedback within a running system in order to derive a clear specification of an intended product. Tools enabling RBP can coordinate the efforts of developers, users and subject matter specialists alike as they work toward consensus on an application's specification by means of a prototype.
{"title":"Tool support for collaborative software prototyping","authors":"Elliot A. Shefrin, James M. Purtilo","doi":"10.1109/ENABL.1995.484545","DOIUrl":"https://doi.org/10.1109/ENABL.1995.484545","url":null,"abstract":"Prototyping is a means by which requirements for software projects can be defined and refined before they are committed to firm specifications for the finished software product. By this process, costly and time-consuming errors in specification can be avoided or minimized. Reconfiguration is the concept of altering the program code, bindings between program modules, or logical or physical distribution of software components while allowing the continuing execution of the software being changed. Combining these two notions suggests the potential for a development environment where requirements can be quickly and dynamically evolved. This paper discusses reconfiguration-based prototyping (RBP), that is, the simultaneous consideration of requirements, software behavior and user feedback within a running system in order to derive a clear specification of an intended product. Tools enabling RBP can coordinate the efforts of developers, users and subject matter specialists alike as they work toward consensus on an application's specification by means of a prototype.","PeriodicalId":275450,"journal":{"name":"Proceedings 4th IEEE Workshop on Enabling Technologies: Infrastructure for Collaborative Enterprises (WET ICE '95)","volume":"100 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1995-04-20","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"131217129","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Pub Date : 1995-04-20DOI: 10.1109/ENABL.1995.484557
R. Furuta, Jaime C. Navón, P. D. Stotts
We informally explain a new Trellis model that incorporates colored tokens into the previously-described timed-Petri-net-based definition. We give examples of using Trellis to define protocols for Computer Supported Cooperative Work (CSCW). We then explain an interesting analog to procedure call we have developed for subdocument invocation in collaborative hyperdocuments. Trellis prototype implementations are based around a client-server architecture and interpret their specifications. Consequently they provide an environment for the rapid prototyping and incremental development of multi-user distributed protocols.
{"title":"Subdocument invocation semantics in collaborative hyperdocuments","authors":"R. Furuta, Jaime C. Navón, P. D. Stotts","doi":"10.1109/ENABL.1995.484557","DOIUrl":"https://doi.org/10.1109/ENABL.1995.484557","url":null,"abstract":"We informally explain a new Trellis model that incorporates colored tokens into the previously-described timed-Petri-net-based definition. We give examples of using Trellis to define protocols for Computer Supported Cooperative Work (CSCW). We then explain an interesting analog to procedure call we have developed for subdocument invocation in collaborative hyperdocuments. Trellis prototype implementations are based around a client-server architecture and interpret their specifications. Consequently they provide an environment for the rapid prototyping and incremental development of multi-user distributed protocols.","PeriodicalId":275450,"journal":{"name":"Proceedings 4th IEEE Workshop on Enabling Technologies: Infrastructure for Collaborative Enterprises (WET ICE '95)","volume":"49 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1995-04-20","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"131988052","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Pub Date : 1995-04-20DOI: 10.1109/ENABL.1995.484547
P. Ciancarini
Software Process Modeling is the activity of formalizing the production lifecycle of software systems. The aim is to formally describe a software development process, that then is effectively used and possibly enacted by an environment. We show that rule-based languages, especially logic programming languages, are an important technology for software process specification, modeling, enactment, and coordination. Because several process activities can be defined by rules. Some initial proposals aimed at animating a software process by a rule-based program embedding some development rules. A further step toward the integration of rule-based languages in the software process has be done using a dynamic knowledge base as project database, and a number of special primitives have been introduced to support process programs. Currently there is a trend toward more complex programming environments, called process-centered development environments. We show how some rule-based coordination languages are being used to build this kind of environment.
{"title":"Modeling the software process using coordination rules","authors":"P. Ciancarini","doi":"10.1109/ENABL.1995.484547","DOIUrl":"https://doi.org/10.1109/ENABL.1995.484547","url":null,"abstract":"Software Process Modeling is the activity of formalizing the production lifecycle of software systems. The aim is to formally describe a software development process, that then is effectively used and possibly enacted by an environment. We show that rule-based languages, especially logic programming languages, are an important technology for software process specification, modeling, enactment, and coordination. Because several process activities can be defined by rules. Some initial proposals aimed at animating a software process by a rule-based program embedding some development rules. A further step toward the integration of rule-based languages in the software process has be done using a dynamic knowledge base as project database, and a number of special primitives have been introduced to support process programs. Currently there is a trend toward more complex programming environments, called process-centered development environments. We show how some rule-based coordination languages are being used to build this kind of environment.","PeriodicalId":275450,"journal":{"name":"Proceedings 4th IEEE Workshop on Enabling Technologies: Infrastructure for Collaborative Enterprises (WET ICE '95)","volume":"19 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1995-04-20","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"125621052","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Pub Date : 1995-04-20DOI: 10.1109/ENABL.1995.484566
B. Silverman, G. Kearsley, Mary L. Rosenberg
How can we prepare engineers and other professionals to work in collaborative environments? In the 1994 Fall semester, we offered an interdisciplinary graduate course in collaborative technology to explore this question. The class involved a variety of different teaching/learning activities including: student debates, videos, guest discussants, software demos, field trips, and hands-on sessions. The primary evaluation mechanism for the class was a team project on collaborative technology.
{"title":"Preparing engineers for collaborative technology: a graduate course","authors":"B. Silverman, G. Kearsley, Mary L. Rosenberg","doi":"10.1109/ENABL.1995.484566","DOIUrl":"https://doi.org/10.1109/ENABL.1995.484566","url":null,"abstract":"How can we prepare engineers and other professionals to work in collaborative environments? In the 1994 Fall semester, we offered an interdisciplinary graduate course in collaborative technology to explore this question. The class involved a variety of different teaching/learning activities including: student debates, videos, guest discussants, software demos, field trips, and hands-on sessions. The primary evaluation mechanism for the class was a team project on collaborative technology.","PeriodicalId":275450,"journal":{"name":"Proceedings 4th IEEE Workshop on Enabling Technologies: Infrastructure for Collaborative Enterprises (WET ICE '95)","volume":"55 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1995-04-20","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"121157350","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Pub Date : 1995-04-20DOI: 10.1109/ENABL.1995.484552
Jack Hong, G. Toye, L. Leifer
The concept of an electronic or digital engineering design notebook used by designers to capture information for re-use and sharing is becoming reality in many different flavors. Our development of PENS (Personal Electronic Notebook with Sharing) responds to observed designers' needs for a lightweight tool that is facile enough to compete with paper notebooks in functionality. As design information is entered into PENS in real-time, the PENS information web grows. As it grows, selections can be incrementally published for sharing with collaborators over the Internet's World-Wide Web. In an era where both network security concerns and distributed collaboration demands are growing together, PENS has the capability for firewall-independent sharing. To evaluate the utility of the PENS notebook concept, a prototype has been developed and used by 14 mechanical engineering design teams that span local and remote design partnerships.
{"title":"Personal Electronic Notebook with Sharing","authors":"Jack Hong, G. Toye, L. Leifer","doi":"10.1109/ENABL.1995.484552","DOIUrl":"https://doi.org/10.1109/ENABL.1995.484552","url":null,"abstract":"The concept of an electronic or digital engineering design notebook used by designers to capture information for re-use and sharing is becoming reality in many different flavors. Our development of PENS (Personal Electronic Notebook with Sharing) responds to observed designers' needs for a lightweight tool that is facile enough to compete with paper notebooks in functionality. As design information is entered into PENS in real-time, the PENS information web grows. As it grows, selections can be incrementally published for sharing with collaborators over the Internet's World-Wide Web. In an era where both network security concerns and distributed collaboration demands are growing together, PENS has the capability for firewall-independent sharing. To evaluate the utility of the PENS notebook concept, a prototype has been developed and used by 14 mechanical engineering design teams that span local and remote design partnerships.","PeriodicalId":275450,"journal":{"name":"Proceedings 4th IEEE Workshop on Enabling Technologies: Infrastructure for Collaborative Enterprises (WET ICE '95)","volume":"31 5","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1995-04-20","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"132359764","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
京公网安备 11010802042870号
京ICP备2023020795号-1
扫码关注我们
求助内容：
应助结果提醒方式：