deletions | additions       diff --git a/Architecture.tex b/Architecture.tex  index f3e6a0e..21d832c 100644  --- a/Architecture.tex  +++ b/Architecture.tex 
...
As mentioned before, Iris was designed to put together existing and newly developed software components in a rich, extensible application. Also, Iris was developed by a distributed team.  In order to minimize the risk deriving from such constraints, we backed Iris with a loosely coupled architecture through a design pattern called Inversion of Control \citep{10.1.1.101.8594}. \citep{ioc}.  But it was not just a matter of risk management: this design pattern also supports the implementation of ``liquid requirements'', i.e. a finite set of predetermined requirements plus an undefinite set of custom requirements to be implemented by users, at least in some simple cases, or, for more advanced features, by third party developers.