Pub Date : 1999-08-30DOI: 10.1109/ICSM.1999.792626
M. Kajko-Mattsson
Software engineering is the fastest growing field of engineering today. Due to this revolutionary development, many conflicts have arisen when defining and using new concepts. This has involved the need for standards, such as the IEEE standard. Despite this, there is still nonuniformity in the use of standard definitions. This could be due to the fact that most of the standard definitions are expressed in natural language. Furthermore, ambiguity may arise when relating some of these concepts to other concepts. We propose a conceptual model of the basic concepts utilised within corrective software maintenance. The goal is to clarify the fundamental concept apparatus. This model should constitute a common forum for communication when conceptualising software problems and defects, and for suggesting maintenance frameworks, models and/or measures.
{"title":"Common concept apparatus within corrective software maintenance","authors":"M. Kajko-Mattsson","doi":"10.1109/ICSM.1999.792626","DOIUrl":"https://doi.org/10.1109/ICSM.1999.792626","url":null,"abstract":"Software engineering is the fastest growing field of engineering today. Due to this revolutionary development, many conflicts have arisen when defining and using new concepts. This has involved the need for standards, such as the IEEE standard. Despite this, there is still nonuniformity in the use of standard definitions. This could be due to the fact that most of the standard definitions are expressed in natural language. Furthermore, ambiguity may arise when relating some of these concepts to other concepts. We propose a conceptual model of the basic concepts utilised within corrective software maintenance. The goal is to clarify the fundamental concept apparatus. This model should constitute a common forum for communication when conceptualising software problems and defects, and for suggesting maintenance frameworks, models and/or measures.","PeriodicalId":193867,"journal":{"name":"Proceedings IEEE International Conference on Software Maintenance - 1999 (ICSM'99). 'Software Maintenance for Business Change' (Cat. No.99CB36360)","volume":"24 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1999-08-30","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"122029738","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 : 1999-08-30DOI: 10.1109/ICSM.1999.792622
A. Sellink, C. Verhoef
When a compiler is designed carefully, it is possible to extract its grammar. We reengineer the extracted grammar to one that is geared towards reengineering. From this reengineering grammar we generate an architecture called a software renovation factory. This includes: generic analysis and transformation functionality and a native pattern language using the concrete syntax of the language for which the renovation is necessary. Moreover, we generate the grammar in HTML format so that reengineers can quickly understand the language. We applied our approach successfully to an exceptionally complex and large proprietary language. Our approach enables rapid development of software renovation factories. We believe that our approach can partly solve the lack of Year 2000 tool support for many languages.
{"title":"Generation of software renovation factories from compilers","authors":"A. Sellink, C. Verhoef","doi":"10.1109/ICSM.1999.792622","DOIUrl":"https://doi.org/10.1109/ICSM.1999.792622","url":null,"abstract":"When a compiler is designed carefully, it is possible to extract its grammar. We reengineer the extracted grammar to one that is geared towards reengineering. From this reengineering grammar we generate an architecture called a software renovation factory. This includes: generic analysis and transformation functionality and a native pattern language using the concrete syntax of the language for which the renovation is necessary. Moreover, we generate the grammar in HTML format so that reengineers can quickly understand the language. We applied our approach successfully to an exceptionally complex and large proprietary language. Our approach enables rapid development of software renovation factories. We believe that our approach can partly solve the lack of Year 2000 tool support for many languages.","PeriodicalId":193867,"journal":{"name":"Proceedings IEEE International Conference on Software Maintenance - 1999 (ICSM'99). 'Software Maintenance for Business Change' (Cat. No.99CB36360)","volume":"33 13 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1999-08-30","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"116788674","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 : 1999-08-30DOI: 10.1109/ICSM.1999.792495
Yuming Zhou, Baowen Xu
Reengineering legacy systems written in conventional procedural languages to equivalent OO systems makes software more maintainable and reliable. In this paper a method for extracting objects from legacy Ada 83 systems using module features is proposed. First, we develop metrics to measure module cohesion. Then, effects on cohesion from changing module components are discussed and rules on how to extract inheritance relations among objects are given. Finally, an object identification tool in APAUS is described.
{"title":"Extracting objects of Ada programs using module features","authors":"Yuming Zhou, Baowen Xu","doi":"10.1109/ICSM.1999.792495","DOIUrl":"https://doi.org/10.1109/ICSM.1999.792495","url":null,"abstract":"Reengineering legacy systems written in conventional procedural languages to equivalent OO systems makes software more maintainable and reliable. In this paper a method for extracting objects from legacy Ada 83 systems using module features is proposed. First, we develop metrics to measure module cohesion. Then, effects on cohesion from changing module components are discussed and rules on how to extract inheritance relations among objects are given. Finally, an object identification tool in APAUS is described.","PeriodicalId":193867,"journal":{"name":"Proceedings IEEE International Conference on Software Maintenance - 1999 (ICSM'99). 'Software Maintenance for Business Change' (Cat. No.99CB36360)","volume":"15 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1999-08-30","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"116487098","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 : 1999-08-30DOI: 10.1109/ICSM.1999.792615
R. Schauer, Sébastien Robitaille, François Martel, R. Keller
The success of an object-oriented software development project highly depends on how well the designers can capture the Hot Spots of the application domain, that is, those aspects that should be kept flexible to accommodate reuse and change. Yet, all too often, Hot Spots are hardly documented and over years of software evolution, the source code that reifies them becomes increasingly entangled with the application specific code. This blurring of the flexible with the rigid parts makes an application hard to maintain, prone to unexpected change impact, and immobile for reuse in related areas. In this paper we apply SPOOL, our prototype environment for reverse engineering, to the recovery of Hot Spots in C++ software. We base the technique for Hot Spot recovery on the design concept of template methods. We present the approach and the interactive analysis capabilities of SPOOL to visualize browse, and inspect Hot Spots in both separate and contextual form. The findings are validated based on two industrial systems.
{"title":"Hot spot recovery in object-oriented software with inheritance and composition template methods","authors":"R. Schauer, Sébastien Robitaille, François Martel, R. Keller","doi":"10.1109/ICSM.1999.792615","DOIUrl":"https://doi.org/10.1109/ICSM.1999.792615","url":null,"abstract":"The success of an object-oriented software development project highly depends on how well the designers can capture the Hot Spots of the application domain, that is, those aspects that should be kept flexible to accommodate reuse and change. Yet, all too often, Hot Spots are hardly documented and over years of software evolution, the source code that reifies them becomes increasingly entangled with the application specific code. This blurring of the flexible with the rigid parts makes an application hard to maintain, prone to unexpected change impact, and immobile for reuse in related areas. In this paper we apply SPOOL, our prototype environment for reverse engineering, to the recovery of Hot Spots in C++ software. We base the technique for Hot Spot recovery on the design concept of template methods. We present the approach and the interactive analysis capabilities of SPOOL to visualize browse, and inspect Hot Spots in both separate and contextual form. The findings are validated based on two industrial systems.","PeriodicalId":193867,"journal":{"name":"Proceedings IEEE International Conference on Software Maintenance - 1999 (ICSM'99). 'Software Maintenance for Business Change' (Cat. No.99CB36360)","volume":"22 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1999-08-30","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"122957847","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 : 1999-08-30DOI: 10.1109/ICSM.1999.792646
F. Fioravanti, P. Nesi, F. Stortoni
Object oriented modeling has been largely adopted in industry in the last few years. Several systems built 4 or 5 years ago may need an adaptive maintenance process in order to better satisfy market and customer needs. A model for effort estimation/prediction of the adaptive maintenance is presented. A selection of metrics for effort estimation has been applied to the general model for evaluating maintenance effort. The metrics presented have been validated against real data. The validation presented has shown that some metrics that can be profitably employed for effort estimation/prediction can be also used with success for the estimation/prediction of the maintenance effort. Moreover the results obtained give some guidelines for maintenance of control of relevant factors for adaptive maintenance.
{"title":"Metrics for controlling effort during adaptive maintenance of object oriented systems","authors":"F. Fioravanti, P. Nesi, F. Stortoni","doi":"10.1109/ICSM.1999.792646","DOIUrl":"https://doi.org/10.1109/ICSM.1999.792646","url":null,"abstract":"Object oriented modeling has been largely adopted in industry in the last few years. Several systems built 4 or 5 years ago may need an adaptive maintenance process in order to better satisfy market and customer needs. A model for effort estimation/prediction of the adaptive maintenance is presented. A selection of metrics for effort estimation has been applied to the general model for evaluating maintenance effort. The metrics presented have been validated against real data. The validation presented has shown that some metrics that can be profitably employed for effort estimation/prediction can be also used with success for the estimation/prediction of the maintenance effort. Moreover the results obtained give some guidelines for maintenance of control of relevant factors for adaptive maintenance.","PeriodicalId":193867,"journal":{"name":"Proceedings IEEE International Conference on Software Maintenance - 1999 (ICSM'99). 'Software Maintenance for Business Change' (Cat. No.99CB36360)","volume":"6 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1999-08-30","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"126315632","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 : 1999-08-30DOI: 10.1109/ICSM.1999.792604
G. Rothermel, Roland H. Untch, Chengyun Chu, M. J. Harrold
Test case prioritization techniques schedule test cases for execution in an order that attempts to maximize some objective function. A variety of objective functions are applicable; one such function involves rate of fault detection-a measure of how quickly faults are detected within the testing process. An improved rate of fault detection during regression testing can provide faster feedback on a system under regression test and let debuggers begin their work earlier than might otherwise be possible. In this paper we describe several techniques for prioritizing test cases and report our empirical results measuring the effectiveness of these techniques for improving rate of fault detection. The results provide insights into the tradeoffs among various techniques for test case prioritization.
{"title":"Test case prioritization: an empirical study","authors":"G. Rothermel, Roland H. Untch, Chengyun Chu, M. J. Harrold","doi":"10.1109/ICSM.1999.792604","DOIUrl":"https://doi.org/10.1109/ICSM.1999.792604","url":null,"abstract":"Test case prioritization techniques schedule test cases for execution in an order that attempts to maximize some objective function. A variety of objective functions are applicable; one such function involves rate of fault detection-a measure of how quickly faults are detected within the testing process. An improved rate of fault detection during regression testing can provide faster feedback on a system under regression test and let debuggers begin their work earlier than might otherwise be possible. In this paper we describe several techniques for prioritizing test cases and report our empirical results measuring the effectiveness of these techniques for improving rate of fault detection. The results provide insights into the tradeoffs among various techniques for test case prioritization.","PeriodicalId":193867,"journal":{"name":"Proceedings IEEE International Conference on Software Maintenance - 1999 (ICSM'99). 'Software Maintenance for Business Change' (Cat. No.99CB36360)","volume":"5 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1999-08-30","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"128080123","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 : 1999-08-30DOI: 10.1109/ICSM.1999.792496
S. Rugaber
Evolving an existing software system is fundamentally different from developing one from scratch. Consequently, tools to support evolution must go beyond traditional development tools. The paper describes the Esprit de Corps Suite (EDCS) of software evolution tools. EDCS supports the mission oriented architectural legacy evolution (MORALE) software reengineering process. The paper briefly describes MORALE before presenting the individual tools and how they interoperate to support legacy system evolution.
发展一个现有的软件系统与从零开始开发一个软件系统是完全不同的。因此，支持进化的工具必须超越传统的开发工具。本文介绍了Esprit de Corps Suite (EDCS)软件开发工具。EDCS支持面向任务的架构遗留演进(士气)软件再工程过程。在介绍单个工具以及它们如何互操作以支持遗留系统演进之前，本文简要地描述了士气。
{"title":"A tool suite for evolving legacy software","authors":"S. Rugaber","doi":"10.1109/ICSM.1999.792496","DOIUrl":"https://doi.org/10.1109/ICSM.1999.792496","url":null,"abstract":"Evolving an existing software system is fundamentally different from developing one from scratch. Consequently, tools to support evolution must go beyond traditional development tools. The paper describes the Esprit de Corps Suite (EDCS) of software evolution tools. EDCS supports the mission oriented architectural legacy evolution (MORALE) software reengineering process. The paper briefly describes MORALE before presenting the individual tools and how they interoperate to support legacy system evolution.","PeriodicalId":193867,"journal":{"name":"Proceedings IEEE International Conference on Software Maintenance - 1999 (ICSM'99). 'Software Maintenance for Business Change' (Cat. No.99CB36360)","volume":"39 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1999-08-30","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"133825418","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 : 1999-08-30DOI: 10.1109/ICSM.1999.792609
I. Chung, H. Kim, Hyun-Seop Bae, Y. Kwon, Dong-Gil Lee
This paper describes a specification-based regression testing technique that can be applied for revalidating concurrent programs after specification changes. This kind of regression testing technique requires sequencing constraints which specify the precedence relations among synchronization events. In our method, the sequencing constraints are extracted automatically from Message Sequence Charts (MSCs) that are considered to be partial and nondeterministic specifications. We show how to identify the sequencing constraints affected by the modifications of a specification rather than creating new sequencing constraints from scratch to reduce the cost of regression testing. We also describe how to determine whether the affected sequencing constraints are satisfied by the program being tested.
{"title":"Testing of concurrent programs after specification changes","authors":"I. Chung, H. Kim, Hyun-Seop Bae, Y. Kwon, Dong-Gil Lee","doi":"10.1109/ICSM.1999.792609","DOIUrl":"https://doi.org/10.1109/ICSM.1999.792609","url":null,"abstract":"This paper describes a specification-based regression testing technique that can be applied for revalidating concurrent programs after specification changes. This kind of regression testing technique requires sequencing constraints which specify the precedence relations among synchronization events. In our method, the sequencing constraints are extracted automatically from Message Sequence Charts (MSCs) that are considered to be partial and nondeterministic specifications. We show how to identify the sequencing constraints affected by the modifications of a specification rather than creating new sequencing constraints from scratch to reduce the cost of regression testing. We also describe how to determine whether the affected sequencing constraints are satisfied by the program being tested.","PeriodicalId":193867,"journal":{"name":"Proceedings IEEE International Conference on Software Maintenance - 1999 (ICSM'99). 'Software Maintenance for Business Change' (Cat. No.99CB36360)","volume":"4 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1999-08-30","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"133336130","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 : 1999-08-30DOI: 10.1109/ICSM.1999.792607
Sébastien Lapierre, E. Merlo, G. Savard, G. Antoniol, R. Fiutem, P. Tonella
This paper presents an approach to automatic unit test data generation for branch coverage using mixed-integer linear programming, execution trees, and symbolic execution. This approach can be useful to both general testing and regression testing after software maintenance and reengineering activities. Several strategies, including original algorithms, to move towards practical test data generation have been investigated in this paper. Methods include: the analysis of minimum path-length partial execution trees for unconstrained arcs, thus increasing the generation performance and reducing the difficulties originated by infeasible paths the reduction of the difficulties originated by nonlinear path conditions by considering alternative linear paths the reduction of the number of test cases, which are needed to achieve the desired coverage, based on the concept of unconstrained arcs in a control flow graph the extension of symbolic execution to deal with dynamic memory allocation and deallocation, pointers and pointers to functions system. Preliminary results are encouraging and show that a high percentage of the program branches can be covered by the test data automatically produced. The approach is flexible to branch selection criteria coming from general testing as well as regression testing.
{"title":"Automatic unit test data generation using mixed-integer linear programming and execution trees","authors":"Sébastien Lapierre, E. Merlo, G. Savard, G. Antoniol, R. Fiutem, P. Tonella","doi":"10.1109/ICSM.1999.792607","DOIUrl":"https://doi.org/10.1109/ICSM.1999.792607","url":null,"abstract":"This paper presents an approach to automatic unit test data generation for branch coverage using mixed-integer linear programming, execution trees, and symbolic execution. This approach can be useful to both general testing and regression testing after software maintenance and reengineering activities. Several strategies, including original algorithms, to move towards practical test data generation have been investigated in this paper. Methods include: the analysis of minimum path-length partial execution trees for unconstrained arcs, thus increasing the generation performance and reducing the difficulties originated by infeasible paths the reduction of the difficulties originated by nonlinear path conditions by considering alternative linear paths the reduction of the number of test cases, which are needed to achieve the desired coverage, based on the concept of unconstrained arcs in a control flow graph the extension of symbolic execution to deal with dynamic memory allocation and deallocation, pointers and pointers to functions system. Preliminary results are encouraging and show that a high percentage of the program branches can be covered by the test data automatically produced. The approach is flexible to branch selection criteria coming from general testing as well as regression testing.","PeriodicalId":193867,"journal":{"name":"Proceedings IEEE International Conference on Software Maintenance - 1999 (ICSM'99). 'Software Maintenance for Business Change' (Cat. No.99CB36360)","volume":"52 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1999-08-30","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"122424084","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 : 1999-08-30DOI: 10.1109/ICSM.1999.792499
N. Schneidewind, B. Kitchenharn, F. Niessink, J. Singer, A. von Mayrhauser, Hongji Yang
The motivation for this panel and debate grew out of discussions held in Session # 2 at the Third Annual Workshop on Empirical Studies of Software Maintenance, WESS '98, Session # 1 Bethesda, Maryland, November 16, 1998 that dealt with the topic: "What are the differences between maintenance tools tools/methods/skills and those of development". This session had the following participants: A. von Mayrhauser (chair), B. A. Kitchenham, F. Niessink, N. Schneidewind, J. Singer, G. H. Travassos, S. Takada, R. Vehvilainen, and H.Yang.Subsequent to WESS, Barbara Kitchenham and Anneliese von Mayrhauser discussed the possibility of our group producing a paper on the Ontology of Maintenance. Then a technical report was published on the subject [1]. This paper is based largely on the ideas expressed in that report.
这次小组讨论和辩论的动机源于1998年11月16日在马里兰州贝塞斯达举行的第三届软件维护实证研究年度研讨会# 2会议上的讨论:“维护工具工具/方法/技能与开发工具/方法/技能之间的区别是什么”。本次会议有以下参与者:a . von mayhauser(主席)、B. a . Kitchenham、F. Niessink、N. Schneidewind、J. Singer、G. H. Travassos、S. Takada、R. Vehvilainen和H. yang。在WESS之后，Barbara Kitchenham和Anneliese von mayhauser讨论了我们小组发表一篇关于维护本体的论文的可能性。然后发表了一份关于这个主题的技术报告。这篇论文主要是根据那份报告中所表达的观点。
{"title":"Resolved: \"Software Maintenance Is Nothing More Than Another Form Of Development\"","authors":"N. Schneidewind, B. Kitchenharn, F. Niessink, J. Singer, A. von Mayrhauser, Hongji Yang","doi":"10.1109/ICSM.1999.792499","DOIUrl":"https://doi.org/10.1109/ICSM.1999.792499","url":null,"abstract":"The motivation for this panel and debate grew out of discussions held in Session # 2 at the Third Annual Workshop on Empirical Studies of Software Maintenance, WESS '98, Session # 1 Bethesda, Maryland, November 16, 1998 that dealt with the topic: \"What are the differences between maintenance tools tools/methods/skills and those of development\". This session had the following participants: A. von Mayrhauser (chair), B. A. Kitchenham, F. Niessink, N. Schneidewind, J. Singer, G. H. Travassos, S. Takada, R. Vehvilainen, and H.Yang.Subsequent to WESS, Barbara Kitchenham and Anneliese von Mayrhauser discussed the possibility of our group producing a paper on the Ontology of Maintenance. Then a technical report was published on the subject [1]. This paper is based largely on the ideas expressed in that report.","PeriodicalId":193867,"journal":{"name":"Proceedings IEEE International Conference on Software Maintenance - 1999 (ICSM'99). 'Software Maintenance for Business Change' (Cat. No.99CB36360)","volume":"1 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1999-08-30","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"131044845","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
扫码关注我们
求助内容：
应助结果提醒方式：