Libros sobre el tema "Software crisis"

1954-, Brown William J., ed. AntiPatterns: Refactoring software, architectures, and projects in crisis. New York: Wiley, 1998.

Boogaard, Martin. Defusing the software crisis: Information systems flexibility through data independence. Amsterdam: Thesis Publishers, 1994.

Hayes, Ian. The year 2000 software crisis: The continuing challenge. Upper Saddle River, N.J: Prentice Hall, 1998.

Zykov, Sergey V. Crisis Management for Software Development and Knowledge Transfer. Cham: Springer International Publishing, 2016. http://dx.doi.org/10.1007/978-3-319-42966-3.

Zykov, Sergey V. IT Crisisology: Smart Crisis Management in Software Engineering. Singapore: Springer Singapore, 2021. http://dx.doi.org/10.1007/978-981-33-4435-8.

Amuta, Adakole. The software crisis: Is ISO9001/TickiT the cure?. London: University of East London, 2003.

Malveau, Raphael C. AntiPatterns: Refactoring Software, Architectures, and Projects in Crisis. New York, New York, USA: John Wiley & Sons, 1998.

M, Ulrich William, ed. The year 2000 software crisis: The continuing challenge. Upper Saddle River, N.J: Prentice Hall PTR, 1998.

Zykov, Sergey V. Managing Software Crisis: A Smart Way to Enterprise Agility. Cham: Springer International Publishing, 2018. http://dx.doi.org/10.1007/978-3-319-77917-1.

Year 2000 software crisis: Solutions for IBM legacy systems. London: International Thomson Computer Press, 1997.

Ulrich, William M. The year 2000 software crisis: Challenge of the century. Upper Saddle River, NJ: Prentice Hall, 1997.

United States. General Accounting Office. Accounting and Information Management Division. Year 2000 computing crisis: A testing guide. Washington, D.C. (P.O. Box 37050, Washington, D.C. 20013): The Office, 1998.

United States. General Accounting Office. Accounting and Information Management Division. Year 2000 computing crisis: A testing guide. Washington, D.C. (P.O. Box 37050, Washington, D.C. 20013): The Office, 1998.

United States. General Accounting Office. Accounting and Information Management Division. Year 2000 computing crisis: An assessment guide. Washington, D.C. (P.O. Box 37050, Washington, D.C. 20013): The Office, 1997.

United States. General Accounting Office. Accounting and Information Management Division. Year 2000 computing crisis: An assessment guide. Washington, D.C: The Office, 1997.

United States. General Accounting Office. Accounting and Information Management Division. Year 2000 computing crisis: Business continuity and contingency planning. Washington, D.C: The Office, 1998.

United States. General Accounting Office. Accounting and Information Management Division. Year 2000 computing crisis: An assessment guide : exposure draft. [Washington, D.C: The Office, 1997.

Kingsley, Paul Anthony. Reuse and the software crisis: The role of the programmer's toolkit. [s.l: The author], 1991.

Jeffrey, Grant R. The millennium meltdown: The year 2000 computer crisis. Toronto, Ont: Frontier Research Publications, Inc., 1998.

J, Murray Marilyn, ed. The year 2000 computing crisis: A millennium date conversion plan. New York: McGraw-Hill, 1996.

Butler, Janet G. The year 2000 crisis: Developing a successful plan for information systems. Charleston, S.C: Computer Technology Research Corp., 1996.

Butler, Janet G. Managing the Year 2000 crisis: Strategies and solutions. Charleston, SC: Computer Technology Research Corp., 1999.

Yourdon, Edward. Time bomb 2000: What the year 2000 computer crisis means to you! 2^a ed. London: Prentice-Hall, 1999.

Yourdon, Edward. Time bomb 2000: What the year 2000 computer crisis means to you! Upper Saddle River, N.J: Prentice Hall PTR, 1998.

Bellec, Caroline. The impact of application generators on the software development crisis: The example of TELON. [S.l: The author], 1993.

Keyes, Tony. The year 2000 computer crisis: An investor's survival guide. Brookeville, MD: Y2K Investor, 1997.

Jennifer, Yourdon, ed. Time bomb 2000: What the year 2000 computer crisis means to you! 2^a ed. Upper Saddle River, N.J: Prentice Hall, 1998.

Yourdon, Edward. Time bomb 2000: What the year 2000 computer crisis means to you! Upper Saddle River, N.J: Prentice Hall PTR, 1998.

Publishers, Auerbach, ed. The year 2000: Crisis or opportunity? : getting your Y2K project off on the right foot. Boca Raton: Auerbach, 1998.

The day the phones stopped: The computer crisis-- the what and why of it, and how we can beat it. New York: Donald I. Fine, 1991.

Lee, Leonard. The day the phones stopped: The computer crisis--the what and why of it, and how we can beat it. New York: Donald I. Fine, 1991.

Jager, Peter De. Managing 00: Surviving the year 2000 computing crisis. New York: Wiley, 1997.

Chandra, Rupa. Global economic crisis and protectionism in services: Implications for India's IT-ITeS exports and the GATS. New Delhi: Indian Council for Research on International Economic Relations, 2009.

Alican, Fuat. TICs en el mundo: Una guía práctica empresarial de las tendencias globales en época de crisis. Cartago: Editorial Tecnológica de Costa Rica, 2011.

United States. General Accounting Office. y United States. Congress. House. Committee on Government Reform and Oversight. Subcommittee on Government Management, Information, and Technology., eds. Year 2000 computing crisis: Testing and other challenges confronting federal agencies : statement of Rona B. Stillman, Chief Scientist for Computers and Telecommunications, Accounting and Information Management Division, before the Subcommittee on Government Management, Information and Technology, Committee on Government Reform and Oversight, House of Representatives. Washington, D.C: The Office, 1998.

Office, General Accounting. Year 2000 computing crisis: Status of Medicare providers unknown : report to Congressional requesters. Washington, D.C. (P.O. Box 37050, Washington, D.C. 20013): The Office, 1999.

United States. General Accounting Office., United States. Congress. House. Committee on Government Reform and Oversight. Subcommittee on Government Management, Information, and Technology. y United States. Congress. House. Committee on Science. Subcommittee on Technology., eds. Year 2000 computing crisis: Strong leadership and effective public/private cooperation needed to avoid major disruptions : statement of Gene L. Dodaro, Assistant Comptroller General, Accounting and Information Management Division, before the Subcommittee on Government Management, Information and Technology, Committee on Government Reform and Oversight, and the Subcommittee on Technology, Committee on Science, House of Representatives. Washington, D.C: The Office, 1998.

Office, General Accounting. Year 2000 computing crisis: Actions needed on electronic data exchanges : report to Congressional requesters. Washington, D.C: The Office, 1998.

The software bomb. New York: St. Martin's Press, 1993.

C̆ervĕn, Pavol. Crackproof your software: The best ways to protect your software against crackers. San Francisco: No Starch Press, 2002.

United States. General Accounting Office., ed. Year 2000 computing crisis: The District of Columbia faces tremendous challenges in ensuring vital services are not disrupted : statement of Jack L. Brock, Jr., Director, Governmentwide and Defense Information Systems, Accounting and Information Management Division, before congressional requesters. [Washington, D.C.]: The Office, 1998.

Ewa, Huebner y Zanero Stefano, eds. Open source software for digital forensics. New York: Springer, 2010.

Die Kriminalisierung von Dual-Use-Software. Berlin: Duncker & Humblot, 2014.

Office, General Accounting. Year 2000 computing crisis: Readiness of state automated systems to support federal welfare programs : report to Congressional requesters. Washington, D.C. (P.O. Box 37050, Washington, D.C. 20013): The Office, 1998.

Office, General Accounting. Year 2000 computing crisis: Status of airports' efforts to deal with date change problem : report to Congressional requesters. Washington, D.C. (P.O. Box 37050, Washington, D.C. 20013): U.S. General Accounting Office, 1999.

Office, General Accounting. Year 2000 computing crisis: Potential for widespread disruption calls for strong leadership and partnerships : report to Congressional requesters. Washington, D.C. (P.O. Box 37050, Washington, D.C. 20013): The Office, 1998.

Office, General Accounting. Year 2000 computing crisis: Costs and planned use of emergency funds : report to the Majority Leader, House of Representatives. Washington, D.C: GAO, 1999.

L, Huband Frank, Shelton R. D y National Science Foundation (U.S.), eds. Protection of computer systems and software: New approaches for combating theft of software and unauthorized intrusion. Clifton, N.J: Law & Business, Inc., 1986.

Office, General Accounting. Year 2000 computing crisis: Status of Bureau of Prison's Year 2000 efforts : report to the Honorable Trent Lott, U.S. Senate. Washington, D.C. (P.O. Box 37050, Washington, D.C. 20013): The Office, 1999.

Office, General Accounting. Year 2000 computing crisis: State Department needs to make fundamental improvements to its Year 2000 program : report to Congressional requesters. Washington, D.C. (P.O. Box 37050, Washington, D.C. 20013): The Office, 1998.