{"title":"Meta-integration for process integrated CASE environments","authors":"T. Ajisaka","doi":"10.1109/ISPW.1994.512765","DOIUrl":"https://doi.org/10.1109/ISPW.1994.512765","url":null,"abstract":"This paper aims firstly at integrating the reference models for software processes (human activities) and for CASE environments (machinery activities), and then at providing meta-integration between services for both activities. Five kinds of integration for tool and process frameworks, including \"cooperative work (CW)\" integration that is newly identified, are investigated by distinguishing their \"contents\" and \"vessels\". Many standards and methods for software engineering fall into one of the ten categories of services, which provides a clear map to understand meta-integration. The interactions between the service categories are then described, after presenting an OSI-like model of CW integration.","PeriodicalId":337172,"journal":{"name":"Proceedings. Ninth International Software Process Workshop","volume":"18 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1994-10-05","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"124839396","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}
{"title":"Process-centered environments: support for human-environment interaction and environment-mediated human cooperation","authors":"Ilham Alloui, Selma Arbaoui, F. Oquendo","doi":"10.1109/ISPW.1994.512778","DOIUrl":"https://doi.org/10.1109/ISPW.1994.512778","url":null,"abstract":"Process enactment involves two kinds of interaction in a PCE (Process Centered Environment): human-environment interaction and environment-mediated human cooperation. In order to provide relevant and useful support to process performance, both kinds of interaction need to be modeled and supported by PCE's process formalisms and mechanisms. Indeed, as processes are dynamic and evolvable, human process performance and human-human interaction may lead to inconsistencies between process enactment and process performance states. PEACE's (Process-centered Enactable and Adaptable Computer-aided Environment) solution to handling such inconsistencies is (i) to provide a process modeling formalism based on the autoepistemic logic that allows to represent in the enactment state, all the knowledge provided from performers-even if it is not definitive or partial-and (ii) to mediate social interaction by providing explicit protocols based on the multi-agent paradigm.","PeriodicalId":337172,"journal":{"name":"Proceedings. Ninth International Software Process Workshop","volume":"65 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1994-10-05","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"121749270","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}
{"title":"Life-cycle (sub) process scenario","authors":"M. H. Penedo","doi":"10.1109/ISPW.1994.512787","DOIUrl":"https://doi.org/10.1109/ISPW.1994.512787","url":null,"abstract":"This paper contains the ISPW9 scenario or process example. It is a continuation of the International Software Process Workshops' tradition of providing a process scenario as an example of life-cycle sub-processes for specifications in different formalisms and implementation and demonstration in different systems. It was defined to support a demonstration day at the International Software Process Workshop (ISPW9).","PeriodicalId":337172,"journal":{"name":"Proceedings. Ninth International Software Process Workshop","volume":"21 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1994-10-05","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"134038347","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}
{"title":"The software process from the developer's perspective: a case study on improving process usability","authors":"K. Culver-Lozo","doi":"10.1109/ISPW.1994.512766","DOIUrl":"https://doi.org/10.1109/ISPW.1994.512766","url":null,"abstract":"For a software process to be used, it must first be understood by the developers applying it. This paper describes the experiences of a software development organization improving the usability its process definitions. By reducing the complexity of the process definition and organizing information around work products and deliverables, the process descriptions more closely match developers' information needs.","PeriodicalId":337172,"journal":{"name":"Proceedings. Ninth International Software Process Workshop","volume":"24 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1994-10-05","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"134283362","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}
{"title":"CSCW and Software Process","authors":"G. Kaiser, S. Kaplan","doi":"10.1109/ISPW.1994.512752","DOIUrl":"https://doi.org/10.1109/ISPW.1994.512752","url":null,"abstract":"1 CSCW vs. Workflow vs. Process The session started off with instant controversy when Simon Kaplan put up figure 1, a Venn diagram with three ovals: the large outer one labeled CSCW, the middle one labeled Workflow, and the small inner one labeled Process. Several attendees suggested that the diagram would be fine if the roles of CSCW and Process were reversed. Bob Balzer complained about Workflow encompassing Process. Naser Barghouti thought overlapping circles would be more appropriate. The main issue was the relationship between CSCW and Process, since Workflow was agreed to be only a subpart of Process assuming our discussion of Process was not restricted to software development processes. For example, Manny Lehman clarified ( a bit later) that the relevant business processes are part of any software process. Lee Osterweil admitted that the CSCW community, per se, is larger than the (software) Process community. But Simon argued that CSCW is also larger in scope and importance, encompassing both formal and cultural concepts while Process is necessarily limited to what can be formalized. Bob asked how Simon defines CSCW. Simon explained that he sees one person working alone as degenerated collaboration. Bob responded that then the computer itself can be viewed as a second agent. K . Narayanaswamy (Swamy) pointed out that CSCW does not, in general, explicitly state the ProDepartment of Computer Science University of Illiois Urbana, IL 61801","PeriodicalId":337172,"journal":{"name":"Proceedings. Ninth International Software Process Workshop","volume":"5 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1994-10-05","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"123504677","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}
{"title":"Process models as multi-reader collaborative hyperdocuments","authors":"P. D. Stotts, R. Furuta","doi":"10.1109/ISPW.1994.512771","DOIUrl":"https://doi.org/10.1109/ISPW.1994.512771","url":null,"abstract":"The Trellis model of human/computer interaction, in the context of hypermedia documents, is a good basis for specifying and applying software process models. The emphasis on user-direction of control gained from the hypermedia paradigm makes Trellis models inherently less program-like and more human-oriented. Trellis differs from other hypermedia models by using parallel automata (colored timed Petri nets) as hyperdocument structure (other models treat hyperdocuments as static graphs). Trellis hyperdocuments are therefore naturally interpreted and analyzed as process specifications. Our work has concentrated on using the colored-tokens in the nets for control of collaborative activity.","PeriodicalId":337172,"journal":{"name":"Proceedings. Ninth International Software Process Workshop","volume":"35 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1994-10-05","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"129050782","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}
{"title":"The need for a cooperative model: the Adele/Tempo experience","authors":"N. Belkhatir, W. Melo","doi":"10.1109/ISPW.1994.512772","DOIUrl":"https://doi.org/10.1109/ISPW.1994.512772","url":null,"abstract":"Our position is that the software process is fundamentally cooperative. We have been developing concepts and mechanism to tackle with cooperation in the Adele/Tempo project. Firstly, we integrated into the Tempo software process formalism a new concept: cooperation classes. In addition, we provided temporal, event-condition-action (TECA) rules in order to monitor and control cooperative activities. Based on TECA rules and cooperation classes, we can describe exchange information policies between software developers as well as rules about the organization, evolution and consistency of software projects. Secondly, we have been developing a transaction management system which is able to support the Tempo cooperative model. This system has been built up to deal with un-predicted events provoked by activities carried out in cooperative work environments.","PeriodicalId":337172,"journal":{"name":"Proceedings. Ninth International Software Process Workshop","volume":"2 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1994-10-05","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"117105305","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}
{"title":"Humans and process frameworks: some critical process elements","authors":"B. Boehm, P. Bose","doi":"10.1109/ISPW.1994.512770","DOIUrl":"https://doi.org/10.1109/ISPW.1994.512770","url":null,"abstract":"Successful engineering of complex software systems require humans to engage collaboratively in multiple critical process elements. This paper identifies those necessary process elements and defines WinWin, a collaborative process model that addresses the process elements. It briefly describes a process support system for the WinWin model.","PeriodicalId":337172,"journal":{"name":"Proceedings. Ninth International Software Process Workshop","volume":"14 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1994-10-05","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"133691548","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}
S. Bandinelli, E. D. Nitto, A. Fuggetta, L. Lavazza
{"title":"Coupled vs decoupled user interaction environments in PSEEs","authors":"S. Bandinelli, E. D. Nitto, A. Fuggetta, L. Lavazza","doi":"10.1109/ISPW.1994.512761","DOIUrl":"https://doi.org/10.1109/ISPW.1994.512761","url":null,"abstract":"We discuss the relationship between the process modeling language (PML) paradigm and user interaction paradigm in a PSEE. On one side, the user interaction paradigm may strongly depend on the PML and its supporting environment. On the other side, it is related to the social context and the specific process in which it is used. A user interaction environment decoupled from the PML may be tailored to the specific user needs, without impacting on the PML concepts and on the PSEE architecture, On the other hand, a user interaction environment coupled with the PML does not require specific modeling work by the process modeler but binds the interaction paradigm to the process language paradigm. We characterize these two extreme alternatives and provide pros and cons for each of them.","PeriodicalId":337172,"journal":{"name":"Proceedings. Ninth International Software Process Workshop","volume":"16 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1994-10-05","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"131413140","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}
{"title":"Process definition formalism maturity levels","authors":"R. Balzer","doi":"10.1109/ISPW.1994.512784","DOIUrl":"https://doi.org/10.1109/ISPW.1994.512784","url":null,"abstract":"Beginning with the observations that process definition formalisms are not very different from general purpose programming languages and that almost every type of programming language has been used as the basis of one or more process definition formalisms, we conclude that the field of process definition formalisms is quite immature. We speculate on the future maturation of this field by proposing a set of maturity levels by which to measure that maturation.","PeriodicalId":337172,"journal":{"name":"Proceedings. Ninth International Software Process Workshop","volume":"45 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1994-10-05","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"129387136","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}