• What is your definition of software architecture?
• How is software architecture positioned in your organization (value and benefits)?
• …

(There were more questions; ask us to invite Dana again if you want to know them all )

Usually, to such a list of questions you really find some (sometimes shallow) answers to work with but the ones Dana posed really got me started on the role of software architecture in general. What indeed is a good definition of software architecture ? Is the value of (good) software architecture a measurable entity ? I think not. Many times during the course of the workshop I pondered about quality and got thrown back to college time when I read “Zen and the art of motorcycle management”, that also addresses the notion of quality: That what you just like. Is that enough ? Certainly not ! With respect to software architecture it also counts if the product (or products) that is (are) based on the architecture even get to production state and actually start adding value for your company. If they do not, then it has all been in vain…

Many issues like these got addressed during the workshop. Also the political forces that influence technical decisions where explained with such clarity that my understanding of what it takes to be a good software architect (and what personal skills I lack !) has grown enormously.

In short, a must-attend workshop for all stakeholders to the process of employing software to extend business for a company: manager, CEO, CFO, engineer and last but certainly not least the architects.