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.

	Webcentric Steve Herron : 14th May 2008
	Domain Driven Design Eric Evans : 13th May 2008
	RESTful Design Peter Rodgers : 8th May 2008
	High volume, low latency syste Simon Brown : 6th May 2008
	Web Development with Groovy & Graeme Rocher : 6th May 2008
	JBoss SEAM and JSF Peter Pilgrim : 16th Apr 2008
	Sharing Architectures Kevin Seal : 8th Apr 2008
	The Next Step in Unit Testing and J... Frank Cohen : 7th Apr 2008
	RESTful design Peter Rodgers : 12th Mar 2008
	Case Study of a Small Tactical Sof... Simon Brown : 4th Mar 2008
	Java Closures - Comparing the Choic... Stephen Colebourne : 3rd Mar 2008
	Auto-Magic Web Apps w Apthena Richard Gemmell : 3rd Mar 2008
	Ajax and JSF: Natural Synergy... Kito Mann : 19th Feb 2008
	Web Framework Smackdown Peter Pilgrim : 19th Feb 2008
	Pimp Your Web App with Ext and Louis Emmett : 21st Jan 2008