Global cio oracles dazzling profit machi…

Machine suit software. 

Oracle was countersued Monday by a company one-one-thousandth its size and if you’re wondering why Oracle decided two months ago to crank up the litigation machine by suing third-party maintenance firm Rimini Street for “massive theft,” it all comes down to money. Lots and lots of money.So much money, in fact, that going by the figures in Oracle’s quarterly consolidated statements of operations released last week, the pot of gold from which Rimini Street had begun to extract a couple of morsels of gold dust accounted for more than $3 billion in Oracle operating profit for the three months ended Feb.

28.That pot of gold is called “Software license updates and product support”—also known as maintenance fees, annual support fees, or 22% annual maintenance fees.

But Rimini was offering comparable services for 11%—a huge savings in these cost-conscious times. Global CIOs: A Site Just For YouVisit InformationWeek’s Global CIO our new online community and information resource for CIOs operating in the global economy.

Hi there, 1 Supplied templates or approved replacement used 2 Covers all aspects and duration of the project 3 Timeline and milestones 4 Risk Analysis 5 Outlines for all deliverable documents eg system and user documentation, reporting and analysis documents 6 Alterations to initial plan explained 7 Alterations to initial requirements explained 8 Report on outstanding issues or problems drawn from logs can anybody provide me with some kind of detail information about above task. Cheers suvrat
by Mn @ April 3, 2007 9:44 pm
Project planning has a different set of documents for every conceivable methodology. The sets that I have used do not eem to map into what you are doing or possibly there is some other misunderstanding. SRS stands for software requirements specifications. It provides a set of detailed requirements for each of the software pieces of the project. SDP stands for the software development plan. It contains many of the things that you list above but not all of them. It would include things like software development milestones and timeline. There are other documents that provide the remaining items. There would be a document that is department wide that describes how to create and document a time line, risk analysis, etc. It would not be program specific.