In this session we will be looking how to avoid such architectural decay and degeneration and how continuous monitoring can improve the situation. (and avoid architectural violations) In addition we will look at "refactoring in the large" and how refactoring can be simulated.
Eclipse JDT has some basic support to enforce dependency rules but as we will see for real architectural checking we need much more...
We will also look at some popular open source projects like ant, findbugs and eclipse (CDT/JDT) and see if and how far architectural erosions happens/ed there.
At the end you will have a good feeling how far an automated and tool supported approach can lead to better results and how they can discover areas of erosion and suggest improvements.
Bio: Speaker Bernhard Merkle (Bernhard.Merkle@gmail.com or @sick.de) Bernhard Merkle works as a Software Architect and Engineer for Software Engineering in the central Research & Development Department at SICK AG, one of the worlds leading producers of sensors and sensor solutions. He serves as internal consultant for the complete Software Development Cycle and is responsible for Process and Methods selection as well as Tool Evaluation and Introduction. In his spare time he gives a lecture about MDSD (Model Driven Software Development)at the University of Furtwangen in the Faculty Application Architecture Master. He regularly writes technical Articles about those and new technologies in IT-magazines and also gave sessions at various conferences (e.g. ACCU, Codegeneration, Conquest, OOP and IX).