Pub Date : 1993-09-01DOI: 10.1109/ICSM.1993.366958
R. Cherinka, C. M. Overstreet, R. Sparks
Describes a process-oriented approach in which software maintainers team up with environment builders to develop a software engineering environment enhancing the support of existing, mature systems. This approach is currently being used to build an integrated work environment based on commercially available tools supporting the entire maintenance lifecycle. A working group, defined by three distinct teams (environment engineering, hardware engineering and tool support), is used to develop the environment. This paper points out important components that are useful to a maintainer and shows an approach to address many of the issues involved in building such an environment.<>
{"title":"Building an integrated software maintenance environment From a maintainer's perspective","authors":"R. Cherinka, C. M. Overstreet, R. Sparks","doi":"10.1109/ICSM.1993.366958","DOIUrl":"https://doi.org/10.1109/ICSM.1993.366958","url":null,"abstract":"Describes a process-oriented approach in which software maintainers team up with environment builders to develop a software engineering environment enhancing the support of existing, mature systems. This approach is currently being used to build an integrated work environment based on commercially available tools supporting the entire maintenance lifecycle. A working group, defined by three distinct teams (environment engineering, hardware engineering and tool support), is used to develop the environment. This paper points out important components that are useful to a maintainer and shows an approach to address many of the issues involved in building such an environment.<<ETX>>","PeriodicalId":228379,"journal":{"name":"1993 Conference on Software Maintenance","volume":"23 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":"121994357","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 : 1993-09-01DOI: 10.1109/ICSM.1993.366930
D. S. Hinley, K. Bennett
Existing systems may be considered as an asset and the software manager should consider seriously the risks of maintenance and ensure that the value of software is maximized in terms of customer benefit. Work aimed at improving the management of software maintenance activities by means of a substantial industrial trial evaluation that focused on improvements to aspects of maintenance management planning and control is reported. The results of the trial have led to the development of an integrated risk management process. It is concluded that risk management is an essential element of software maintenance management best-practice.<>
{"title":"Reducing the risks in software improvement through process-orientated management","authors":"D. S. Hinley, K. Bennett","doi":"10.1109/ICSM.1993.366930","DOIUrl":"https://doi.org/10.1109/ICSM.1993.366930","url":null,"abstract":"Existing systems may be considered as an asset and the software manager should consider seriously the risks of maintenance and ensure that the value of software is maximized in terms of customer benefit. Work aimed at improving the management of software maintenance activities by means of a substantial industrial trial evaluation that focused on improvements to aspects of maintenance management planning and control is reported. The results of the trial have led to the development of an integrated risk management process. It is concluded that risk management is an essential element of software maintenance management best-practice.<<ETX>>","PeriodicalId":228379,"journal":{"name":"1993 Conference on Software Maintenance","volume":"140 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":"116458655","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 : 1993-09-01DOI: 10.1109/ICSM.1993.366955
S. Rugaber, S. Doddapaneni
It is becoming increasingly desirable to move older application programs from their traditional mainframe execution environments to networked workstations. These management information systems are most often written in COBOL and store their data in files. A networked environment enables the use of a relational database management system and its fourth-generation access language, SQL. A conceptual framework is described that comprises a variety of strategies for making such a transition. Decision criteria for selecting among them are then presented. Finally, a variety of experiments intended to explore the strategies are recounted. The experiments include efforts to automate parts of the process.<>
{"title":"The transition of application programs from COBOL to a fourth generation language","authors":"S. Rugaber, S. Doddapaneni","doi":"10.1109/ICSM.1993.366955","DOIUrl":"https://doi.org/10.1109/ICSM.1993.366955","url":null,"abstract":"It is becoming increasingly desirable to move older application programs from their traditional mainframe execution environments to networked workstations. These management information systems are most often written in COBOL and store their data in files. A networked environment enables the use of a relational database management system and its fourth-generation access language, SQL. A conceptual framework is described that comprises a variety of strategies for making such a transition. Decision criteria for selecting among them are then presented. Finally, a variety of experiments intended to explore the strategies are recounted. The experiments include efforts to automate parts of the process.<<ETX>>","PeriodicalId":228379,"journal":{"name":"1993 Conference on Software Maintenance","volume":"56 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":"122776275","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 : 1993-09-01DOI: 10.1109/ICSM.1993.366959
W. Melo, N. Belkhatir
TEMPO, a process-centered software engineering environment, assists in cooperative work by means of an approach based on a communication model. The executable formalism used to define software engineering activities is described, and it is shown how constraints related to the use of objects in these activities are expressed using the role concept. The communication model is then presented. Thanks to this model, strategies governing the cooperation between various software processes are specified by the concept of active, programmable connections. A connection is a communication channel that links two roles. Message exchange is controlled using TECA (temporal event-condition-action) rules, executed by a trigger mechanism. These allow for the programming of synchronization strategies between processes, propagating the effects of an executed action on one or more connection points. The temporary modes of TECA rules allow for transactions of long duration, because these can be used to reason on past activities. Coherence control of objects handled by activities of long duration is performed by the work environments. The union between connections and work environments makes it possible to support the cooperating processes and object sharing between processes.<>
{"title":"Supporting software maintenance processes in TEMPO","authors":"W. Melo, N. Belkhatir","doi":"10.1109/ICSM.1993.366959","DOIUrl":"https://doi.org/10.1109/ICSM.1993.366959","url":null,"abstract":"TEMPO, a process-centered software engineering environment, assists in cooperative work by means of an approach based on a communication model. The executable formalism used to define software engineering activities is described, and it is shown how constraints related to the use of objects in these activities are expressed using the role concept. The communication model is then presented. Thanks to this model, strategies governing the cooperation between various software processes are specified by the concept of active, programmable connections. A connection is a communication channel that links two roles. Message exchange is controlled using TECA (temporal event-condition-action) rules, executed by a trigger mechanism. These allow for the programming of synchronization strategies between processes, propagating the effects of an executed action on one or more connection points. The temporary modes of TECA rules allow for transactions of long duration, because these can be used to reason on past activities. Coherence control of objects handled by activities of long duration is performed by the work environments. The union between connections and work environments makes it possible to support the cooperating processes and object sharing between processes.<<ETX>>","PeriodicalId":228379,"journal":{"name":"1993 Conference on Software Maintenance","volume":"46 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":"120922874","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 : 1993-09-01DOI: 10.1109/ICSM.1993.366938
V. Narat
An approach to storing source code using a relational database is described. The goal of this approach is to assist in the maintenance of source code, especially in producing cross references documentation. Why this approach was chosen and how the system's architecture was set up are explained. The emphasis, however, is placed upon the results obtained by using this system, in terms of volume and response time.<>
{"title":"Using a relational database for software maintenance: A case study","authors":"V. Narat","doi":"10.1109/ICSM.1993.366938","DOIUrl":"https://doi.org/10.1109/ICSM.1993.366938","url":null,"abstract":"An approach to storing source code using a relational database is described. The goal of this approach is to assist in the maintenance of source code, especially in producing cross references documentation. Why this approach was chosen and how the system's architecture was set up are explained. The emphasis, however, is placed upon the results obtained by using this system, in terms of volume and response time.<<ETX>>","PeriodicalId":228379,"journal":{"name":"1993 Conference on Software Maintenance","volume":"123 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":"127061651","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 : 1993-09-01DOI: 10.1109/ICSM.1993.366927
H. Agrawal, J. R. Horgan, E. W. Krauser, S. London
The purpose of regression testing is to ensure that bug fixes and new functionality introduced in a new version of a software do not adversely affect the correct functionality inherited from the previous version. Efficient methods of selecting small subsets of regression test sets that can be used to ensure correct functionality are explored.<>
{"title":"Incremental regression testing","authors":"H. Agrawal, J. R. Horgan, E. W. Krauser, S. London","doi":"10.1109/ICSM.1993.366927","DOIUrl":"https://doi.org/10.1109/ICSM.1993.366927","url":null,"abstract":"The purpose of regression testing is to ensure that bug fixes and new functionality introduced in a new version of a software do not adversely affect the correct functionality inherited from the previous version. Efficient methods of selecting small subsets of regression test sets that can be used to ensure correct functionality are explored.<<ETX>>","PeriodicalId":228379,"journal":{"name":"1993 Conference on Software Maintenance","volume":"28 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":"127268613","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 : 1993-09-01DOI: 10.1109/ICSM.1993.366937
Linda M. Keszenheimer
Object-oriented software engineering must address new issues during system evolution, namely, the effects of class evolution on existing class methods. A class dictionary graph describes the class structure and relationships of a given domain. A propagation pattern defines object behavior by describing responsibilities among a group of collaborating classes. The behavior described in a propagation pattern is mapped onto the class structure defined in a class dictionary graph, and the appropriate C++ code is generated. Class structures evolve in many ways. The effects of class evolution on the object behavior defined in existing propagation patterns are detailed, and the requirements for adapting propagation patterns during class evolution, as compared to the efforts of maintaining C++ code, are described.<>
{"title":"Specifying and adapting object behavior during system evolution","authors":"Linda M. Keszenheimer","doi":"10.1109/ICSM.1993.366937","DOIUrl":"https://doi.org/10.1109/ICSM.1993.366937","url":null,"abstract":"Object-oriented software engineering must address new issues during system evolution, namely, the effects of class evolution on existing class methods. A class dictionary graph describes the class structure and relationships of a given domain. A propagation pattern defines object behavior by describing responsibilities among a group of collaborating classes. The behavior described in a propagation pattern is mapped onto the class structure defined in a class dictionary graph, and the appropriate C++ code is generated. Class structures evolve in many ways. The effects of class evolution on the object behavior defined in existing propagation patterns are detailed, and the requirements for adapting propagation patterns during class evolution, as compared to the efforts of maintaining C++ code, are described.<<ETX>>","PeriodicalId":228379,"journal":{"name":"1993 Conference on Software Maintenance","volume":"10 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":"134571221","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 : 1993-09-01DOI: 10.1109/ICSM.1993.366954
T. Khoshgoftaar, J. Munson, D. Lanning
By modeling the relationship between software complexity attributes and software quality attributes, software engineers can take actions early in the development cycle to control the cost of the maintenance phase. The effectiveness of these model-based actions depends heavily on the predictive quality of the model. An enhanced modeling methodology that shows significant improvements in the predictive quality of regression models developed to predict software changes during maintenance is applied here. The methodology reduces software complexity data to domain metrics by applying principal components analysis. It then isolates clusters of similar program modules by applying cluster analysis to these derived domain metrics. Finally, the methodology develops individual regression models for each cluster. These within-cluster models have better predictive quality than a general model fitted to all of the observations.<>
{"title":"A comparative study of predictive models for program changes during system testing and maintenance","authors":"T. Khoshgoftaar, J. Munson, D. Lanning","doi":"10.1109/ICSM.1993.366954","DOIUrl":"https://doi.org/10.1109/ICSM.1993.366954","url":null,"abstract":"By modeling the relationship between software complexity attributes and software quality attributes, software engineers can take actions early in the development cycle to control the cost of the maintenance phase. The effectiveness of these model-based actions depends heavily on the predictive quality of the model. An enhanced modeling methodology that shows significant improvements in the predictive quality of regression models developed to predict software changes during maintenance is applied here. The methodology reduces software complexity data to domain metrics by applying principal components analysis. It then isolates clusters of similar program modules by applying cluster analysis to these derived domain metrics. Finally, the methodology develops individual regression models for each cluster. These within-cluster models have better predictive quality than a general model fitted to all of the observations.<<ETX>>","PeriodicalId":228379,"journal":{"name":"1993 Conference on Software Maintenance","volume":"86 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":"124413165","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 : 1993-07-01DOI: 10.1109/ICSM.1993.366952
L. Briand, S. Morasca, V. Basili
Software architecture appears to be one of the main factors affecting software maintainability. Therefore, in order to be able to predict and assess maintainability early in the development process one needs to be able to measure the high-level design characteristics that affect the change process. To this end, a measurement approach based on precise assumptions derived from the change process is proposed. The change process is based on object-oriented design principles and is partially language independent. Metrics for cohesion, coupling, and visibility are defined in order to capture the difficulty of isolating, understanding, designing and validating changes.<>
{"title":"Measuring and assessing maintainability at the end of high level design","authors":"L. Briand, S. Morasca, V. Basili","doi":"10.1109/ICSM.1993.366952","DOIUrl":"https://doi.org/10.1109/ICSM.1993.366952","url":null,"abstract":"Software architecture appears to be one of the main factors affecting software maintainability. Therefore, in order to be able to predict and assess maintainability early in the development process one needs to be able to measure the high-level design characteristics that affect the change process. To this end, a measurement approach based on precise assumptions derived from the change process is proposed. The change process is based on object-oriented design principles and is partially language independent. Metrics for cohesion, coupling, and visibility are defined in order to capture the difficulty of isolating, understanding, designing and validating changes.<<ETX>>","PeriodicalId":228379,"journal":{"name":"1993 Conference on Software Maintenance","volume":"36 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1993-07-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"115410891","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
扫码关注我们
求助内容：
应助结果提醒方式：