Autoren: Peter Eeles
As technical lead on a software development project, the architect is responsible for its technical outcome.
As 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 "A Day in the Life" of a software architect, by drawing upon the presenter's own experiences together with those of several experienced software architects that the presenter has interviewed.