Home > Computing and Information Technology > Information technology: general topics > Social and ethical aspects > The Year 2000 Software Problem: Quantifying the costs and Assessing the Consequences
49%
The Year 2000 Software Problem: Quantifying the costs and Assessing the Consequences

The Year 2000 Software Problem: Quantifying the costs and Assessing the Consequences

          
5
4
3
2
1

Available


Premium quality
Premium quality
Bookswagon upholds the quality by delivering untarnished books. Quality, services and satisfaction are everything for us!
Easy Return
Easy return
Not satisfied with this product! Keep it in original condition and packaging to avail easy return policy.
Certified product
Certified product
First impression is the last impression! Address the book’s certification page, ISBN, publisher’s name, copyright page and print quality.
Secure Checkout
Secure checkout
Security at its finest! Login, browse, purchase and pay, every step is safe and secured.
Money back guarantee
Money-back guarantee:
It’s all about customers! For any kind of bad experience with the product, get your actual amount back after returning the product.
On time delivery
On-time delivery
At your doorstep on time! Get this book delivered without any delay.
Quantity:
Add to Wishlist

About the Book

As the year 2000 rapidly approaches, an anxious clock is ticking for the world business community: When the twentieth century ends, many software applications will either stop working or produce erroneous results because their logic cannot accept the transition from 1999 to 2000. This problem is embedded in millions of aging software applications, and the costs of fixing the year 2000 software problem may constitute the single greatest expense in history. In this new book, Capers Jones offers a framework for examining the effect that the year 2000 problem will have on your company, placing this timely issue into a practical business perspective. The Year 2000 Software Problem explains what it will cost to address this impending issue, quantifying the expenses by country, industry, programming language, and application. The book further examines the expected results of not achieving year 2000 compliance and estimates what the damages and recovery costs will be. Highlights include: *An executive overview of the year 2000 problem and why it is significant *A discussion of the impact of repairing databases, repositories, and data warehouses *An explanation of the litigation risks and liability issues associated with this problem *A description of the important topic of year 2000 testing The information contained in this book will allow you to fully understand what needs to be done to minimize the risks and problems that the year 2000 problem will inevitably bring. The author's pragmatic approach allows you to assess the scope of the problem, identify the appropriate solution strategy, and test and measure the effectiveness of your solution implementation. 0201309645B04062001

Table of Contents:
Foreword by Paul Strassmann. Preface. Acknowledgments. 1. Introduction and Executive Overview. Potential Year 2000 Problems that Affect Daily Life. Potential Year 2000 Problems that Affect Executives. Timeline for Starting Year 2000 Repairs in 1998. A Two-Year Calendar for Millennium Software Repairs. A One-Year Calendar of Post 2000 Damages and Litigation. Rules of Thumb for Year 2000 Resources. 2. The Origins of the Year 2000 Problem. Root Causes of the Year 2000 Problem. Hazardous Implications of the Year 2000 Problem. Beneficial Implications of the Year 2000 Problem. Fallacies Associated with the Year 2000 Problem. 3. Terms and Concepts Associated with the Year 2000 Problem. Application. Software Portfolios. Data Base. Software Staff. Enterprise. Software Sites. Test Libraries. 4. Function Points Versus Lines of Code Metrics for the Year 2000 Problem. Function Points and Programming Languages. The Volume of U.S. Software Expressed in Function Points. Function Points and Mixed Language Projects. A Year 2000 Repair Case Study. Correlating the Gartner Group LOC data and the SPR function point data. A Checklist of Year 2000 Repair and Recovery Costs. Relative Costs of Year 2000 Damages and Repairs. A Checklist of Critical Software Application Types. 5. The Size of the Year 2000 Problem for the United States. The Volume of Software Installed in the United States. Hardware/Performance Implications of the Year 2000 Problem. Year 2000 Repairs by Industry. Year 2000 Repairs by Company Size. Triage of Software Applications. Year 2000 Repairs by Programming Language. Year 2000 Repairs by State. Aggregation of all Year 2000 Costs for the United States. Tools and Technologies Which Affect the Year 2000 Problem. Examples of Return on Investment Calculations. Unusual Methods for Speeding Up Year 2000 Repairs. Around the clock year 2000 repair centers. Suspension of anti-trust regulations for year 2000 repairs. Suspension of non-year 2000 projects. Suspension of Euro-currency conversions. Acquisition of year 2000 service companies. Year 2000 Schedules Versus Resources. Shortage of Programmers and Reluctance to Work on Year 2000. Small Companies and the Year 2000 Personnel Shortage. Post 2000 Software Personnel Surplus. The Emergence of Year 2000 Insurance. The Emergence of Certification for Year 2000 Service Providers. The Emergence of the de Jager Year 2000 Stock Index. Personal Computer Year 2000 Problems. Scorecard of Year 2000 Preparations by Industry. Cautions about Database Repairs Using Date Field Expansion. Cautions about Dead Code Repair Costs. Cautions About Missing or Uncompilable Source Code. The Prognosis of Object Code Year 2000 Repairs. 6. Testing, Test Case Errors, and Repairing Software Regression Test Libraries. General Forms of Testing and the Year 2000 Problem. Subroutine testing. Unit testing. New function testing. Regression testing. Integration testing. System testing. Specialized Forms of Testing and the Year 2000 Problem. Stress or capacity testing. Performance testing. Viral protection testing. Security testing. Platform testing. Year 2000 testing. Independent testing. The Forms of Testing Involving Users or Clients. Usability testing. Field (Beta) testing. Lab testing. Customer acceptance testing. Clean-room statistical testing. Numbers of Testing Stages for Year 2000 Software Projects. Testing Stages in Lawsuits Alleging Poor Quality. Using Function Points to Estimate Test Case Volumes. 7. Repairing Data Bases, Repositories, and Data Warehouses. 8. Litigation and Liability Potential for the Year 2000 Problem. Financial Disclosure and Executive Year 2000 Liabilities. Year 2000 Disclosure Requirements for Public Companies. Accounting Standards for Year 2000 Costs. Possible Tax Credits for U.S. Companies. Possible U.S. Tax Consequences From Reusable Repairs. 9. Business Failure Potential for the Year 2000 Problem. Business Failure Potentials Based on Company Size. Business Failure Potentials Based on Industry. Business Failure Potentials Based on Financial Health. Business Failure Potentials Based on Litigation. Codicil: Business Failures Based on Loss of Essential Services. 10. The Emergence of the Year 2000 Repair Industry. 11. The Development of “Masking” for Year 2000 Repairs. Windowing. Compression. Encapsulation. Bridging. Object Code Date Interception. 12. International Year 2000 Repair Effort. Year 2000 Repairs by Country. Year 2000 Problem and 35 Urban Areas. The Overlap of the Year 2000 and Euro-currency Conversion. Aggregation of Global Year 2000 Repairs. 13. Why Do Year 2000 Costs Vary? Variations in Burden and Overhead. Variations in Work Habits and Unpaid Overtime. 14. Post 2000 Problem and Recovery Prognosis. Damages from Unrepaired MIS applications. Damages from Unrepaired Systems Software. Damages from Unrepaired Embedded Software. Damages from Unrepaired Military Software. Damages from Unrepaired Commercial Software. Damages from Unrepaired Scientific Software. Damages from Unrepaired End-User Software Pattern of Expenses for Damages and Recovery. Evaluating Pre-2000 and Post-2000 Expenses for the U.S. Sources of Error in Year 2000 Cost Estimates. Sources of Error in Software Year 2000 Repairs. Sources of Error in Test Library Year 2000 Repairs. Sources of Error in Data Base Year 2000 Repairs. Sources of Error in Litigation Year 2000 Costs. Evaluating Global Pre-2000 and Post-2000 Costs. 15. Defenses Against Unrepaired Year 2000 Problems. General Strategies as the Year 2000 Approaches. Corporate Year 2000 Defense Strategies. Manual Back-Ups for Automated Processes. Advice for Non-Compliant Companies. Federal Government Year 2000 Defense Strategies. Military Year 2000 Defense Strategies. State and Local Government Year 2000 Defense Strategies. Personal Year 2000 Defense Strategies. Summary and Conclusions. Appendix A: Sources of Information in this Report. Appendix B: Additional Information on the Year 2000 Problem. Appendix C: Year 2000 World Wide Web Sites. Appendix D: Programming Languages And the Year 2000 Problem. Appendix E: Annotated Bibliography of Year 2000 Books. Appendix F: Glossary of Year 2000 Terms. 0201309645T04062001


Best Sellers


Product Details
  • ISBN-13: 9780201309645
  • Publisher: Pearson Education (US)
  • Publisher Imprint: Addison Wesley
  • Height: 235 mm
  • No of Pages: 368
  • Sub Title: Quantifying the costs and Assessing the Consequences
  • Width: 188 mm
  • ISBN-10: 0201309645
  • Publisher Date: 02 Jan 1998
  • Binding: Paperback
  • Language: English
  • Spine Width: 18 mm
  • Weight: 635 gr


Similar Products

How would you rate your experience shopping for books on Bookswagon?

Add Photo
Add Photo

Customer Reviews

REVIEWS           
Click Here To Be The First to Review this Product
The Year 2000 Software Problem: Quantifying the costs and Assessing the Consequences
Pearson Education (US) -
The Year 2000 Software Problem: Quantifying the costs and Assessing the Consequences
Writing guidlines
We want to publish your review, so please:
  • keep your review on the product. Review's that defame author's character will be rejected.
  • Keep your review focused on the product.
  • Avoid writing about customer service. contact us instead if you have issue requiring immediate attention.
  • Refrain from mentioning competitors or the specific price you paid for the product.
  • Do not include any personally identifiable information, such as full names.

The Year 2000 Software Problem: Quantifying the costs and Assessing the Consequences

Required fields are marked with *

Review Title*
Review
    Add Photo Add up to 6 photos
    Would you recommend this product to a friend?
    Tag this Book
    Read more
    Does your review contain spoilers?
    What type of reader best describes you?
    I agree to the terms & conditions
    You may receive emails regarding this submission. Any emails will include the ability to opt-out of future communications.

    CUSTOMER RATINGS AND REVIEWS AND QUESTIONS AND ANSWERS TERMS OF USE

    These Terms of Use govern your conduct associated with the Customer Ratings and Reviews and/or Questions and Answers service offered by Bookswagon (the "CRR Service").


    By submitting any content to Bookswagon, you guarantee that:
    • You are the sole author and owner of the intellectual property rights in the content;
    • All "moral rights" that you may have in such content have been voluntarily waived by you;
    • All content that you post is accurate;
    • You are at least 13 years old;
    • Use of the content you supply does not violate these Terms of Use and will not cause injury to any person or entity.
    You further agree that you may not submit any content:
    • That is known by you to be false, inaccurate or misleading;
    • That infringes any third party's copyright, patent, trademark, trade secret or other proprietary rights or rights of publicity or privacy;
    • That violates any law, statute, ordinance or regulation (including, but not limited to, those governing, consumer protection, unfair competition, anti-discrimination or false advertising);
    • That is, or may reasonably be considered to be, defamatory, libelous, hateful, racially or religiously biased or offensive, unlawfully threatening or unlawfully harassing to any individual, partnership or corporation;
    • For which you were compensated or granted any consideration by any unapproved third party;
    • That includes any information that references other websites, addresses, email addresses, contact information or phone numbers;
    • That contains any computer viruses, worms or other potentially damaging computer programs or files.
    You agree to indemnify and hold Bookswagon (and its officers, directors, agents, subsidiaries, joint ventures, employees and third-party service providers, including but not limited to Bazaarvoice, Inc.), harmless from all claims, demands, and damages (actual and consequential) of every kind and nature, known and unknown including reasonable attorneys' fees, arising out of a breach of your representations and warranties set forth above, or your violation of any law or the rights of a third party.


    For any content that you submit, you grant Bookswagon a perpetual, irrevocable, royalty-free, transferable right and license to use, copy, modify, delete in its entirety, adapt, publish, translate, create derivative works from and/or sell, transfer, and/or distribute such content and/or incorporate such content into any form, medium or technology throughout the world without compensation to you. Additionally,  Bookswagon may transfer or share any personal information that you submit with its third-party service providers, including but not limited to Bazaarvoice, Inc. in accordance with  Privacy Policy


    All content that you submit may be used at Bookswagon's sole discretion. Bookswagon reserves the right to change, condense, withhold publication, remove or delete any content on Bookswagon's website that Bookswagon deems, in its sole discretion, to violate the content guidelines or any other provision of these Terms of Use.  Bookswagon does not guarantee that you will have any recourse through Bookswagon to edit or delete any content you have submitted. Ratings and written comments are generally posted within two to four business days. However, Bookswagon reserves the right to remove or to refuse to post any submission to the extent authorized by law. You acknowledge that you, not Bookswagon, are responsible for the contents of your submission. None of the content that you submit shall be subject to any obligation of confidence on the part of Bookswagon, its agents, subsidiaries, affiliates, partners or third party service providers (including but not limited to Bazaarvoice, Inc.)and their respective directors, officers and employees.

    Accept

    New Arrivals


    Inspired by your browsing history


    Your review has been submitted!

    You've already reviewed this product!
    ASK VIDYA