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 : BORL: Time to BUY! -- Ignore unavailable to you. Want to Upgrade?

To: Scott Pedigo who wrote (8716)	1/23/1998 7:01:00 PM
From: Tom C	Respond to of 10836

A solution to a suspect legacy application might be to replace it, rather than try to fix it, in which case the effect would be positive. While I agree with you, the window of opportunity is closing quickly.. well actually I believe the window is closed. If you are the manager in charge of a core enterprise system that took several years to develop and has been continually modified for ten years, would you bet the ranch (company) on a new technology. Given the success rate of large systems development and the uncompromising delivery date (2000). Would you patch or build anew? At this point it time, if I have a date problem, I'd start patching up the old system unless I had another job lined up and I have no regard for the future of the company. An enterprise application can easily take a year for analysis and design. Implementation should be the shortest period, this is followed by testing which often takes 40% of the total time to field the application. The option to replace large complex applications is not really an option any more. Compounding the problem is that the effort to patch existing applications is draining resources from new systems development. I have seen several instances where large companies have issued edicts saying. "no new systems development until the Y2K problem is resolved". Go to the Forte thread if you want to see the effect of Y2K on enterprise development . Look at the Oracle Application's business if you want too see the effect on pre-packaged applications which are already written but take a long time for analysis, design and customization. These are just my opinions, there are many factors affecting ORCL and FRTE that may be not be related to Y2K. I do not follow PeopleSoft, BAAN or SAP, but if these pre-packaged enterprise vendors start doing poorly then the roll-your-own option will do poorly as well (just my opinion). Borland need to concentrate on new enterprise development opportunities. This market, corporate development, is shrinking because of Y2K concerns (justified or not), but I think it is to late to go for replacement of large complicated systems. Regards Tom ps: Just my hunble opinion pss: Lewis E. I am sorry if my oft hand remark or attempt to be cute while responding to a poster to you, caused you any anxiety. I was being flippant., I am sorry if you took it to be a put down, which upon rereading is the only way it would be taken. I'll try to be more careful.