moinsen / Software historyDE ↗
← 2000

Event

Der Jahreswechsel als Softwaretest

Context and research status
  • Kennung: 2000-jahr-2000-problem
  • Zeitraum: 1999–2000
  • Datumsgenauigkeit: Jahr, sofern im Text nicht genauer / year unless specified in text
  • Art: historische Entwicklung / historical development
  • Kategorien: Wandel und Einflussfaktoren, Ereignisse
  • Akteure und Rollen: Unternehmen und Behörden: Anpassung bestehender Software
  • Region: International

Many older programs used two-digit years. When the year changed to 2000, dates could be interpreted incorrectly; many programs had been adjusted beforehand. Source

In 1997 the US Government Accountability Office’s predecessor recommended inventorying critical systems, planning conversions and thorough testing; its examples of failures were warning scenarios. The UK Department of Trade and Industry later reported no material Y2K-related disruption in its own operations over the rollover. It reported £3.5 million for centrally coordinated corrections, including advice and contingency planning. A single departmental account is not a worldwide assessment. Sources

As of 15 September 1999, the US Department of Justice estimated its Year 2000 work would cost US$165 million, including US$118 million for mission-critical IT systems. Its report describes validation and contingency planning. These figures are an agency estimate at that time, not final or worldwide costs. Department report

One observed error affected reports at US Social Security field offices: one zero in the year 2000 was suppressed. According to the audit, the agency reported correcting it by 15 January 2000 and considered the incident insignificant. February 29 was another separately tested date; the agency reported no processing problems that day. Audit report

Sources

Offen

Weitere Ereignisse, Einflussfaktoren und unabhängige Einordnung sind zu recherchieren. / Further events, influences and independent context remain to be researched.