<<< Previous speaker Next speaker >>>

Wolfgang Strunk, Siemens

 Wolfgang  Strunk

Wolfgang Strunk is software architect at Siemens Enterprise Communications in Munich, Germany. His main area is building a large scale service oriented framework as a base for developing unified communication applications.

Wolfgang has more than 10 years experience developing SW in different markets. He has lead the design and implementation of several large-scale industrial software projects most of them in the area of telecommunication. The common thread is a focus on customer-centric design based on object-oriented concepts. Prior to his development work, he worked as research assistant at University of Hamburg and wrote a number of articles on development tools, frameworks and patterns.

When he is not working, you can find him spending time playing handball or hiking with his wife Roya and daughters Anahita and Taraneh in the german Alps.

Presentation: "The Symphonia Product-Line"

Time: Tuesday 16:55 - 17:55

Location: Conference Hall


When we decided to start building the Siemens OpenSOA product line, it was pretty clear, we would have to deliver the first building block, our so called Symphonia framework, in a "rock solid" quality. As the framework is the runtime environment for all other applications, ervery error would directly influence all other applications. The quality of the architecture should not only be reflected as it is in the implemented system, but we wanted to be able to address it by a number of measures upfront: we defined non functional requirements and tests to proof them prior to the implementation of the affected parts instead of just testing them late in the process. We introduced test driven development to have running and tested software in every stage of the project. We conducted architectural assessments by internal and external auditors.

Nevertheless, it turned out lately that three factors were more important than all others: first of all architecturall quality is directly correlated to the degree your software satisfies the requirements. Secondly it is more important how well the architecture can be maintained and evolved than that you reached a good architecture at one point in time. Lastly you have a good portion of work to establish a development community which cares for quality as a matter of course and does not judge testing quality into the product as the last production step before delivery.

Password protected Download slides