\section{Conclusion}

Figure~\ref{fig:ARtheWrongWay} shows how {\bf not} to work towards the future:
\begin{myList}
\item Don't merge blindly
\item Don't a priori declare SW to be reusable
\end{myList}

\FigureImposeWidth{ARtheWrongWay}{Don't do}{\textwidth}

While figure~\ref{fig:ARrefactoring} illustrates architectural refactoring, applied on the
example of a digital television. The steps taken here are:

{\it From TV to Hybrid TV.} The conventional TV is refactored to use a more modern HW
platform, while the lower layer is factored out. The set top box is physically integrated
in the television, while at software level both applications are pragmatically interfaced.

{\it From Hybrid TV to Digital TV.} More hardware is shared between the TV part and the set top
box part of the system, with as refactoring goals: reduction of resource usage and
enabling a more harmonized user interface. The set top box platform is redesigned to
make this possible.

{\it From Digital TV to ``All-in-one'' TV.}  The TV computing infrastructure is simplified (reduce
lines of count), while the next ``legacy'' application is merged in: storage.

\FigureImposeWidth{ARrefactoring}{Conclusion: Refactoring the Architecture is a must}{\textwidth}
