In this book, we are particularly concerned with the role of software architect. It is succinctly
described in the WWISA-charter, where it says “client advocacy is the cornerstone
of the architect’s role”, that is, the software architect is the one understanding the clients
needs, and translating them into the form understood by the software engineers. He discusses
and assesses several alternative designs, plans and controls the realization of the one
agreed upon, and is responsible and accountable–within reasonable limits—for the overall
effectiveness of the project. In a nutshell, a software architect is to a software system what
a building architect is to a building. Thus the name.