REFERENCES
Alexander, Christopher. 1964. Notes on the synthesis of form. Cambridge: Harvard University Press.
Ambrose, Brig. Gen. Gary A. 1999. Top 10 tips for handling Y2K. Air Force News. August 4.
Anderson, Mark C., Rajiv D. Banker, and Sury Ravindran. 2006. Value Implications of Investments in Information Technology. Management Science. 52(9): 1359–1376. September.
Ashton, Thomas V. 1998. Year 2000 certification: Air Force tenets to success. Crossfire: The Journal of Defense Software Engineering. August.
Barr, Stephen. 1997. “Year 2000” Report Flunks 3 Agencies, Lawmakers Urge Special Aide to Handle Looming Computer Problem. The Washington Post. September 16.
Bennington, Herbert D. 1983. Production of large computer programs. IEEE Annals of the History of Computing. 5(4): 350–361. October–December.
Benson, Robert L. 2001. The Venona Story. National Security Agency.
Bertalanffy, Ludwig Von. 1976. General System Theory: Foundations, Development, Applications. New York: George Braziller.
Brooks, Frederick. 1995. The mythical man-month: Essays on software engineering. Reading, Mass.: Addison-Wesley Publishing Company. 20th anniversary edition.
CCRP (Common Controls Replacement Project). 1999. CCRP Statement on Year 2000 Compliance. March.
Collins, James. 2001. Good to great: Why some companies make the leap–and others don't. New York: HarperBusiness.
Corcoran, Elizabeth. 1998. Inside Microsoft: An edgy, driven world. The Washington Post. October 18.
Davenport, Thomas H. 1997. Information Ecology: Mastering the Information and Knowledge Environment. New York: Oxford University Press USA.
Demarco, Tom, and Timothy Lister. 1999. Peopleware: Productive projects and teams. 2nd edition. New York: Dorset House Publishing Company.
EOP (Executive Office of the President). 1998a. Protecting America’s Critical Infrastructure: Presidential Decision Directive 63. May 22.
EOP (Executive Office of the President). 1998b. White Paper: The Clinton Administration’s Policy on Critical Infrastructure Protection: Presidential Decision Directive 63. May 22.
FAC (Federal Acquisition Circular). 1997. FAC No. 97-01. August 22.
Farrell, Chris, Ochen Kaylan, and Catherine Winter. 2004. The Surprising Legacy of Y2K. Radio broadcast and website. American RadioWorks. Accessed online March 6, 2006 (http://americanradioworks.publicradio.org/features/y2k/index.html).
GAO (General Accounting Office). 2000. Year 2000 Computing Challenge: Lessons Learned Can Be Applied to Other Management Challenges. GAO/AIMD-00-290. September.
GAO (General Accounting Office). 1999. Defense Computers: DOD Y2K Functional End-to-End Testing Progress and Test Event Management (Letter Report). GAO/AIMD-00-12. October.
GAO (General Accounting Office). 1998a. Military Readiness: Reports to Congress Provide Few Details on Deficiencies and Solutions. GAO/NSIAD-98-68. March.
GAO (General Accounting Office). 1998b. Year 2000 Computing Crisis: Business Continuity and Contingency Planning. GAO/AIMD-10.1.19. August.
GAO (General Accounting Office). 1998c. Year 2000 Computing Crisis: A Testing Guide. GAO/AIMD-10.1.21. November.
GAO (General Accounting Office). 1997. Year 2000 Computing Crisis: An Assessment Guide. GAO/AIMD-10.1.14. September.
Gharajedaghi, Jamshid. 1999. Systems Thinking: Managing Chaos and Complexity. Oxford, United Kingdom: Butterworth-Heinemann.
Hughes, Thomas P. 1998. Rescuing Prometheus: Four monumental projects that changed the modern world. New York: Pantheon Books.
IEEE (Institute of Electrical and Electronics Engineers). 1999. Year 2000 Technical Information Statement. July 30.
IEEE (Institute of Electrical and Electronics Engineers). 1998. The Y2K date problem: A bad moon rising. The Institute. February.
Isaacs, Charles. 1999. The Value of Leveraging Y2K Inventory Information for Corporate Risk Management and Model-Based Contingency Planning. Information Systems Frontiers. 1:2 (163-172). August.
ITMRA (Information Technology Management Reform Act) of 1996. Pub. L. No. 104-106. Section 5125.
Kling, Rob. 1999. What Is Social Informatics and Why Does It Matter? D-Lib Magazine. 5:1. January. Accessed online March 6, 2007 (http://www.dlib.org/dlib/january99/kling/01kling.html).
Kling, Rob, and Walter Scacchi. 1982. The Web of Computing: Computer Technology as Social Organization. In Yovits, Marshall, editor, Advances in Computers, 21, 1–90. New York: Academic Press.
Leveson, Nancy G. 1994. High pressure steam engines and computers. IEEE Computer. 27(10): 65–73. October.
LMIS (Lockheed Martin Information Systems). 1999. Year 2000 Issues. Statement accessed on company website during 1999.
Malhotra, Yogesh. 1993. Role of Information Technology in Managing Organizational Change and Organizational Interdependence. Brint Institute. Accessed online May 18, 2006 (http://www.brint.com/papers/change/).
Marcoccia, Louis J. 1998. Building Infrastructure for Fixing the Year 2000 Bug: A Case Study. Journal of Software Maintenance: Research and Practice. 10(5): 333–325. September–October.
McCartney, Laton. 2001. Trends: Change agents. CIO Insight. May 1. Accessed online May 18, 2006 (http://www.cioinsight.com/article2/0,1397,1438214,00.asp).
Mercado, Rachel C. 1999. Yale–New Haven Hospital Remediation Plan: Medical Devices and the Year 2000. Journal of Clinical Engineering. 24(4): 16–22. July–August.
Mussington, David. 2002. Concepts for Enhancing Critical Infrastructure Protection: Relating Y2K to CIP Research and Development. Santa Monica, Calif.: RAND.
Newsweek. 1997. The day the world shuts down (cover story). June 2.
OMB (Office of Management and Budget). 1997. Year 2000 Interagency Committee Best Practices Guide. Draft document.
Ornstein, Robert E. 1975. The Psychology of Consciousness. Gretna, La.: Pelican Books.
Paterno, Fabiano, and Cristiano Mancini. 1998. Developing adaptable hypermedia. In Proceedings of the 4th international conference on intelligent user interfaces. New York: ACM Press.
PCCIP (President’s Commission on Critical Infrastructure Protection). 1997. Critical Foundations: Protecting America’s Infrastructures. Washington, DC: U.S. Government Printing Office. October.
Peters, F. Whitten. 2000. Remarks by the Secretary of the Air Force at the American Institute of Aeronautics and Astronautics International Global Air and Space 2000 Forum on Future Space in the Military. May 12.
QLogic Corporation. 1999. Y2K compliance statement, Version 1.1. Accessed on company website during 1999.
Rosenberg, Eric. 2001. Studies of Gulf War reveal U.S. military deficiencies. Seattle Post-Intelligencer. January 18.
SAGE. 2006. SAGE website. Accessed online May 14, 2006 (http://www.sage.org/field/).
SAGE. 2000. SAGE System Administrator Salary Profile 1999. Berkeley, Calif.
Standish Group. 1994. The chaos report. West Yarmouth, Mass. Accessed online May 18, 2006 (http://www.standishgroup.com/sample_research/chaos_1994_1.php).
USAF (United States Air Force). 2000a. Air Force Year 2000 Final Report.
USAF (United States Air Force). 2000b. Global vigilance reach & power: America's Air Force Vision 2020. Washington, DC.
USAF (United States Air Force). 2000c. Air Force Policy Letter Digest. April.
USAF (United States Air Force). 1999a. Air Force Critical Infrastructure Program, Air Force Policy Directive 10-24. December 1.
USAF (United States Air Force). 1999b. Air Force Assessment Master Plan for Operations in the Year 2000. May 15.
USAF (United States Air Force). 1997. Air Force Communications Agency Year 2000 Guidance Package. April 1.
U.S.-Canada Power System Outage Task Force. 2004. Final Report on the August 14, 2003, Blackout in the United States and Canada: Causes and Recommendations. April.
USA Today Tech Report. 1997. For some computers 2000 will never come. August 22.
Weill, Peter, and Marianne Broadbent. 1998. Leveraging the New Infrastructure. Boston, Mass.: Harvard Business School Press.
Weinraub, Mark. 2001. NASDAQ fixes system but traders struggle. Reuters. July 2.
Wick, Corey. 2000. Knowledge management and leadership opportunities for technical communicators. Technical Communication. 47(4): 515–529. November.
Y2K Act. 1999. Pub. L. No. 106-37.
