\section{The architect}

\FigureImposeWidth{MSmeddlerAndHeroes}{The architect integrating all
specialist teamplayers}{.6\textwidth}

The architecting function is ideally performed by every teammember.
However the primary responsibility for the balance and consistency
of requirements, specification and design is owned by the architect.
Figure~\ref{fig:MSmeddlerAndHeroes} shows the architect meddling with
the work performed by all teammembers, in order to obtain the balance
and maintain the consistency.

\FigureImposeWidth{CAFCRprofileSA}{Required architect know-how per view,
typical for current architects and the preferred profile.}{.4\textwidth}

The role of the architect is to (proactively) integrate the work of
all the specialists. This role requires sufficient know-how in the five views,
see figure~\ref{fig:CAFCRprofileSA}. Most current architects have a
dominant technical view on the world and should acquire more know-how
from the customer world.

\FigureImposeWidth{MATfromSpecialistToSystemArchitect}
{The architect maintains technical roots}{.9\textwidth}

This broad profile of the architect does not evolve automatically.
Potential architects grow by stepwise broadening their scope,
see figure~\ref{fig:MATfromSpecialistToSystemArchitect}.
The intermediate roles are quite important in complex systems,
it prevents the need for an impossible broad and heavy superarchitect.


