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.

	nicolas yuen accessibility API in Flex Nicolas Yuen : 17th Mar 2010
	Grails plugin testing Peter Ledbrook : 15th Mar 2010
	Lift - Getting started with Scala and Li Richard Dallaway : 8th Mar 2010
	PrimeFaces: Next Generation JSF Componen Cagatay Civici : 3rd Mar 2010
	Integrating JSF with Spring Web Flow Karl Widmer : 3rd Mar 2010
	Pax Exam 2.0 – Testing in the Cloud... Toni Menzel : 22nd Feb 2010
	OSGi-based Workflow Engine Doreen Seider : 22nd Feb 2010
	Dependency Injection OSGi style Felix Meschberger : 22nd Feb 2010
	JVM language Guillaume LaForge : 22nd Feb 2010
	Creating Proximity over a Distance Jutta Eckstein : 22nd Feb 2010
	dm Server 2.0 Glyn Normington : 22nd Feb 2010
	Re-writing Java classes in Scala - and m Colin Howe : 8th Feb 2010
	Erjang - A Java Hacker in Erlang Land Krestan Krab Thorup : 3rd Feb 2010
	Scala for Java Miles Sabin : 28th Jan 2010
	Professional Code Jam... Peter Pilgrim : 26th Jan 2010