OOPSLA '04

Program
Technical Program
  Invited Speakers
  Technical Papers
  Onward!
  Panels
  Practitioner Reports
  Tutorials
Workshops
DesignFest
Educators' Symposium
Demonstrations
Posters
Doctoral Symposium
Exhibits
Student Research Comp.
FlashBoF
 
Turing Lecture
 
Social Events
 
Week at a Glance
 
Final Program (1.5M .pdf)

Find in Program
 

Page
Printer-friendly

Basket
view, help

"Healing the Architecture"
Object-Oriented Programming, Systems, Languages and Applications
Home    Program    Housing & Transportation    Registration    Submissions    Wiki    Maps
 
  > Technical Program > Tutorials > All Tutorials

 : Wednesday Afternoon Tutorials (1:30 - 17:00) : Architecture and the Enterprise : Wednesday

Healing the Architecture

Meeting Room 13
Wednesday, 13:30, half day
 


 
7·8·9·10·11·12·13·14·15·16·17·18·19·20·21

Klaus Marquardt, Draeger Medical AG:  Klaus Marquardt is lead software architect at Dr?ger Medical in L?beck, Germany. Since 1996 he is responsible for the architecture of a family of life supporting machines, and he has managed to combine architecture quality and sustainability with an attitude to learning and problem solving. Klaus has co-organized various workshops at previous OOPSLA conferences on agile development and software architecture, and contributed to other conferences including EuroPLoP, OOP (Germany), OT (UK), VikingPLoP, and JAOO (Denmark). He is program chair of EuroPLoP 2004.

Tutorial number: 47

Having a job title is an insufficient qualification for being a software architect. Seasoned architects have learned how to transition the architecture vision into the projects' reality. They are able to detect problems before they have become critical, and know a variety of different measures appropriate to the situation at hand.

This tutorial gives the participants a new way to look at software architecture, which is appropriate beyond the up-front architecture especially for projects in crises and agile development. The knowledge of early symptom recognition and selection of a reaction can be collected in the form of diagnoses and therapies. The tutorial covers problems related to organization and process, design and implementation, role and attitude in a mixture of lecture and interactive exercises. Attendees will be able to relate their experiences to already known and proven solutions.

Intermediate: Attendees should have finished a significant project and collected first experience with software architecture or an architect.