Y2k 5 Essay, Research Paper
*Using a 100-year logic window
The logic window approach allows the system to determine the century or decade of a given year by comparing the value of the two digit field against an application window. One version of this technique allows for a sliding window, in which one changes the boundaries of the window and the user is notified when the window is about to advance. This technique does require some extra spending and code logic that must be matched to this two digit date to ensure that all computations are performed correctly. But, despite this extra overhead, this approach avoids massive interorganizational changes and if the applications in the company do not deal with data that is more than 100 years apart, this approach may be very attractive to many companies.
*Employing a data bridge that uses a logic window
This widely used solution converts the application to a four-digit year without changing the two-year format for the external interfaces.
*Reversing the system clock and using a 28-year time bridge
By either adding or subtracting 28 years to the system clock, one can retain the same days of the week and month. This approach, though, is only good for periods that have a leap year every four years, and thus is approach only works until 28 February 2100.
*Replacing the system (including retiring it)
For some companies it is a more feasible solution to replace the existing systems with y2k safe products or merge with companies that already have y2k safe systems and retire their own systems rather than attempting to change their existing systems.
*Doing nothing at all
The final option is to do nothing at all. This does not mean to ignore the problem, but rather it means that the y2k risk should be seriously analyzed to see whether the problems caused would be very significant, or if any problems will exist at all. If the problems are minor, then a company has the option of not overhauling its entire system but rather teach its employees to work around these problems.
The upgrading of computer systems to cope with the arrival of the Millennium is presenting one of the most significant challenges the IT community has had to face. Companies are having to come to terms with the possible collapse of their systems because of a simple date change. The pressure on computer departments to reduce the impact of this predicament on budgets and workload is considerable.
Expanding the year field to four digits seems like a very viable solution. Although it is understandable that it will require a lot of time and especially a lot of money for the company, I believe that if the company has the money to implement this kind of solution, it will pay off in the long run. After a company analyzes the possible problems to be wreaked on computer systems on 1 January 2000, and if the possible problems would be grave and numerous, then I believe that the same company should seriously consider expanding the year field to four digits. The company should also ensure that they change the logic assessing, for if they don t then the revised system will corrupt. But, if the company protects itself against the system corrupting itself then this approach is the most complete and thorough solution if the company can afford it, and furthermore the system will operate correctly for the next 2,600 years.
Another solution offered by the article is the use of Logic Windows, in which a sliding window is used and this sliding window can be periodically advanced as needed. Furthermore, users can be notified when the window is about to advance. I believe this option is a very good solution also, if expanding the year field to four digits is too expensive for a company. Although this solution is also costly and requires cost logic, it avoids the mass changes that the expansion approach requires. This approach is very attractive to companies since it requires no data changes. So if a company s applications don t deal with data that is more than 100 years apart and if that same company doesn t have the money needed to finance expanding the year field to four digits, then I believe this solution is the best.
A company can also reverse the system clock and use a 28 year time bridge, when 28 years are either added or subtracted to the system clock. Although this approach is good for systems that no longer have the source code, cannot recompile the source code, or have purchased components that are not century ready, it is only a temporary solution, because this approach only works for periods that have a leap year every four years. And since this approach is only good until 28 February 2100, then a company may be again faced with the same y2k problems and have to restructure its system a second time. So, although I believe that this solution is a good temporary solution, I think that the first two solutions are better because they offer longer – term solutions for a company s information systems.
I believe that merging with or buying a company that has y2k safe systems and retiring their own is a solution that may not be viable for smaller companies. Smaller companies cannot afford to buy another company and merging may not be possible for more specialized companies. Thus, this solution is not applicable for all companies.
Finally, the solution of not doing anything at all is also a good one. For some companies, the problems posed by the y2k risk are minor, and a major overhaul of the information systems is not necessary. In fact, the company could find itself spending a lot of money on overhauling its systems for a risk that may not really affect them at all. If a company correctly and thoroughly analyzes the risk posed by y2k and they find that the risks are minor, then it could spend a significantly smaller amount of money in simply training its personnel on how to work around the minor problems in their systems. Thus, this solution is obviously the best if the company finds that the problems they encounter on 1 January 2000 will be small and relatively inconsequential.
In conclusion, this article poses many viable solutions to the y2k problem. The initial step for any company, though , is for it to thoroughly analyze the problems it will face in January 2000. Once that step is correctly completed, then the company can implement whatever solutions prove to be the best for their systems.