The transition from architectural vision to production code is not always an easy one. Of course we plan for a certain amount of change and accept that some decisions will, on occasion, be wrong. However, without effective communication of the architecture and timely feedback mechanisms, can we really expect to see software that we recognise?

Whether we're up to our elbows in an agile team or riding a barrel down a waterfall project, our choice of what we define and how we convey it can have an enormous bearing on how the architecture is reflected in the software. This session takes a look at some techniques for sharing the architecture and not just publishing it.

	Lean Agile Jumpstart John Stevenson : 27th Jul 2010
	7 Things About Java 7 Ben Evans : 27th Jul 2010
	Yura.net - Swing ME : 27th Jul 2010
	Scala (An Overview) Kevin Wright : 27th Jul 2010
	Diabolical Developer Martijn Verburg : 27th Jul 2010
	Wicket and Scala : 27th Jul 2010
	Scaling with Akka Maciej Matyjas : 14th Jul 2010
	Zen and the art of build script maintena John Smart : 8th Jul 2010
	SEAM Hibernator/Validator Mike Burton : 5th Jul 2010
	Scala Modules Neil Bartlett : 5th Jul 2010
	Scala, Why Now? Peter Pilgrim : 5th Jul 2010
	Final Talk Peter Pilgrim : 5th Jul 2010
	Keynote Jeremy Grelle : 16th Jun 2010
	Building Flex Applications with Grails. Tomas Lin : 16th Jun 2010
	An Intro to the Spring ActionScript Fram Christophe Herreman : 16th Jun 2010