Index: anr/section-4.1.tex
===================================================================
--- anr/section-4.1.tex	(revision 65)
+++ anr/section-4.1.tex	(revision 99)
@@ -17,5 +17,5 @@
 In figures, the dotted boxes are the softwares or formats that COACH
 has to provide and to support.
-\vspace*{.75ex}\par
+\parlf
 For the system generation presented in figure~\ref{archi-csg}, the conductor
 is the tool \verb!CSG! (COACH System Generator). Its inputs are a process
@@ -35,9 +35,8 @@
 FPGA device\footnote{Additional partial bitstreams are generated in case of
  dynamic partial reconfiguration}.
-\\
 %To proove CSG that COACH is open and CSG is really configurable, COACH will
 %basically support 3 architecture template (the COACH template based on a
 %MIPS processors and a VCI token ring, the Altera template based on the NIOS
-%and AVALON bus, the Xilinx template based on the MICROBLAZE and OPB bus)
+%and AVALON bus, the Xilinx template based on the MICROBLAZE and PLB bus)
 %and 2 operating systems (DNA/OS and MUTEK). Furthermore, thus is enforced
 %by the \mustbecompleted{FIXME:zied} contribution that consists in
@@ -46,5 +45,5 @@
 %Finally, it is important to notice that this work is a strong
 %enhancement of the SocLib software.
-\vspace*{.75ex}\par
+\parlf
 The software architecture for HAS is presented in figure~\ref{archi-hls}.
 The input is a single task of the process network. The HAS tools do not work
@@ -61,5 +60,5 @@
 Furthermore, the back-end tools uses a macro-cell library (functional and memory
 unit).
-\vspace*{.75ex}\par
+\parlf
 In addition to digital system design, HPC requires a supplementary
 partitioning step presented in figure~\ref{archi-hpc}. The designer
@@ -70,22 +69,23 @@
 simulator. Once the partitioning is validated, the design of the FPGA part
 is done through \verb!CSG! (figure~\ref{archi-csg}).
-\vspace*{.75ex}\par
 \mustbecompleted{FIXME == MODIFICATION DE LA FIGURE}
-The project is split into 8 tasks numbered from 0 to 7.
-The first task (task 0) is the project management, the last one (task 7) is
-the dissemination the other task are listed below:
-\begin{enumerate}
-\item\textbf{\Backbone:} This task tackles the fundamental points of the
+\parlf
+The project is split into 8 tasks numbered from 1 to 8. There are described
+bellow and detailled in section \ref{task-description}.
+\begin{description}
+\item[Task-1: \textit{Project management}]
+    This task relies to the monitoring of the COACH project.
+\item[Task-2: \textit{\Backbone}] This task tackles the fundamental points of the
 	project such as the defintion of the COACH inputs and outputs,
     the internal formats (e.g. \xcoach), the architectural templates and
     the design flow.
-\item\textbf{System generation:} This task addresses the prototyping and
+\item[task-3: \textit{System generation}] This task addresses the prototyping and
     the generation of digital system. Apart from HAS that belong to the task 3
     and 4, its components are those presented figure~\ref{archi-csg}
     (e.g.  \verb!CSG!, operating systems).
-\item\textbf{HAS front-end:} This task mainly focusses on four functionalities:
+\item[Task-4: \textit{HAS front-end}] This task mainly focusses on four functionalities:
     optimization of the memory usage, parallelism enhancement through loop
     transformations, coarse grain parallelization and ASIP generation.
-\item\textbf{HAS back-end:} This task groups two functionalities:
+\item[Task-5: \textit{HAS back-end}] This task groups two functionalities:
     High-Level Synthesis of data dominated description and HLS of control
     dominated description.
@@ -93,13 +93,21 @@
     that will allow the coprocessors to respect the processor \& the bus
     frequency.
-\item\textbf{Communication between PC \& FPGA-SoC:}
+\item[Task-6: \textit{PC/FPGA communication middleware}]
     This task pools the features dedicated to HPC. The main are the
     partitioning validation (see figure~\ref{archi-hpc}), the sytem drivers for
     both PC and FPGA-SoC sides, the hardware communication components and
 	support for dynamic partial reconfiguration.
-\item\textbf{Demonstrators:}
+\item[Task-7: \textit{Industrial demonstrators}]
     This task groups the demonstrators of the COACH project.
-    \mustbecompleted{FIXME}
-\end{enumerate}
+    Most of them are industrial applications that will be developped with the COACH
+    framework.
+    Others consist in integrating COACH framework as a driver of industrial proprietary
+    design tools.
+\item{Task 8: \textit{Dissemination}}
+    This task relies to the diffusion of the project results.
+    It mainly consists of the production of 4 COACH releases (\verb!T0+12!, \verb!T0+18!,
+    \verb!T0+24! and \verb!T0+36!)
+    and the publication on a WEB site of a tutorial.
+\end{description}
 %
 \begin{figure}\leavevmode\center
@@ -109,28 +117,28 @@
 \end{figure}
 Figure~\ref{dependence-task} presents the tasks dependencies.
-"$task-N \longrightarrow task-M$" means that $task-N$ impacts the $task-M$. 
+"$T_N \longrightarrow T_M$" means that $T_N$ impacts the $T_M$. 
 The more bold is the arrow, the more important is the dependency.
 The graph shows:
 \begin{itemize}
-\item Even that $T3$ and $T4$ functionalities are complementary, their
+\item Even that $T4$ and $T5$ functionalities are complementary, their
 developments are independent (thanks to \xcoach internal format).
-\item $T2$ slightly depends on $T3$ and $T4$. Indeed, $T2$ may works
-without $T3$ and $T4$ if we limit to digital systems without hardware
+\item $T3$ slightly depends on $T4$ and $T5$. Indeed, $T3$ may works
+without $T4$ and $T5$ if we limit to digital systems without hardware
 accellerators. 
-\item $T2$ strongly impacts on $T5$ but, $T2$ does not depend at all on
-$T5$. So demonstrators ($T6$) of embedded system would not be impacted if
-$T5$ would fail.  
-\item $T1$ drives all the tasks ($T2$, $T3$, $T4$, $T5$) at the heart of
+\item $T3$ strongly impacts on $T6$ but, $T3$ does not depend at all on
+$T6$. So demonstrators ($T7$) of embedded system would not be impacted if
+$T6$ would fail.  
+\item $T2$ drives all the tasks ($T3$, $T4$, $T5$, $T6$) at the heart of
 the COACH project.
-\item The demonstrators developped in $T6$, of course, strongly depends on the achievements 
-of the prvious tasks ($T1$, $T2$, $T3$, $T4$, $T5$).
-\item $T7$ and $T0$ respectively depends on and impacts all the other tasks.
+\item The demonstrators developped in $T7$, of course, strongly depends on the achievements 
+of the prvious tasks ($T2$, $T3$, $T4$, $T5$, $T6$).
+\item $T8$ and $T1$ respectively depends on and impacts all the other tasks.
 \end{itemize}
 This organisation offers enough robustness to insure the success of the
-project except for the specification task $T1$. 
-
-The only critical task in this chart is T1. \label{xcoach-problem}
+project except for the specification task $T2$. 
+\\
+The only critical task in this chart is $T2$. \label{xcoach-problem}
 However, the partners met
 10 times (a one day meeting per month) during the last year to prepare the
 specification and the project proposal. This gives us a degree of confidence 
-that T1 will be completed in time.
+that $T2$ will be completed in time.
