[an error occurred while processing this directive]

TOOLS USA 2002

Keynote Speeches

Monday | Tuesday | Wednesday

Keynote addresses are an essential part of the TOOLS USA program. They will set the professional tone for the conference, highlighting current issues and key industry trends.

Each keynote is tailored to the immediate needs of the audience, with themes and speakers carefully selected to deliver maximum value. Our intention: to create an environment that will engage conference participants allowing you to synthesize trends in a big picture context and to design formats that encourage idea generation.

The result is a high value learning experience which is guaranteed to spark ideas and shape strategies.

Monday, July 29
How to Prove a Class
Bertrand Meyer, Professor of Software Engineering at ETH Zurich, adjunct professor at Monash University (Melbourne), ISE

Track: Keynote
Date: Monday, July 29
Time: 11:00am - 12:00pm
Location: El Cabrillo Banquet Room

Abstract: Coming Soon.

 

Rotor and Mono
Miguel de Icaza

Track: Keynote
Date: Monday, July 29
Time: 1:30pm - 2:30pm
Location: El Cabrillo Banquet Room

Abstract: Coming Soon.

 

Tuesday, July 30
Development Process for Large Scale J2EE Applications and Web Services Projects
Christophe Job, Oracle, VP of Application Development Tools

Track: Keynote
Date: Tuesday, July 30
Time: 11:00am - 12:00pm
Location: El Cabrillo Banquet Room

Abstract: With the underlying J2EE standards now well established and a rich set of best practices becoming the norm for J2EE development, developers are seeking a development experience that brings productivity to the J2EE application development process itself. This session discusses and analyzes the development process and the environment required for rapidly and easily creating high quality J2EE applications and Web services. Some of the topics considered will include: Frameworks (MVC and Business Logic), best practices, application tuning and testing, collaborative development, standards support, utilities and open sources.

 

Web Services and the gap between IT and business
Ali Arsanjani, IBM

Track: Keynote
Date: Tuesday, July 30
Time: 1:30pm - 2:30pm
Location: El Cabrillo Banquet Room

Abstract: Coming Soon.

 

Wednesday, July 31
TBA
Christine Mingins, Monash University (Australia)

Track: Keynote
Date: Wednesday, July 31
Time: 11:00am - 12:00pm
Location: El Cabrillo Banquet Room

Abstract: Coming Soon.

 

Productivity in Software
Roger Osmond, Amalasoft and EMC Corporation

Track: Keynote
Date: Wednesday, July 31
Time: 1:30pm - 2:30pm
Location: El Cabrillo Banquet Room

Abstract

Software productivity has been traditionally a measure of the efficiency of the software development process - a producer-oriented view. It is more meaningful to measure also the efficacy of the software produced, in the view of the consumer. This concept is key to consumer-oriented product development.

More specifically, software productivity can be measured only by considering more than the cost of software production. It is necessary also to consider the effect of software production on consumer satisfaction. It is, in the end, a kind of cost-benefit equation, where the direct immediate cost is to the producer and the immediate benefit is to the consumer.

The benefit to the producer is derived from the benefit to the consumer. Business-for-profit is not altruistic, but a good business model, driven by consumer satisfaction, might appear to be. The goal of for-profit businesses is sustainable profitability. Consumer satisfaction and cost-effectiveness combine to be the critical keys to achieving that goal. A producer that does not adequately satisfy its consumers will eventually fail. Producers that continue to push out inferior product (with respect to consumer satisfaction) will in time reap as they sow.

There might appear to be counterexamples in the software industry. Looking more closely, though (and for the moment ignoring such factors as lack of competition), the formula might not be so skewed after all.

The analysis must focus on what is and is not "good-enough", where good-enough means satisfying the consumer's requirements, as the consumer perceives them. For an organization to succeed, through consumer satisfaction, it must understand the role of good-enough in measuring and improving software productivity.

Please Note: Program content subject to change.

[an error occurred while processing this directive]