Silicon Investor (SI) -- The First Internet Community

STOCKTALK

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor. We ask that you disable ad blocking while on Silicon Investor in the best interests of our community. If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.

Technology Stocks : CSGI ...READY FOR TAKE-OFF! -- Ignore unavailable to you. Want to Upgrade?

To: tech who wrote (1270)	11/19/1997 8:42:00 AM
From: tech	Respond to of 3391

Social Security: Lines of Uncorrected Code Just Doubled For the Social Security system, it's back to the drawing board. They thought they had 30 million lines of code to go through and repair. Actually, according to COMPUTERWORLD (Nov. 17), it's 34 million lines. Then, in late 1996, they discovered an additional 33 million lines in 54 state-administered Social Security programs. They are disability programs: well-named, as it turns out. This fact was only recently called to Congress's attention by the General Accounting Office. So, Social Security, which had received an "A" from Congressman Stephen Horn as the most advanced Federal agency for y2k repairs, turns out to be as messed up as the others. Well, maybe not as messed up as the FAA and the Treasury Department, but messed up nonetheless. They have no contingency plans for a y2k failure. The article reported: "The SSA said it hadn't developed them because it felt its early start on the year 2000 problem would make those plans unnecessary. And in another Alice-in-Wonderland explanation, it also said it hadn't developed backup plans because it simply had to meet the deadline. In other words, if you aren't allowed to fail, you won't fail." Social Security had been claiming 80% compliance. It took them since 1991 to achieve this. But now the amount of code they -- or somebody -- must correct is twice as large as they had believed. Now, at best, they are 80% compliant with half of their code. SSA exchanges 6,700 data fields with other organizations, the COMPUTERWORLD article reported. This raises the problem of noncompliant imported data. Where is the good news on y2k? Where are the reports of near-compliance that anyone can trust? ******** Has anyone started, finished and successfully tested a Year 2000 project ?

To: tech who wrote (1270)	11/19/1997 8:51:00 AM
From: tech	Respond to of 3391

The Number of Errors Per Lines of Repaired Code Martyn Emery provides a general rule of thumb. * * * * * * * Whilst there can be no generic standards in terms of Y2K defect rates. The concept of assuring a high quality threshold is applicable when it comes to the selection of companies who are performing offshore remedial activities. If these companies can not demonstrate that they measure defects, how on earth can they be sure about the quality of their work? A good figure for defects at present would be 5-10 defects per thousand lines of changed code. This is after acceptance test, and counting defects from December 99 through to April 2001. So if you modify a million lines of code, plan for 5-10,000 defects. What company finished a Year 2000 project for Millennium in which they automatically converted code and no errors were found once this code was tested ?