By Topic

When past solutions cause future problems [Year 2000 problem]

Sign In

Cookies must be enabled to login.After enabling cookies , please use refresh or reload or ctrl+f5 on the browser for the login options.

Formats Non-Member Member
$31 $13
Learn how you can qualify for the best price for this item!
Become an IEEE Member or Subscribe to
IEEE Xplore for exclusive pricing!
close button

puzzle piece

IEEE membership options for an individual and IEEE Xplore subscriptions for an organization offer the most affordable access to essential journal articles, conference papers, standards, eBooks, and eLearning courses.

Learn more about:

IEEE membership

IEEE Xplore subscriptions

1 Author(s)

Currently, a worldwide effort is underway to uncover the calendar-related programs embedded in our legacy software. When these applications were first coded, had programmers rigorously and repeatedly questioned how their code handled date validity, the Year 2000 problem-the largest crisis the information technology industry has yet faced-could have been greatly mitigated. Most code lasts for longer than its original programmers anticipated, and sometimes even outlives successive generations of hardware and operating systems. Not surprisingly, when this legacy code is ported to a new environment, inherited solutions cause new problems. The author suggests several techniques for avoiding or resolving these issues

Published in:

Software, IEEE  (Volume:14 ,  Issue: 5 )