The issue of measuring IT from a business value vantage point continues to be a major challenge for most organizations.

In this article, I'll consider Java development tools, OO and O-R databases, packaged applications, and corporate applications. I'll wrap up the whole discussion of Java with a summary and my speculations about what will happen in the remainder of 1998.

This month's topic is the Open Trading Protocol (OTP), a protocol being developed by a consortium to enable entities to negotiate a trade over the

DCI's Data Warehouse World and Miller Freeman, Inc.'s IT Forum '98 have both been around for a number of years (although IT Forum was formerly called DB/Expo and it now includes Unix Plus Windows NT Ex

The latest Microsoft Repository Data Warehousing Workshop brought together approximately 250 vendors and developers of DSS, software development, and data transformation tools to solicit their input in the development of the Microsoft Repository as t

Copyright 1998 by ITBAHI Corporation. All rights reserved.

Copyright 1998 by ITBAHI Corporation. All rights reserved.

Copyright 1998 by ITBAHI Corporation. All rights reserved.

Copyright 1998 by Capers Jones. All rights reserved.

Risks are present in virtually every software project, and as a result, "risk management" is typically discussed in very generic terms. However, there are a few types of projects for which the risks seem particularly pervasive and severe; they deserve a specific discussion of risk-management issues and guidelines.

Risks are present in virtually every software project, and as a result, "risk management" is typically discussed in very generic terms. However, there are a few types of projects for which the risks seem particularly pervasive and severe; they deserve a specific discussion of risk-management issues and guidelines.

Risks are present in virtually every software project, and as a result, "risk management" is typically discussed in very generic terms. However, there are a few types of projects for which the risks seem particularly pervasive and severe; they deserve a specific discussion of risk-management issues and guidelines.

There is no single best way for organizations of all types to do risk management. Instead, there appears to be a maturity model for risk management that has at least three levels. Some organizations work on one or two levels. Those working in high-risk environments may take advantage of all three levels, using that which is appropriate to their circumstances.

There is no single best way for organizations of all types to do risk management. Instead, there appears to be a maturity model for risk management that has at least three levels. Some organizations work on one or two levels. Those working in high-risk environments may take advantage of all three levels, using that which is appropriate to their circumstances.

There is no single best way for organizations of all types to do risk management. Instead, there appears to be a maturity model for risk management that has at least three levels. Some organizations work on one or two levels. Those working in high-risk environments may take advantage of all three levels, using that which is appropriate to their circumstances.

Part of the culture of the software industry is that projects and programs can be very complex and are prone to embarrassing delays, budget overruns, and outright failure. Yet research has shown that most project failures could have been avoided, frequently by up- front investment in a comprehensive risk management plan.

Part of the culture of the software industry is that projects and programs can be very complex and are prone to embarrassing delays, budget overruns, and outright failure. Yet research has shown that most project failures could have been avoided, frequently by up- front investment in a comprehensive risk management plan.