| Y2K baseline inventory |
An initial inventory of system data using 54 of 108 data elements identified by the Air Force Year 2000 Working Group.
|
| Y2K Challenge |
The challenge to an institution to respond to the Y2K problem.
|
| Y2K compliant |
Tested and proven capable of correct identification, manipulation, and calculation using dates outside the range of 1900-1999; or not dependent on dates in order to function.
|
| Y2K event horizon |
The year a system is expected to experience Year 2000-related problems
as a result of date projections.
|
| Y2K noncompliant |
Tested and proven not capable of reliably using dates outside the range of 1900-1999.
|
| Y2K OK |
Ready for the Year 2000.
|
| Y2K readiness plan |
A detailed plan for bringing an organization’s system into Y2K compliance.
|
| Y2K ready |
This expression has been used with several different, and contradictory, meanings: 1. Y2K compliant. 2. Ready for Y2K, but not necessarily Y2K compliant; implies the organization has contingency plans in case computer systems fail. 3. Able to handle date manipulation and store four-digit dates, but not requiring the user to enter a four-digit year.
|
| Y2P |
Year 2000 Problem. In the 1980s and before, most computer programs were designed to store only the last two digits of the years on all dates. When the Year 2000 comes, these programs will show dates of 00, which may be interpreted the same as 1900. This discrepancy may cause widespread problems, especially in the large computer systems used in government and big industries. Efforts to correct the problem before 2000 may be too late.
|
| Year 2000 compliant |
Tested and proven capable of correct identification, manipulation, and calculation using dates outside the range of 1900-1999; or not dependent on dates in order to function.
|
| Year 2000 noncompliant |
Tested and proven not capable of reliably using dates outside the range of 1900-1999.
|
| Year 2000 Problem |
(Y2P). In the 1980s and before, most computer programs were designed to store only the last two digits of the years on all dates. When the Year 2000 comes, these programs will show dates of 00, which may be interpreted the same as 1900. This discrepancy may cause widespread problems, especially in the large computer systems used in government and big industries. Efforts to correct the problem before 2000 may be too late.
|
| Year 2000 readiness plan |
A detailed plan by which an organization will bring its computer systems into Year 2000 compliance. The phases of such a plan must include planning, assessment, remediation, testing, further corrections as necessary, and testing again until the system is fully Y2K compliant.
|
| Year 2000 remediation |
The process of revising a system to make it Year 2000 compliant.
|
| Year 2000 scoping |
An assessment of the time, money, and other resources necessary to bring all systems in an enterprise into Year 2000 compliance.
|
| Year 2000 transition |
The revision of a system and its programs so it can correctly process dates outside the range of 1900-1999.
|
| YMARK2000 |
A testing tool for Year 2000 compliance from NSTL.
|
| YY |
A two-digit-year date format; for example, 95 for 1995.
|
| YYYY |
A four-digit-year date format; for example, 1995 for 1995.
|
