Abstract:
IBM and author of The Process of Software Architecting\n\nAs technical lead on a software development project, the architect is responsible for its technical outcome. Some aspects of the architect's role are well-understood, such as deriving an architecture from a set of architecturally-significant requirements. However, there are other aspects to the role that are often overlooked, but that are equally important. The purpose of this session is to consider the process of architecting based on Peter's own experiences together with those of several experienced software architects that Peter has interviewed.