Block 3 of M813 focusses on the functional/logical view of software architecting. Although there’s more to software architecture than just the functional view, that’s all we focus on in this module. (I believe that M814 will extend beyond the functional side to encompass all viewpoints of the software or system architecture.)
A quick web search on the role of the software architect turned up a really interesting and useful website (http://www.codingthearchitecture.com/) which includes an excellent presentation* from 2009 on the software architect’s role, relating to both the definition of a new system, and its delivery. The key thing appears to be the ability to balance competing demands of being both in the details and being able to step back and see the big picture. Isn’t that true of so many high-level roles (E.g. thinking about that Finance Director role I felt ill-equipped to handle, I was stuck too much in the detail, whereas others I’ve seen spend too much time in the ivory tower and not enough in the detail… perhaps there’s a need for more training and development opportunities for professionals in developing this one particular ability.)
While I certainly don’t have the software development experience per se, I have a whole lot of experience (not all of it the most happy experience 🙂 of systems in an enterprise context, and I can certainly see a possible avenue opening up for me in this general direction. One other things which jumps out at me from this presentation though, is the focus on proactivity and being able to (confident in one’s ability to!) lead from the front. Now this, on reflection, is the number one way I fall down (again, regardless of context or profession) and I really do need to engage in practical skills development in confidence for leadership.
*The slide-deck of the presentation – well worth a peruse – is available online and as a PDF download, here: http://www.codingthearchitecture.com/presentations/dw2009-pitfalls-for-new-software-architects/