deletions | additions       diff --git a/Architecture.tex b/Architecture.tex  index 7ba5b81..7d6e61f 100644  --- a/Architecture.tex  +++ b/Architecture.tex 
...
At startup the Iris application reads the list of Components to be initiated, and calls their init call-back, which is in turn passed useful information like the SEDManager, or hooks to the application environment (more information is provided in the following sections).  The advantages of this architecture are both functional and non functional: it helped our heterogeneous developing team to work in a loosely coupled way, reducing the overall project risk, but it also provides the extensible framework we were seeking in the first place. As a matter of fact, Plug-ins that can be loaded at run time (see section \ref{sec:plugins}) implement the same interfaces that the built-in components do (see section \ref{sec:builtin}), \ref{sec:components}),  and they are instantiated exactly the same way. The only difference is in the timing: built-in Components get instantiated when the application itself is intialized, while plug-in can be instantiated (and discarded) at any time during the application execution.