Pub Date : 1998-11-16DOI: 10.1109/ICSM.1998.738490
P. Oman
This panel, comprised of noted practitioners and researchers involved with measuring systems that undergo change, will present data from industry demonstrating the problems in modeling the quality of evolving systems. Lessons learned, from years of experience and experimentation, will be listed and discussed so that participants from the audience can gain insights and, hopefully, avoid some of the pitfalls inherent in measuring software that changes on a regular basis. Included in the discussion will be examples from industrial systems being constructed or maintained by Northern Telecom, Hewlett-Packard, StorageTek, JPL, and IBM.
{"title":"Hitting the Moving Target: Trials and Tribulations of Modeling Quality in Evolving Software Systems","authors":"P. Oman","doi":"10.1109/ICSM.1998.738490","DOIUrl":"https://doi.org/10.1109/ICSM.1998.738490","url":null,"abstract":"This panel, comprised of noted practitioners and researchers involved with measuring systems that undergo change, will present data from industry demonstrating the problems in modeling the quality of evolving systems. Lessons learned, from years of experience and experimentation, will be listed and discussed so that participants from the audience can gain insights and, hopefully, avoid some of the pitfalls inherent in measuring software that changes on a regular basis. Included in the discussion will be examples from industrial systems being constructed or maintained by Northern Telecom, Hewlett-Packard, StorageTek, JPL, and IBM.","PeriodicalId":271895,"journal":{"name":"Proceedings. International Conference on Software Maintenance (Cat. No. 98CB36272)","volume":"97 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1998-11-16","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"117194438","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 : 1998-11-16DOI: 10.1109/ICSM.1998.738507
R. Hall, D. Heimbigner, A. Wolf
Software distribution is evolving from a physical media approach to one where it is practical and advantageous to leverage the connectivity of networks. Network distribution of software systems provides timeliness and continuity of evolution not possible with physical media distribution methods. To support network-based software distribution, companies and organizations such as Microsoft, Marimba, and the Desktop Management Task Force (DMTF) are strengthening their efforts to package software systems in a way that is conducive to network distribution and management. The result of these efforts has led to the creation of software description languages and schema such as the Open Software Description format created by Microsoft and Marimba and the Management Information Format created by DMTF. While these efforts are steps in the right direction, they do not address deployment issues in a complete and systematic fashion. The contribution of this paper is to evaluate these leading software description technologies.
{"title":"Evaluating software deployment languages and schema: an experience report","authors":"R. Hall, D. Heimbigner, A. Wolf","doi":"10.1109/ICSM.1998.738507","DOIUrl":"https://doi.org/10.1109/ICSM.1998.738507","url":null,"abstract":"Software distribution is evolving from a physical media approach to one where it is practical and advantageous to leverage the connectivity of networks. Network distribution of software systems provides timeliness and continuity of evolution not possible with physical media distribution methods. To support network-based software distribution, companies and organizations such as Microsoft, Marimba, and the Desktop Management Task Force (DMTF) are strengthening their efforts to package software systems in a way that is conducive to network distribution and management. The result of these efforts has led to the creation of software description languages and schema such as the Open Software Description format created by Microsoft and Marimba and the Management Information Format created by DMTF. While these efforts are steps in the right direction, they do not address deployment issues in a complete and systematic fashion. The contribution of this paper is to evaluate these leading software description technologies.","PeriodicalId":271895,"journal":{"name":"Proceedings. International Conference on Software Maintenance (Cat. No. 98CB36272)","volume":"1 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1998-11-16","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"130604413","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 : 1998-11-16DOI: 10.1109/ICSM.1998.738511
J. Voas
Reliable Software Technologies
可靠的软件技术
{"title":"Maintaining COTS-based Systems: Is it Possible?","authors":"J. Voas","doi":"10.1109/ICSM.1998.738511","DOIUrl":"https://doi.org/10.1109/ICSM.1998.738511","url":null,"abstract":"Reliable Software Technologies","PeriodicalId":271895,"journal":{"name":"Proceedings. International Conference on Software Maintenance (Cat. No. 98CB36272)","volume":"45 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1998-11-16","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"124852603","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 : 1998-03-16DOI: 10.1109/ICSM.1998.738513
N. Schneidewind
Obviously, COTS components are different from custom components with respect to one or more of the following attributes: source, development paradigm, safety, reliability, maintainability, availability, security, and other attributes. However, the important question is whether they should be treated differently when deciding to deploy them for operational use; we suggest the answer is no. We use reliability as an example to justify our answer. In order to demonstrate its reliability, a COTS component must pass the same reliability evaluations as the custom components, otherwise the COTS components will be the weakest link in the chain of components and will be the determinant of software system reliability. The challenge is that there will be less information available for evaluating COTS components than for custom components but this does not mean we should despair and do nothing. Actually, there is a lot we can do even in the absence of documentation on COTS components because the customer will have information about how COTS components are to be used in the larger system. To illustrate our approach, we will consider the reliability, maintainability, and availability (RMA) of COTS components as used in larger systems.
{"title":"Methods for assessing COTS reliability, maintainability, and availability","authors":"N. Schneidewind","doi":"10.1109/ICSM.1998.738513","DOIUrl":"https://doi.org/10.1109/ICSM.1998.738513","url":null,"abstract":"Obviously, COTS components are different from custom components with respect to one or more of the following attributes: source, development paradigm, safety, reliability, maintainability, availability, security, and other attributes. However, the important question is whether they should be treated differently when deciding to deploy them for operational use; we suggest the answer is no. We use reliability as an example to justify our answer. In order to demonstrate its reliability, a COTS component must pass the same reliability evaluations as the custom components, otherwise the COTS components will be the weakest link in the chain of components and will be the determinant of software system reliability. The challenge is that there will be less information available for evaluating COTS components than for custom components but this does not mean we should despair and do nothing. Actually, there is a lot we can do even in the absence of documentation on COTS components because the customer will have information about how COTS components are to be used in the larger system. To illustrate our approach, we will consider the reliability, maintainability, and availability (RMA) of COTS components as used in larger systems.","PeriodicalId":271895,"journal":{"name":"Proceedings. International Conference on Software Maintenance (Cat. No. 98CB36272)","volume":"109 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1998-03-16","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"115171961","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 : 1998-03-16DOI: 10.1109/ICSM.1998.738522
D. Castelli
This paper presents a technique for reducing the effort required to replay database schema design during maintenance. This technique is based on the reuse of the refinement steps, the schemas and the verification of the original design. For each of them, the technique specifies the conditions under which reuse can be applied and which are the local changes that must be operated on the components of the previous design.
{"title":"Reuse in replaying database design","authors":"D. Castelli","doi":"10.1109/ICSM.1998.738522","DOIUrl":"https://doi.org/10.1109/ICSM.1998.738522","url":null,"abstract":"This paper presents a technique for reducing the effort required to replay database schema design during maintenance. This technique is based on the reuse of the refinement steps, the schemas and the verification of the original design. For each of them, the technique specifies the conditions under which reuse can be applied and which are the local changes that must be operated on the components of the previous design.","PeriodicalId":271895,"journal":{"name":"Proceedings. International Conference on Software Maintenance (Cat. No. 98CB36272)","volume":"102 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1998-03-16","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"115214530","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 : 1998-03-16DOI: 10.1109/ICSM.1998.738487
G. Rothermel, M. J. Harrold, Jeffery Ostrin, Christie Hong
Test suite minimization techniques attempt to reduce the cost of saving and reusing tests during software maintenance, by eliminating redundant tests from test suites. A potential drawback of these techniques is that in minimizing a test suite, they might reduce the ability of that test suite to reveal faults in the software. A study showed that minimization can reduce test suite size without significantly reducing the fault detection capabilities of test suites. To further investigate this issue, we performed an experiment in which we compared the costs and benefits of minimizing test suites of various sizes for several programs. In contrast to the previous study, our results reveal that the fault detection capabilities of test suites can be severely compromised by minimization.
{"title":"An empirical study of the effects of minimization on the fault detection capabilities of test suites","authors":"G. Rothermel, M. J. Harrold, Jeffery Ostrin, Christie Hong","doi":"10.1109/ICSM.1998.738487","DOIUrl":"https://doi.org/10.1109/ICSM.1998.738487","url":null,"abstract":"Test suite minimization techniques attempt to reduce the cost of saving and reusing tests during software maintenance, by eliminating redundant tests from test suites. A potential drawback of these techniques is that in minimizing a test suite, they might reduce the ability of that test suite to reveal faults in the software. A study showed that minimization can reduce test suite size without significantly reducing the fault detection capabilities of test suites. To further investigate this issue, we performed an experiment in which we compared the costs and benefits of minimizing test suites of various sizes for several programs. In contrast to the previous study, our results reveal that the fault detection capabilities of test suites can be severely compromised by minimization.","PeriodicalId":271895,"journal":{"name":"Proceedings. International Conference on Software Maintenance (Cat. No. 98CB36272)","volume":"28 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1998-03-16","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"115731700","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 : 1998-03-16DOI: 10.1109/ICSM.1998.738518
Maria Jo, Castro Sousa, Helena Mendes Moreira
This research paper presents the results of a field survey for the characterisation of Software Maintenance Process in Portugal. It was concluded that the three biggest problems related to the Software Maintenance Process are: the lack of software maintenance process models, the lack of documentation of applications and the lack of time to satisfy the requests. Only 2.7% of the people who answered the questionnaire consider the software maintenance process very efficient; 70.2% consider it of a very low level of efficiency.
{"title":"A survey on the Software Maintenance Process","authors":"Maria Jo, Castro Sousa, Helena Mendes Moreira","doi":"10.1109/ICSM.1998.738518","DOIUrl":"https://doi.org/10.1109/ICSM.1998.738518","url":null,"abstract":"This research paper presents the results of a field survey for the characterisation of Software Maintenance Process in Portugal. It was concluded that the three biggest problems related to the Software Maintenance Process are: the lack of software maintenance process models, the lack of documentation of applications and the lack of time to satisfy the requests. Only 2.7% of the people who answered the questionnaire consider the software maintenance process very efficient; 70.2% consider it of a very low level of efficiency.","PeriodicalId":271895,"journal":{"name":"Proceedings. International Conference on Software Maintenance (Cat. No. 98CB36272)","volume":"8 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1998-03-16","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"130216429","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 : 1998-03-16DOI: 10.1109/ICSM.1998.738497
R. Fiutem, G. Antoniol
Traceability is a key issue to ensure consistency among software artifacts of subsequent phases of the development cycle. However few works have addressed the theme of tracing object oriented design into its software. This paper presents an approach to check the compliance of OO design with respect to source code. The process works on design artefacts expressed in OMT notation and accepts C++ source code. It recovers an "as is" design from the code, compares recovered design with the actual design and helps the user to deal with inconsistency by pointing out regions of code which do not match with design. The recovery process exploits regular expression and edit distance to bridge the gap between code and design. Results as well as consideration related to presentation issues are reported in the paper.
{"title":"Identifying design-code inconsistencies in object-oriented software: a case study","authors":"R. Fiutem, G. Antoniol","doi":"10.1109/ICSM.1998.738497","DOIUrl":"https://doi.org/10.1109/ICSM.1998.738497","url":null,"abstract":"Traceability is a key issue to ensure consistency among software artifacts of subsequent phases of the development cycle. However few works have addressed the theme of tracing object oriented design into its software. This paper presents an approach to check the compliance of OO design with respect to source code. The process works on design artefacts expressed in OMT notation and accepts C++ source code. It recovers an \"as is\" design from the code, compares recovered design with the actual design and helps the user to deal with inconsistency by pointing out regions of code which do not match with design. The recovery process exploits regular expression and edit distance to bridge the gap between code and design. Results as well as consideration related to presentation issues are reported in the paper.","PeriodicalId":271895,"journal":{"name":"Proceedings. International Conference on Software Maintenance (Cat. No. 98CB36272)","volume":"29 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1998-03-16","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"114293416","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 : 1998-03-16DOI: 10.1109/ICSM.1998.738499
Hsiang-Jui Kung, Cheng Hsu
The Software Maintenance Life Cycle Model (SMLC) was developed providing a basis to help software maintenance planning. The management framework was developed based on the SMLC concept to operationalize the model. This paper provides results from two cases to validate the model and the framework.
{"title":"Software Maintenance Life Cycle Model","authors":"Hsiang-Jui Kung, Cheng Hsu","doi":"10.1109/ICSM.1998.738499","DOIUrl":"https://doi.org/10.1109/ICSM.1998.738499","url":null,"abstract":"The Software Maintenance Life Cycle Model (SMLC) was developed providing a basis to help software maintenance planning. The management framework was developed based on the SMLC concept to operationalize the model. This paper provides results from two cases to validate the model and the framework.","PeriodicalId":271895,"journal":{"name":"Proceedings. International Conference on Software Maintenance (Cat. No. 98CB36272)","volume":"3 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1998-03-16","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"128111491","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
扫码关注我们
求助内容：
应助结果提醒方式：