IEEE 2000.2-1999

Identify best practices for defining a user-specific test plan for "Y2K" (Year 2000 rollover and related date-specific issues) validation. A taxonomy of system elements and features which are likely to exhibit Y2K failures. A user-customizable template for test plans and test scenarios for detection of defective (with respect to Y2K) system elements and features. A user-customizable methodology and process for determining the testing impact of various remediation, validation, and reporting methods. It is not intended that these practices be employable in a mechanical or rote fashion: significant engineering judgment must be exercised by the user of this document in applying its recommendations. To provide users of computer software, firmware, and hardware systems with recommended practices for assessing the system elements within their organization that may be at risk of failure due to Year 2000 rollover or related date-specific issues. New IEEE Standard - Inactive-Withdrawn. This document provides users of computer hardware, firmware, software, or data systems with recommended practices for assessing and demonstrating the system elements within their organization that may be at risk of failure due to the Year 2000 problem and related date-specific issues. This recommended practice provides the framework for detailed planning and execution of all steps and tasks involved in testing for Year 2000 compliance. The resulting plan will outline the testing approach and identify system elements that are at risk of failure when crossing into the Year 2000 or using data that includes dates after 2000-01-01.