Greetings,

I'd like to find statistics (if they exist) of how much time and money
is lost to US companies each year due to:
* Engineers having to work around ugly legacy code
* Team members having to work with buggy or outmoded in-house tools
* Time that could have been saved if someone had been given time to
write an in-house tool.

< According to the Standish Group, last year, $382 billion was spent
in the USA on software development.
http://metric.cse.unsw.edu.au/Metrics2003/keynotes02.html

According to the Gartner Group 60% to 80% of the average annual IT
application development budget is spent on reengineering legacy
applications.
http://216.239.51.104/search?q=cache:nCHs7-4bRkoJ:www.seec.com/investor_pdf/10k-1999.pdf+%22legacy+code%22++%22development+budget%22+&hl=en&ie=UTF-8

A study by the Research Triangle Institute (RTI) found software
developers spend approximately 80 percent of development costs on
identifying and correcting defects.  The cost to U.S. industry of
buggy software is an estimated $59.5 billion.
http://www.nist.gov/public_affairs/releases/n02-10.htm

This means that for software developers the annual cost of
reengineering legacy codes is between $229.2 and $305.6 billion. If
the cost to end users is added in the cost to U.S. companies is
between $299.7 and $365.1 billion.

In 2002 a Caper Jones study found that software is released with 15
percent of original faults remaining. Companies spent 44 percent of
their time reworking software.
http://216.239.51.104/search?q=cache:-vBcK1fkI-gJ:www.sao.org/newsletter/pdfs/jul03/Doug_Mendenhall_0703.pdf+%22is+spent%22+%22software+development%22+billion+2002+industry&hl=en&ie=UTF-8

An article by Federico Zoufaly discusses the issues and challenges
facing legacy systems. Around 80% of IT systems are running on legacy
platforms. International Data Corp. estimates that 200 billion lines
of legacy code are still in use today on more than 10,000 large
mainframe sites. A December 2001 study by the Hurwitz Group that found
only 10% of enterprises have fully integrated their most
mission-critical business processes.
D
riving the need for change is the cost versus the business value of
legacy systems, which according to some industry polls represent as
much as 85-90% of an IT budget for operation and maintenance.

Studies show that 50-90% of the time spent in re-engineering software
systems is used to understand these systems.
http://www.cas.ibm.com/archives/1998/workshops/legacy.html

The cost of maintaining software and managing its evolution now
represents over 90% of its cost.
http://www.sei.cmu.edu/cbs/mls/mls.htm

A study into how software engineers spend their time shows that they
spent 57% of their time fixing bugs.
http://216.239.51.104/search?q=cache:oqNp2bEqwsYJ:www.site.uottawa.ca/~tcl/papers/Cascon/Cascon97MergedPages.ps+%22legacy+code%22+bugs+%22their+time%22+engineers&hl=en&ie=UTF-8

Development time is cut by 50% by using tools to deal with legacy
code. The market for tools to deal with legacy code could be worth
over $100 billion over the next ten years.
http://www.relativity.com/News/coverage/Forbes-CrackingCode.htm

Software engineers spend more time understanding existing code that
they do designing, programming, testing or debugging.
http://216.239.51.104/search?q=cache:M5DpSfhQpjwJ:www.cobolexpo.com/cx2002/proceedings/proceedings/(061702)%2520(321)%2520Nexxit%2520COBOL%2520Expo.doc+%22rewriting+legacy+code%22++%22development+time%22&hl=en&ie=UTF-8

According to a report by Jim Morgan the global market for application
modernization tools and services is worth over $50 billion. The U.S.
market accounts for seventy percent or $35 billion.
http://216.239.51.104/search?q=cache:M5DpSfhQpjwJ:www.cobolexpo.com/cx2002/proceedings/proceedings/(061702)%2520(321)%2520Nexxit%2520COBOL%2520Expo.doc+%22companies%22+billion+%22legacy+code%22+costs&hl=en&ie=UTF-8

Spending $313,000 on a tool to analyze legacy code saved one company
$2.5 million.
http://www.informationweek.com/753/legacy.htm >


<Additional links:>

<Times taken to alter code can be drastically reduced by using a tool
to analyze legacy codes.>
<http://www.softwarerevolution.com/technology1.html>

<Issues and challenges facing Legacy Systems.>
<http://www.developer.com/java/article.php/1492531>

<IBM introduces a cure for spaghetti code.>
<http://www.midrangeserver.com/tfh/tfh041403-story03.html>

<Hurwitz report.>
<http://216.239.37.104/search?q=cache:gDiei_jNECcJ:www.adtools.com/info/whitepaper/moving_cobol_to.net.pdf+%22legacy+code%22+%22companies%22+hours+development&hl=en&ie=UTF-8>

<Case study – tools used to analyze legacy code in air force
software.>
<http://www.relativity.com/airforce.htm>

<Case study – Blue Cross Blue Shield FEP>
<http://www.relativity.com/bluecross.htm>


<Search strategy:>

<"legacy code" hours "development budget">
<://www.google.com/search?hl=en&lr=&ie=ISO-8859-1&q=+%22legacy+code%22+hours+%22development+budget%22>

<2003 "legacy code" development time>
<://www.google.com/search?hl=en&lr=&ie=ISO-8859-1&q=2003+%22legacy+code%22&as_q=development+time>

<usa"software development" billion>
<://www.google.com/search?hl=en&lr=&ie=ISO-8859-1&q=usa%22software+development%22+billion+>

<"legacy code" "standish group">
<://www.google.com/search?q=%22legacy+code%22+%22standish+group%22&hl=en&lr=&ie=UTF-8&start=10&sa=N>

<"legacy code" "gartner" 2003 time bugs>
<://www.google.com/search?q=%22legacy+code%22+%22gartner%22+2003+time+bugs&hl=en&lr=&ie=UTF-8&start=10&sa=N>

<"legacy code"  "engineers spend" debugging>
<://www.google.com/search?q=%22legacy+code%22++%22engineers+spend%22+debugging&hl=en&lr=&ie=ISO-8859-1>


<Hope this helps.>