Recently read a book "Large Scale Software Architecture - A practical guide to using UML." After a long time found a book which is very precise, practical and to the point; especially the details about the architecture view points. Authors Jeff Garland and Richard Anthony have done a splendid job.
I believe that language and technology are the barriers which architects create for themselves. A open mind can solve problem faster, easier and cheaper.
Who would have thought a generation of scripting / web scripting languages like python and perl could automate your tasks, parse xml and html, handle interupts, run periodic programs, provide regular expression and scripting engines to your programs.
Architect should break the language barrier and select something most suitable for the task. If a task demands something to be done by multiple languages so be it.
Recently devising localization architecture for client user interface (web pages) the need for parsing HTML arose. Optimal solution led to "python" (a programming language - to those uninitiated) which can make the task achievable in few hundred lines of code. Most importantly I could find that the HTML parser was in-built and sample code available to use.
This is a huge dilemma.
But according to me the ultimately choice is an architect who
- understands concerns of various stakeholders
- practical implementation approach rather than theoretical (rare breed)
- focuses on quality right from word go (hence saves costs!)
- technology passion is required but with emotional detachment. [it is this which spoils the game]
- must believe in processes and following them
I think these qualities can get any job done good enough!!!
Hope this helps,
(This is my answer to question posted on IASA Group on Linked In - http://www.linkedin.com/groupAnswers?viewQuestionAndAnswers=&gid=1523&discussionID=7285433&sik=1253305771360&split_page=1&report.success=PdmtybENV2mnc3t3p8JpWuFiB1ZhaD9OnKUphCsu7LRNRYTOK1wrHHO_rcDN0rVBb1wuxUyPL-SZ)