IEEE DRAFT 2000.2 : D13 99

1 Overview
1.1 Scope
1.2 Purpose
1.3 Assumptions
2 Normative references
3 Definitions
3.1 acceptable deviation
3.2 bridge
3.3 failure
3.4 future regression
3.5 ordinal date (OD)
3.6 pass
3.7 real time clock (RTC)
3.8 special logic
3.9 system elements
3.10 system time
3.11 user defined date systems
3.12 Year 2000 rollover
4 Editorial conventions and warnings
4.1 Editorial conventions
4.2 Warnings
5 Methodology
5.1 Year 2000 life cycle:
5.2 Test process
5.3 Impact of external constraints of the Year 2000 testing
          strategy
5.4 Test impact of remediation techniques
5.5 Special considerations involving embedded systems
5.6 Special-condition dates
5.7 Special date conditions
5.8 System components to be tested
6 System elements at risk
6.1 Interfaces: Shared control blocks/API/DDE/OLE
6.2 Archiving/restoring
6.3 Backup and restore
6.4 Calculations
6.5 Date determination
6.6 Hardware
6.7 Computer numerical controls
6.8 Communication protocols
6.9 Compilers
6.10 Event-triggers
6.11 Error handling
6.12 File access system
6.13 Globalization/internationalization
6.14 Synchronization of distributed networks
6.15 Import/export
6.16 Multi-systems windowing
6.17 Licensing
6.18 Logs/date stamps
6.19 Merge
6.20 Parsing/validation
6.21 Performance
6.22 Operational time periods
6.23 Queries, filters and data views
6.24 Data recovery
6.25 Bridge testing
6.26 Sorting
6.27 User Interface (Input and Output)
6.28 Date format
Annex A Search strings (informative)
Annex B Dates (informative)
Annex C Example archive documentation (informative)
Annex E Coverage overview (informative)
Annex F Date systems (informative)
Annex G Informative references (informative)

Scope of this document to identify Recommended Practices for defining a user-specific test plan for Year 2000 validation. Includes taxonomy of system elements and features which are likely to exhibit Year 2000 failures, test scenarios which may be used as templates for the creation of test cases to detect defective system elements with respect to the Year 2000 and a customizable methodology and process for determining the testing impact of various remediation techniques, validation techniques, and documentation of test results. Caution in not employing this document in a mechanical fashion; it should be used to supplement standard testing procedures that encourage proper coverage and consistency of testing.