Y2K1
T h e Y e a r 2 0 0 0 P r o b l e m Argument for the statement "The Year 2000 bug will have such extensive repercussions that families and individuals should begin planning now for the imminent chaos." The Ticking Bomb Introduction A serious problem called the "Millennium Bug", and also known as the "Year 2000 Problem" and "Y2K", is bringing a new century celebration into a daunting nightmare. In the 1860s and 1970s, when computer systems were first built, the computer hardware, especially information storage space, was at a premium. With an effort to minimise storage costs, numeric storage spaces were drained to the smallest possible data type. Ignoring the fact that software may be run in multiple centuries, programmers started conserving storage spaces by using two digits to specify a year, rather than four. Consequently, on January 1, 2000, unless the software is corrected, most software programs with date or time may malfunction or may not recognize the entries in the year fields "00" as the year as "1900" instead of "2000" . Year 2000 problem is not restricted only to the above exigency. 20 years ago, everybody understood that a leap year came every 4th year except for every 100th year. However, a piece of algorithm
has been forgotten by most people - a leap year does exist every 400 years. A Year 2000 compliant computer system may fail to process, produce error messages or generate incorrect data even if it receives contaminated programs or data from a third party that is not Year 2000 compliant. Documentation showing the processing steps being performed by the company's computer system in order to accomplish business functions needs to be available to ensure that all procedures are present and accounted for. A case in point, a typical medium size organisation, a state comptroller's office in United States, is predicted to spend US$5. So, the standard flaw lurks in the CMOS Real Time Clock date when Year 2000 is reached as it reads an out-of-range date. Other Dilemma Implied However, to ensure that the corrected work runs free of errors after January 1, 2000 midnight, testing of the changed code must be performed. Only if companies start corrective action soon enough and devote sufficient resources to the effort can minimise the effect of this universal nightmare. Year 2000 - Making Applications Date Intelligent (1997).
Common topics in this essay:
Millennium Bug,
Consequently January,
Driving Licence,
Importantly Award,
Dilemma Six-digit,
Real Clock,
Group's CHAOS,
Hardware Dilemma,
Dilemma Implied,
Calculated Age,
millennium bug,
date fields,
current date,
cmos real,
date birth,
computer system,
real clock,
cmos real clock,
current date birth,
january 1,
birth date,
computer systems,
date birth date,
january 1 2000,
date system running,
|
Acceptance Essays
