J. Softw. Maintenance Res. Pract.最新文献_第5页

Building infrastructure for fixing the year 2000 bug: a case study 构建用于修复2000年错误的基础设施:一个案例研究

J. Softw. Maintenance Res. Pract. Pub Date : 1998-09-01 DOI: 10.1002/(SICI)1096-908X(199809/10)10:5%3C333::AID-SMR176%3E3.0.CO;2-7

L. Marcoccia

引用次数: 4

Model-based design of reverse engineering tools 基于模型的逆向工程工具设计

J. Softw. Maintenance Res. Pract. Pub Date : 1998-09-01 DOI: 10.1002/(SICI)1096-908X(199809/10)10:5%3C353::AID-SMR178%3E3.0.CO;2-

S. Jarzabek, Guosheng Wang

{"title":"Model-based design of reverse engineering tools","authors":"S. Jarzabek, Guosheng Wang","doi":"10.1002/(SICI)1096-908X(199809/10)10:5%3C353::AID-SMR178%3E3.0.CO;2-","DOIUrl":"https://doi.org/10.1002/(SICI)1096-908X(199809/10)10:5%3C353::AID-SMR178%3E3.0.CO;2-","url":null,"abstract":"SUMMARY Tools built in an ad hoc way and without proper models often display problems for both tool users and designers. Firstly, without systematic analysis and good understanding of the underlying software process model, we have little chance to design a tool that will adequately address user’s needs. Next, because one tool is often used in many different situations and by people who have different working habits, tools should be flexible and allow a user to customise tools functionalities. Ad hoc built tools usually are not flexible enough, as possible variations in tool functions had not been incorporated into the tool architecture to make future customisations possible. Finally, ad hoc design practice does not lead to accumulating the tool design know-how, makes it difficult to repeat successful solutions and slows down the process of understanding and improving tool design methods. We applied conceptual modelling in design of tools for software maintenance to alleviate some of the above problems. In this paper, we describe a model-based method to designing reverse engineering tools. The design starts by modelling low level source program design models, higher level design models to be recovered and heuristic rules a reverse engineering tool uses to recover higher level designs from lower level designs. On one hand, conceptual models lead to better understanding of tool requirements. On the other hand, model-based approach leads to the design of a generic design abstractor, a component of a reverse engineering tool that evaluates reverse engineering heuristics. A generic design abstractor adds flexibility to reverse engineering tools in two ways: (1) we can customise the generic design abstractor to meet requirements of a reverse engineering project in hand and (2) a programmer (an end-user of a reverse engineering tool) can define new reverse engineering heuristics and tune in recovered designs.","PeriodicalId":383619,"journal":{"name":"J. Softw. Maintenance Res. Pract.","volume":"103 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1998-09-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"124623693","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}

引用次数: 11

An evaluation of reverse engineering tool capabilities 对逆向工程工具能力的评估

J. Softw. Maintenance Res. Pract. Pub Date : 1998-09-01 DOI: 10.1002/(SICI)1096-908X(199809/10)10:5%3C305::AID-SMR175%3E3.0.CO;2-7

Berndt Bellay, H. Gall

引用次数: 45

Incremental delivery reduces maintenance cost: a COCOMO-based study 增量交付减少维护成本:基于cocomo的研究

J. Softw. Maintenance Res. Pract. Pub Date : 1998-07-01 DOI: 10.1002/(SICI)1096-908X(199807/08)10:4%3C225::AID-SMR170%3E3.0.CO;2-R

P. Hsia, Chih-Tung Hsu, D. Kung, E. J. Byrne

引用次数: 1

Q-MOPP: qualitative evaluation of maintenance organizations, processes and products Q-MOPP:对维修组织、过程和产品进行定性评价

J. Softw. Maintenance Res. Pract. Pub Date : 1998-07-01 DOI: 10.1002/(SICI)1096-908X(199807/08)10:4%3C249::AID-SMR172%3E3.0.CO;2-7

L. Briand, Yong-Mi Kim, W. Melo, C. Seaman, V. Basili

引用次数: 18

An incremental approach to software systems re-engineering 软件系统再工程的增量方法

J. Softw. Maintenance Res. Pract. Pub Date : 1998-05-01 DOI: 10.1002/(SICI)1096-908X(199805/06)10:3%3C181::AID-SMR171%3E3.0.CO;2-7

Michael R. Olsem

{"title":"An incremental approach to software systems re-engineering","authors":"Michael R. Olsem","doi":"10.1002/(SICI)1096-908X(199805/06)10:3%3C181::AID-SMR171%3E3.0.CO;2-7","DOIUrl":"https://doi.org/10.1002/(SICI)1096-908X(199805/06)10:3%3C181::AID-SMR171%3E3.0.CO;2-7","url":null,"abstract":"Software re-engineering can dramatically improve an organization's ability to maintain and upgrade its legacy production systems. But the risks that accompany traditional re-engineering tend to offset the potential benefits. \u0000 \u0000 \u0000 \u0000Incremental software re-engineering is the practice of re-engineering a system's software components on a phased basis, and then re-incorporating those components into production also on a phased basis. Incremental software re-engineering allows for safer re-engineering, increased flexibility and more immediate return on investment. But commercial automation to support incremental software re-engineering is currently weak. In addition, project managers need a methodology to plan and implement software re-engineering projects based on the incremental approach. \u0000 \u0000 \u0000 \u0000This paper covers the advantages of incremental software re-engineering and what is available concerning support technology. The paper describes a process methodology for planning and implementing incremental software re-engineering projects. Finally, gaps in the support technology are identified with suggestions for future tools from vendors. © 1998 John Wiley & Sons, Ltd.","PeriodicalId":383619,"journal":{"name":"J. Softw. Maintenance Res. Pract.","volume":"141 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1998-05-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"132538283","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}

引用次数: 25

Framework for tool evaluation for a maintenance environment 维护环境的工具评估框架

J. Softw. Maintenance Res. Pract. Pub Date : 1998-05-01 DOI: 10.1002/(SICI)1096-908X(199805/06)10:3%3C203::AID-SMR173%3E3.0.CO;2-0

M. Vierimaa, J. Taramaa, Heli Puustinen, Kati Suominen, Tommi Ketola

{"title":"Framework for tool evaluation for a maintenance environment","authors":"M. Vierimaa, J. Taramaa, Heli Puustinen, Kati Suominen, Tommi Ketola","doi":"10.1002/(SICI)1096-908X(199805/06)10:3%3C203::AID-SMR173%3E3.0.CO;2-0","DOIUrl":"https://doi.org/10.1002/(SICI)1096-908X(199805/06)10:3%3C203::AID-SMR173%3E3.0.CO;2-0","url":null,"abstract":"Tool evaluation forms an essential part of tool development. Unfortunately, there are only a few solutions for this activity. As part of the AMES project, tool evaluation was implemented as part of a more comprehensive framework, used with the development and application of several AMES tools for application maintenance. These included an application understanding tool-set, a disabbreviation tool, a reverse-engineering tool and an impact analysis tool-set. In addition, the requirement for applicability both to on-board space software and to tool software has directed our approach in setting requirements for tools evaluation. The central element of the evaluation process was an AMES-developed framework including evaluation criteria and the use of a goal/question/metrics (GQM) based approach. The criteria have produced detailed information about each tool. The final result can be regarded as a combination of the score for each criterion and explicit metrics data. In addition, descriptive information about applications was used in tool evaluation.  1998 John Wiley & Sons, Ltd.","PeriodicalId":383619,"journal":{"name":"J. Softw. Maintenance Res. Pract.","volume":"7 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1998-05-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"126196081","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}

引用次数: 2

Little languages: little maintenance? 小语言:小维护?

J. Softw. Maintenance Res. Pract. Pub Date : 1998-03-01 DOI: 10.1002/(SICI)1096-908X(199803/04)10:2%3C75::AID-SMR168%3E3.0.CO;2-5

A. Deursen, P. Klint

引用次数: 303

Using application understanding to support impact analysis 使用应用程序理解来支持影响分析

J. Softw. Maintenance Res. Pract. Pub Date : 1998-03-01 DOI: 10.1002/(SICI)1096-908X(199803/04)10:2%3C93::AID-SMR169%3E3.0.CO;2-6

M. Joanna Fyson, C. Boldyreff

{"title":"Using application understanding to support impact analysis","authors":"M. Joanna Fyson, C. Boldyreff","doi":"10.1002/(SICI)1096-908X(199803/04)10:2%3C93::AID-SMR169%3E3.0.CO;2-6","DOIUrl":"https://doi.org/10.1002/(SICI)1096-908X(199803/04)10:2%3C93::AID-SMR169%3E3.0.CO;2-6","url":null,"abstract":"Any change to one component of a software system is likely to be felt in other components, a phenomenon known as ‘ripple effect’. Impact analysis is the process of identifying all those components of a system which may be affected by ripple effect. This requires a knowledge of the dependencies between components. \u0000 \u0000 \u0000 \u0000A software system consists not only of the source code, but also of all life cycle work products including requirements, design and test documents. Any of these components may be the subject of a change request, and should therefore be included in impact analysis. \u0000 \u0000 \u0000 \u0000The ripple propagation graph (RPG) for impact analysis, developed as part of the AMES (Application Management Environments and Support) project, models an application in such a way that dependencies can be traced in order to identify all affected components. It is an object-relationship model consisting of the components of a system at some level of granularity, and the various relationships between them. \u0000 \u0000 \u0000 \u0000This paper describes the AMES RPG, and how the results of the application understanding (AU) toolset, developed (again as part of the AMES project) to support the process of gaining an understanding of an application, can be used to provide some of the data required to populate the RPG. © 1998 John Wiley & Sons, Ltd.","PeriodicalId":383619,"journal":{"name":"J. Softw. Maintenance Res. Pract.","volume":"1 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1998-03-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"131102986","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}

引用次数: 33

Software maintenance management strategies: observations from the field 软件维护管理策略:从现场观察

J. Softw. Maintenance Res. Pract. Pub Date : 1997-11-01 DOI: 10.1002/(SICI)1096-908X(199711/12)9:6%3C365::AID-SMR160%3E3.0.CO;2-J

G. Stark, P. Oman

{"title":"Software maintenance management strategies: observations from the field","authors":"G. Stark, P. Oman","doi":"10.1002/(SICI)1096-908X(199711/12)9:6%3C365::AID-SMR160%3E3.0.CO;2-J","DOIUrl":"https://doi.org/10.1002/(SICI)1096-908X(199711/12)9:6%3C365::AID-SMR160%3E3.0.CO;2-J","url":null,"abstract":"There is much literature describing software maintenance process models, but few comparative studies on the approaches used by managers in the field. This paper describes three software maintenance management strategies currently implemented by six organizations. The strategies are compared on the attributes of performance, economics, efficiency and end-product quality. The paper defines operational measurements for each attribute and describes the data collected over the past two years. \u0000 \u0000 \u0000 \u0000The three strategies investigated were labelled the fixed staff/variable schedule, variable staff/fixed schedule and the variable staff/variable schedule. Each strategy has attributes that make it appealing for implementation by a software maintenance project manager. The fixed staff/variable schedule strategy had the fastest priority change response time, the variable staff/fixed schedule strategy had the highest throughput and the best on-schedule performance, and the variable staff/variable schedule had the lowest cost and highest quality. Thus, the key task for a manager is defining the attribute that they would most like to optimize and choosing a strategy that supports that goal. © 1997 John Wiley & Sons, Ltd.","PeriodicalId":383619,"journal":{"name":"J. Softw. Maintenance Res. Pract.","volume":"45 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1997-11-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"125168629","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}

引用次数: 13