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

Using risk analysis to manage software maintenance 使用风险分析来管理软件维护

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

S. Sherer

引用次数: 23

A quantitative comparison of perfective and corrective software maintenance 对完美的和正确的软件维护进行定量比较

J. Softw. Maintenance Res. Pract. Pub Date : 1997-09-01 DOI: 10.1002/(SICI)1096-908X(199709/10)9:5%3C281::AID-SMR154%3E3.0.CO;2-P

J. Henry, James P. Cain

引用次数: 25

Program understanding behaviour during enhancement of large-scale software 大型软件增强过程中的程序理解行为

J. Softw. Maintenance Res. Pract. Pub Date : 1997-09-01 DOI: 10.1002/(SICI)1096-908X(199709/10)9:5%3C299::AID-SMR157%3E3.0.CO;2-S

A. V. Mayrhauser, M. Vans, A. Howe

{"title":"Program understanding behaviour during enhancement of large-scale software","authors":"A. V. Mayrhauser, M. Vans, A. Howe","doi":"10.1002/(SICI)1096-908X(199709/10)9:5%3C299::AID-SMR157%3E3.0.CO;2-S","DOIUrl":"https://doi.org/10.1002/(SICI)1096-908X(199709/10)9:5%3C299::AID-SMR157%3E3.0.CO;2-S","url":null,"abstract":"This paper reports on a software understanding field study during the enhancement of large-scale software. The participants were professional software maintenance personnel from industry. The paper reports on the general understanding process, the kinds of actions programmers preferred during the enhancement task, the level of abstraction at which they were working, and role of hypotheses in the enhancement strategies they used. The results of the observations are also interpreted in terms of the information needs of these personnel during the enhancement task. We found that programmers work predominantly at the code and algorithmic levels with differences depending on the stage of the enhancement. They frequently switch between levels of abstraction. The programmers' main concerns are with what software does and how this is accomplished, not why software was built a certain way. These questions guide the work process. There was strong indication that memory (over)load is an issue. This is, of course, related to the size of the software. Information is sought and cross-referenced from a variety of sources from application domain concepts to code-related information, outpacing current maintenance environments' capabilities which are mostly stratified by information sources, making cross-referencing difficult. © 1997 John Wiley & Sons, Ltd.","PeriodicalId":383619,"journal":{"name":"J. Softw. Maintenance Res. Pract.","volume":"60 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1997-09-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"114918733","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}

引用次数: 96

Software licensing models amid market turbulence 市场动荡中的软件许可模式

J. Softw. Maintenance Res. Pract. Pub Date : 1997-09-01 DOI: 10.1002/(SICI)1096-908X(199709/10)9:5%3C271::AID-SMR158%3E3.0.CO;2-E

C. Wendt, N. Imparato

引用次数: 2

Using COBOL defensive traps 使用COBOL防御陷阱

J. Softw. Maintenance Res. Pract. Pub Date : 1997-09-01 DOI: 10.1002/(SICI)1096-908X(199709/10)9:5%3C329::AID-SMR156%3E3.0.CO;2-Z

Eric Garrigue Vesely

引用次数: 0

Determinants of software maintenance profiles: an empirical investigation 软件维护概要的决定因素:一项实证调查

J. Softw. Maintenance Res. Pract. Pub Date : 1997-07-01 DOI: 10.1002/(SICI)1096-908X(199707/08)9:4%3C235::AID-SMR153%3E3.0.CO;2-3

C. Kemerer, S. Slaughter

{"title":"Determinants of software maintenance profiles: an empirical investigation","authors":"C. Kemerer, S. Slaughter","doi":"10.1002/(SICI)1096-908X(199707/08)9:4%3C235::AID-SMR153%3E3.0.CO;2-3","DOIUrl":"https://doi.org/10.1002/(SICI)1096-908X(199707/08)9:4%3C235::AID-SMR153%3E3.0.CO;2-3","url":null,"abstract":"Software maintenance is a task that is difficult to manage effectively. In part, this is because software managers have very little knowledge about the types of maintenance work that are likely to occur. If managers could forecast changes to software systems, they could more effectively plan, allocate workforce and manage change requests. But, the ability to forecast software modifications depends on whether there are predictable patterns in maintenance work. We posit that there are patterns in maintenance work and that certain characteristics of software modules are associated with these patterns. \u0000 \u0000We examine modification profiles for 621 software modules in five different business systems of a commercial merchandiser. We find that only a small number of modules in these systems is likely to be modified frequently, and that certain maintenance patterns emerge. Modules frequently enhanced are in systems whose functionality is considered strategic. Modules frequently repaired have high software complexity, are large in size, and are relatively older. However, modules that have been code generated are less likely to be repaired. Older and larger modules are restructured and upgraded more frequently. Our results suggest that these characteristics of software modules are associated with predictable maintenance profiles. Such profile information can be used by software managers to predict and plan for maintenance more effectively. In addition, our results suggest the use of code generators as a means of reducing repair maintenance. © 1997 John Wiley & Sons, Ltd.","PeriodicalId":383619,"journal":{"name":"J. Softw. Maintenance Res. Pract.","volume":"33 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1997-07-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"125109147","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}

引用次数: 82

Maintenance of COTS-intensive software systems 维护cots密集型软件系统

J. Softw. Maintenance Res. Pract. Pub Date : 1997-07-01 DOI: 10.1002/(SICI)1096-908X(199707/08)9:4%3C203::AID-SMR155%3E3.0.CO;2-6

D. Hybertson, Anh D. Ta, William M. Thomas

引用次数: 18

Interview with Takashi Sano

J. Softw. Maintenance Res. Pract. Pub Date : 1997-07-01 DOI: 10.1002/(SICI)1096-908X(199707/08)9:4%3C253::AID-SMR151%3E3.0.CO;2-D

T. Sano, W. Tsai, Sanjai Rayadurgam

引用次数: 2

A technique for the selective revalidation of OO software 一种面向对象软件选择性重新验证的技术

J. Softw. Maintenance Res. Pract. Pub Date : 1997-07-01 DOI: 10.1002/(SICI)1096-908X(199707/08)9:4%3C217::AID-SMR152%3E3.0.CO;2-2

P. Hsia, Xiaolin Li, D. Kung, Chih-Tung Hsu, Liang Li, Y. Toyoshima, Cris Chen

{"title":"A technique for the selective revalidation of OO software","authors":"P. Hsia, Xiaolin Li, D. Kung, Chih-Tung Hsu, Liang Li, Y. Toyoshima, Cris Chen","doi":"10.1002/(SICI)1096-908X(199707/08)9:4%3C217::AID-SMR152%3E3.0.CO;2-2","DOIUrl":"https://doi.org/10.1002/(SICI)1096-908X(199707/08)9:4%3C217::AID-SMR152%3E3.0.CO;2-2","url":null,"abstract":"The object-orientated paradigm provides the power for software development but at the same time introduces some brand new problems. One of these problems is that the relationships among classes are more complex and difficult to identify than those in the traditional paradigm. This problem becomes a major obstacle for regression testing of OO software, in which the relationships among classes as well as those between test cases and classes, must be determined a priori. In this paper we propose a new method to select only a fraction of the test cases from the entire test suite to revalidate an OO software system. This method is based on the concepts of class firewall and of marking all the classes ‘touched’ by a test case. From the class firewall, we can identify all of the affected classes after a new version of software is released. Together with the markings, we can also identify all the test cases in the test suite that need to be retested after the software change. A step-by-step process is proposed to identify the relationships between classes and test cases, compute the class firewall, and select only the appropriate test cases for retesting. © 1997 John Wiley & Sons, Ltd.","PeriodicalId":383619,"journal":{"name":"J. Softw. Maintenance Res. Pract.","volume":"21 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1997-07-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"131532540","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}

引用次数: 69

Development and Application of an Automated Source Code Maintainability Index 一个自动源代码可维护性索引的开发与应用

J. Softw. Maintenance Res. Pract. Pub Date : 1997-05-01 DOI: 10.1002/(SICI)1096-908X(199705)9:3%3C127::AID-SMR149%3E3.0.CO;2-S

Kurt D. Welker, P. Oman, Gerald Atkinson

{"title":"Development and Application of an Automated Source Code Maintainability Index","authors":"Kurt D. Welker, P. Oman, Gerald Atkinson","doi":"10.1002/(SICI)1096-908X(199705)9:3%3C127::AID-SMR149%3E3.0.CO;2-S","DOIUrl":"https://doi.org/10.1002/(SICI)1096-908X(199705)9:3%3C127::AID-SMR149%3E3.0.CO;2-S","url":null,"abstract":"When software maintenance results in changing the source code, the change frequently occurs in an undisciplined manner that results in source code that is inherently more difficult to maintain. The long-term effect may be thought of as a downward spiral that culminates in virtually ‘unmaintainable’ code where it is more cost effective to just start again. Too often, software personnel and managers, aware that the code is becoming less maintainable, have been unable to estimate with useful accuracy the degree to which maintainability has diminished. The result is that they either continue to waste time and money maintaining code which is effectively unmaintainable, or they opt to live with what seems to be bad code, not touching it for fear of breaking it. To avoid this state of affairs, software developers need to be able to quanitify both the current level of software maintainability and the impact on it of any given change. \u0000 \u0000 \u0000 \u0000This paper discusses the application of software metrics as a tool for quantifying code maintainability and, by extension, for making decisions. The first part of the discussion focuses on deriving a minimal set of easily calculated metrics which, when taken together, can produce a single-valued quantification (or index) of code maintainability. Case studies are then presented which serve to illustrate not only the degree to which software can degrade over time, but how this ‘maintainability index’ (MI) can be used to quantify maintainability and aid decision making. Finally, a methodology for making metric assessments readily available to software personnel is presented so that they can now easily integrate maintainability metrics into maintenance (and development) processes. As a result, the downward spiral of code degradation becomes at least recognizable, hopefully less precipitous, and perhaps avoidable entirely. © 1997 by John Wiley & Sons, Ltd.","PeriodicalId":383619,"journal":{"name":"J. Softw. Maintenance Res. Pract.","volume":"59 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1997-05-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"127856847","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}

引用次数: 85