The Year 2000 Problem Solver provides a five-step plan for technical managers who are in charge of fixing year 2000 problems. The awareness step offers tips for technical staff on how to communicate the problem to management--a critical part of any year 2000 strategy. The assessment step helps you determine the best strategy for solving the problem, and the renovation step gets you started in the execution of your strategy. The validation step walks you through the testing and quality assurance phase, while the implementation step helps you assess how your company's system interfaces with other systems. Over half of the book is dedicated to listing contact information for vendors who provide year 2000 solutions.
From the Publisher
". . .clearly and concisely explains the problem then provides a 5-step strategy (awareness, assessment, renovation, validation, implementation) to solving the crisis." Computer Book Review, 9/97 "This book is a practical gateway to the future for corporate managers, information managers, academician, and home personal computer users. It is easy to read and will be useful as a collateral text on "Year 2000" research issues" Washington Science Books & Films, 7/97 "This concise guidebook, by Bryce Ragland, is best suited for experienced information professionals. To get the most out of this book, you should understand the Y2K problem and the programming consequences. Of the book's 270 pages, 165 are devoted to a bibliography of article references, analysis and coversion tools, vendors offering conversion services, help resources, and case studies. Instead of focusing solely on fixing applications, Ragland correctly places higher value on the data itself. He discusses how to keep existing legacy data from being corrupted during conversion of existing applications or by updates from newer Y2K-aware applications. Ragland's recommendations, such as creating task teams and motivating upper management, are appropriate to larger, enterprise settings."BYTE Magazine, 8/97 "This book explains the problem in clear concise terms and provides a strategy in the form of five step process for individuals and companies to combat this looming crisis." Charlotte Sun Herals, 7/97 ". ..best suited for experienced information professionals." BYTE, 08/97 "The Year 2000 Problem Solver explains not only how to deal with the technical aspects of your year-2000 problem but also how to handle it from a management perspective. Ragland believes that because the problem is pervasive across almost all systems, management must be concerned with interfaces, the timing of the implementation, and how to ensure that users are kept happy. There is also a helpful chapter on the costs of solving a year-2000 problem. The book includes a glossary of terms, a resource guide, and a thorough index." Infoworld, 07/97"This, too, is a well-organized overview, but it's much less detailed than the Ulrich and Hayes book. The author dispatches year 2000 testing, which can comprise half of a year 2000 effort, in a mere six pages. The last half of the book is an exhaustive list of year 2000 tools grouped by function and platform. Normally, that would feel like padding, but if it helps you find a tool for those old WANG VS applications, it could by itself be worth the price of the book." Computerworld, 3/10/97 ". . .a well written book" Com.Links Library, 4/97 ". . .a clear plan for facing and resolving the situation in this remedy-oriented coverage." Bookwatch, 5/97 Ragland does a particularly thorough job of giving us information and options."Computer Shopper, 5/97
As the year 2000 approaches, computer systems in place throughout the world are starting to go haywire because they treat the year as two digits instead of four. Minor problem? Hardly. It's been estimated that businesses and governments worldwide will spend at least $300 million in the next few years to correct it! For all the systems administrators and managers scurrying to meet the millennium deadline, this crucial guide will be a problem-solver and a lifesaver. Wisely addressing the Year 2000 Problem from a managerial as well as technical viewpoint, the author spells out a five-step approach for disaster prevention. He alerts readers to the most likely trouble spots-those involving systems that handle inventory, actuary, and critical accounting or business forecasting tasks. Furthermore, he points out that 2000 is also a leap year, which creates a whole other set of concerns! Systems that aren't ready for the year 2000 may well face total collapse. Just as the "millennium problem" is shaping up as one of the computer world's most explosive topics in the upcoming year. The Year 2000 Problem Solver is sure to be one of its bestsellling books.
As the year 2000 approaches, computer systems in place throughout the world are starting to go haywire because they treat the year as two digits instead of four. It's been estimated that businesses and governments worldwide will spend at least $300 million to correct this. For all the system administrators and managers scurrying to meet the millennium deadline, this crucial guide will be a problem-solver and a lifesaver.