Object-oriented analysis and design methodologies take full advantage of the object approach when it comes to modeling the objects in a system. However, system behavior continues to be modeled using essentially the same tools as in traditional systems analysis: state diagrams and dataflow diagrams. In this paper we extend the notion of specialization to these process representations and identify a set of transformations which, when applied to a process description, always result in specialization. We analyze specific examples in detail and demonstrate that such a use of specialization is not only theoretically possible, but shows promise as a method for categorizing and analyzing processes. We identify a number of apparent inconsistencies between process specialization and the object specialization which is part of the object-oriented approach. We demonstrate that these apparent inconsistencies are superficial and that the approach we take is compatible with the traditional notion of specialization.
{"title":"Applying specialization to process models","authors":"George M. Wyner, Jintae Lee","doi":"10.1145/224019.224050","DOIUrl":"https://doi.org/10.1145/224019.224050","url":null,"abstract":"Object-oriented analysis and design methodologies take full advantage of the object approach when it comes to modeling the objects in a system. However, system behavior continues to be modeled using essentially the same tools as in traditional systems analysis: state diagrams and dataflow diagrams. In this paper we extend the notion of specialization to these process representations and identify a set of transformations which, when applied to a process description, always result in specialization. We analyze specific examples in detail and demonstrate that such a use of specialization is not only theoretically possible, but shows promise as a method for categorizing and analyzing processes. We identify a number of apparent inconsistencies between process specialization and the object specialization which is part of the object-oriented approach. We demonstrate that these apparent inconsistencies are superficial and that the approach we take is compatible with the traditional notion of specialization.","PeriodicalId":338751,"journal":{"name":"Conference on Organizational Computing Systems","volume":"28 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2018-02-08","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"126885187","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}
In cooperative software development, each programmer has their own plans and conflicts or redundancies inevitably arise among them. We are concerned with two main problems: first, to control changes without sacrificing programmers’ flexibility, and, second, to guide change activities to conform project policies. Traditional methods of change request management focus on the management process s~cture based on project policies while cooperative development methodologies concern mainly with the conflict resolutions among each changes. In this paper, we describe an architecture which deals with proposal of changes. Based on plan integration it seamlessly supports both change coordination through negotiations and the change management process to have changes converge until they meet the project goals.
{"title":"Combining local negotiation and global planning in cooperative software development projects","authors":"Kazuo Okamura","doi":"10.1145/168555.168582","DOIUrl":"https://doi.org/10.1145/168555.168582","url":null,"abstract":"In cooperative software development, each programmer has their own plans and conflicts or redundancies inevitably arise among them. We are concerned with two main problems: first, to control changes without sacrificing programmers’ flexibility, and, second, to guide change activities to conform project policies. Traditional methods of change request management focus on the management process s~cture based on project policies while cooperative development methodologies concern mainly with the conflict resolutions among each changes. In this paper, we describe an architecture which deals with proposal of changes. Based on plan integration it seamlessly supports both change coordination through negotiations and the change management process to have changes converge until they meet the project goals.","PeriodicalId":338751,"journal":{"name":"Conference on Organizational Computing Systems","volume":"14 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2017-08-24","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"122923918","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}
Answer Garden allows organizations to develop databases of commonly asked questions that grow “organically” as new questions arise and are answered. It is designed to help in situations (such as field service organizations and customer “hot lines”) where there is a continuing stream of questions, many of which occur over and over, but some of which the organization has never seen before. The system includes a branching network of diagnostic questions that helps users find the answers they want. If the answer is not present, the system automatically sends the question to the appropriate expert, and the answer is returned to the user as well as inserted into the branching network. Experts can also modify this network in response to users' problems. Our initial Answer Garden database contains questions and answers about how to use the X Window System.
{"title":"Answer Garden: a tool for growing organizational memory","authors":"M. Ackerman, T. Malone","doi":"10.1145/91474.91485","DOIUrl":"https://doi.org/10.1145/91474.91485","url":null,"abstract":"Answer Garden allows organizations to develop databases of commonly asked questions that grow “organically” as new questions arise and are answered. It is designed to help in situations (such as field service organizations and customer “hot lines”) where there is a continuing stream of questions, many of which occur over and over, but some of which the organization has never seen before. The system includes a branching network of diagnostic questions that helps users find the answers they want. If the answer is not present, the system automatically sends the question to the appropriate expert, and the answer is returned to the user as well as inserted into the branching network. Experts can also modify this network in response to users' problems.\u0000Our initial Answer Garden database contains questions and answers about how to use the X Window System.","PeriodicalId":338751,"journal":{"name":"Conference on Organizational Computing Systems","volume":"1 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2015-09-10","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"116918408","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}
The reorganization of function-oriented, hierachically structured firms into interacting business process networks of functional islands integrated by flow of material and information is a major challenge for a company that wants to meet the steadily changing business demands of today. As information has become an important production resource during the last decades, the reorganization of information management has to accompany organizational restructuring. In this paper we propose a partially decentralized and business process oriented information management approach for quality management processes. We will describe how conceptual modeling of those processes supports the information system design within this approach. Staring from a presentation of the developed architecture, we will describe our experiences with several information access and engineering mechanisms that make use of the defined conceptual models.
{"title":"Business process oriented information management: conceptual models at work","authors":"P. Peters, P. Szczurko, M. Jarke, M. Jeusfeld","doi":"10.1145/224019.224041","DOIUrl":"https://doi.org/10.1145/224019.224041","url":null,"abstract":"The reorganization of function-oriented, hierachically structured firms into interacting business process networks of functional islands integrated by flow of material and information is a major challenge for a company that wants to meet the steadily changing business demands of today. As information has become an important production resource during the last decades, the reorganization of information management has to accompany organizational restructuring. In this paper we propose a partially decentralized and business process oriented information management approach for quality management processes. We will describe how conceptual modeling of those processes supports the information system design within this approach. Staring from a presentation of the developed architecture, we will describe our experiences with several information access and engineering mechanisms that make use of the defined conceptual models.","PeriodicalId":338751,"journal":{"name":"Conference on Organizational Computing Systems","volume":"143 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1995-08-13","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"122503310","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}
Workflow systems have been proposed as a means for automating business procedures. While growing in popularity, many fundamental problems, such as supporting unstructured office activities, still remain before this technology will be especially useful in the office. This paper examines difficulties associated with handling unstructured office activities and argues that it is both necessary and possible for workflow technology to better support office workers who perform these activities. The approach illustrated in this paper advocates reducing the rigidity of the workflow system's computational model, which, in turn, requires the system to better support the contextual information needs of the workers performing the unstructured activities.
{"title":"Supporting unstructured workflow activities in the Bramble ICN system","authors":"Richard L. Blumenthal, G. Nutt","doi":"10.1145/224019.224032","DOIUrl":"https://doi.org/10.1145/224019.224032","url":null,"abstract":"Workflow systems have been proposed as a means for automating business procedures. While growing in popularity, many fundamental problems, such as supporting unstructured office activities, still remain before this technology will be especially useful in the office. This paper examines difficulties associated with handling unstructured office activities and argues that it is both necessary and possible for workflow technology to better support office workers who perform these activities. The approach illustrated in this paper advocates reducing the rigidity of the workflow system's computational model, which, in turn, requires the system to better support the contextual information needs of the workers performing the unstructured activities.","PeriodicalId":338751,"journal":{"name":"Conference on Organizational Computing Systems","volume":"38 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1995-08-13","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"125656474","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}
Introducing document and workflow management systems causes two main problems:How can the supported business processes be adequately modeled? How can existing information systems and databases be integrated? Within this paper, we present tools, methods and other approaches, which are designed to solve these problems. They are illustrated by the offer processing of a machine tool company. This process starts with a customer inquiry for a particular product and finishes with a customized offer. Several levels of integrated document and workflow management are discussed in section 2. This is followed by an introduction to the current offer processing used by our partner company INA Waelzlager Schaeffler KG, in which we highlight its main weaknesses. The fourth section describes a newly developed document-oriented tool to model business processes, and which serves also as a means of analyzing the current offer processing. The subject matter of the next chapter is the prototypical realization of a document and workflow management system at INA, which also comprises integrated application programs. The objective consists of a “lean integration” in order to avoid methods like total IS-reengineering or the use of highly integrated, but rigid standard software, where these are unreasonable heavy for small to medium enterprises.
{"title":"Integrated document and workflow management applied to the offer processing of a machine tool company","authors":"Stefan Morschheuser, Heinz Raufer","doi":"10.1145/224019.224030","DOIUrl":"https://doi.org/10.1145/224019.224030","url":null,"abstract":"Introducing document and workflow management systems causes two main problems:How can the supported business processes be adequately modeled?\u0000How can existing information systems and databases be integrated?\u0000\u0000Within this paper, we present tools, methods and other approaches, which are designed to solve these problems. They are illustrated by the offer processing of a machine tool company. This process starts with a customer inquiry for a particular product and finishes with a customized offer.\u0000Several levels of integrated document and workflow management are discussed in section 2. This is followed by an introduction to the current offer processing used by our partner company INA Waelzlager Schaeffler KG, in which we highlight its main weaknesses. The fourth section describes a newly developed document-oriented tool to model business processes, and which serves also as a means of analyzing the current offer processing. The subject matter of the next chapter is the prototypical realization of a document and workflow management system at INA, which also comprises integrated application programs. The objective consists of a “lean integration” in order to avoid methods like total IS-reengineering or the use of highly integrated, but rigid standard software, where these are unreasonable heavy for small to medium enterprises.","PeriodicalId":338751,"journal":{"name":"Conference on Organizational Computing Systems","volume":"41 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1995-08-13","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"130231189","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}
This paper explores the meaning of the concept of self-control in the context of Business Process Reengineering (BPR). BPR is a radical approach that breaks with many conventional ideas from applied management and organization theory. The delegation of control and decision-authority is a key concept within BPR, and reengineering advocates argue that employees should control themselves. Self-controlled employees represents a radical shift from what could be considered as 'status quo', and it will certainly be a challenge to implement this. This paper examines some major roadblocks that might reduce the likelihood for self-control to be realized in the context of BPR.
{"title":"Business process reengineering: examining some major roadblocks to increased self-control for the employee","authors":"Jon Iden","doi":"10.1145/224019.224027","DOIUrl":"https://doi.org/10.1145/224019.224027","url":null,"abstract":"This paper explores the meaning of the concept of self-control in the context of Business Process Reengineering (BPR). BPR is a radical approach that breaks with many conventional ideas from applied management and organization theory. The delegation of control and decision-authority is a key concept within BPR, and reengineering advocates argue that employees should control themselves. Self-controlled employees represents a radical shift from what could be considered as 'status quo', and it will certainly be a challenge to implement this. This paper examines some major roadblocks that might reduce the likelihood for self-control to be realized in the context of BPR.","PeriodicalId":338751,"journal":{"name":"Conference on Organizational Computing Systems","volume":"28 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1995-08-13","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"133885015","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}
This paper focuses on the set of group endeavors that exists within the structure of an organization. The environment in which organizations exist is becoming increasingly dynamic. Cooperative tasks are increasing and workgroup computing is becoming more pervasive. There are computer-mediated tools and systems to support organizations' coordination of group endeavors. These systems, however, are incomplete and therefore do not adequately give organizations the flexibility that a dynamic environment requires. The need for unified information systems is looming. The solution is to provide consistent and comprehensive, computer-mediated, shared task support for the coordination of group endeavors in all domains, in dynamic, and increasingly complex environments. Workflow and project management are prototypical of that collaborative use. This paper evaluates workflow processes and projects in order to gain an understanding of requirements that will serve as a conceptual foundation for this cooperative systems environment.
{"title":"Goals and processes: a task basis for projects and workflows","authors":"N. Craven, D. Mahling","doi":"10.1145/224019.224045","DOIUrl":"https://doi.org/10.1145/224019.224045","url":null,"abstract":"This paper focuses on the set of group endeavors that exists within the structure of an organization. The environment in which organizations exist is becoming increasingly dynamic. Cooperative tasks are increasing and workgroup computing is becoming more pervasive. There are computer-mediated tools and systems to support organizations' coordination of group endeavors. These systems, however, are incomplete and therefore do not adequately give organizations the flexibility that a dynamic environment requires. The need for unified information systems is looming. The solution is to provide consistent and comprehensive, computer-mediated, shared task support for the coordination of group endeavors in all domains, in dynamic, and increasingly complex environments. Workflow and project management are prototypical of that collaborative use. This paper evaluates workflow processes and projects in order to gain an understanding of requirements that will serve as a conceptual foundation for this cooperative systems environment.","PeriodicalId":338751,"journal":{"name":"Conference on Organizational Computing Systems","volume":"40 3 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1995-08-13","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"123608032","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}
This paper presents a technique for system redesign called Priority Workshop. The technique aims at widening the circle of decision makers, avoiding arbitrary decisions, and providing an arena for making priorities transparent to those who are affected. Priority Workshop has been conducted in a software company co-operating with several user organisations. The example presented, indicates that Priority Workshops may be a valuable means for users to influence the redesign process.
{"title":"Priority workshops: springboard for user participation in redesign activities","authors":"K. Braa","doi":"10.1145/224019.224047","DOIUrl":"https://doi.org/10.1145/224019.224047","url":null,"abstract":"This paper presents a technique for system redesign called Priority Workshop. The technique aims at widening the circle of decision makers, avoiding arbitrary decisions, and providing an arena for making priorities transparent to those who are affected. Priority Workshop has been conducted in a software company co-operating with several user organisations. The example presented, indicates that Priority Workshops may be a valuable means for users to influence the redesign process.","PeriodicalId":338751,"journal":{"name":"Conference on Organizational Computing Systems","volume":"1 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1995-08-13","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"131930882","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}
Recently a faction of software engineering researchers has focused their attention on studying the process by which software is produced, stimulating interest in models to specify, design, and implement software. A significant part of the practicing software industry must produce software that conforms to a documentation standard (military standard 2167A) for software products; it is intended to ensure that delivered software meets the documentation requirements. This paper is a case study of how a government software contractor might use models to define a process for designing and implementing a software product that complies with the documentation requirements. The intent of the paper is to apply business process modeling technology to the software engineering domain, thus exploring strengths and weaknesses of our evolving models of group collaboration. The case study illustrates an alternative way to design, analyze, and track software processes. It also attempts to illustrate how the model might “break down” as the basis of an enactment model if it were to be used to coordinate the work of a large number of software developers.
{"title":"Software engineering process model: a case study","authors":"G. Nutt","doi":"10.1145/224019.224053","DOIUrl":"https://doi.org/10.1145/224019.224053","url":null,"abstract":"Recently a faction of software engineering researchers has focused their attention on studying the process by which software is produced, stimulating interest in models to specify, design, and implement software. A significant part of the practicing software industry must produce software that conforms to a documentation standard (military standard 2167A) for software products; it is intended to ensure that delivered software meets the documentation requirements. This paper is a case study of how a government software contractor might use models to define a process for designing and implementing a software product that complies with the documentation requirements. The intent of the paper is to apply business process modeling technology to the software engineering domain, thus exploring strengths and weaknesses of our evolving models of group collaboration. The case study illustrates an alternative way to design, analyze, and track software processes. It also attempts to illustrate how the model might “break down” as the basis of an enactment model if it were to be used to coordinate the work of a large number of software developers.","PeriodicalId":338751,"journal":{"name":"Conference on Organizational Computing Systems","volume":"79 21","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1995-08-13","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"131472117","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
扫码关注我们
求助内容：
应助结果提醒方式：