A Key To Big Blue's IOD Strategy -- Visual Studio Magazine

Data Driverby David Ramel

A Key To Big Blue's IOD Strategy

I attended a press conference earlier this month in New York, where Big Blue talked up its latest prize -- Cognos Inc., which it acquired last month for $5 billion -- marking the company's largest acquisition ever. Executives at IBM explained why the company abandoned its longstanding stance on partnering with various BI players.

While pledging to be open, Steve Mills, senior vice president and general manager of IBM's software group, said performance management must be an embedded component of its Information On Demand strategy. "It was time to bring these things together and make them one contiguous set of capabilities," Mills said.

Posted by Jeffrey Schwartz on 02/20/2008

comments powered by Disqus

Featured

Compare New GitHub Copilot Free Plan for Visual Studio/VS Code to Paid Plans

The free plan restricts the number of completions, chat requests and access to AI models, being suitable for occasional users and small projects.
Diving Deep into .NET MAUI

Ever since someone figured out that fiddling bits results in source code, developers have sought one codebase for all types of apps on all platforms, with Microsoft's latest attempt to further that effort being .NET MAUI.
Copilot AI Boosts Abound in New VS Code v1.96

Microsoft improved on its new "Copilot Edit" functionality in the latest release of Visual Studio Code, v1.96, its open-source based code editor that has become the most popular in the world according to many surveys.
AdaBoost Regression Using C#

Dr. James McCaffrey from Microsoft Research presents a complete end-to-end demonstration of the AdaBoost.R2 algorithm for regression problems (where the goal is to predict a single numeric value). The implementation follows the original source research paper closely, so you can use it as a guide for customization for specific scenarios.
Versioning and Documenting ASP.NET Core Services

Building an API with ASP.NET Core is only half the job. If your API is going to live more than one release cycle, you're going to need to version it. If you have other people building clients for it, you're going to need to document it.