Pub Date : 1991-10-15DOI: 10.1109/ICSM.1991.160330
H. Leung, L. White
A software test cost model which can be used to compare the retest-all strategy to a selective strategy is proposed. A test cost model is presented, and the conditions under which the selective strategy is more economical than the retest-all strategy are identified. Recently introduced regression testing strategies are reviewed. It is found that the relative cost depends on four factors: the selection, the execution, the checking cost, and the ratio of the size of the selected previous test to the size of the total previous test.<>
{"title":"A cost model to compare regression test strategies","authors":"H. Leung, L. White","doi":"10.1109/ICSM.1991.160330","DOIUrl":"https://doi.org/10.1109/ICSM.1991.160330","url":null,"abstract":"A software test cost model which can be used to compare the retest-all strategy to a selective strategy is proposed. A test cost model is presented, and the conditions under which the selective strategy is more economical than the retest-all strategy are identified. Recently introduced regression testing strategies are reviewed. It is found that the relative cost depends on four factors: the selection, the execution, the checking cost, and the ratio of the size of the selected previous test to the size of the total previous test.<<ETX>>","PeriodicalId":269572,"journal":{"name":"Proceedings. Conference on Software Maintenance 1991","volume":null,"pages":null},"PeriodicalIF":0.0,"publicationDate":"1991-10-15","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"130538160","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 : 1991-10-15DOI: 10.1109/ICSM.1991.160340
P. Rossi, P. Antonini, T. Lanza
The telecom company SIP promoted a program specifically designed for the management of the product maintainability level of its software. SIP started from a study of the intrinsic maintainability of a software product, defined as a property of the product representing the facility of performing maintenance actions (evolutionary, corrective, adaptive and perfective) on the code, irrespective of external elements such as a documentation, standards, etc. By measuring with appropriate metrics the complexity of the product-seen as the difficulty of interacting with the listing and which is inversely related with the maintainability-it is possible to obtain indexes representative of its actual state of maintainability. The authors deal with the control flow of COBOL programs. Within the scope of these types of measurements, the two different possible approaches-structural and dimensional-are examined.<>
{"title":"Experience on the control of software maintenance in SIP","authors":"P. Rossi, P. Antonini, T. Lanza","doi":"10.1109/ICSM.1991.160340","DOIUrl":"https://doi.org/10.1109/ICSM.1991.160340","url":null,"abstract":"The telecom company SIP promoted a program specifically designed for the management of the product maintainability level of its software. SIP started from a study of the intrinsic maintainability of a software product, defined as a property of the product representing the facility of performing maintenance actions (evolutionary, corrective, adaptive and perfective) on the code, irrespective of external elements such as a documentation, standards, etc. By measuring with appropriate metrics the complexity of the product-seen as the difficulty of interacting with the listing and which is inversely related with the maintainability-it is possible to obtain indexes representative of its actual state of maintainability. The authors deal with the control flow of COBOL programs. Within the scope of these types of measurements, the two different possible approaches-structural and dimensional-are examined.<<ETX>>","PeriodicalId":269572,"journal":{"name":"Proceedings. Conference on Software Maintenance 1991","volume":null,"pages":null},"PeriodicalIF":0.0,"publicationDate":"1991-10-15","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"125683962","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 : 1991-10-15DOI: 10.1109/ICSM.1991.160306
Latifa Ben Arfa Rabai, A. Mili, L. Sekhri
An empirical study of the management of software maintenance is presented, based on completion of an earlier study. The survey at hand has been conducted by means of live interviews with analysts and software managers, using a translated version of B.P. Lientz and E.B. Swanson's (1978) survey form (slightly adjusted at times to take into account a difference of data processing culture). The authors accumulated a total of 150 completed survey forms, properly distributed on the various sectors of the Tunisian data processing industry. For the sake of comparison or confirmation, the authors mention a similar study that was carried out by one of the authors with some companies in Algeria. This study covers a total of sixty surveys, taken in 1988 and 1989. The final results are presented. The issues discussed are scale of effect issues, organizational issues, productivity technique issues and problem area issues.<>
{"title":"An empirical study of software maintenance","authors":"Latifa Ben Arfa Rabai, A. Mili, L. Sekhri","doi":"10.1109/ICSM.1991.160306","DOIUrl":"https://doi.org/10.1109/ICSM.1991.160306","url":null,"abstract":"An empirical study of the management of software maintenance is presented, based on completion of an earlier study. The survey at hand has been conducted by means of live interviews with analysts and software managers, using a translated version of B.P. Lientz and E.B. Swanson's (1978) survey form (slightly adjusted at times to take into account a difference of data processing culture). The authors accumulated a total of 150 completed survey forms, properly distributed on the various sectors of the Tunisian data processing industry. For the sake of comparison or confirmation, the authors mention a similar study that was carried out by one of the authors with some companies in Algeria. This study covers a total of sixty surveys, taken in 1988 and 1989. The final results are presented. The issues discussed are scale of effect issues, organizational issues, productivity technique issues and problem area issues.<<ETX>>","PeriodicalId":269572,"journal":{"name":"Proceedings. Conference on Software Maintenance 1991","volume":null,"pages":null},"PeriodicalIF":0.0,"publicationDate":"1991-10-15","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"130811411","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 : 1991-10-15DOI: 10.1109/ICSM.1991.160329
R. Gopal
Dynamic program slicing based on program dependence relations is discussed. The dynamic dependence relations can be generated in parallel with the execution of a program. The only information that is needed is the identification of the statement that is currently being executed, and the current state of the program (variables that are defined or used). This information is used to update the relations and the intermediate dependence information sets that are maintained for each level of nested compound statements. Once these sets have been updated, the program execution information about the current statement can be discarded and space can be reclaimed. An improved technique with space requirements proportional to the nesting depth of compound statements (loops and conditionals) in a program is described.<>
{"title":"Dynamic program slicing based on dependence relations","authors":"R. Gopal","doi":"10.1109/ICSM.1991.160329","DOIUrl":"https://doi.org/10.1109/ICSM.1991.160329","url":null,"abstract":"Dynamic program slicing based on program dependence relations is discussed. The dynamic dependence relations can be generated in parallel with the execution of a program. The only information that is needed is the identification of the statement that is currently being executed, and the current state of the program (variables that are defined or used). This information is used to update the relations and the intermediate dependence information sets that are maintained for each level of nested compound statements. Once these sets have been updated, the program execution information about the current statement can be discarded and space can be reclaimed. An improved technique with space requirements proportional to the nesting depth of compound statements (loops and conditionals) in a program is described.<<ETX>>","PeriodicalId":269572,"journal":{"name":"Proceedings. Conference on Software Maintenance 1991","volume":null,"pages":null},"PeriodicalIF":0.0,"publicationDate":"1991-10-15","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"131156183","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 : 1991-10-15DOI: 10.1109/ICSM.1991.160324
N. Wilde, R. Huitt
Some of the difficulties that may be expected in the maintenance of software developed using the new object oriented languages are described. The concepts of inheritance and of polymorphism provide the great strengths of these languages but they also introduce difficulties in program analysis and understanding. The authors analyze problems of dynamic binding, object dependencies, dispersed program structure, control of polymorphism, high level understanding and detailed code understanding. Examples are presented based on code from the Smalltalk V environment. Recommendations are made for possible tool support, particularly using the concepts of dependency analysis, external dependency graphs, and clustering methodologies. Some suggestions are made concerning maintenance in firefighting situations, when a failed system must be brought back into service with a minimum of lost time.<>
{"title":"Maintenance support for object oriented programs","authors":"N. Wilde, R. Huitt","doi":"10.1109/ICSM.1991.160324","DOIUrl":"https://doi.org/10.1109/ICSM.1991.160324","url":null,"abstract":"Some of the difficulties that may be expected in the maintenance of software developed using the new object oriented languages are described. The concepts of inheritance and of polymorphism provide the great strengths of these languages but they also introduce difficulties in program analysis and understanding. The authors analyze problems of dynamic binding, object dependencies, dispersed program structure, control of polymorphism, high level understanding and detailed code understanding. Examples are presented based on code from the Smalltalk V environment. Recommendations are made for possible tool support, particularly using the concepts of dependency analysis, external dependency graphs, and clustering methodologies. Some suggestions are made concerning maintenance in firefighting situations, when a failed system must be brought back into service with a minimum of lost time.<<ETX>>","PeriodicalId":269572,"journal":{"name":"Proceedings. Conference on Software Maintenance 1991","volume":null,"pages":null},"PeriodicalIF":0.0,"publicationDate":"1991-10-15","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"131911898","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 : 1991-10-15DOI: 10.1109/ICSM.1991.160302
F. Lanubile, P. Maresca, G. Visaggio
An environment is described which supports the reengineering cycle at the design level and provides a homogeneous software configuration for the maintenance process. The environment is based on an integration tool which takes the output from a static analyzer, used for reverse engineering and populates the repository of a computer-aided-software-engineering (CASE) tool, usually used in forward engineering. The integration allows enhancement of the knowledge of the program, the reliability of modifications, the reusability and the change management. A case study is shown in which the design of a sample program is recaptured from the source code.<>
{"title":"An environment for the reengineering of Pascal programs","authors":"F. Lanubile, P. Maresca, G. Visaggio","doi":"10.1109/ICSM.1991.160302","DOIUrl":"https://doi.org/10.1109/ICSM.1991.160302","url":null,"abstract":"An environment is described which supports the reengineering cycle at the design level and provides a homogeneous software configuration for the maintenance process. The environment is based on an integration tool which takes the output from a static analyzer, used for reverse engineering and populates the repository of a computer-aided-software-engineering (CASE) tool, usually used in forward engineering. The integration allows enhancement of the knowledge of the program, the reliability of modifications, the reusability and the change management. A case study is shown in which the design of a sample program is recaptured from the source code.<<ETX>>","PeriodicalId":269572,"journal":{"name":"Proceedings. Conference on Software Maintenance 1991","volume":null,"pages":null},"PeriodicalIF":0.0,"publicationDate":"1991-10-15","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"133454792","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 : 1991-10-15DOI: 10.1109/ICSM.1991.160310
G. Canfora, A. Cimitile, U. D. Carlini
Some of the reasons for difficulties arising in the use of design documents produced by reverse engineering tools are analyzed. With reference to intermodular dataflow analysis for Pascal software systems, an interactive tool is proposed to more effectively help the maintainer. The tool is based on: the production of intermodular dataflow information by static analysis of the code; their representation in a Prolog program dictionary; and a Prolog abstractor that allows specific queries of maintainers to be answered. A logic-based approach to the design and implementation of an interactive tool which analyzes the intermodularal data flow of a program is discussed.<>
{"title":"A logic based approach to reverse engineering tools production","authors":"G. Canfora, A. Cimitile, U. D. Carlini","doi":"10.1109/ICSM.1991.160310","DOIUrl":"https://doi.org/10.1109/ICSM.1991.160310","url":null,"abstract":"Some of the reasons for difficulties arising in the use of design documents produced by reverse engineering tools are analyzed. With reference to intermodular dataflow analysis for Pascal software systems, an interactive tool is proposed to more effectively help the maintainer. The tool is based on: the production of intermodular dataflow information by static analysis of the code; their representation in a Prolog program dictionary; and a Prolog abstractor that allows specific queries of maintainers to be answered. A logic-based approach to the design and implementation of an interactive tool which analyzes the intermodularal data flow of a program is discussed.<<ETX>>","PeriodicalId":269572,"journal":{"name":"Proceedings. Conference on Software Maintenance 1991","volume":null,"pages":null},"PeriodicalIF":0.0,"publicationDate":"1991-10-15","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"127643192","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 : 1991-10-15DOI: 10.1109/ICSM.1991.160300
C. Desclaux, M. Ribault
MACS's goal is to offer a customizable software maintenance assistance system. Its main concern is to help the maintainer in gaining a deep understanding of existing or in-progress applications, of the factual data (change management world and abstraction recovery world), the design decisions rationale (reasoning world), and the mapping of domain to programming components (interconnection world). This broad reverse-engineering approach is enhanced by impact analysis techniques to better perceive the interaction between components. The MACS supervisor proposes a set of maintenance process models to guide the maintainer through the MACS worlds. Knowledge base and expert system techniques are used in conjunction with software engineering techniques, which makes MACS a KADME (knowledge assistance for development and maintenance environment).<>
{"title":"MACS: maintenance assistance capability for software-a KADME","authors":"C. Desclaux, M. Ribault","doi":"10.1109/ICSM.1991.160300","DOIUrl":"https://doi.org/10.1109/ICSM.1991.160300","url":null,"abstract":"MACS's goal is to offer a customizable software maintenance assistance system. Its main concern is to help the maintainer in gaining a deep understanding of existing or in-progress applications, of the factual data (change management world and abstraction recovery world), the design decisions rationale (reasoning world), and the mapping of domain to programming components (interconnection world). This broad reverse-engineering approach is enhanced by impact analysis techniques to better perceive the interaction between components. The MACS supervisor proposes a set of maintenance process models to guide the maintainer through the MACS worlds. Knowledge base and expert system techniques are used in conjunction with software engineering techniques, which makes MACS a KADME (knowledge assistance for development and maintenance environment).<<ETX>>","PeriodicalId":269572,"journal":{"name":"Proceedings. Conference on Software Maintenance 1991","volume":null,"pages":null},"PeriodicalIF":0.0,"publicationDate":"1991-10-15","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"130640411","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 : 1991-10-15DOI: 10.1109/ICSM.1991.160342
A. Murtha
The development of a flexible configuration control tool for a dynamic software system is discussed. The configuration management tool provides the ability to automatically install or remove software patches from any software baseline. Its innovative concept is that configuration changes are temporary as long as desired. Installation and removal of patches requires only shutting down the application code, setting the desired configuration through a user-friendly interface, and then restarting the application. If a patch survives the rigors of operations for a few weeks, it is safe to permanently incorporate it into the baseline. If a patch fails while in the temporary state, it can easily be removed. The results of using this tool are discussed.<>
{"title":"The development of a configuration control tool","authors":"A. Murtha","doi":"10.1109/ICSM.1991.160342","DOIUrl":"https://doi.org/10.1109/ICSM.1991.160342","url":null,"abstract":"The development of a flexible configuration control tool for a dynamic software system is discussed. The configuration management tool provides the ability to automatically install or remove software patches from any software baseline. Its innovative concept is that configuration changes are temporary as long as desired. Installation and removal of patches requires only shutting down the application code, setting the desired configuration through a user-friendly interface, and then restarting the application. If a patch survives the rigors of operations for a few weeks, it is safe to permanently incorporate it into the baseline. If a patch fails while in the temporary state, it can easily be removed. The results of using this tool are discussed.<<ETX>>","PeriodicalId":269572,"journal":{"name":"Proceedings. Conference on Software Maintenance 1991","volume":null,"pages":null},"PeriodicalIF":0.0,"publicationDate":"1991-10-15","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"132959171","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 : 1991-10-15DOI: 10.1109/ICSM.1991.160320
M. J. Harrold, B. Malloy
A unified interprocedural program representation, the unified interprocedural graph (UIG) is presented; it combines the features of existing program representations to permit access to information for modifying, understanding, analyzing, testing and debugging. The algorithms developed for each of these independent graphs are adapted to use this unified representation by identifying the subset of nodes and edges required for that computation. The UIG can be incorporated into a maintenance environment and the associated algorithms used to build program maintenance tools. The authors present a brief overview of the graph representations on which the UIG is based and illustrate them with an example. The algorithms that use these graphs to gather the interprocedural information are described.<>
{"title":"A unified interprocedural program representation for a maintenance environment","authors":"M. J. Harrold, B. Malloy","doi":"10.1109/ICSM.1991.160320","DOIUrl":"https://doi.org/10.1109/ICSM.1991.160320","url":null,"abstract":"A unified interprocedural program representation, the unified interprocedural graph (UIG) is presented; it combines the features of existing program representations to permit access to information for modifying, understanding, analyzing, testing and debugging. The algorithms developed for each of these independent graphs are adapted to use this unified representation by identifying the subset of nodes and edges required for that computation. The UIG can be incorporated into a maintenance environment and the associated algorithms used to build program maintenance tools. The authors present a brief overview of the graph representations on which the UIG is based and illustrate them with an example. The algorithms that use these graphs to gather the interprocedural information are described.<<ETX>>","PeriodicalId":269572,"journal":{"name":"Proceedings. Conference on Software Maintenance 1991","volume":null,"pages":null},"PeriodicalIF":0.0,"publicationDate":"1991-10-15","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"130202096","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
扫码关注我们
求助内容：
应助结果提醒方式：