A transformational guide to the profession of software architecture.Whether a structure is built of bricks, steel, or computer code, the process begins with an architect and client. Together they arrive at a shared vision--a plan--that the architect guides through the bidding, construction, and implementation phases. The Parthenon and the Empire State Building were built according to architectural designs, but the software industry has been building information skyscrapers without architects. It is time for the profession to become a reality.Successful software-based technology is designed, then built. It does not "develop." Who creates the design? An enormous grass-roots demand exists for software architects-but a true profession of software architecture is not yet established. Many software professionals adopt the gravitas of the title "software architect," but fail to fulfill the true, classical role. Drawing on deep metaphors from traditional architecture, Marc T. Sewell, President of the Worldwide Institute of Software Architects, and Laura M. Sewell examine the nature of architecture, what defines a software architect, and how the profession is coming of age.The Software Architect's Profession is lingo-free. It is a book of philosophy that will enable anyone to understand software construction, and it is the first "line in the sand" defining the parameters of this fledgling, yet ancient, e-profession.Key areas include: Bridging the chasm that separates clients from technical professionalsDifferentiating the professions within the software construction industry and defining the roles and accountabilities of software engineers and software"builders"Discussing the vocational temperament and aptitudes that characterize architectsReviewing the phases of architecture Describing the critical role of the client in understanding and validating the desig