To: patrick gillis who wrote (8102 ) 12/30/1997 8:21:00 PM From: TokyoMex Respond to of 31646
Subject: Checkfree Date: Tue, Dec 30, 1997 18:40 EST From: Dewave1 Message-id: <19971230234001.SAA10009@ladder01.news.aol.com> I've been a user and investor of checkfree for 4 years. This has recently popped up on their website. Enjoy. January 1, 2000 approaches. Is it doomsday or just another day? Our goal at CheckFree is to make the year 2000 just another routine date for our leading financial products and services. We are responding to this challenge with a thorough effort to adapt our products and to help you adapt your systems for the changing century. CheckFree offers a very wide variety of software products and services to meet various financial application needs. Some of those products remain in active development and maintenance, while others have been displaced with more modern technologies and capabilities. Some of those displaced products will not be made Year 2000 compliant. However, the vast majority of CheckFree products are already or will soon be Year 2000 compliant. The few that will not be made Year 2000 compliant will have migration alternatives for our customers. As of October 1997, here's what the breakdown looks like: 25 Products are already compliant in released versions 30 Products and Services are in the process of being made compliant; 20 of which are on target to be complete by the end of 1997 10 Products will not be made compliant Year 2000 Testing Methodology While each CheckFree product has a unique certification plan for Year 2000 compliance, a common philosophy crosses each plan. Products are tested under three primary conditions: Date-related fields throughout the application must meet five properties: 1.Storage - correctly represent valid dates beyond the year 2000 and minimally to the year 2038. 2.Branching - correctly compare valid dates beyond the year 2000 and minimally to the year 2038. 3. Arithmetic - correctly calculate duration between two dates, calculate date based on starting date and duration, and calculate day of week, day within year, week within year. 4.Representation - successfully convert from one convention to another (e.g., CCYY-MM-DD to CCYY-DDD). 5. Extended semantics - completely eliminate special meanings associated with the years "99" and "00". Software product performs correctly if initiated on a minimum of 12 testable dates Software product operates correctly if system clock rolls over to a minimum of 12 testable dates The following dates were chosen to represent the minimal set to be used across all products, recognizing that each product may have its own unique need to test additional dates: 1.1/4/1999 - first business day in 1999 2.9/9/1999 - potential end-of-file indicator for compressed date of 9/9/99 3.12/1/1999 - first business day in December 1999 4.12/31/1999 - last day in 1999 5.1/1/2000 - first day in 2000; first potential for date comparison failure 6. 1/3/2000 - first business day in 2000 7.1/31/2000 - month end for first month in 2000 8.2/29/2000 - leap day in 2000 9.12/31/2000 - last day in 2000 10.1/1/2001 - first day in 2001 11.1/31/2001 - month end for first month in 2001 12.2/29/2004 - second leap day in 21st century