Changeset 65 for anr

Timestamp:

Feb 2, 2010, 9:55:00 PM (15 years ago)

Author:

coach

Message:

IA: modif UBS

File:

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

anr/section-4.1.tex

@@ -14 +14 @@
 %
 Figures~\ref{archi-csg}, \ref{archi-hls} and \ref{archi-hpc}
-summarize the software architecture of the COACH framework we plan to develop.
+summarize the software architecture of the COACH framework we will develop.
 In figures, the dotted boxes are the softwares or formats that COACH
-has to provide.
+has to provide and to support.
 \vspace*{.75ex}\par
 For the system generation presented in figure~\ref{archi-csg}, the conductor
@@ -67 +67 @@
 other running in a FPGA plugged on the PCI/X PC bus. The two parts exchange data
 through communication primitives (tag 2) implemented in a library.
-The relevance of the partitioning is evaluated through a
+To evaluate the relevance of the partitioning, the designer can build a
 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}
@@ -110 +108 @@
 \caption{\label{dependence-task}Task dependencies}
 \end{figure}
-Figure~\ref{dependence-task} presents the dependencies between the tasks.
-"$task-N \longrightarrow task-M$" means that $task-N$ requires $task-M$
-to work and be demonstrated. The more bold is the arrow, the more important is
-the dependency.
+Figure~\ref{dependence-task} presents the tasks dependencies.
+"$task-N \longrightarrow task-M$" means that $task-N$ impacts the $task-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
 developments are independent (thanks to \xcoach internal format).
-\item $T2$ depends slightly from $T3$ and $T4$. Indeed, $T2$ may works
+\item $T2$ slightly depends on $T3$ and $T4$. Indeed, $T2$ may works
 without $T3$ and $T4$ if we limit to digital systems without hardware
-accellerators.
-\item $T5$  strongly depends on $T2$ but, $T2$ does not depend at all on
+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
-the COACH project. 
+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.
 \end{itemize}