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.

	Xtend Sven Efftinge : 1st Feb 2012
	JSR Martijn Verburg : 1st Feb 2012
	Neo4j Internals Tobias Lindaaker : 25th Jan 2012
	HTML5 & Android Webview Dave Springgay : 19th Jan 2012
	ScalaMock Paul Butcher : 18th Jan 2012
	Real-world Clojure Malcolm Sparks : 17th Jan 2012
	1000 lines of Clojure Julian Birch : 17th Jan 2012
	paredit-mode Neale Swinnerton : 17th Jan 2012
	Clojure & MaxMSP Nick Rothwell : 17th Jan 2012
	Grails 2 Peter Ledbrook : 16th Jan 2012
	Enterprise Integration John T. Davies : 12th Dec 2011
	Spock Luke Daley : 8th Dec 2011
	Getting Groovy on the Web and Desktop Andres Almiray : 8th Dec 2011
	DiscoBot: Groovy on Android Erik Pragt : 8th Dec 2011
	KEYNOTE - Groovy Update Guillaume LaForge : 8th Dec 2011