Changeset 33 for anr/section-4.1.tex

Timestamp:

Jan 14, 2010, 5:31:54 PM (14 years ago)

Author:

coach

Message:

Paul: des petites améliorations
M anr/section-3.2.tex
M anr/section-4.1.tex

File:

• anr/section-4.1.tex (modified) (5 diffs)

anr/section-4.1.tex

@@ -12 +12 @@
 \end{figure}
 %
-The figures~\ref{archi-csg}, \ref{archi-hls} and \ref{archi-hpc}
-summarize the software architecture of COACH framework we plan to develop.
+Figures~\ref{archi-csg}, \ref{archi-hls} and \ref{archi-hpc}
+summarize the software architecture of the COACH framework we plan to develop.
 In figures, the dotted boxes are the softwares or formats that COACH
 has to provide.
@@ -48 +48 @@
 The input is a single task of the process network. The HAS tools do not work
 directly on the C++ task description but on an internal format called
-\xcoach generated by a the GNU C compiler (GCC) tainted by a COACH
+\xcoach generated by a the GNU C compiler (GCC) 
+%Paul: ``tainted'' ça ve dire ``souillé''. Qu'est-ce que tu veux dire
+%exactement: piloté, modifié ....?
+tainted by a COACH
 driver. This allows on the one hand to insure that all the tools will
 accept the same C++ description and on the other hand to make possible
@@ -69 +72 @@
 is done through \verb!CSG! (figure~\ref{archi-csg}).
 \vspace*{.75ex}\par
-The project is splitted into 8 tasks numbered from 0 to 7.
+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:
@@ -95 +98 @@
     both PC and FPGA-SoC sides, the hardware communication components.
 \item\textbf{Demonstrators:}
-    This task groups the demostrators of the COACH project.
+    This task groups the demonstrators of the COACH project.
     \mustbecompleted{FIXME}
 \end{enumerate}
@@ -122 +125 @@
 \item $T7$ and $T0$ respectively depends on and impacts all the other tasks.
 \end{itemize}
-So this organisation offers enough robustness for insure the success of the
-project except for the specification task $T1$. However, the partners meet
-10 times (a one day meeting per month) during the last years to prepare the
-specification and the project proposal.
+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.
+
+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.