maybe this will be of some use. my background does not allow me to deduce the veracity of his comments but rick will be able to determine if this is of value...m

In Today's Westergaard Year 2000:

Y2K Double Feature: "POWERful Prognostications" and "Global-Local Y2K"

Feature #1: "POWERful Prognostications" Today Dick Mills begins a two-part column on Y2K testing in the electric utility industry. For those who read reports on this type of testing to get an idea of what to expect come January 2000, this series is a must read. It is designed to give readers the knowledge to understand what the results of these tests mean, and whether or not they can be trusted. This piece focuses on the types of tests that are conducted and the pros and cons of each. http://www.y2ktimebomb.com/PP/RC/dm9907.htm

Feature #2: "Global-Local Y2K" In this week's issue of "Global-Local Y2K," columnist Chuck Lanza reports on his recent attendance and participation in the international conference on disaster management: Disaster '99. This year's conference featured a presentation on Y2K given by Mr. Lanza himself. This article relates the topics he discussed. http://www.y2ktimebomb.com/GL/CL/gl9907.htm

John Yellig (yellig@westergaard.com) Editor Westergaard Year 2000

-- Anonymous, February 19, 1999

Answers

Excellent article on testing by Dick Mills. Especially liked the "smoke testing" info, right on target, and the Swedish "false" y2k finding is not uncommon, testing errors for complicated system are not unusual.

FactFinder

-- Anonymous, February 20, 1999

Dear Marianne,

I think that Dick Mills should go into the fields of testing. This is written from behind a desk and far from practical. Never heard of smoke testing, never done it either. Testing for Y2K readiness takes place in two steps : 1 embedded system itself 2 Integral test: the whole system with all the embedded systems in real life.

Menno

-- Anonymous, February 23, 1999

Marianne,

here is a little bit more information from http://www.fcc.gov/year2000/y2kguide.html

Step Four: Unit Testing

Testing is done in two steps. Unit testing occurs when individual components in isolation are tested. Integrated testing occurs when components are carefully reintroduced into their systems in order to ensure compatibility.

Testing is vital to the implementation of a Y2K strategy. Experts suggest devoting 50 percent of your overall effort to testing. Testing permits you to uncover overlooked areas of difficulty. One auto company which felt confident about its level of compliance tested one of its plants only to discover that the factory doors would not unlock. Testing should be considered for all equipment, including equipment that is thought to be problem free, especially where that equipment is considered critical. Be aware that a fix implemented in one part of a system can have ramifications throughout the rest of the system. According to Bellcore, a new defect is introduced into software code with every 4.5 fixes. In addition, in the best of situations, 5 percent of defects are not discovered until after testing has been completed and the code has been made operational. Be prepared to test for and respond to the effect that fixes will have on systems.

If testing cannot be completed on all systems, an order or priority should be developed with the most critical systems being tested first.

Testing should be done with care to ensure that the testing itself results in no harm to the system or individuals.

| Additional Information |

Step Five: Integration & System Testing

Once remediated and tested, equipment must carefully be integrated back into a system. You should take care to ensure that equipment that works in isolation also works when plugged back in. If the format of data has changed for a piece of equipment, than any other piece of equipment with which it works must be able to understand that new format.

Integration also involves "synchronized implementation." This means that where two systems work together and exchange data, a change in data format in one system must occur at the same time as a change in a data format in the other. This may mean working with the companies with whom you interconnect to ensure that upgrades are conducted at the same time and will be compatible.

Once your preparations are complete, be sure to maintain a "clean" environment. Do not integrate any untested component, hardware, or software into your system.

-- Anonymous, February 24, 1999