June 2010 Edition
Computer Science Department, University of Cape Town
| MIT Notes Home | Edition Home |
| MSc-IT Study Material June 2010 Edition Computer Science Department, University of Cape Town | MIT Notes Home | Edition Home | |
In the end, companies involved did a lot of checking and spend a lot of money in correcting the problem – resulting in no serious disasters. However, the question of responsibility remains. Who should pay for the cost of upgrading or modifying relevant hardware or software?
Hardware Manufacturer?
Company using the computers?
Computer Professionals who designed the system?
Professional Society?
All of the Above?
1970: 2 byte data for storing year information saved expensive space – the professionals did a good job.
1980: Same answer
1990: Same answer? Were the systems expected to last for 10 years? What is the cost of storage at this time? What is the cost of upgrading old system?
1995: Same answer? Were the systems expected to last for 5 years? Storage and upgrade cost? Should professionals warn companies of the Y2K problems? Should CSSA have a recommended code of Practice concerning this issue?
1998: Same question, different answer? Client companies all had policies. These were communicated to the shareholders and everyone accepted their responsibilities.
So it has been a lesson. The best strategy is:
State clearly the role responsibilities of all concerned. Professional needed to explain and document the problem and then to offer options.
Make sure that all involved understood the effect of their work on humans. Clients needed to understand available options – they needed to realise that the option of staying with 2 digits was short-term and unsafe.
Hold those responsible who fail to live up to their responsibility.