The ability to produce future proof and sustainable code - using modern methods and a sound approach to Software Projects - are important cornerstones of efficient Software production.

Conference Day 1 offers inspiration and updated knowledge to all Developers, Project Managers and Managers, through lectures and discussions with our internationally renowned speakers and experts.

Programme *)

08:00 Registration

09:00 Conference Starts

12:00 Lunch

17:00 Conference Ends

17-19 Free After Conference Pub

*) Coffee, Sandwich, Cake
& Refreshments are
served during the day!

Key Note:

A lot of people still believe that agile software development is for small teams only. However, the agile value system and the principles behind as stated in the agile manifesto don't say anything about team or project size.

Furthermore the projects I'm working on are typically large, distributed and mission-critical. Therefore, several years ago I took the challenge and tried agile software development in the large. Meanwhile I made the similar experience on many large projects: Also large and even distributed teams can benefit from a value system that is beneficial for small teams.

In this talk I want to show how to scale agile processes to teams of 300. In fact, the same techniques are also relevant to teams of ten or more developers, especially within large organizations.

One of the most popular features of languages such as Smalltalk, ObjectiveC, and Ruby is duck typing. The basic thought behind duck typing is that if an object walks like a duck and talks like a duck, then the language is happy to treat it as if it a duck. In other words: the object’s type is determined by what it can do, not by its class.

Web services exchange information, often in a common, interlingual format such as XML. What happens when we apply the principles behind duck typing to Web services?

This talk presents WS-DuckTyping: not a new W3C standard; but rather a way to deal with XML as if it were a duck. We will give a number of practical tips to implement this Anatidaeic development style, including working with XPath to extract information from incoming Web service request, whether and how to validate XML with a schema, and more. Finally, we will show some recent improvements into Spring Web Services which facilitate WS-DuckTyping.

Since the dawn of the computer age, software delivery has struggled with the communication gap between the business users of our software and the development teams that create it. This seminar explores why this communication gap exists and the various attempts we have made to close it, and presents a new metaphor for creating effective communication between business and technical audiences.

This session was first presented with Martin Fowler from Thoughtworks as a keynote at QCon 2007 entitled "The Yawning Crevasse of Doom"

Software Quality Monitoring and Visualization

Goal of any software engineering is to build software with a decent quality at a decent price. You cannot control what you cannot measure.

The price of software is easy to measure but quality is not. With the VizzAnalyzer we provide a tool to measure quality in software development projects.

Quality could be a lot of things: usability, maintainability, compliance to standards, performance, portability etc. Moreover, what is considered “a decent quality” differs over domains, companies, customers, projects, products, development environments, and times. It is therefore pivotal that quality measurements and tools can be swiftly adapted to the level of decency required in a certain environment. VizzAnalyzer is a highly configurable framework with development language, quality goals, and way of presentation and interpretation as variation points.

In our talk, we present concepts of quality monitoring. Using VizzAnalyzer as the measurement and visualization tool, we demonstrate possible insights and interpretations in quality measurements of some open source software products.

Automated acceptance testing is one of the key practices in agile software development. The presence of a good acceptance test suite allows a system to grow and evolve to meet the changing needs of the business, potentially over many years. It is therefore essential that these tests capture the intent of the system, and are as independent as possible of the current implementation and environment.

In this talk I will explore how to meet these challenges in practice : my main contention is that we should start to see acceptance testing primarily as managing the changes in the system behaviour, rather than asserting that certain statements about the system are always true. I will also demonstrate the open-source testing tools TextTest and JUseCase, which are developed according to this philosophy.

We summarize the most important and recent findings in Software Engineering research and how they can affect your everyday software development.

Industry and academia is in something of a "Moment 22" and must both update their views of each other. One prevailing view in industry is that academic SE research is irrelevant since it is not based on real problems and systems. And among academics one view is that large parts of the industry use outdated methods and does not know about crucial results that could help increase quality and decrease costs.

To get out of this "gap" both sides must be willing to listen and help each other. This talk is a step in this direction. It goes through SE research studies and extracts the results in a no-frills, down-to-earth, hands-on language.

Why should you care about SE research and how can it help you?

And what can you do to help the researchers be even more relevant to you in the future?

Conference Step 1 is also held:

In English!

Programme *)

In cooperation with: