Product Description
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
From the Publisher
A must-read if you want to know how big the Y2K really is.In this book, Capers Jones, an internationally known and respected leader in the software and business communities, offers his wealth of insights and quantitative reseach on the Year 2000 software crisis. Calling upon his 20+ years of experience in the software engineering and project management arenas, he provides you with a framework of determining the impact the Y2K will have on your systems and business imperatives. The book clearly defines the scope of the problem, notes the most promising approaches to addressing the problem, and offers guidance for those executives responsible for managing Y2K projects. Jones not only explains the costs of fixing the problem, but also the costs and issues associated with not fixing it correctly or ingnoring the Y2K entirely.
The data in this book is considered some of the most reliable information available: Jones has supplied pieces of his data to a number of other Y2K books on the market, including Leon Kappelman's Solving the Year 2000 Problem, Dick Lefkon's Year 2000 Best Practices for Y2K Millenium Computing, and Bryce Raglands' The Year 2000 Problem Solver.
If you want to determine exactly how big the Y2K problem really is both globally and for your own business, you should read this book. It is extremely thorough and well-written: an easy and informative read.