In the current climate of e-business froth, the business-IT strategy development process appears to be a cumbersome effort, a luxury that can only push the firm further behind in the race with the various dot-com activities of competitors.

Paul Evitts, the president of neoLogistiks in Toronto, has just published a very interesting book: A UML Pattern Language (Macmillan Technical Publishing, Software Engineering Series, 2000. ISBN 1-57870-118-X).

Like most consultants, I spend an uncommon amount of time on airplanes. I'll admit to sometimes enjoying the quiet time away from e-mail and telephones to work or read. On a recent flight to a client site, I was poring over the February issue of The Atlantic Monthly.

Like most consultants, I spend an uncommon amount of time on airplanes. I'll admit to sometimes enjoying the quiet time away from e-mail and telephones to work or read. On a recent flight to a client site, I was poring over the February issue of The Atlantic Monthly.

In the current climate of e-business froth, the business-IT strategy development process appears to be a cumbersome effort, a luxury that can only push the firm further behind in the race with the various do

In the current climate of e-business froth, the business-IT strategy development process appears to be a cumbersome effort, a luxury that can only push the firm further behind in the race with the various do

Like most consultants, I spend an uncommon amount of time on airplanes. I'll admit to sometimes enjoying the quiet time away from e-mail and telephones to work or read.

Like most consultants, I spend an uncommon amount of time on airplanes. I'll admit to sometimes enjoying the quiet time away from e-mail and telephones to work or read.

There are several difficulties involved with building the next generation of systems that integrate the functions in current Web applications (traditional front office, order entry) with the back office (order fulfillment). The first difficulty is unambiguously defining the user requirements; the second is managing the organizational changes necessary to deploy the technical solution.

There are several difficulties involved with building the next generation of systems that integrate the functions in current Web applications (traditional front office, order entry) with the back office (order fulfillment). The first difficulty is unambiguously defining the user requirements; the second is managing the organizational changes necessary to deploy the technical solution.

BEA held its annual Users Conference this past month. Everyone was in a good mood. BEA's stock has gone from $65 to over $130 in the past two months and it's still listed as a "strong buy" by most analysts. The underlying reason, as I've mentioned on several occasions in the past, is that BEA has made all the right moves.

All software development projects require two complementary methodologies. A systems development methodology is required to specify the tasks, techniques, and deliverables of each phase of the project. A project management methodology is required to estimate, schedule, and monitor the project. Currently, object-oriented systems development methodologies are focused on the development of "green field" systems.

BEA held its annual Users Conference this past month. Everyone was in a good mood. BEA's stock has gone from $65 to over $130 in the past two months and it's still listed as a "strong buy" by most analysts.

BEA held its annual Users Conference this past month. Everyone was in a good mood. BEA's stock has gone from $65 to over $130 in the past two months and it's still listed as a "strong buy" by most analysts.