{"title":"Proceedings of the 2nd International Workshop on Software configuration management","authors":"R. Taylor","doi":"10.1145/72910","DOIUrl":"https://doi.org/10.1145/72910","url":null,"abstract":"","PeriodicalId":198444,"journal":{"name":"Proceedings of the 2nd International Workshop on Software configuration management","volume":"7 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1989-10-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"126343819","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}
A. Lie, R. Conradi, T. Didriksen, Even-André Karlsson
We present the change oriented model of versioning, which focuses strongly on functional changes in a software product and therefore can be seen as an alternative to the traditional, “version oriented” models. The change oriented model is used as a basis for the versioning in the EPOS software engineering database, which features an integrated transaction and versioning mechanism.
{"title":"Change oriented versioning in a software engineering database","authors":"A. Lie, R. Conradi, T. Didriksen, Even-André Karlsson","doi":"10.1145/72910.73348","DOIUrl":"https://doi.org/10.1145/72910.73348","url":null,"abstract":"We present the change oriented model of versioning, which focuses strongly on functional changes in a software product and therefore can be seen as an alternative to the traditional, “version oriented” models. The change oriented model is used as a basis for the versioning in the EPOS software engineering database, which features an integrated transaction and versioning mechanism.","PeriodicalId":198444,"journal":{"name":"Proceedings of the 2nd International Workshop on Software configuration management","volume":"29 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1989-10-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"120962335","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 aspects of a design management model. The area of design management may range from items such as users, access-rights, version- and configuration management to projects and tasks. This paper concentrates on the aspects of configuration management within Design Management Model (DMM). It is part of and implemented within a framework for engineering tool development and tool integration called Base/OPEN. The DMM is presented as an end-user views it through a tool called Browser.
{"title":"Design management in base/OPEN","authors":"Per Lundholm","doi":"10.1145/72910.73345","DOIUrl":"https://doi.org/10.1145/72910.73345","url":null,"abstract":"This paper presents aspects of a design management model. The area of design management may range from items such as users, access-rights, version- and configuration management to projects and tasks. This paper concentrates on the aspects of configuration management within Design Management Model (DMM). It is part of and implemented within a framework for engineering tool development and tool integration called Base/OPEN. The DMM is presented as an end-user views it through a tool called Browser.","PeriodicalId":198444,"journal":{"name":"Proceedings of the 2nd International Workshop on Software configuration management","volume":"74 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1989-10-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"115227674","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}
When a software system is developed by a large team of programmers, and has matured’ for several years, changes to the code may introduce unexpected interactions between diverse parts of the system. This occurs because the system has become too large for one person to fully understand, and the original design documentation has become obsolete as the system has evolved. Symptoms of structural problems include too many unnecessary recompilations, unintended cyclic dependency chains, and some types of difficulties with understanding, modifying, and testing the system. Most structural problems cannot be solved by making a few “small” changes, and most require the programmer to understand the overall pattern of interactions in order to solve the problem.
{"title":"Cross references are features","authors":"R. Schwanke, M. Platoff","doi":"10.1145/72910.73351","DOIUrl":"https://doi.org/10.1145/72910.73351","url":null,"abstract":"When a software system is developed by a large team of programmers, and has matured’ for several years, changes to the code may introduce unexpected interactions between diverse parts of the system. This occurs because the system has become too large for one person to fully understand, and the original design documentation has become obsolete as the system has evolved. Symptoms of structural problems include too many unnecessary recompilations, unintended cyclic dependency chains, and some types of difficulties with understanding, modifying, and testing the system. Most structural problems cannot be solved by making a few “small” changes, and most require the programmer to understand the overall pattern of interactions in order to solve the problem.","PeriodicalId":198444,"journal":{"name":"Proceedings of the 2nd International Workshop on Software configuration management","volume":"37 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1989-10-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"132310461","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 need to integrate several versions of a program into a common one arises frequently, but it is a tedious and time consuming task to merge programs by hand. The program-integration algorithm recently proposed by S. Horwitz, J. Prins, and T. Reps provides a way to create a semantics-based tool for program integration. The integration algorithm is based on the assumption that any change in the behavior, rather than the text, of a program variant is significant and must be preserved in the merged program. An integration system based on this algorithm will determine whether the programs incorporate interfering changes, and, if they do not, will automatically create an integrated program that includes all changes as well as all features that are preserved in all variants. In this paper we discuss how an integration tool can illustrate the causes of interference to the user when interference is detected. Our main technical result is an alternative characterization of the integration algorithm's interference criterion that is more suitable for illustrating the causes of interference. We then propose six methods for an integration system to display information to demonstrate the causes of interference to the user.
将一个程序的多个版本集成为一个通用版本的需求经常出现，但是手工合并程序是一项乏味且耗时的任务。S. Horwitz, J. Prins和T. Reps最近提出的程序集成算法提供了一种创建基于语义的程序集成工具的方法。集成算法基于这样一个假设，即程序变体的行为(而不是文本)中的任何变化都是重要的，并且必须保留在合并的程序中。基于该算法的集成系统将确定程序是否包含干扰变化，如果没有，将自动创建包含所有变化以及保留在所有变体中的所有特征的集成程序。在本文中，我们讨论了当检测到干扰时，集成工具如何向用户说明干扰的原因。我们的主要技术成果是对积分算法的干扰判据的另一种描述，它更适合于说明干扰的原因。然后，我们提出了六种集成系统显示信息的方法，以展示干扰用户的原因。
{"title":"Illustrating interference in interfering versions of programs","authors":"T. Reps, T. Bricker","doi":"10.1145/72910.73347","DOIUrl":"https://doi.org/10.1145/72910.73347","url":null,"abstract":"The need to integrate several versions of a program into a common one arises frequently, but it is a tedious and time consuming task to merge programs by hand. The program-integration algorithm recently proposed by S. Horwitz, J. Prins, and T. Reps provides a way to create a semantics-based tool for program integration. The integration algorithm is based on the assumption that any change in the behavior, rather than the text, of a program variant is significant and must be preserved in the merged program. An integration system based on this algorithm will determine whether the programs incorporate interfering changes, and, if they do not, will automatically create an integrated program that includes all changes as well as all features that are preserved in all variants. In this paper we discuss how an integration tool can illustrate the causes of interference to the user when interference is detected. Our main technical result is an alternative characterization of the integration algorithm's interference criterion that is more suitable for illustrating the causes of interference. We then propose six methods for an integration system to display information to demonstrate the causes of interference to the user.","PeriodicalId":198444,"journal":{"name":"Proceedings of the 2nd International Workshop on Software configuration management","volume":"98 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1989-10-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"115081650","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 source definition of an object is seen essentially as a hypertext-like structure. At any place within the hypertext structure, an alternative to existing text can be introduced with a suitable notation, with a formal description of the situations in which that piece of text is to be activated or considered part of the overall source definition of the object. Such hypertext structures can themselves contain variations in text by including further nested hypertext structures inside.
{"title":"A text-based representation for program variants","authors":"K. Narayanaswamy","doi":"10.1145/72910.73343","DOIUrl":"https://doi.org/10.1145/72910.73343","url":null,"abstract":"The source definition of an object is seen essentially as a hypertext-like structure. At any place within the hypertext structure, an alternative to existing text can be introduced with a suitable notation, with a formal description of the situations in which that piece of text is to be activated or considered part of the overall source definition of the object. Such hypertext structures can themselves contain variations in text by including further nested hypertext structures inside.","PeriodicalId":198444,"journal":{"name":"Proceedings of the 2nd International Workshop on Software configuration management","volume":"9 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1989-10-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"124238689","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}
Sun's Network Software Environment (NSE) provides configuration management services for engineering applications [1] [2] [3]. This paper describes the NSE and the object schema it was based on. It emphasizes the design decisions we made in constructing the system.
{"title":"A schema for configuration management","authors":"T. Miller","doi":"10.1145/72910.73342","DOIUrl":"https://doi.org/10.1145/72910.73342","url":null,"abstract":"Sun's Network Software Environment (NSE) provides configuration management services for engineering applications [1] [2] [3]. This paper describes the NSE and the object schema it was based on. It emphasizes the design decisions we made in constructing the system.","PeriodicalId":198444,"journal":{"name":"Proceedings of the 2nd International Workshop on Software configuration management","volume":"40 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1989-10-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"116469619","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}
Over the past five years our group has developed several large systems, including a workstation operating system, using the Modula family of languages, notably Modula-2+ [RLW85] and, recently, Modula-3 [CDG+88]. The language implementations were developed in-house and span several host and target environments. Consequently all the familiar configuration management (CM) problems are present, both in the language implementations themselves and in the application software which uses them. In response to these problems we have evolved tools and techniques, some of them innovative, some borrowed from others, to solve our problems in the Modula-2 environment. Currently we are developing a programming environment for Modula-3, which uses persistent abstract syntax trees as the basis for tool integration. Initially we are concentrating on the development of conventional tools for programming in the small, such as a compiler. However, in the longer term we plan to investigate database support for the environment and support for programming in the large and many. This paper outlines our experiences with the Modula-2 tools and states our position on pertinent issues.
{"title":"Experiences in configuration management for modula-2","authors":"Mick J. Jordan","doi":"10.1145/72910.73358","DOIUrl":"https://doi.org/10.1145/72910.73358","url":null,"abstract":"Over the past five years our group has developed several large systems, including a workstation operating system, using the Modula family of languages, notably Modula-2+ [RLW85] and, recently, Modula-3 [CDG+88]. The language implementations were developed in-house and span several host and target environments. Consequently all the familiar configuration management (CM) problems are present, both in the language implementations themselves and in the application software which uses them. In response to these problems we have evolved tools and techniques, some of them innovative, some borrowed from others, to solve our problems in the Modula-2 environment. Currently we are developing a programming environment for Modula-3, which uses persistent abstract syntax trees as the basis for tool integration. Initially we are concentrating on the development of conventional tools for programming in the small, such as a compiler. However, in the longer term we plan to investigate database support for the environment and support for programming in the large and many. This paper outlines our experiences with the Modula-2 tools and states our position on pertinent issues.","PeriodicalId":198444,"journal":{"name":"Proceedings of the 2nd International Workshop on Software configuration management","volume":"18 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1989-10-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"116961302","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 previous work, we described the design and implementation of a software hypertext environment for managing configured software descriptions [5]. That environment served as a basis for providing a facility for creating, managing, and revising the descriptions (ie, documentation) associated with the engineering of a software system’s life cycle. It described the structures we employed for organizing, linking, and visualizing software life cycle documents as configured descriptions. It further described how this visualization mechanism utilizes a module interconnection language (NuMIL) based description of a large program in order to graphically depict (sub)system configuration structures, as well as to graphically or logically browse relations between the configuration and its source code. This paper describes a new set of concepts and mechanisms which add a more rigorous, correctness-preserving foundation to the automated management of configured software life cycle descriptions. Specifically, there are two principal concepts embodied in this work, and an associated environment which supports their operationalization as well. The first involves the generalization, extension, and application of module interconnection language concepts to all software life cycle descriptions, not just to source code as used previously. This involves development of a formalism that views all objects created during a software system’s life cycle (e.g., individual requirements, design diagrams, test plans) as having an “interface” through which information resources are provided or required. Resource type and configuration relations are then associated with the interfaces, which in turn must be compatible for two or more software objects to be interconnected. As such, software life cycle objects can be composed or interconnected into life cycle stage descriptions (e.g., Requirements Analysis, Design, Testing). Further, descriptions associated with successive software life cycle descriptions, as defined by the user (e.g., design, implementation, testing), are also main-
{"title":"Assuring the correctness of configured software descriptions","authors":"Song C. Choi, W. Scacchi","doi":"10.1145/72910.73349","DOIUrl":"https://doi.org/10.1145/72910.73349","url":null,"abstract":"In previous work, we described the design and implementation of a software hypertext environment for managing configured software descriptions [5]. That environment served as a basis for providing a facility for creating, managing, and revising the descriptions (ie, documentation) associated with the engineering of a software system’s life cycle. It described the structures we employed for organizing, linking, and visualizing software life cycle documents as configured descriptions. It further described how this visualization mechanism utilizes a module interconnection language (NuMIL) based description of a large program in order to graphically depict (sub)system configuration structures, as well as to graphically or logically browse relations between the configuration and its source code. This paper describes a new set of concepts and mechanisms which add a more rigorous, correctness-preserving foundation to the automated management of configured software life cycle descriptions. Specifically, there are two principal concepts embodied in this work, and an associated environment which supports their operationalization as well. The first involves the generalization, extension, and application of module interconnection language concepts to all software life cycle descriptions, not just to source code as used previously. This involves development of a formalism that views all objects created during a software system’s life cycle (e.g., individual requirements, design diagrams, test plans) as having an “interface” through which information resources are provided or required. Resource type and configuration relations are then associated with the interfaces, which in turn must be compatible for two or more software objects to be interconnected. As such, software life cycle objects can be composed or interconnected into life cycle stage descriptions (e.g., Requirements Analysis, Design, Testing). Further, descriptions associated with successive software life cycle descriptions, as defined by the user (e.g., design, implementation, testing), are also main-","PeriodicalId":198444,"journal":{"name":"Proceedings of the 2nd International Workshop on Software configuration management","volume":"66 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1989-10-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"129656038","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}
One part of the “Software Configuration Management” — software version control — is the task of controlling different versions of documents. Most existing version control systems accomplish this task by managing variant and revision trees of single documents. The structure of these trees depends on the chronological evolution of the software project. We call this form of organization “intermixed organization” of variants and revisions. This paper points out the disadvantages of that organization, introduces a new way of version management - the “orthogonal organization” - and then compares the two organizations by means of an example.
{"title":"Orthogonal version management","authors":"C. Reichenberger","doi":"10.1145/72910.73361","DOIUrl":"https://doi.org/10.1145/72910.73361","url":null,"abstract":"One part of the “Software Configuration Management” — software version control — is the task of controlling different versions of documents. Most existing version control systems accomplish this task by managing variant and revision trees of single documents. The structure of these trees depends on the chronological evolution of the software project. We call this form of organization “intermixed organization” of variants and revisions. This paper points out the disadvantages of that organization, introduces a new way of version management - the “orthogonal organization” - and then compares the two organizations by means of an example.","PeriodicalId":198444,"journal":{"name":"Proceedings of the 2nd International Workshop on Software configuration management","volume":"34 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1989-10-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"128151071","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
扫码关注我们
求助内容：
应助结果提醒方式：