Changeset 385 for anr

Timestamp:

Feb 22, 2011, 11:30:07 PM (14 years ago)

Author:

coach

Message:

ia: bull to 24 hm + correction MDS.

Location:

anr

Files:

• anr.tex (modified) (1 diff)
• lettres-2011/Alsim.pdf (added)
• lettres-2011/Teamcast.pdf (added)
• section-1.tex (modified) (2 diffs)
• section-dissemination.tex (modified) (1 diff)
• section-position.tex (modified) (2 diffs)
• section-project-description.tex (modified) (1 diff)
• section-ressources.tex (modified) (2 diffs)
• task-demonstrator.tex (modified) (2 diffs)

anr/anr.tex

@@ -155 +155 @@
     \vspace*{0.5ex}Total requested \\ funding
   \end{minipage}
-    & \makebox[3cm]{ \mustbecompleted{???} \euro}
+    & \makebox[3cm]{ 999399.88 \euro}
       & \begin{minipage}{4.15cm}\center Project Duration \end{minipage}
         & \begin{minipage}{3cm}\center 36 months \end{minipage} \\\hline

anr/section-1.tex

@@ -6 +6 @@
 an implementation path directly from HLLs to hardware. Thus, Electronic System
 Level (ESL) design methodologies (Virtual Prototyping, Co-design, High-Level
-Synthesis...) are now mature and but don’t allow still the full automation of a
+Synthesis...) are now mature but don’t allow still the full automation of a
 system-level design flow.
 Unfortunately, ESL tool development today has primarily focused on the design of
@@ -35 +35 @@
 \end{itemize}
 %
-Finally,a large number of SMEs and large companies, (see "letters of interest" Annex \ref{lettre-soutien}),
+Finally, a large number of SMEs and large companies, (see "letters of interest" Annex \ref{lettre-soutien}),
 have expressed their interest for this project:
 \altera, FLEXRAS, INPIXAL, CAMKA System, RENESAS Design, EADS-ASTRIUM,
-CONTINENTAl,
-\mustbecompleted{ADACSYS, ATEME, ALSIM, SILICOMP-AQL, ABOUND Logic.}.\\
-\altera, a major FPGA company provides FPGA cards to the project.
+CONTINENTAl, TEAMCAST, ALSIM.
+\altera, a major FPGA company provides FPGA boards to the project.
 These companies are either FPGA providers (engaged to collaborate by delivering FPGA board to partners),
 design houses, EDA companies, or system integrators.

anr/section-dissemination.tex

@@ -170 +170 @@
 \letterOfInterest{CAMKA System}{lettres-2011/Camka.pdf},
 \letterOfInterest{RENESAS Design}{lettres-2011/Renesas-dossier.jpg},
-\letterOfInterest{EADS-ASTRIUM}{lettres-2011/Astrium.pdf}.
-\letterOfInterest{CONTINENTAL}{lettres-2011/Continental.pdf}.
-\letterOfInterest{CONTINENTAL}{lettres-2011/Continental.pdf}.
-\letterOfInterest{CONTINENTAL}{lettres-2011/Continental.pdf}.
-\letterOfInterest{CONTINENTAL}{lettres-2011/Continental.pdf}.
-\letterOfInterest{CONTINENTAL}{lettres-2011/Continental.pdf}.
+\letterOfInterest{EADS-ASTRIUM}{lettres-2011/Astrium.pdf},
+\letterOfInterest{CONTINENTAL}{lettres-2011/Continental.pdf},
+\letterOfInterest{TeamCast}{lettres-2011/Teamcast.pdf},
+\letterOfInterest{ALSIM}{lettres-2011/Alsim.pdf}.
 %\letterOfInterest{ADACSYS}{lettres-2011/Coach_ADACSYS_lettre_interet},
 %\letterOfInterest{ATEME}{lettres-2011/ATEME.pdf},

anr/section-position.tex

@@ -30 +30 @@
 More specifically, COACH focuses on:
 \begin{itemize}
-\item High level methods and concepts (esp. Requirements and architectural level) for system
+\item High level methods and concepts (esp. eequirements and architectural level) for system
 design, development and integration, addressing complexity aspects and modularity.
 \item Open and modular design environments, enabling flexibility and extensibility by
@@ -38 +38 @@
 environment, suitable for co-operative and distributed development.
 \item Integration of the solutions and engines being developed into a state of the art SoC and system
-design flow, using the IP-XACT IEEE 1685 standard
+design flow, using the IP-XACT IEEE 1685 specification.
 \end{itemize}
 The COACH results will contribute to strengthen Europe's competitive position by developing

anr/section-project-description.tex

@@ -155 +155 @@
 other tasks.
 \label{xcoach-problem}
-Nevertheless, we are confident becausein preparation to this project,
+Nevertheless, we are confident because in preparation to this project,
 academic partners are already working close together and know well each other's
 technologies, and also a lot of face to face meeting are planned at the

anr/section-ressources.tex

@@ -80 +80 @@
 %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
 
-The global effort is \textbf{367} \hommemois (\hommemoislong),
-the part of academic partners is \textbf{245} \hommemois (\textbf{67\%} of the global effort)
-and the part of the industrial partners is 122 \hommemois (\textbf{33\%} of the
+The global effort is \textbf{355} \hommemois (\hommemoislong),
+the part of academic partners is \textbf{245} \hommemois (\textbf{69\%} of the global effort)
+and the part of the industrial partners is 110 \hommemois (\textbf{31\%} of the
 global effort).
 The tables in annexe~\ref{effort:by:livrable} gives this global effort by deliverables,
@@ -170 +170 @@
     and a summary by tasks in the following table.
     \bull employees involved in the project are a manager for 9 \hommemois
-    and an engineer  for 27 \hommemois.}
+    and an engineer for 15 \hommemois.}
   {10}{}
 

anr/task-demonstrator.tex

@@ -28 +28 @@
         The deliverable is the specification of the demonstrator in COACH input format
         defined in the {\NOVERSuseModelSpecification} deliverable.
-      \itemL{12}{36}{d}{\Sbull}{\bull demonstrator}{3:7:10}
+      \itemL{12}{36}{d}{\Sbull}{\bull demonstrator}{2:4:5}
         \setMacroInAuxFile{bullAppSpecification}
         Validation of the demonstrator, the deliverable is a document
@@ -119 +119 @@
         using the COACH milestone of T0+18.
       \itemL{27}{36}{d+x}{\Smds}{Evaluation}{0:3:3}
-        \OtherPartner{18}{36}{Sbull}{0:4:4.5}
+        \OtherPartner{18}{36}{Sbull}{0:2:3.5}
         \OtherPartner{18}{36}{Sthales}{0:4:4.5}
         This deliverable is a document that validates and evaluates the COACH final release