The year 2000 problem results from the use of two digit year fields in computer systems instead of four. If systems are not corrected to become year 2000 compliant, many significant problems could result. For example, a bank program could calculate the time period for a 30 year mortgage begun in 1996 to be in negative years based on the subtraction 26-96. Any computer system that makes use of dates is potentially at risk, and that is most of them. The cost and scope of correcting this problem is staggering.
Most large organizations have millions of lines of program code affected.
Given the vast effort required for a year 2000 conversion and the disappointing progress made by many organizations to date on this issue, some experts have predicted disastrous consequences. The year 2000 issue clearly presents an important business challenge since the very survival of organizations may depend on it. While it should be recognized that general codes of conduct such as this are subject to different interpretations by different people who have good intentions, at least several provisions of the ACM code suggest that systems developers may have an ethical obligation to act on the year 2000 problem. If one's superiors do not act to curtail or mitigate such dangers, it may be necessary to 'blow the whistle' to help correct the problem or reduce the risk. Code of Ethics is a succinct code that identifies ten responsibilities of its members.