Resumen
This article describes the seven work plans for Year-2000 (Y2K) software upgrade projects. The seven approaches are pruning the business, waiting, replacing the application by a purchase or new build, expanding YY year fields to YYYY, using other "intelligent" digits, dating window(s) and date-shifting of code or data. All seven approaches are easy to understand, especially waiting. Part of the triage approach should be to determine which functions or programs can safely be ignored until next decade because their shortcomings will be cosmetic at worst. At the opposite end of "do nothing" are systems absolutely critical to the business but have a truly prohibitive Y2K compliance cost. If the company will become unprofitable due to that outlay, consider shutting it down or selling it. The third approach could modernize the business, but the users would not be able to regression-test incrementally. The fourth method is the most appealing and elegant Y2K date-fix approach. One can make similar changes to keep up with industry-wide formats. But time is short and resources limited to expand all to YYYY.