Changeset 356 for anr/task-demonstrator.tex

Timestamp:

Feb 6, 2011, 2:29:09 PM (13 years ago)

Author:

coach

Message:

1ere Pre-release

File:

• anr/task-demonstrator.tex (modified) (6 diffs)

anr/task-demonstrator.tex

@@ -55 +55 @@
         \setMacroInAuxFile{trtAppSpecification}
         This deliverable is a document that specifies the application.
-      \itemL{6}{12}{x}{\Sthales}{\thales demonstrator}{4:0:0}
-        This deliverable is the code of the application specified in the former
-        deliverable (\trtAppSpecification).
+      \itemV{6}{12}{x}{\Sthales}{\thales demonstrator}
+        The deliverable is the specification of the demonstrator in COACH input format
+        defined in the {\NOVERSuseModelSpecification} deliverable (milestone M2).
+      \itemL{12}{27}{x}{\Sthales}{\thales demonstrator}{3:2:2}
+        Validation of demonstrator for M4 milestone.
+        The deliverable is the specification of the demonstrator in COACH
+        milestone M4.
     \end{livrable}
 %
@@ -67 +71 @@
     be able to partition the application on the architecture.
     \begin{livrable}
-      \itemL{6}{18}{x}{\Sthales}{SPEAR-DE adaptation}{6:7:0}
+      \itemL{6}{27}{x}{\Sthales}{SPEAR-DE adaptation}{6:7:3}
         \setMacroInAuxFile{trtSpearde}
         Adaptation of SPEAR-DE for COACH framework.
@@ -73 +77 @@
     \end{livrable}
 %
-  \subtask{\mds use case}
+\subtask{\mds use case}
     The goal of the \mds demonstrator will be to experiment and validate the good integration
     of the COACH tools into an industrial SoC design flow for critical systems. This demonstrator will be based on 
@@ -82 +86 @@
     generic enough or at least customizable in order to be at the basis of the further deployement into 
     actual design flows. The objectives of this demonstrator are the following:
-\begin{itemize}
-        \item Validate the IP-XACT packaging of the generated SoC
-        \item Experiment the integration of the generated SoC into the top level (TLM or RTL) of a bigger system
-        \item Bring a focus on flow capabilities for requirements traceability from system properties, down to sub-systems implementation
-\end{itemize}
-
+    \begin{itemize}
+          \item Validate the IP-XACT packaging of the generated SoC.
+          \item Experiment the integration of the generated SoC into the top level
+      (TLM or RTL) of a bigger system.
+          \item Bring a focus on flow capabilities for requirements traceability
+      from system properties, down to sub-systems implementation.
+    \end{itemize}
     \begin{livrable}
       \itemV{0}{12}{d}{\Smds}{Use case}
@@ -97 +102 @@
         This deliverable is the final demonstrator specified in (\mdsAppSpecification).
     \end{livrable}
-
+%
 \subtask{Evaluation report}
     In this sub-task, \mds, \thales and \bull will evaluate the COACH platform.
@@ -113 +118 @@
         using the COACH milestone of T0+18.
       \itemL{27}{36}{d+x}{\Smds}{Evaluation}{0:3:3}
-        \OtherPartner{18}{36}{Sbull}{0:4:5}
-        \OtherPartner{18}{36}{Sthales}{0:4:5}
+        \OtherPartner{18}{36}{Sbull}{0:4:4.5}
+        \OtherPartner{18}{36}{Sthales}{0:4:4.5}
         This deliverable is a document that validates and evaluates the COACH final release
         for the demonstrators.