Risk 2000
Contenido multimedia no disponible por derechos de autor o por acceso restringido. Contacte con la institución para más información.
| Tag | 1 | 2 | Value |
|---|---|---|---|
| LDR | 00000nab a2200000 i 4500 | ||
| 001 | MAP20071030047 | ||
| 003 | MAP | ||
| 005 | 20080418122012.0 | ||
| 007 | hzruuu---uuuu | ||
| 008 | 980424e19970401usa|||| | |00010|eng d | ||
| 040 | $aMAP$bspa | ||
| 084 | $a936 | ||
| 100 | 1 | $0MAPA20080237585$aBaker, Pamela Smith | |
| 245 | 1 | 0 | $aRisk 2000$cby Pamela Smith Baker |
| 520 | $aThe year 2000 problem is the result of the method used by most computer programmers to code dates used in computer legacy systems. When computer technology was young and memory space was very limited, every line of program space was very limited, every line of program space written was precious. Conserving memory was imperative, so computer programmers coded calendar dating systems usin MM-DD-YY (month, day, year), the shortest method available. As the memory capacity of computers grew, many programmers continued to use the six-digit dating system out of habit. Others did not anticipate that the software they were creating would las into the next millennium. Whatever the reason for continuing to use a six-digit code, it is now apparent that not many programmers or users realized the system would not work for the year 2000. When December 31. 1999 turns into January 1, 2000 most computer programs around the globe will read 01-01-00 and immediately assume that the year is 1900 | ||
| 650 | 1 | 1 | $0MAPA20080608118$aProgramas informáticos |
| 650 | 1 | 1 | $0MAPA20080630584$aSistemas controlados por ordenador |
| 650 | 1 | 1 | $0MAPA20080543488$aCódigos |
| 650 | 1 | 1 | $0MAPA20080557393$aCalendarios |
| 650 | 1 | 1 | $0MAPA20080588953$aAnálisis de riesgos |
| 650 | 1 | 1 | $0MAPA20080591182$aGerencia de riesgos |
| 650 | 1 | 1 | $0MAPA20080546991$aEmpresas |
| 740 | 0 | $aRisk management | |
| 773 | 0 | $tRisk management$dNew York$gnº 4, April 1997 ; p. 55-58 |