Y2k 5 Essay, Research Paper

*Using a 100-year logic window

The logic window attack allows the system to find the century or decennary of a given twelvemonth 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 progress. This technique does necessitate some excess disbursement and codification logic that must be matched to this two figure day of the month to guarantee that all calculations are performed right. But, despite this excess operating expense, this attack avoids monolithic interorganizational alterations and if the applications in the company do non cover with informations that is more than 100 old ages apart, this attack may be really attractive to many companies.

*Employing a information span that uses a logic window

This widely used solution converts the application to a four-digit twelvemonth without altering the biennial format for the external interfaces.

*Reversing the system clock and utilizing a 28-year clip span

By either adding or deducting 28 old ages to the system clock, one can retain the same yearss of the hebdomad and month. This attack, though, is merely good for periods that have a leap twelvemonth every four old ages, and therefore is attack merely works until 28 February 2100.

*Replacing the system ( including retiring it )

For some companies it is a more executable solution to replace the bing systems with y2k safe merchandises or merge with companies that already have y2k safe systems and retire their ain systems instead than trying to alter their bing systems.

*Doing nil at all

The concluding option is to make nil at all. This does non intend to disregard the job, but instead it means that the Y2K hazard should be earnestly analyzed to see whether the jobs caused would be really important, or if any jobs will be at all. If the jobs are minor, so a company has the option of non passing its full system but instead learn its employees to work around these jobs.

Analysis

The upgrading of computing machine systems to get by with the reaching of the Millennium is showing one of the most important challenges the IT community has had to face. Companies are holding to come to footings with the possible prostration of their systems because of a simple day of the month alteration. The force per unit area on computing machine sections to cut down the impact of this quandary on budgets and work load is considerable.

Expanding the twelvemonth field to four figures seems like a really feasible solution. Although it is apprehensible that it will necessitate a batch of clip and particularly a batch of money for the company, I believe that if the company has the money to implement this sort of solution, it will pay off in the long tally. After a company analyzes the possible jobs to be wreaked on computing machine systems on 1 January 2000, and if the possible jobs would be sedate and legion, so I believe that the same company should earnestly see spread outing the twelvemonth field to four figures. The company should besides guarantee that they change the logic assessing, for if they don t so the revised system will pervert. But, if the carbon monoxide

mpany protects itself against the system perverting itself so this attack is the most complete and thorough solution if the company can afford it, and moreover the system will run right for the following 2,600 old ages.

Another solution offered by the article is the usage of Logic Windows, in which a sliding window is used and this skiding window can be sporadically advanced as needed. Furthermore, users can be notified when the window is about to progress. I believe this option is a really good solution besides, if spread outing the twelvemonth field to four figures is excessively expensive for a company. Although this solution is besides dearly-won and requires cost logic, it avoids the mass changes that the enlargement attack requires. This attack is really attractive to companies since it requires no information alterations. So if a company s applications don t trade with informations that is more than 100 old ages apart and if that same company doesn T have the money needed to finance spread outing the twelvemonth field to four figures, so I believe this solution is the best.

A company can besides change by reversal the system clock and utilize a 28 twelvemonth clip span, when 28 old ages are either added or subtracted to the system clock. Although this attack is good for systems that no longer hold the beginning codification, can non recompile the beginning codification, or have purchased constituents that are non century ready, it is merely a impermanent solution, because this attack merely works for periods that have a leap twelvemonth every four old ages. And since this attack is merely good until 28 February 2100, so a company may be once more faced with the same Y2K jobs and have to reconstitute its system a 2nd clip. So, although I believe that this solution is a good impermanent solution, I think that the first two solutions are better because they offer longer & # 8211 ; term solutions for a company s information systems.

I believe that unifying with or purchasing a company that has y2k safe systems and retiring their ain is a solution that may non be feasible for smaller companies. Smaller companies can non afford to purchase another company and meeting may non be possible for more specialised companies. Therefore, this solution is non applicable for all companies.

Finally, the solution of non making anything at all is besides a good 1. For some companies, the jobs posed by the Y2K hazard are minor, and a major inspection and repair of the information systems is non necessary. In fact, the company could happen itself passing a batch of money on passing its systems for a hazard that may non truly impact them at all. If a company right and exhaustively analyzes the hazard posed by Y2Ks and they find that the hazards are minor, so it could pass a significantly smaller sum of money in merely developing its forces on how to work around the minor jobs in their systems. Therefore, this solution is evidently the best if the company finds that the jobs they encounter on 1 January 2000 will be little and comparatively inconsequential.

In decision, this article poses many feasible solutions to the Y2K job. The initial measure for any company, though, is for it to thoroughly analyze the jobs it will confront in January 2000. Once that measure is right completed, so the company can implement whatever solutions prove to be the best for their systems.