{"title":"A dynamic integration architecture for high availability real-time systems","authors":"John E. Stockenberg","doi":"10.1109/ICSM.1993.366956","DOIUrl":"https://doi.org/10.1109/ICSM.1993.366956","url":null,"abstract":"Describes a software architecture which supports incremental system and software integration, hardware and software maintenance, and system evolution and reconfiguration without imposing a significant impact on system performance or availability. The approach utilizes a compact command language for controlling the dynamic integration of new or replacement software and hardware components into a distributed real-time system while that system is operating normally. The approach works with current languages, architectures and applications and does not depend on the availability of redundant processing components. The dynamic integration command language is described using a typical usage scenario, and the results of a prototype implementation effort are discussed, in which real-time dynamic integration commands have been shown to have performance times in the 20-30-/spl mu/s range.<<ETX>>","PeriodicalId":228379,"journal":{"name":"1993 Conference on Software Maintenance","volume":"101 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1993-09-27","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"133147043","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}
{"title":"Management problems seen in software maintenance: An empowerment study","authors":"N. Chapin","doi":"10.1109/ICSM.1993.366929","DOIUrl":"https://doi.org/10.1109/ICSM.1993.366929","url":null,"abstract":"A survey of the problems faced by managers and supervisors of application software maintenance work is described. The responses were interpreted in terms of empowerment. Five conclusions emerged about managers and supervisors: 1) they see themselves as more powerless to take effective action on identified problems in the short run than in the long run; 2) they see themselves individually as largely powerless to take effective action on the problems they see; 3) they see themselves as organizationally largely powerless to take effective action on the problems they see; 4) they see the vast majority of problems as not being technical problems; and 5) they showed no significant differences across different industries. Overall, maintenance supervisors and managers do not recognize that the majority of the problems they feel unempowered about are themselves the result of management action or inaction where management has or had the power to take effective action.<<ETX>>","PeriodicalId":228379,"journal":{"name":"1993 Conference on Software Maintenance","volume":"115 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1993-09-27","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"116592329","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}
L. White, V. Narayanswamy, T. Friedman, M. Kirschenbaum, Paul Piwowarski, Mitsuru Oha
{"title":"Test Manager: A regression testing tool","authors":"L. White, V. Narayanswamy, T. Friedman, M. Kirschenbaum, Paul Piwowarski, Mitsuru Oha","doi":"10.1109/ICSM.1993.366928","DOIUrl":"https://doi.org/10.1109/ICSM.1993.366928","url":null,"abstract":"CWRU has participated in a joint project with IBM in developing an internal regression testing tool called Test Manager. The objective of Test Manager is to aid in regression testing at the unit testing, integration testing, or function testing levels and also to produce a reduced regression test set to verify the software changes indicated by the user. A conceptual basis for the tool, called a firewall, and a description of the factors which influenced the design of the tool are given. The tool utilizes a Prolog database; a set of experiments that determined how that database should best be structured is described. Timing and space requirements and future work and enhancements to the tool are discussed.<<ETX>>","PeriodicalId":228379,"journal":{"name":"1993 Conference on Software Maintenance","volume":"160 ","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1993-09-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"120940376","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}
{"title":"Do design records really benefit software maintenance","authors":"R. Arnold, M. Slovin, N. Wilde","doi":"10.1109/ICSM.1993.366939","DOIUrl":"https://doi.org/10.1109/ICSM.1993.366939","url":null,"abstract":"Recently the design record concept has been suggested for reducing software life-cycle costs. A design record is a collection of information, usually in an online repository, to support software evolution. The impact to date of design records on software maintenance is examined. Design record terminology and related work are discussed. How design records can affect maintenance and whether they have done so are also discussed. It is shown that, despite the popularity of the concept, relatively little quantitative experimental evidence exists that design records reduce maintenance costs in practice. Open issues that design record researchers should address to make design records more beneficial to software maintenance and criteria for what information should be in a design record, especially if the design record is to have a significant impact on software maintenance, are suggested.<<ETX>>","PeriodicalId":228379,"journal":{"name":"1993 Conference on Software Maintenance","volume":"292 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1993-09-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"122960251","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}
{"title":"Representative sampling within software quality assurance","authors":"Neera Bansal Talbert","doi":"10.1109/ICSM.1993.366945","DOIUrl":"https://doi.org/10.1109/ICSM.1993.366945","url":null,"abstract":"Estimating the representative sampling size, by constructing confidence levels from risk analysis, is an integral part of the software quality assurance (SQA) audit function. How the combination of two valid industry mechanisms can be used to determine a truly representative sampling size and maximize limited resources is described. The goal is to produce a high-quality product which is cost effective. Through risk management and statistical sampling, the Mission Operations Directorate Information Systems Group (MODIS) has reduced the number of audits required for a project and reduced SQA costs without compromising quality.<<ETX>>","PeriodicalId":228379,"journal":{"name":"1993 Conference on Software Maintenance","volume":"20 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1993-09-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"124158941","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}
P. Linos, P. Aubet, Laurent Dumas, Yann Helleboid, Patricia Lejeune, P. Tulula
{"title":"CARE: An environment for understanding and re-engineering C programs","authors":"P. Linos, P. Aubet, Laurent Dumas, Yann Helleboid, Patricia Lejeune, P. Tulula","doi":"10.1109/ICSM.1993.366949","DOIUrl":"https://doi.org/10.1109/ICSM.1993.366949","url":null,"abstract":"The authors' focus is on facilitating incremental understanding and re-engineering of existing C programs. A software environment called CARE (computer-aided re-engineering) is used as a vehicle toward that goal. CARE maintains a repository of control-flow and data-flow dependencies (i.e., entities and their relations) of C programs. These dependencies can be visualized using a novel presentation model. Moreover, CARE entails transformation tools that support various ways of displaying program dependencies and facilitate incremental program modifications. An empirical evaluation of the CARE environment using small size C programs is performed. In addition, CARE is used in order to modify the source code of a medium-to-large size program. The results from this empirical evaluation of CARE indicate that its presentation model and transformation tools are a promising step towards improving the effectiveness of understanding and re-engineering existing C programs. Finally, the authors discuss some issues raised during the modification exercise with CARE when using a medium-to-large size program.<<ETX>>","PeriodicalId":228379,"journal":{"name":"1993 Conference on Software Maintenance","volume":"143 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1993-09-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"114730655","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}
{"title":"Dynamic program dicing","authors":"T. Y. Chen, Y. Y. Cheung","doi":"10.1109/ICSM.1993.366925","DOIUrl":"https://doi.org/10.1109/ICSM.1993.366925","url":null,"abstract":"Program dicing, introduced by J. R. Lyle and M. Weiser (Proc. 2nd Int. Conf. Comput. Appl., pp. 887-883, 1987), is a debugging technique built upon program slicing. Their dicing methodology is referred to as static program dicing in this paper. Since it is difficult to apply static program dicing effectively under some circumstances, an extension of program dicing, dynamic program dicing, is introduced here. Several strategies of constructing dynamic dices are also discussed. Although a dynamic slice is included in its corresponding static slice, a dynamic dice is not necessarily included in its corresponding static dice. Some conditions under which dynamic dice is more precise than static dice are investigated.<<ETX>>","PeriodicalId":228379,"journal":{"name":"1993 Conference on Software Maintenance","volume":"1 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1993-09-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"129125649","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}
{"title":"Impact analysis-Towards a framework for comparison","authors":"R. Arnold, S. Bohner","doi":"10.1109/ICSM.1993.366933","DOIUrl":"https://doi.org/10.1109/ICSM.1993.366933","url":null,"abstract":"The term impact analysis is used with many meanings. A three-part framework for characterizing and comparing diverse impact analysis approaches is defined. The parts correspond to how an approach is used to accomplish impact analysis, how an approach does impact analysis internally, and the effectiveness of the impact analysis approach. To illustrate the framework's application, five impact analysis approaches are illustrated according to it.<<ETX>>","PeriodicalId":228379,"journal":{"name":"1993 Conference on Software Maintenance","volume":"9 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1993-09-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"114172110","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}
{"title":"Reuse reengineering and validation via concept assignment","authors":"A. Cimitile, A. R. Fasolino, P. Maresca","doi":"10.1109/ICSM.1993.366940","DOIUrl":"https://doi.org/10.1109/ICSM.1993.366940","url":null,"abstract":"The first step in a software reuse reengineering process is to analyze the structural characteristics of the existing software so as to produce software component sets, each of which is a candidate for clustering and reengineering into a reusable module. This step is founded on one or more candidature criteria and the cost of the following steps depends on their quality. The notions of completeness and adequacy as applied to candidature criteria are introduced, the need for an adequacy validation process before they are applied on a software system is outlined. An adequate validation process founded on the assignment of a concept to the candidate modules is proposed, and the results of an application of this process are described and discussed.<<ETX>>","PeriodicalId":228379,"journal":{"name":"1993 Conference on Software Maintenance","volume":"20 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1993-09-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"132741973","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}
{"title":"Developing formal software process definitions","authors":"D. Drew","doi":"10.1109/ICSM.1993.366960","DOIUrl":"https://doi.org/10.1109/ICSM.1993.366960","url":null,"abstract":"Projects, within Paramax, which have achieved high maturity ratings, as measured against the SEI Capability Maturity Model (CMM), have based their process improvement efforts on formal process definitions for software engineering activities. A process definition methodology (ADPM) has been developed based on these project level experiences. This methodology supports the creation of software engineering process definitions at the organizational level while allowing for unique project instantiations within the organization. It specifically addresses the special case of capturing existing informal processes that one would typically find in ongoing software maintenance contracts.<<ETX>>","PeriodicalId":228379,"journal":{"name":"1993 Conference on Software Maintenance","volume":"22 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1993-09-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"133768163","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号
