AOSD.net
Conference archive · Edition 8
2009

Speeches By Daugherty, Murphy, And Stankovic

March 4–6 keynotes · University of Virginia · Charlottesville, USA

The University of Virginia, Charlottesville — venue of AOSD 2009
The University of Virginia ballroom hosted the keynotes of the 8th AOSD conference.

A summary of the keynotes delivered in the ballroom of the University of Virginia, Charlottesville, Virginia, USA — the venue of the 8th AOSD conference, 2009. Each morning, from 9:00 to 10:30, a different voice took the podium.

Wednesday, March 4The Future Of Software Architecture For Large-Scale Business Solutions

Portrait of Paul Daugherty of Accenture

Paul Daugherty

Chief Technology Architect · Accenture

Subtitled Modularity, Scalability, and Separation of Concerns, the speech held that embracing advanced software engineering approaches carries great promise for solving the business challenges arising from the complexity of today's large-scale software projects. Modularization, for instance, holds that promise for reducing software design complexity — and the key to modularization is an adequate separation of concerns.

Thursday, March 5Cyber-Physical Systems: Aspects As Basis For Robustness And Openness

Portrait of Prof. John A. Stankovic of the University of Virginia

Prof. John A. Stankovic

Computer Science Department · University of Virginia

The speech addressed the great expansion in communication and computing capabilities. Cyber-physical systems are the systems that bridge the cyber-world of communication and computing with the physical environment — seeking to transform how people relate to, and control, their physical world. That includes aerospace systems, medical systems, defence systems, robotic systems, factory automation, and process control, among others.

Friday, March 6Everyday Aspects

Portrait of Prof. Gail Murphy of the University of British Columbia

Prof. Gail Murphy

Computer Science Department · University of British Columbia

The speech related the importance of modularization to everyday tasks. Programmers carry out evolutionary tasks by making changes to many modules, including the target system — and through all of it, aspect-oriented programming makes things easier and better through a modularization that can be far harder to achieve in other languages.

How do the everyday tasks of information workers compare to the programmer's use of modularity? Do they, too, have gains to make from it?Gail Murphy's closing question