In November 1999, the Public Accounts Committee of the British House of Commons published a report entitled "Improving the Delivery of Government IT Projects." It draws lessons from 25 cases from the 1990s where the implementation of IT systems resulted in "delay, confusion, and inconvenience to the citizen and, in many cases, poor value for money to the taxpayer." The Committee warned that, if those lessons go un

In last week's Architecture/e-Business E-Mail Advisor, I discussed the Common Object Request Broker Architecture (CORBA) and the fact that most companies are using CORBA mixed with some other technology, like Java and Enterprise JavaBeans. At the same time, I suggested that the Object Management Group (OMG) was increasingly focused on standards derived from other OMG specifications, especially UML, MOF, and XMI.

There is renewed interest in development of systems that are able to survive attacks, accidents, and failures, while maintaining the ability to provide users with essential services [1]. Such systems require new approaches during various lifecycle activities. We find that a spiral model, modified to highlight survivability considerations, is one way to approach systems development so as to gain survivability [2].

Beginning in about March of this year, you could almost hear the collective sighs of relief from managers of established (i.e., pre-Web) companies. Before that, it had begun to seem that the rules of the business game were different for "e-firms" than they were for others. Great sums of money were being thrown at any new business idea that involved a Web site.

The Object Management Group (OMG) was established in the late 1980s to coordinate the work of a number of companies that wanted to develop standards for object-oriented (OO) development. After some discussion, the group agreed to focus first on the problem of facilitating communications between different OO languages. To do this, it developed CORBA -- the Common Object Request Broker Architecture.

Don't I wish I could knock out a snappy 25-words-or-less definition of what is or is not "privacy"? No such luck.

When was the last time anyone came to the IT department and said, "I want you to solve a problem for me. It's a rather parochial problem, and its solution will not measurably improve our ability to achieve our vision, but I'd like you to do it anyway"? The answer is, of course, never.

A recent report published by TrendWatch suggested that the average age of Web designers/developers is 30 years of age and that the individuals are hired right out of college. One has to be careful with averages, of course. The statistic might mean that half of the designers were 20 and that the other half were 40.

Just a few short months ago, it was quite possible to bring a nifty dot-com idea before the marketplace and have hoards of investors willing to fling money at it. Nevermind that the idea was untested and, incidentally, had never made any money, nor had much prospect of doing so.

Piecemeal, poorly coordinated integration initiatives can send an enterprise one step forward and two steps back. Integration is at the top of many corporate agendas; but what are we really trying to integrate? And how do these efforts interrelate across business units, data architectures, applications, suppliers, customers, and other integration initiatives?

Microsoft has made a number of major announcements in the last couple of weeks. If one was a cynic, one might suggest that Microsoft is eager to drive up its stock value and to counteract the despair surrounding Judge Jackson's order to break up the company into two separate companies.

The quality of a Web site is fundamentally based in its information content -- if that content is hard to locate and understand, the value of the site is significantly diminished. Here are five reasons why you should conduct usability testing of your e-commerce site:

Over the past four years, operational risk management activities have evolved from simple information gathering to a functional discipline with dedicated staff using established formal policies and procedures.