\documentclass[11pt]{article}

\usepackage{hyphenat}
\usepackage{xspace}
\usepackage{amsmath}
\usepackage{graphicx}
\usepackage{subfigure}
\usepackage{wrapfig}
\usepackage{fancyhdr}
\usepackage{hyperref}
\usepackage{boxedminipage}
\usepackage{color}
\usepackage{helvet}
\usepackage[utf8]{inputenc}
\usepackage{natbib}
\usepackage{todonotes}
\usepackage{blindtext}

\setlength{\bibsep}{0.0pt}

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\newcommand{\ThesisTitle}{My Bachelor/Master/Diploma Thesis Title\xspace}
\newcommand{\ProjectAcronym}{\textsc{MBMDTT}\xspace}

% % some commands for commenting
\usepackage{ifthen}
\usepackage{amssymb}
\usepackage[normalem]{ulem} % for \sout
\newboolean{showcomments}
\setboolean{showcomments}{true} % toggle to show or hide comments
\ifthenelse{\boolean{showcomments}}
  {
		%\usepackage{showkeys} %Show lables and refs
		\newcommand{\nbb}[2]{
		% \fbox{\bfseries\sffamily\scriptsize#1}
		\fcolorbox{black}{yellow}{\bfseries\sffamily\scriptsize#1}
		{\sf$\blacktriangleright$\textcolor{blue}{\textit{#2}}$\blacktriangleleft$}
		% \marginpar{\fbox{\bfseries\sffamily#1}}
		}
		
		\newcommand{\version}{\emph{\scriptsize$-$9.2.2011$-$}}
		\newcommand{\remarks}[1]{\color{red}[#1]\color{black}}
		\newcommand{\copied}[1]{\color{green}[#1]\color{black}}
		\newcommand{\modified}[1]{\color{blue}[#1]\color{black}}
		\newcommand{\raw}{$\rightarrow$}
		\newcommand{\old}[1]{\textcolor[rgb]{0.8,0.8,0.8}{#1}}%old stuff
		\newcommand{\ins}[1]{\textcolor{blue}{\uline{#1}}} % please insert
		\newcommand{\del}[1]{\textcolor{red}{\sout{#1}}} % please delete
		\newcommand{\chg}[2]{\textcolor{red}{\sout{#1}}{\raw}\textcolor{blue}{\uline{#2}}} % please change
		\newcommand{\ugh}[1]{\textcolor{red}{\uwave{#1}}} % please rephrase
  }
  {
		\newcommand{\nbb}[2]{}
		\newcommand{\remarks}[1]{}
		\newcommand{\modified}[1]{#1}
		\newcommand{\copied}[1]{#1}
		\newcommand{\version}{}
		\newcommand{\old}[1]{#1} % please rephrase
		\newcommand{\ugh}[1]{#1} % please rephrase
		\newcommand{\ins}[1]{#1} % please insert
		\newcommand{\del}[1]{} % please delete
		\newcommand{\chg}[2]{#2} % please change
  }
% reviewer and advisor comments
\newcommand{\lars}[1]{\nbb{Lars}{#1}}
\newcommand{\avh}[1]{\nbb{Andre}{#1}}
\newcommand{\dusan}[1]{\nbb{Dusan}{#1}}

% if you want to add a TODO
\newcommand{\TODO}[1]{\todo[inline]{#1}}

\newenvironment{compact_itemize}{

 \begin{itemize}
  \setlength{\itemsep}{1pt}
  \setlength{\parskip}{0pt}
  \setlength{\parsep}{0pt}
}{
  \end{itemize}
 }

% Dealing with identifiers
\newcommand{\mathid}[1]{\textit{#1}}
\newcommand{\codeid}[1]{\texttt{#1}}
% \let\codeid=\mathid
\def\|#1|{\mathid{#1}}
\def\<#1>{\codeid{#1}}


%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

\renewcommand{\familydefault}{\sfdefault}

\voffset-0.0cm
\hoffset0.0cm
\topmargin0.0cm
\headheight0.0cm
\headsep0.0cm
\topskip0.0cm
\textwidth 16cm
\textheight 22cm
\oddsidemargin-0.245cm
\evensidemargin-0.245cm
\footskip1.0cm

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
%Header +Footer
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

\pagestyle{fancyplain}
\usepackage{lastpage}
\fancyhf{}
\renewcommand{\headrulewidth}{0pt} % remove lines
\renewcommand{\footrulewidth}{0.5pt}
\lfoot{ \fancyplain{}{\ThesisTitle} }
\rfoot{ \fancyplain{}{Page \thepage \xspace of \pageref{LastPage}} }
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
%\usepackage{multibib}
%\newcites{own}{   }


%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
% Summaries and results
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

\newenvironment{keypoints}{%
\medskip\noindent
\begin{boxedminipage}{\linewidth}\vspace{6pt}
\begin{compact_itemize}}{%
\end{compact_itemize}\vspace{-6pt}
\end{boxedminipage}}


%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
% Document start
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

\begin{document}

\section*{\ThesisTitle\ -- (\ProjectAcronym)}
\subsection*{---\,Proposal for a Master's/Bachelor's Thesis\,---}

\sloppy

\noindent Firstname Lastname

\noindent Advised by:
\begin{itemize}
 \item \ldots
\end{itemize}

\begin{center}
\line(1,0){450}
\end{center}

\section*{Topic Description}
This is my topic description.
In this section I will provide a short introduction on what is the problem at hand, why it is a problem, and what I propose to do.
Shaw~\citep{Shaw2003} wrote a paper with hints on how to write good software engineering research papers.
By the way, this was an example for using the \textit{natbib} command \texttt{\textbackslash{}citet\{\}}.
\textit{AspectJ} is tool to weave cross-cutting concerns into Java programs~\citep{AspectJ}. This was just an example for using the \textit{natbib} command \texttt{\textbackslash{}citep\{\}}.
Some grouped references from the SE@HU Group: \citep{Aleti09BGM,Grunske07CW,Grunske06LBPP,Grunske08}, as well as an article example: \citep{Grunske07JSS}.\\

General advice: You should make good use of \emph{diagrams, graphics, tables} and/or other visual elements to explain your topics.






\section{State of the art and preliminary work}
% When analyzing software, we typically use abstractions that tell us what happened in the past and what will not happen in the future.  Such a clear separation is useful for logical reasoning.

In the following, I will review the state of the art with respect to the topic goals and specifically focus on the currently available code-based and model-based performance problem detection approaches and their applications to locate and remove performance problems.
Current work in the field can be divided into $n$ groups of general approaches: \emph{the first group}, \emph{the second group} \ldots.
\subsection{The first group of approaches} \label{subsec_FirstGroupRelated}
Here I say something smart about the first group of approaches to show the reader that I have a general understanding of the field and of what has been done by other groups of researchers so far.

\paragraph*{Open challenges addressed by the thesis project.}

In this proposal, we will develop something that nobody else does, related to the first set of approaches.  My approach has the advantage that it is \emph{much better than other approaches}.  As an example, reconsider \autoref{subsec_FirstGroupRelated}, but now including \emph{something I think is important}.  By quantifying this we can do \emph{that}.  By capturing and quantifying \emph{this}, we open a wide range of new applications, pushing forward the state of the art in this field. We strive to address the following challenges that we identified by studying the literature in the field:

\begin{keypoints}
	\item How can we utilize \emph{this} in order to obtain \emph{that}?
	\item Based on that, how can we develop an even faster way to do \emph{this} while meeting the crucial requirements?
	\item In what way will performing \emph{that} influence the realm of time and space?
\end{keypoints}



\subsection{The second group of approaches} \label{subsec_SecondGroupRelated}
\ldots

\paragraph*{Open challenges addressed by the thesis project.}

Challenges related to the second group of approaches:

\begin{keypoints}
	\item \ldots
	\item \ldots
	\item \ldots
\end{keypoints}




\section{Objectives and work program}


\subsection{Anticipated total duration of the project}

I anticipate a total duration of \emph{4 or 6 months.}


\subsection{Objectives}
\label{sec-objectives}

This thesis aims to improve and investigate the following:

\begin{compact_itemize}
	\item In \emph{one field}, the focus is on \emph{something}, while \emph{problems are these}, where yet undiscovered defects may loom.
	\item In \emph{other field}, the goal is to \emph{do this}, unveiling new horizons.
	\item In \emph{the third}, the idea is to achieve excellent achievement in the field of excellence.
\end{compact_itemize}
The key concept for these aims is \emph{this}, a  technique which does \emph{that}.  These techniques are \emph{normal} in contrast to \emph{abnormal} behavior, and thus fuel the innovations above.

In order to reach the overall goal of the project, \ProjectAcronym is structured into four work packages, outlined below, whose interplay could be visualized in a similar way as in \autoref{fig-approach}. If I would use this exact figure in my proposal, it would probably not get accepted. Additionally, I may of course have more or less than four work packages, depending on what suits my project.

\begin{figure}[htb]
\begin{centering}
\includegraphics[width=0.99\textwidth]{img/verdun-sketch-anon.pdf}
\caption{Example overview of a project}\label{fig-approach}
\end{centering}
\end{figure}


%short introduction of work package macros (for consistency)
\newcommand{\WPone}{Something, something and doing something}
\newcommand{\WPtwo}{Working in a coal mine}
\newcommand{\WPthree}{Sixteen tons}
\newcommand{\WPfour}{Celebration preparation}

\begin{description}
	\item[\ref{wp:something}: \WPone.] The first work package (\ref{wp:something}) will provide something.
\end{description}
\noindent
Problems from \ref{wp:something} will then form a base for the next three work packages (\ref{wp:work-something}, \ref{wp:do-this} and \ref{wp:do-that}).
\begin{description}
	\item[\ref{wp:work-something}: \WPtwo.] The second work package will use \emph{something} to do the work on doing \emph{the things}.
	\item[\ref{wp:do-this}: \WPthree.]  Using a white-box approach, dirt will be dug.
	\item[\ref{wp:do-that}: \WPfour.]  In the fourth work package, using data provided by \ref{wp:work-something}, we prepare the celebration party if this proposal gets accepted.
\end{description}
In all work packages, the research shall be driven by \emph{some procedure} on real-life systems or dead-life systems.  Furthermore, the results from WP2--WP4 will continuously provide feedback for WP1. This is basically a lot of nonsensical text.


\subsection{Work programme incl. proposed research methods}
\label{subsec-workprogram}

\begin{figure}[ht]
\centering
\includegraphics[width=\linewidth]{img/gantt}
\caption{An example work plan of another project}
\label{fig:work-plan}
\end{figure}


% In this section, subsections are organized by packages -- AZ
\newcounter{wp}
\let\oldthesubsection=\thesubsection
\def\thesubsection{WP\arabic{wp}}
% \def\package#1{\subsection[\protect\thesubsection{} {#1}]{#1}}
\def\package#1{\addtocounter{wp}{1}\subsection{#1}}

% Use \task to introduce tasks
\let\oldthesubsubsection=\thesubsubsection
\def\thesubsubsection{\thesubsection.\arabic{subsubsection}}
% \def\task#1{\subsubsection[\thesubsubsection{} {#1}]{#1}}
\let\task=\subsubsection

In the following, we present the details of each of the work packages, discussing the motivation, the research plan together with the individual tasks, as well as the intended research methodology and validation strategy to be used. An anonymized example work plan is shown in \autoref{fig:work-plan}.

%%%%%%%%%%%%%%%%%%%% New WP Starts
\package{\WPone.}
\label{wp:something}

\paragraph{Challenges and motivation.}
Here, you should summarize challenges and motivation for the work package at hand. For example, you could write things like:

For this work package, the main challenge will be to find the right balance between something and something else.  This search will be driven by \emph{other things} and experiments in \ref{wp:work-something}, \ref{wp:do-this}, \ref{wp:do-that}.

\paragraph{Research plan and individual research tasks.}
In this work package, we create the theoretical foundation for the required \emph{somethings} that satisfy the requirements of the \emph{something elses}.

\task{Refining something}
\label{task-wp1-1}

The first task aims to provide effective algorithms for probabilistic model construction.  Existing approaches~\cite{Hoorn2012} will be used as a baseline to derive algorithms that do \emph{something}. I am now just citing~\cite{AspectJ} for the fun of it.  It is widely accepted that Novel \emph{probabilistic something} approaches are expected to
\begin{compact_itemize}
    \item do \emph{something} that will be explained here in a sentence or two, and
    \item do \emph{something else}, using {\it aReallyNiceFramework}~\cite{Frey2011}.
\end{compact_itemize}
%
To this end, we will have to deal with two challenges:
\begin{description}
    \item[Noise.] Look at this wonderful paragraph with mathematical formulae.  Rather than learning a complete model that covers the entire state space, axioms that capture \emph{conditional probabilities} between two or more events may already be sufficient for producing test suites with comparable quality.  For instance, if we know that two events $A$~and~$B$ normally follow each other (formally: $\mathcal{P}_{\geq 1} [\square(A \Rightarrow \mathcal{P}_{\geq 0.99}(\Diamond B) )]$), we can focus on precisely such sequences (to test common behavior), or its complement (to test uncommon behavior).

    \item[Granularity.]  We would be na\"\i{}ve to expect a single ``one size fits all'' specification. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Alea iacta est.
\end{description}

\noindent It is thus expected that this WP is driven by the impact of algorithmic choices on the effectiveness of the mined specifications in tasks \ref{wp:do-this}, \ref{wp:do-that}, and~\ref{wp:work-something}.  After an experimental evaluation on a large set of sample instances, each iteration of the WP will thus produce individual software assessment tasks.

\paragraph{Research methodology and validation strategy.}
In this work package, we use different fundamental methods to greatly decrease performance, and we avoid any technique that provides even the slightest increase of accuracy. Hah, got you! No, we don't do that, of course. We use some profound methods and mechanisms that provide assistance to our research. You should state here, how you intend to achieve your stated goals and how you intend to validate your results in the end.

\task{The second important task}
\label{task-wp1-2}

Do something similar to what was done in \ref{task-wp1-1}.

%%%%%%%%%%%%%%%%%%%% New WP Starts
\package{\WPtwo.}
\label{wp:work-something}
Again, describe what you will do in this package, refine it in subtasks.

%%%%%%%%%%%%%%%%%%%% New WP Starts
\package{\WPthree.}
\label{wp:do-this}
Again, describe what you will do in this package, refine it in subtasks. Gets repetitive, doesn't it?

%%%%%%%%%%%%%%%%%%%% New WP Starts
\package{\WPfour.}
\label{wp:do-that}
Again, describe what you will do in this package, refine it in subtasks. It's enough, stop it already!


\let\thesubsection=\oldthesubsection
\let\thesubsubsection=\oldthesubsubsection
\setcounter{subsection}{3}

\subsection{Data handling}
%[Example content]
%The research work done in the project does not depend on the collection and management of large sets of scientific data.

%Scientific papers published within the project can be found in the publication sections of the web pages of the participating groups and researchers.

All results from the thesis experiments will be publicly available, including all data and all code. In addition, the thesis source code will be made available through a public repository (e.g. github.com), such that additional researchers can use it and contribute to the project. Each published experiment will be made replicable through included automated scripts.

\subsection{Other information}
If any.







\section{Bibliography}

\bibliographystyle{alpha}
\bibliography{bibliography}

\section{Project requirements}
Description of what is required for project.
\subsection{Cooperation with other researchers}
List of researchers you plan to collaborate with, if any. If so, to what extent and in what manner do you plan to collaborate?

\subsection{Scientific equipment}
If you need some equipment, describe it here. Cars and planes will not be made available, though, no matter how badly you need it.

\subsection{Project-relevant interests in commercial enterprises}
Describe them here.

%\section{Additional information}
%Any additional information.
\end{document}

