By alashcraft
via rdaarchitecture.blogspot.com
Published: Jul 31 2008 / 02:04
Welcome to the first in a (hopefully) long and fruitful series of discussions about the role of an architect in the world of software development. I’ll be sharing insights from RDA architects and hopefully spark some conversation around what it means to be an architect. The focus will be on the role of an architect and how a person can do a better job in that role. We’ll distill down our experiences into a set of principles that should be useful to someone, somewhere. To be better architects, first we need to understand what an architect is.
Comments
christian.posta replied ago:
Steve,
Your principle that "The architect is the conduit between the business problem and the technical solution" is still kind of vague to me. You could apply the same principle to a software developer who's job it is to understand the business domain, the problem that's being solved, and develop a technical solution.
Voters For This Link (7)
Voters Against This Link (0)