Changes

The '''Y2K problem''' is a problem in computer hardware and software programming where unintended results may take place if a year represented as two digits is not interpreted correctly.  There are two basic aspects to the Y2K problem:<br />  - Determining the correct value of a 2-digit year.  ''Example - does "20" represent 1920 or 2020?''<br />  - Performing date-based calculations correctly.  ''Example - if you subtract "97" (1997) from "07" (2007), will you get 10 years, or minus 90?''

The '''Y2K problem''' is a problem in [[computer]] [[hardware]] and [[software]] [[programming]] where unintended results may take place if a year represented as two digits is not interpreted correctly.  There are two basic aspects to the Y2K problem:<br />  - Determining the correct value of a 2-digit year.  ''Example - does "20" represent 1920 or 2020?''<br />  - Performing date-based calculations correctly.  ''Example - if you subtract "97" (1997) from "07" (2007), will you get 10 years, or minus 90?''

The origins of the problem lie in the high cost of data storage in the early days of computing, where  storing a date in 6 digits (mmddyy) versus 8 (mmddyyyy) could result in significant savings depending on volume.  If the specifications for a piece of software were well-designed this is not a problem, but in many cases the century component of a 2-digit year was assumed instead of being explicitly accounted for in programming.

The origins of the problem lie in the high cost of data storage in the early days of computing, where  storing a date in 6 digits (mmddyy) versus 8 (mmddyyyy) could result in significant savings depending on volume.  If the specifications for a piece of software were well-designed this is not a problem, but in many cases the century component of a 2-digit year was assumed instead of being explicitly accounted for in programming.

Since Y2K analysis and remediation usually involves repeated testing of the same set of code, many companies and government agencies developed and/or improved their competency in software quality assurance.   

Since Y2K analysis and remediation usually involves repeated testing of the same set of code, many companies and government agencies developed and/or improved their competency in software quality assurance.   

The shortage of programmers trained in legacy languages like COBOL in the late 1990's provided an opportunity for companies in low-cost nations like India to offer outsourcing services to new markets.  Companies found that commodity-type assignments like Y2K remediation were a good fit for offshore outsourcing under these circumstances.  <ref>http://www.lib.utk.edu/news/readyfortheworld/archives/the_world_is_flat/001189.html</ref>The momentum in using offshore programming continued and accelerated after January 1, 2000 had passed.

The shortage of programmers trained in legacy languages like [[COBOL]] in the late 1990's provided an opportunity for companies in low-cost nations like India to offer outsourcing services to new markets.  Companies found that commodity-type assignments like Y2K remediation were a good fit for offshore outsourcing under these circumstances.  <ref>http://www.lib.utk.edu/news/readyfortheworld/archives/the_world_is_flat/001189.html</ref>The momentum in using offshore programming continued and accelerated after January 1, 2000 had passed.

==Notes==

==Notes==

{{reflist}}

{{reflist}}