International Conference on Software Maintenance, 2003. ICSM 2003. Proceedings.最新文献_第3页

Mining the maintenance history of a legacy software system 挖掘遗留软件系统的维护历史

International Conference on Software Maintenance, 2003. ICSM 2003. Proceedings. Pub Date : 2003-09-22 DOI: 10.1109/ICSM.2003.1235410

J. Sayyad-Shirabad, T. Lethbridge, S. Matwin

引用次数: 72

A classification of unanticipated runtime software changes in Java 对Java中未预期的运行时软件更改的分类

International Conference on Software Maintenance, 2003. ICSM 2003. Proceedings. Pub Date : 2003-09-22 DOI: 10.1109/ICSM.2003.1235401

Jens Gustavsson

引用次数: 21

Source code based function point analysis for enhancement projects 源代码基于功能点分析的增强项目

International Conference on Software Maintenance, 2003. ICSM 2003. Proceedings. Pub Date : 2003-09-22 DOI: 10.1109/ICSM.2003.1235445

A. S. Klusener

引用次数: 8

Evolution of a software maintenance organization from cost center to service center 软件维护组织从成本中心到服务中心的演变

International Conference on Software Maintenance, 2003. ICSM 2003. Proceedings. Pub Date : 2003-09-22 DOI: 10.1109/ICSM.2003.1235423

S. Smit, P. D. With, G. V. Dijk

引用次数: 2

Software systems integration and architectural analysis - a case study 软件系统集成和架构分析-一个案例研究

International Conference on Software Maintenance, 2003. ICSM 2003. Proceedings. Pub Date : 2003-09-22 DOI: 10.1109/ICSM.2003.1235441

R. Land, I. Crnkovic

{"title":"Software systems integration and architectural analysis - a case study","authors":"R. Land, I. Crnkovic","doi":"10.1109/ICSM.2003.1235441","DOIUrl":"https://doi.org/10.1109/ICSM.2003.1235441","url":null,"abstract":"Software systems no longer evolve as separate entities but are also integrated with each other. The purpose of integrating software systems can be to increase user-value or to decrease maintenance costs. Different approaches, one of which is software architectural analysis, can be used in the process of integration planning and design. This paper presents a case study in which three software systems were to be integrated. We show how architectural reasoning was used to design and compare integration alternatives. In particular, four different levels of the integration were discussed (interoperation, a so-called enterprise application integration, an integration based on a common data model, and a full integration). We also show how cost, time to delivery and maintainability of the integrated solution were estimated. On the basis of the case study, we analyze the advantages and limits of the architectural approach as such and conclude by outlining directions for future research: how to incorporate analysis of cost; time to delivery; and risk in architectural analysis, and how to make architectural analysis more suitable for comparing many aspects of many alternatives during development. Finally we outline the limitations of architectural analysis.","PeriodicalId":141256,"journal":{"name":"International Conference on Software Maintenance, 2003. ICSM 2003. Proceedings.","volume":"9 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2003-09-22","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"129655196","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}

引用次数: 35

Impact analysis and change management of UML models UML模型的影响分析和变更管理

International Conference on Software Maintenance, 2003. ICSM 2003. Proceedings. Pub Date : 2003-09-22 DOI: 10.1109/ICSM.2003.1235428

L. Briand, Y. Labiche, Leeshawn O'Sullivan

{"title":"Impact analysis and change management of UML models","authors":"L. Briand, Y. Labiche, Leeshawn O'Sullivan","doi":"10.1109/ICSM.2003.1235428","DOIUrl":"https://doi.org/10.1109/ICSM.2003.1235428","url":null,"abstract":"The use of Unified Modeling Language (UML) analysis/design models on large projects leads to a large number of interdependent UML diagrams. As software systems evolve, those diagrams undergo changes to, for instance, correct errors or address changes in the requirements. Those changes can in turn lead to subsequent changes to other elements in the UML diagrams. Impact analysis is then defined as the process of identifying the potential consequences (side-effects) of a change, and estimating what needs to be modified to accomplish a change. In this article, we propose a UML model-based approach to impact analysis that can be applied before any implementation of the changes, thus allowing an early decision-making and change planning process. We first verify that the UML diagrams are consistent (consistency check). Then changes between two different versions of a UML model are identified according to a change taxonomy, and model elements that are directly or indirectly impacted by those changes (i.e., may undergo changes) are determined using formally defined impact analysis rules (written with Object Constraint Language). A measure of distance between a changed element and potentially impacted elements is also proposed to prioritize the results of impact analysis according to their likelihood of occurrence. We also present a prototype tool that provides automated support for our impact analysis strategy, that we then apply on a case study to validate both the implementation and methodology.","PeriodicalId":141256,"journal":{"name":"International Conference on Software Maintenance, 2003. ICSM 2003. Proceedings.","volume":"77 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2003-09-22","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"129762844","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}

引用次数: 212

Deriving tolerant grammars from a base-line grammar 从基线语法派生出容错语法

International Conference on Software Maintenance, 2003. ICSM 2003. Proceedings. Pub Date : 2003-09-22 DOI: 10.1109/ICSM.2003.1235420

Steven Klusener, R. Lämmel

{"title":"Deriving tolerant grammars from a base-line grammar","authors":"Steven Klusener, R. Lämmel","doi":"10.1109/ICSM.2003.1235420","DOIUrl":"https://doi.org/10.1109/ICSM.2003.1235420","url":null,"abstract":"A grammar-based approach to tool development in reengineering and reverse engineering promises precise structure awareness, but it is problematic in two respects. Firstly, it is a considerable up-front investment to obtain a grammar for a relevant language or cocktail of languages. Existing work on grammar recovery addresses this concern to some extent. Secondly, it is often not feasible to insist on a precise grammar, e.g., when different dialects need to be covered. This calls for tolerant grammars. In this paper, we provide a well-engineered approach to the derivation of tolerant grammars, which is based on previous work on error recovery, fuzzy parsing, and island grammars. The technology of this paper has been used in a complex Cobol restructuring project on several millions of lines of code in different Cobol dialects. Our approach is founded on an approximation relation between a tolerant grammar and a base-line grammar which serves as a point of reference. Thereby, we avoid false positives and false negatives when parsing constructs of interest in a tolerant mode. Our approach accomplishes the effective derivation of a tolerant grammar from the syntactical structure that is relevant for a certain re- or reverse engineering tool. To this end, the productions for the constructs of interest are reused from the base-line grammar together with further productions that are needed for completion.","PeriodicalId":141256,"journal":{"name":"International Conference on Software Maintenance, 2003. ICSM 2003. Proceedings.","volume":"72 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2003-09-22","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"126303891","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}

引用次数: 44

Measuring software sustainability 衡量软件可持续性

International Conference on Software Maintenance, 2003. ICSM 2003. Proceedings. Pub Date : 2003-09-22 DOI: 10.1109/ICSM.2003.1235455

R. Seacord, J. Elm, Wolfhart B. Goethert, G. Lewis, Daniel Plakosh, John E. Robert, L. Wrage, M. Lindvall

引用次数: 41

Experience in developing interoperations among legacy information systems using partial reverse engineering 有使用部分逆向工程开发遗留信息系统间互操作的经验

International Conference on Software Maintenance, 2003. ICSM 2003. Proceedings. Pub Date : 2003-09-22 DOI: 10.1109/ICSM.2003.1235444

Michael Johnson, C. Dampney

{"title":"Experience in developing interoperations among legacy information systems using partial reverse engineering","authors":"Michael Johnson, C. Dampney","doi":"10.1109/ICSM.2003.1235444","DOIUrl":"https://doi.org/10.1109/ICSM.2003.1235444","url":null,"abstract":"At ICSM01 Johnson and Rosebrugh proposed a new methodology, based on formal specification techniques and partial reverse engineering, for developing interoperations among legacy information systems. The present brief paper reports on progress to date in designing such interoperations for major health informatics information systems. We describe briefly the methodology, argue for the value of partial reverse engineering and the benefits of the formal specification approach (based on category theory) that we use, and evaluate the methodology in two case studies. The main new result is the following. The ICSM01 paper correctly predicted that what was called there \"full-duplex interoperation\" would often provide more interoperability than is in fact required. We have discovered that the provision of full-duplex interoperability is indeed usually unnecessary, and it is costly because of the need to modify the legacy system. We proposed the development of \"half-duplex interoperation\" to avoid these costs, and we have since developed the half-duplex techniques. Nevertheless, the half-duplex techniques can still require some legacy system modification. Following recent work on partial information, we are developing an extension to the view based interoperation technique that avoids legacy system modification in over 92% of the cases we have investigated.","PeriodicalId":141256,"journal":{"name":"International Conference on Software Maintenance, 2003. ICSM 2003. Proceedings.","volume":"43 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2003-09-22","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"121601168","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}

引用次数: 1

Making maximum use of legacy code: Transavia Internet booking engine 最大限度地利用遗留代码:Transavia互联网预订引擎

International Conference on Software Maintenance, 2003. ICSM 2003. Proceedings. Pub Date : 2003-09-22 DOI: 10.1109/ICSM.2003.1235460

Cees Mul

引用次数: 0