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

A Software Tool for Maintaining File and Macro Build Dependencies 用于维护文件和宏构建依赖关系的软件工具

J. Softw. Maintenance Res. Pract. Pub Date : 1996-12-01 DOI: 10.1002/(SICI)1096-908X(199611)8:6%3C421::AID-SMR140%3E3.0.CO;2-Z

J. Buffenbarger

{"title":"A Software Tool for Maintaining File and Macro Build Dependencies","authors":"J. Buffenbarger","doi":"10.1002/(SICI)1096-908X(199611)8:6%3C421::AID-SMR140%3E3.0.CO;2-Z","DOIUrl":"https://doi.org/10.1002/(SICI)1096-908X(199611)8:6%3C421::AID-SMR140%3E3.0.CO;2-Z","url":null,"abstract":"Translating each of a UNIX software system's source files into an object file, and linking the object files into an executable file, can be a time-consuming process. Object file generation accounts for most of this time. Tools that recognize and avoid unnecessary object file regeneration are very popular. Many such tools are named MAKE. \u0000 \u0000 \u0000 \u0000A software system often contains a parameter file. A parameter file is a source file, textually included by every other source file, which defines macros shared by multiple source files. Each object file depends on the parameter file, according to file dependencies. MAKE-like tools only understand file dependencies. So, when a software developer changes a macro in a parameter file, every object file is regenerated, regardless of whether its corresponding source file actually refers to the changed macro. \u0000 \u0000 \u0000 \u0000Unnecessary object file regeneration can be avoided by replacing some file dependencies with macro dependencies, which express that an object file depends on a macro. \u0000 \u0000 \u0000 \u0000DEP is a tool implementing a method for automatically detecting and maintaining a software system's file and macro dependencies. DEP works with any flavour of MAKE to minimize the cost of rebuilding an executable file.","PeriodicalId":383619,"journal":{"name":"J. Softw. Maintenance Res. Pract.","volume":"23 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1996-12-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"127595360","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

Methodologies and Software Maintenance 方法和软件维护

J. Softw. Maintenance Res. Pract. Pub Date : 1996-09-15 DOI: 10.1002/(SICI)1096-908X(199609)8:5%3C295::AID-SMR138%3E3.0.CO;2-G

M. Taylor, T. Wood-Harper

引用次数: 9

Methods of Measuring Software Reuse for the Prediction of Maintenance Effort 用于预测维护工作的软件重用度量方法

J. Softw. Maintenance Res. Pract. Pub Date : 1996-09-15 DOI: 10.1002/(SICI)1096-908X(199609)8:5%3C309::AID-SMR136%3E3.0.CO;2-G

R. Leach

{"title":"Methods of Measuring Software Reuse for the Prediction of Maintenance Effort","authors":"R. Leach","doi":"10.1002/(SICI)1096-908X(199609)8:5%3C309::AID-SMR136%3E3.0.CO;2-G","DOIUrl":"https://doi.org/10.1002/(SICI)1096-908X(199609)8:5%3C309::AID-SMR136%3E3.0.CO;2-G","url":null,"abstract":"A major difficulty in evaluating the costs of reusing software is determining the amount of reused software artefacts in systems. Determining the amount of reuse in a system is important for software maintenance because reused software is likely to need less corrective maintenance than newly developed software. Reusing software can also decrease costs of testing and integration. In this paper, we describe some practical techniques for measuring the amount of software reuse using simple tools. The goal is to provide accurate assessment of the state of existing software systems in order to assess quality and deploy resources efficiently. The techniques for software developed on the UNIX system use the standard utilities ‘find’ and ‘diff’. Software developed under configuration management by the ‘sccs’ utility is measured using the ‘prs’ utility. Techniques are also given for measurement of the amount of reuse in software that was developed on personal computers. Each of the methods was used for reuse measurement at NASA’s Goddard Space Flight Center. The methods were applied to measure reuse in moderately large software systems used for ground centre control of spacecraft.","PeriodicalId":383619,"journal":{"name":"J. Softw. Maintenance Res. Pract.","volume":"30 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1996-09-15","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"115888120","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

A Risk Index for Software Producers 软件生产者的风险指数

J. Softw. Maintenance Res. Pract. Pub Date : 1996-09-15 DOI: 10.1002/(SICI)1096-908X(199609)8:5%3C281::AID-SMR137%3E3.0.CO;2-W

H. Leung

{"title":"A Risk Index for Software Producers","authors":"H. Leung","doi":"10.1002/(SICI)1096-908X(199609)8:5%3C281::AID-SMR137%3E3.0.CO;2-W","DOIUrl":"https://doi.org/10.1002/(SICI)1096-908X(199609)8:5%3C281::AID-SMR137%3E3.0.CO;2-W","url":null,"abstract":"Software risk management has been receiving increasing attention lately. A key activity of software risk management is the quantification of the risk of using a software product. Previous attempts to define the risk index have taken the users' viewpoint. The loss due to a product failure is computed based on its impact on the users. Yet, the impact of a failure on the software producer is different from that of the users. A high risk module according to the users may not be treated the same by the producer. This paper presents a method to determine the producer risk index for quantifying the probability and impact of failure on the producer at the product release time. The producer can use the results to determine whether it is more economical to improve the software quality or to release the product with the achieved quality level. The index can also be used to estimate the maintenance effort. The approach makes use of two recent developments in software complexity metrics, principal component analysis and reliability growth modelling. A new classification scheme for failure impact is introduced. Results from applying the producer risk index to a telecommunication software system are presented.","PeriodicalId":383619,"journal":{"name":"J. Softw. Maintenance Res. Pract.","volume":"62 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1996-09-15","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"125065222","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}

引用次数: 4

Improving the Maintainability of Software 提高软件的可维护性

J. Softw. Maintenance Res. Pract. Pub Date : 1996-09-01 DOI: 10.1002/(SICI)1096-908X(199609)8:5%3C345::AID-SMR134%3E3.0.CO;2-U

Richard West

{"title":"Improving the Maintainability of Software","authors":"Richard West","doi":"10.1002/(SICI)1096-908X(199609)8:5%3C345::AID-SMR134%3E3.0.CO;2-U","DOIUrl":"https://doi.org/10.1002/(SICI)1096-908X(199609)8:5%3C345::AID-SMR134%3E3.0.CO;2-U","url":null,"abstract":"The monograph, Improving the Maintainability of Software, has the objective of providing practical guidance on the maintainability of software: maintainability definitions, factors, building and improvement suggestions, and an assessment method. \u0000 \u0000 \u0000 \u0000The first part of this review provides an introduction to the monograph and discusses the general software maintainability guidance it provides. The second part provides a more in-depth review of the maintainability assessment method. \u0000 \u0000 \u0000 \u0000This monograph is easy to read and understand. The guidance provided appeals to common sense and reflects an understanding of many software maintenance concerns. Although the scope of the monograph is primarily business information systems, the guidance is basically sound for many other types of applications in business, industry, government and military organizations. The defined framework of maintainability factors, features, and measures provides interesting guidance for discovering potential areas of concern. Identifying these areas of concern can be a basis for directing action and resources to the more critical maintenance activities. The maintainability assessment method provided by this monograph is not adequately supported by references or detailed information. \u0000 \u0000 \u0000 \u0000Definitely read this monograph for its practical guidance. But be careful when applying the maintainability assessment method and analysing the results.","PeriodicalId":383619,"journal":{"name":"J. Softw. Maintenance Res. Pract.","volume":"61 6 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1996-09-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"116429811","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}

引用次数: 4

The GUMP Process for Software Maintenance and Maintenance Education GUMP软件维护过程与维护教育

J. Softw. Maintenance Res. Pract. Pub Date : 1996-08-01 DOI: 10.1002/(SICI)1096-908X(199607)8:4%3C229::AID-SMR130%3E3.0.CO;2-7

N. Wilde, Scott M. Brown

{"title":"The GUMP Process for Software Maintenance and Maintenance Education","authors":"N. Wilde, Scott M. Brown","doi":"10.1002/(SICI)1096-908X(199607)8:4%3C229::AID-SMR130%3E3.0.CO;2-7","DOIUrl":"https://doi.org/10.1002/(SICI)1096-908X(199607)8:4%3C229::AID-SMR130%3E3.0.CO;2-7","url":null,"abstract":"Software producing organizations attempt to improve their cost, schedule and quality performance by defining an organizational software process model. Educators try to teach their students the virtues of following such a process in software development and maintenance. But most software process models are proprietary so there are few readily available examples to help guide these efforts. \u0000 \u0000 \u0000 \u0000This paper outlines the ‘Generic University of West Florida Maintenance Process (GUMP)’ which has been developed, used and refined over a period of almost two years in an educational setting. It describes the key maintenance process issues identified in this experience and the rationale for the solutions adopted in GUMP. As an academic tool, GUMP has greatly improved the learning experience in our project courses; two of our graduates have taken it as a starting point for developing a process for their employers. \u0000 \u0000 \u0000 \u0000Full documentation for GUMP is publicly available on-line and may be copied and adapted as needed. GUMP is presented not as a ‘perfect’ process, but simply as a starting point that may be useful to either maintainers or educators as a point of reference for software process concepts.","PeriodicalId":383619,"journal":{"name":"J. Softw. Maintenance Res. Pract.","volume":"8 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1996-08-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"131378902","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}

引用次数: 0

Evolutionary Method of Delivery as Applied to a Large Re-engineering Effort 应用于大型再工程工作的演化交付方法

J. Softw. Maintenance Res. Pract. Pub Date : 1996-08-01 DOI: 10.1002/(SICI)1096-908X(199607)8:4%3C269::AID-SMR133%3E3.0.CO;2-V

S. Mohan

引用次数: 0

A Specification Driven Slicing Process for Identifying Reusable Functions 用于识别可重用功能的规范驱动切片过程

J. Softw. Maintenance Res. Pract. Pub Date : 1996-05-31 DOI: 10.1002/(SICI)1096-908X(199605)8:3%3C145::AID-SMR127%3E3.0.CO;2-9

A. Cimitile, A. D. Lucia, M. Munro

引用次数: 75

Offshore Software Maintenance Methodology 离岸软件维护方法

J. Softw. Maintenance Res. Pract. Pub Date : 1996-05-31 DOI: 10.1002/(SICI)1096-908X(199605)8:3%3C179::AID-SMR128%3E3.0.CO;2-S

M. Kumar, V. Das, N. Netaji

引用次数: 6

Software Metrics and Microcode: A Case Study 软件度量和微码:一个案例研究

J. Softw. Maintenance Res. Pract. Pub Date : 1996-05-31 DOI: 10.1002/(SICI)1096-908X(199605)8:3%3C199::AID-SMR129%3E3.0.CO;2-N

G. Triantafyllos, S. Vassiliadis, J. Delgado-Frías

引用次数: 6