<html><head><meta name="color-scheme" content="light dark"></head><body><pre style="word-wrap: break-word; white-space: pre-wrap;">\svnInfo $Id: workplan.tex 20439 2010-11-01 10:51:35Z kohlhase $
\svnKeyword $HeadURL: https://svn.kwarc.info/repos/kwarc/doc/macros/forCTAN/dfgproposal/workplan.tex $
\section{Objectives and Work Schedule \deu{(Ziele und Arbeitsprogramm)}}

\subsection{Objectives}

\paragraph{O1: ???}
\paragraph{O2: ???}
\paragraph{O3: ???}

\subsection{Work Schedule} 
\begin{todo}{from the proposal template}
  Give a short high-level introduction to how the work in the project should proceed,
  explain Tables~\ref{fig:wplist} and~\ref{fig:activities}.
\end{todo}
The project is organized around \dfgcount{all}{wa} large-scale work areas which correspond
to the objectives formulated above. These are subdivided into \dfgcount{all}{wp} work
packages, which we summarize in Figure~\ref{fig:wplist}. Work rea
\euRef{wa}{mansubsus}{label} will run over the whole project\ednote{come up with a better
  example, this is still oriented towards an EU project} duration of {\ipower}. All work
packages in {\euRef{wa}{systems}{label}} will and have to be covered simultaneously in
order to benefit from design-implementation-application feedback loops.

\wpfig
\ganttchart[draft,xscale=.45] 

\begin{workplan}
 
\begin{workarea}[id=mansubsus,title={Management, Support \&amp; Sustainability}, short=Management]
  This work-group has two work packages: one for management proper
  ({\euref{wp}{management}{label}}), and one each for dissemination
  ({\euref{wp}{dissem}{label}})
   
  This work group ensures the dissemination and creation of the periodic integrative
  reports containing the periodic Project Management Report, the Project Management
  Handbook, an Knowledge Dissemination Plan ({\euref{wp}{management}{label}}), the
  Proceedings of the Annual {\ipower} Summer School as well as non-public Dissemination
  and Exploitation plans ({\euref{wp}{dissem}{label}}), as well as a report of the 
  {\ipower} project milestones. 
   
\begin{workpackage}[id=management,lead=JU,
                    title=Project Management,
                    JURM=2,JURAM=8,PCRM=2]
Based on the ``Bewilligungsbescheid'' of the DFG , and based on the financial and
administrative data agreed, the project manager will carry out the overall project
management, including administrative management.  A project quality handbook will be
defined, and a {\ipower} help-desk for answering questions about the format (first
project-internal, and after month 12 public) will be established. The project management
will consist of the following tasks 
\begin{tasklist} 
\begin{task}[id=foo,start=0,len=3,requires=\taskin{t1}{dissem}]
  To perform the administrative, scientific/technical, and financial management of the
  project 
\end{task}
\begin{task}[force=0.5,start=13,len=4]
  To co-ordinate the contacts with the DFG and other funding bodies, building on the
  results in \taskref{management}{foo}
\end{task}
\begin{task}
  To control quality and timing of project results and to resolve conflicts
\end{task}
\begin{task}
  To set up inter-project communication rules and mechanisms
\end{task}
\end{tasklist}

\end{workpackage}
 
\begin{workpackage}[id=dissem,lead=PC,
 title=Dissemination and Exploitation,
 PCRM=8,JURAM=2] 
Much of the activity of a project involves small groups of nodes in joint work. This work
 package is set up to ensure their best wide-scale integration, communication, and
 synergetic presentation of the results. Clearly identified means of dissemination of
 work-in-progress as well as final results will serve the effectiveness of work within the
 project and steadily improve the visibility and usage of the emerging semantic services.


 The work package members set up events for dissemination of the research and
 work-in-progress results for researchers (workshops and summer schools), and for industry
 (trade fairs). An in-depth evaluation will be undertaken of the response of test-users.
 
 \begin{tasklist}
  \begin{task}[id=t1,start=6,len=1]
    sdfkj
  \end{task}
  \begin{task}[start=12,len=1]
    sdflkjsdf
  \end{task}
  \begin{task}[start=18,len=1]
    sdflkjsdf
  \end{task}
 \begin{task}[start=22,len=2] 
 \end{task}
\end{tasklist}

Within two months of the start of the project, a project website will go live. This
website will have two areas: a members' area and a public area.\ldots
\end{workpackage}
\end{workarea}
 

\begin{workarea}[id=systems,title={System Development}]
  This work-group has two work packages: one for the development of the
  {\LaTeX} class ({\euref{wp}{class}{label}}), and for the proposal template
  ({\euref{wp}{temple}{label}})

  This work group coordinates the system development.

\begin{workpackage}[id=class,lead=JU,
                    title=A LaTeX class for EU Proposals,short=Class,
                    JURM=12,JURAM=8,PCRM=12,PCRAM=2]
We plan to develop a {\LaTeX} class for marking up EU Proposals

We will follow strict software design principles, first comes a
requirements analys, then \ldots
\begin{tasklist}
  \begin{task}[start=0,len=2]
    sdfsdf
  \end{task}
  \begin{task}[start=4,len=4]
    sdfsdf
  \end{task}
  \begin{task}[id=t3,start=10,len=4]
    sdfsdf
  \end{task}
  \begin{task}[start=20,len=4]
    sdfsdfd
  \end{task}
\end{tasklist}
\end{workpackage} 

\begin{workpackage}[id=temple,lead=PC,
  title= Proposal Template,short=Template,JURM=12]

We plan to develop a template file for {\ipower} proposals

We abstract an example from existing proposals
\begin{tasklist}
  \begin{task}[start=6,len=6]
    sdfdsf 
  \end{task}
  \begin{task}[id=temple2,start=18,len=6,requires=\taskin{t3}{class}]
    sdfsdf
  \end{task} 
\end{tasklist}
\end{workpackage}
\end{workarea}

\end{workplan} 

%%% Local Variables: 
%%% mode: LaTeX
%%% TeX-master: "proposal"
%%% End: 

% LocalWords:  workplan.tex wplist dfgcount wa mansubsus duratio ipower wpfig
% LocalWords:  ganttchart xscale workplan workarea euref dissem workpackage foo
% LocalWords:  tasklist taskin taskref sdfkj sdflkjsdf sdfsdf sdfsdfd sdfdsf
</pre></body></html>