Book details of 'Solving the Year 2000 Crisis (Artech House Computer Science Library)'

Title	Solving the Year 2000 Crisis (Artech House Computer Science Library)
Author(s)	Patrick McDermott, Peter McDermott
ISBN	0890067252
Language	English
Published	June 1998
Publisher	Artech House

---

Back to shelf Computer
Amazon.com info for Solving the Year 2000 Crisis (Artech House Computer Science Library)

Score:

Vote for this book

The Virtual Bookcase Reviews of 'Solving the Year 2000 Crisis (Artech House Computer Science Library)':

Reviewer Rob Slade wrote:
(Okay, it's late. All I can say is, I just got it.) Part one gives an outline of the problem itself. Chapter one looks at the various types of things that can go wrong. This is reasonably clear, although it could have had a few more examples. There are a number of factors that make the problem note quite as bad as some suggest, and these are discussed in chapter two. On the other hand, chapter three points out why it is not going to be easy. Chapter four talks, rather briefly, about some of the disaster scenarios, and why they won't happen. Overall, the section is a very good explanation of the technical aspects of the problem, but is weakened by ignoring the cumulative affects of multiple failures in independent systems. Part two examines solutions to the problem. Chapter five looks tersely at replacement of old systems. Expansion of date fields is discussed in chapter six. Windowing, in chapter seven, is presented as a quick but possibly dirty fix. Chapter eight reviews the possibility of compressing data in order to extend the life of the program while maintaining existing data structures. It is possible, as chapter nine points out, that you can get away with not fixing Y2K errors, since they can be worked around. Special cases of windowing (encapsulation) and replacement (abandonment) are reviewed respectively in chapters ten and eleven. The previous material having looked at methods, chapter twelve discusses searching out the code that needs to be addressed. Chapter thirteen presents the need for assessments and choices in finding a solution. Part three looks at the people you will need. Chapter fourteen talks about issues of staffing. Assuming you want someone else to do it for you, chapter fifteen looks briefly at consultants and outsourcing. Tools that might help are reviewed in chapter sixteen. Chapter seventeen takes a stab at making a guess at roughing out how much this is all going to cost you. Part four looks at the Y2K fix project. Chapter eighteen is an excellent overview of the type of information you will need to plan the project. Decisions on what to fix and what to abandon are discussed in chapter nineteen. Using the fact that Y2K issues are simple but pervasive, chapter twenty suggests a factory approach. Chapter twenty one is a quick guide to project planning. Part five reviews business issues. Chapter twenty two looks at the aspects facing the small business, and the resources it has. While parts two to four generally apply to large systems, chapter twenty three presents a quick check for PC and desktop use. Points of failure important to your business should be identified as suggested by chapter twenty four. Testing of your preparations is covered in chapter twenty five. Although the bulk of the book was written for those faced with the technical task of correcting Y2K programming problems, the material is very readable, and generally presents the issues briefly, but reasonably. In terms of presenting the problem, the book is on a par with "The Year 2000 Software Problem" by Jones (see reviews). copyright Robert M. Slade, 1999
Add my review for Solving the Year 2000 Crisis (Artech House Computer Science Library)

Book description:

The Millennium is almost upon us, and with it comes perhaps the single most troubling dilemma in computer history: how to solve the Year 2000 (Y2K) Problem. This expertly authored, one-source reference provides an answer to this problem by revealing practical, how-to instructions on planning, preparing, and executing a project that will make your company Y2K compliant. Solving the Year 2000 Crisis helps programmers, managers, and consultants gain a clear understanding of the Y2K Problem -- and how to beat it -- from the ground up. It closely examines and evaluates the 7 major problem-solving approaches currently available, helps you choose the best method for your particular company or organization, then provides you with the information you need to implement a solution. Well-written sections on project staffing and management help you determine whether to build your Y2K team with existing employees or consultants, and show you how to choose the best tools for improving their productivity. The book also addresses the business side of the Y2K issue -- you learn the impact of the problem on PC and desktop systems, and how to find and test potential failure points. Appendices contain ready-made program code in COBOL, C++, FORTRAN, and Visual Basic that illustrate possible solutions, and may be used to help solve your problem.