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.

	Porting a large financial library to OSG Richard Gomes : 29th Jun 2009
	Java in the Google Cloud Chris Read : 29th Jun 2009
	NatTable - a high performance SWT data g Dan Pollitt : 29th Jun 2009
	Developing JavaFX applications in Eclips Neil Bartlett : 29th Jun 2009
	Itemis: Xtext - Developing Domain Specif Heiko Behrens : 29th Jun 2009
	The Basics of OpenGL Paul Thomas : 22nd Jun 2009
	widget framework Richard Hyndman : 22nd Jun 2009
	Iron Ruby Michael Delaney : 16th Jun 2009
	Grails eye for the Spring guy Russ Miles : 15th Jun 2009
	Spring in Government Paul Sweby : 15th Jun 2009
	Open Source project Martijn Verburg : 11th Jun 2009
	Grails eye for the Spring guy Russ Miles : 10th Jun 2009
	Yahoo! BOSS, Build your Own Se Ted Drake : 2nd Jun 2009
	JBehave 2 : 27th May 2009
	Open Source Project Martijn Verburg : 26th May 2009