Identifying high maintenance legacy software

Legacy software maintenance is a significant cost item for many engineering organizations. This study is a preliminary report on work to investigate maintenance data, usage, and source code for legacy software used by an engineering design company to support a variety of functions, including electro...

Ausführliche Beschreibung

Gespeichert in:
Bibliographische Detailangaben
Veröffentlicht in:Journal of software maintenance and evolution 2002-11, Vol.14 (6), p.429-446
Hauptverfasser: Harrison, Matthew S., Walton, Gwendolyn H.
Format: Artikel
Sprache:eng
Schlagworte:
Online-Zugang:Volltext
Tags: Tag hinzufügen
Keine Tags, Fügen Sie den ersten Tag hinzu!
container_end_page 446
container_issue 6
container_start_page 429
container_title Journal of software maintenance and evolution
container_volume 14
creator Harrison, Matthew S.
Walton, Gwendolyn H.
description Legacy software maintenance is a significant cost item for many engineering organizations. This study is a preliminary report on work to investigate maintenance data, usage, and source code for legacy software used by an engineering design company to support a variety of functions, including electromagnetic, thermal, mechanical loading, vibration, and aerodynamic analysis. The results verify the applicability to legacy engineering software of previous research that concluded that size and structural metrics alone are not good indicators of high maintenance costs. Unlike previous research, the study also evaluates the effect of program usage on maintenance cost. Over the three‐year period of this study of 71 legacy engineering programs, 11 of the programs (15%) accounted for 80% of all maintenance and 67% of all program runs. The highest maintenance programs were not always the largest programs or the worst structured programs. 49% of the programs accounted for only 1% of total maintenance but 42% of the total lines of code (LOC) thus invalidating LOC as an indicator for maintenance cost. While additional work is needed to validate these findings across other organizations and other code sets, these preliminary results provide strong evidence that expected program usage can be a useful indicator of long‐term maintenance cost. Copyright © 2002 John Wiley & Sons, Ltd.
doi_str_mv 10.1002/smr.256
format Article
fullrecord <record><control><sourceid>proquest_cross</sourceid><recordid>TN_cdi_proquest_miscellaneous_1671458892</recordid><sourceformat>XML</sourceformat><sourcesystem>PC</sourcesystem><sourcerecordid>1671458892</sourcerecordid><originalsourceid>FETCH-LOGICAL-c3306-1926ddce5ce78ec547b6b1c5b5e6696077d847ed4561ea4c9a0e9c525cb51b553</originalsourceid><addsrcrecordid>eNp10EtLw0AUhuFBFKxV_AvZKWjqTOaWLLXYWqgKXqi7YTI5aUdzaWdSav69kUh3rs5ZPHyLF6FzgkcE4-jGl24UcXGABoTTKMSCxIf7H38coxPvPzHGVEo5QNezDKrG5q2tlsHKLldBqW3VQKUrA0EBS23awNd5s9MOTtFRrgsPZ393iN4n92_jh3D-PJ2Nb-ehoRSLkCSRyDID3ICMwXAmU5ESw1MOQiQCS5nFTELGuCCgmUk0hsTwiJuUk5RzOkSX_e7a1Zst-EaV1hsoCl1BvfWKCEkYj-Mk6uhFT42rvXeQq7WzpXatIlj99lBdD9X16ORVL3e2gPY_pl4fX3od9tr6Br73WrsvJSSVXC2epiphlI0nC6nu6A-bOW8T</addsrcrecordid><sourcetype>Aggregation Database</sourcetype><iscdi>true</iscdi><recordtype>article</recordtype><pqid>1671458892</pqid></control><display><type>article</type><title>Identifying high maintenance legacy software</title><source>Wiley</source><creator>Harrison, Matthew S. ; Walton, Gwendolyn H.</creator><creatorcontrib>Harrison, Matthew S. ; Walton, Gwendolyn H.</creatorcontrib><description>Legacy software maintenance is a significant cost item for many engineering organizations. This study is a preliminary report on work to investigate maintenance data, usage, and source code for legacy software used by an engineering design company to support a variety of functions, including electromagnetic, thermal, mechanical loading, vibration, and aerodynamic analysis. The results verify the applicability to legacy engineering software of previous research that concluded that size and structural metrics alone are not good indicators of high maintenance costs. Unlike previous research, the study also evaluates the effect of program usage on maintenance cost. Over the three‐year period of this study of 71 legacy engineering programs, 11 of the programs (15%) accounted for 80% of all maintenance and 67% of all program runs. The highest maintenance programs were not always the largest programs or the worst structured programs. 49% of the programs accounted for only 1% of total maintenance but 42% of the total lines of code (LOC) thus invalidating LOC as an indicator for maintenance cost. While additional work is needed to validate these findings across other organizations and other code sets, these preliminary results provide strong evidence that expected program usage can be a useful indicator of long‐term maintenance cost. Copyright © 2002 John Wiley &amp; Sons, Ltd.</description><identifier>ISSN: 1532-060X</identifier><identifier>EISSN: 1532-0618</identifier><identifier>DOI: 10.1002/smr.256</identifier><language>eng</language><publisher>Chichester, UK: John Wiley &amp; Sons, Ltd</publisher><subject>amount of maintenance ; Computer programs ; engineering applications ; Indicators ; Legacy ; Maintenance ; maintenance cost drivers ; Maintenance costs ; Organizations ; Software ; software evolution ; software metrics ; software usage ; Vibration</subject><ispartof>Journal of software maintenance and evolution, 2002-11, Vol.14 (6), p.429-446</ispartof><rights>Copyright © 2002 John Wiley &amp; Sons, Ltd.</rights><lds50>peer_reviewed</lds50><woscitedreferencessubscribed>false</woscitedreferencessubscribed><citedby>FETCH-LOGICAL-c3306-1926ddce5ce78ec547b6b1c5b5e6696077d847ed4561ea4c9a0e9c525cb51b553</citedby><cites>FETCH-LOGICAL-c3306-1926ddce5ce78ec547b6b1c5b5e6696077d847ed4561ea4c9a0e9c525cb51b553</cites></display><links><openurl>$$Topenurl_article</openurl><openurlfulltext>$$Topenurlfull_article</openurlfulltext><thumbnail>$$Tsyndetics_thumb_exl</thumbnail><linktopdf>$$Uhttps://onlinelibrary.wiley.com/doi/pdf/10.1002%2Fsmr.256$$EPDF$$P50$$Gwiley$$H</linktopdf><linktohtml>$$Uhttps://onlinelibrary.wiley.com/doi/full/10.1002%2Fsmr.256$$EHTML$$P50$$Gwiley$$H</linktohtml><link.rule.ids>314,780,784,1417,27924,27925,45574,45575</link.rule.ids></links><search><creatorcontrib>Harrison, Matthew S.</creatorcontrib><creatorcontrib>Walton, Gwendolyn H.</creatorcontrib><title>Identifying high maintenance legacy software</title><title>Journal of software maintenance and evolution</title><addtitle>J. Softw. Maint. Evol.: Res. Pract</addtitle><description>Legacy software maintenance is a significant cost item for many engineering organizations. This study is a preliminary report on work to investigate maintenance data, usage, and source code for legacy software used by an engineering design company to support a variety of functions, including electromagnetic, thermal, mechanical loading, vibration, and aerodynamic analysis. The results verify the applicability to legacy engineering software of previous research that concluded that size and structural metrics alone are not good indicators of high maintenance costs. Unlike previous research, the study also evaluates the effect of program usage on maintenance cost. Over the three‐year period of this study of 71 legacy engineering programs, 11 of the programs (15%) accounted for 80% of all maintenance and 67% of all program runs. The highest maintenance programs were not always the largest programs or the worst structured programs. 49% of the programs accounted for only 1% of total maintenance but 42% of the total lines of code (LOC) thus invalidating LOC as an indicator for maintenance cost. While additional work is needed to validate these findings across other organizations and other code sets, these preliminary results provide strong evidence that expected program usage can be a useful indicator of long‐term maintenance cost. Copyright © 2002 John Wiley &amp; Sons, Ltd.</description><subject>amount of maintenance</subject><subject>Computer programs</subject><subject>engineering applications</subject><subject>Indicators</subject><subject>Legacy</subject><subject>Maintenance</subject><subject>maintenance cost drivers</subject><subject>Maintenance costs</subject><subject>Organizations</subject><subject>Software</subject><subject>software evolution</subject><subject>software metrics</subject><subject>software usage</subject><subject>Vibration</subject><issn>1532-060X</issn><issn>1532-0618</issn><fulltext>true</fulltext><rsrctype>article</rsrctype><creationdate>2002</creationdate><recordtype>article</recordtype><recordid>eNp10EtLw0AUhuFBFKxV_AvZKWjqTOaWLLXYWqgKXqi7YTI5aUdzaWdSav69kUh3rs5ZPHyLF6FzgkcE4-jGl24UcXGABoTTKMSCxIf7H38coxPvPzHGVEo5QNezDKrG5q2tlsHKLldBqW3VQKUrA0EBS23awNd5s9MOTtFRrgsPZ393iN4n92_jh3D-PJ2Nb-ehoRSLkCSRyDID3ICMwXAmU5ESw1MOQiQCS5nFTELGuCCgmUk0hsTwiJuUk5RzOkSX_e7a1Zst-EaV1hsoCl1BvfWKCEkYj-Mk6uhFT42rvXeQq7WzpXatIlj99lBdD9X16ORVL3e2gPY_pl4fX3od9tr6Br73WrsvJSSVXC2epiphlI0nC6nu6A-bOW8T</recordid><startdate>200211</startdate><enddate>200211</enddate><creator>Harrison, Matthew S.</creator><creator>Walton, Gwendolyn H.</creator><general>John Wiley &amp; Sons, Ltd</general><scope>BSCLL</scope><scope>AAYXX</scope><scope>CITATION</scope><scope>7SC</scope><scope>8FD</scope><scope>JQ2</scope><scope>L7M</scope><scope>L~C</scope><scope>L~D</scope></search><sort><creationdate>200211</creationdate><title>Identifying high maintenance legacy software</title><author>Harrison, Matthew S. ; Walton, Gwendolyn H.</author></sort><facets><frbrtype>5</frbrtype><frbrgroupid>cdi_FETCH-LOGICAL-c3306-1926ddce5ce78ec547b6b1c5b5e6696077d847ed4561ea4c9a0e9c525cb51b553</frbrgroupid><rsrctype>articles</rsrctype><prefilter>articles</prefilter><language>eng</language><creationdate>2002</creationdate><topic>amount of maintenance</topic><topic>Computer programs</topic><topic>engineering applications</topic><topic>Indicators</topic><topic>Legacy</topic><topic>Maintenance</topic><topic>maintenance cost drivers</topic><topic>Maintenance costs</topic><topic>Organizations</topic><topic>Software</topic><topic>software evolution</topic><topic>software metrics</topic><topic>software usage</topic><topic>Vibration</topic><toplevel>peer_reviewed</toplevel><toplevel>online_resources</toplevel><creatorcontrib>Harrison, Matthew S.</creatorcontrib><creatorcontrib>Walton, Gwendolyn H.</creatorcontrib><collection>Istex</collection><collection>CrossRef</collection><collection>Computer and Information Systems Abstracts</collection><collection>Technology Research Database</collection><collection>ProQuest Computer Science Collection</collection><collection>Advanced Technologies Database with Aerospace</collection><collection>Computer and Information Systems Abstracts – Academic</collection><collection>Computer and Information Systems Abstracts Professional</collection><jtitle>Journal of software maintenance and evolution</jtitle></facets><delivery><delcategory>Remote Search Resource</delcategory><fulltext>fulltext</fulltext></delivery><addata><au>Harrison, Matthew S.</au><au>Walton, Gwendolyn H.</au><format>journal</format><genre>article</genre><ristype>JOUR</ristype><atitle>Identifying high maintenance legacy software</atitle><jtitle>Journal of software maintenance and evolution</jtitle><addtitle>J. Softw. Maint. Evol.: Res. Pract</addtitle><date>2002-11</date><risdate>2002</risdate><volume>14</volume><issue>6</issue><spage>429</spage><epage>446</epage><pages>429-446</pages><issn>1532-060X</issn><eissn>1532-0618</eissn><abstract>Legacy software maintenance is a significant cost item for many engineering organizations. This study is a preliminary report on work to investigate maintenance data, usage, and source code for legacy software used by an engineering design company to support a variety of functions, including electromagnetic, thermal, mechanical loading, vibration, and aerodynamic analysis. The results verify the applicability to legacy engineering software of previous research that concluded that size and structural metrics alone are not good indicators of high maintenance costs. Unlike previous research, the study also evaluates the effect of program usage on maintenance cost. Over the three‐year period of this study of 71 legacy engineering programs, 11 of the programs (15%) accounted for 80% of all maintenance and 67% of all program runs. The highest maintenance programs were not always the largest programs or the worst structured programs. 49% of the programs accounted for only 1% of total maintenance but 42% of the total lines of code (LOC) thus invalidating LOC as an indicator for maintenance cost. While additional work is needed to validate these findings across other organizations and other code sets, these preliminary results provide strong evidence that expected program usage can be a useful indicator of long‐term maintenance cost. Copyright © 2002 John Wiley &amp; Sons, Ltd.</abstract><cop>Chichester, UK</cop><pub>John Wiley &amp; Sons, Ltd</pub><doi>10.1002/smr.256</doi><tpages>18</tpages></addata></record>
fulltext fulltext
identifier ISSN: 1532-060X
ispartof Journal of software maintenance and evolution, 2002-11, Vol.14 (6), p.429-446
issn 1532-060X
1532-0618
language eng
recordid cdi_proquest_miscellaneous_1671458892
source Wiley
subjects amount of maintenance
Computer programs
engineering applications
Indicators
Legacy
Maintenance
maintenance cost drivers
Maintenance costs
Organizations
Software
software evolution
software metrics
software usage
Vibration
title Identifying high maintenance legacy software
url https://sfx.bib-bvb.de/sfx_tum?ctx_ver=Z39.88-2004&ctx_enc=info:ofi/enc:UTF-8&ctx_tim=2025-01-07T16%3A12%3A42IST&url_ver=Z39.88-2004&url_ctx_fmt=infofi/fmt:kev:mtx:ctx&rfr_id=info:sid/primo.exlibrisgroup.com:primo3-Article-proquest_cross&rft_val_fmt=info:ofi/fmt:kev:mtx:journal&rft.genre=article&rft.atitle=Identifying%20high%20maintenance%20legacy%20software&rft.jtitle=Journal%20of%20software%20maintenance%20and%20evolution&rft.au=Harrison,%20Matthew%20S.&rft.date=2002-11&rft.volume=14&rft.issue=6&rft.spage=429&rft.epage=446&rft.pages=429-446&rft.issn=1532-060X&rft.eissn=1532-0618&rft_id=info:doi/10.1002/smr.256&rft_dat=%3Cproquest_cross%3E1671458892%3C/proquest_cross%3E%3Curl%3E%3C/url%3E&disable_directlink=true&sfx.directlink=off&sfx.report_link=0&rft_id=info:oai/&rft_pqid=1671458892&rft_id=info:pmid/&rfr_iscdi=true