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 : 2000: Y2K Civilized Discussion -- Ignore unavailable to you. Want to Upgrade?

To: flatsville who wrote (140)	8/12/1999 11:51:00 PM
From: B.K.Myers	Read Replies (1) \| Respond to of 662

What percentage of any given time frame should be allotted to a "shake-down" period on a generic installation? Did you include that in the above 6-15 months estimate? Flatsville, you ask good pertinent questions. I wish I could answer them with more confidence. I think that you would find different "shake-down" periods used by different companies. It would probably depend on the conditions of the company's original data, the quality of the conversion programs and the competence level of the staff. Having done my best to evade your question, personally I would think that at least one parallel system test would be prudent. I think that 2 - 6 weeks would probably "shake out" most of the bugs and I did include this period in my previous estimation. However, many (if not most) companies seem to just slap systems into production with only minimum testing. I remember the days when no software would be moved to production without extensive testing. Now programmers test their own software modifications, move them to production and stand by in case problems arise. I think somebody on this thread mentioned the "test for success" syndrome that appears to be commonplace with Y2K testing. From what I have seem over the past few years, this is becoming an industry standard. B.K. P.s. Thanks for the earlier GPS post.