To: John Mansfield who wrote (323 ) 4/25/1998 7:30:00 AM From: John Mansfield Respond to of 618
Update of the well known GM master test document Here are some sections that struck me. From reading the whole document, one can see how very complicated y2k projects are on enterprise level. John _________ 'Please take the time to skim the entire document. Some have followed the testing procedures without understanding that judgment must be exercised to decide which tests apply to a specific component or system. Time spent planning will be paid back many times, the test procedures are not organized in the most efficient order for actually performing the tests. 'A basic assumption of the component inventory method is that "mass produced" components have shareable test results, this assumption must be questioned often, and in the case of modern PC's has been found to be a bad assumption. In practice we have found that all PC's must be tested where vital to operations. '5.2 Year 2000 Testing Report Forms The following sections explain the purpose and use of the Year 2000 Component Test Report and Year 2000 System Test Report Forms. The Year 2000 repository has been designed to share component Y2K status, and support tracking of system level test results which are unique to local inventory items. By responding with the results of your testing to the corporate program office the contents of the compliance database can be updated. Please e-mail this information to the GM Year 2000 Program Office care of: Joseph Buffa Year 2000 Office Manufacturing & Facilities, 'EMERGENCY TEST RESULTS If during the course of Year 2000 testing an error or failure is encountered which is a safety hazard or causes severe data loss or equipment damage sent out an EMERGENCY TEST REPORT. Use the standard test report form, but send the information to your Y2K Program Office contact for wide distribution immediately. Normal test reports are stored for sharing in the Lotus Notes database, but emergency test reports are distributed to all teams to reduce possible risks associated with testing. '3.21 Stress Testing The goal in stress testing is to ensure that modifications to remediate a system or application for Y2K compliance do not materially impact system performance. Also the prior design of a system may have dependencies on numerical order which are affected when the change from 1999 to 2000 occurs. A test under normal or extreme loading should be considered, measured system response for the prior version of the system is advised to document the results. The impact of changes may not surface immediately, tests should cover a large enough span of time or number of execution cycles. '4. Year 2000 Certification Process This section addresses the process of Year 2000 certification . The objective is to have identified all of the potential Year 2000 problems, assessed the risk to operations, corrected problems which require correction, and document all work around. The specific certification and documentation requirements are available through the GM corporate and sector Y2K program offices. 'The Year 2000 Component & Combined Component Test Report Form is available in an Excel 5.0 electronic versions for: ú English (international paper size A4) - TSTCC_IO.XLS ú English (US paper size 8.5x11) - TSTCC_US.XLS ú German (international paper size A4) - TSTCC_DE.XLS ú Spanish (international paper size A4) - TSTCC_SP.XLS ú Polish (international paper size A4) - TSTCC_PO.XLS ú Hungarian (international paper size A4) - TSTCC_UN.XLS ú Portuguese (international paper size A4) - TSTCC_PR.XLSyear2000.unt.edu