attachment:generic-template.tex of WritingTechnicalPapersInLaTeX

   1 \documentclass[pdf,bookmarks,colorlinks=true]{IEEEtran}
   2 \usepackage{times}
   3 \usepackage{amsmath}
   4 \usepackage{hyperref}
   5 \usepackage{url}
   6 \usepackage{psfrag}    %Shouldn't use this if you plan on using pdflatex!
   7 \usepackage{graphicx}
   8 \usepackage{wrapfig}   %for wrapping text around figures and tables
   9 
  10 %Included for Gather Purpose in WinEdt only:
  11 %input "my.bib"
  12 
  13 \title{\bf Generic Technical Paper Skeleton}
  14 
  15 \author{Scot Anderson\\
  16 Southern Adventist University\\
  17 scot@southern.edu
  18 }
  19 
  20 \begin{document}
  21 
  22 \maketitle
  23 
  24 \begin{abstract}
  25 
  26 The abstract should describe the basic message of the paper, including: the
  27 problem, why your solution should be of interest, some notion that your
  28 solution is effective, and a teaser about how it has been evaluated. Cover all
  29 of this using between 75 and 150 words. The abstract is thus the hardest part
  30 to write. Sometimes I try to write it first, but the final version is usually
  31 composed of items drawn from the introduction, and then condensed, as the last
  32 step of writing the paper.
  33 
  34 \end{abstract}
  35 
  36 %   \tableofcontents
  37 %   \newpage
  38 
  39 % \doublespace
  40 
  41 \section{Introduction}
  42 \label{sec:Introduction}
  43 
  44 \textbf{The problem we have solved:}
  45 
  46 %\begin{itemize}
  47 %\item
  48 Concentrate on making {\em this} assertion and {\em only} this assertion in a
  49 succinct set of 1 to 3 paragraphs
  50 
  51 %\item
  52 A common mistake is to explain too much of the problem context first. Instead,
  53 state the problem essentially as a claim, and leave explanations supporting
  54 your claim to the next part, ``Why it is not already solved.''
  55 
  56 %\end{itemize}
  57 
  58 
  59 \textbf{Why the problem is not already solved or other solutions
  60 are ineffective in one or more important ways}
  61 
  62 %\begin{itemize}
  63 %\item
  64 Your new idea need not solve every problem but it should solve at least one
  65 that is not already solved
  66 
  67 %\item
  68 This is the place to provide a succinct description of the problem context
  69 giving enough information to support the claim that a problem exists, made in
  70 the preceding problem declaration.
  71 
  72 %\end{itemize}
  73 
  74 
  75 \textbf{Why our solution is worth considering and why is it effective
  76 in some way that others are not}
  77 
  78 %\begin{itemize}
  79 %\item
  80 A succinct statement of {\em why} the reader should care enough to read the
  81 rest of the paper.
  82 
  83 %\item
  84 This should include a statement about the characteristics of your solution to
  85 the problem which 1) make it a solution, and 2) make it superior to other
  86 solutions to the same problem.
  87 
  88 %\end{itemize}
  89 
  90 
  91 \textbf{How the rest of the paper is structured}
  92 %\begin{itemize}
  93 %\item
  94 The short statement below is often all you need, but you should change it when
  95 your paper has a different structure, or when more information is {\em
  96 required} to describe what a given section contains. If it isn't {\em required}
  97 then you don't want to say it here.
  98 
  99 %\end{itemize}
 100 
 101 The rest of this paper first discusses related work in
 102 \ref{sec:RelatedWork}, and then describes our implementation in
 103 \ref{sec:Implementation}. \ref{sec:Evaluation} describes how we evaluated
 104 our system and presents the results. \ref{sec:Conclusion} presents our
 105 conclusions and describes future work.
 106 
 107 \section{Related Work}
 108 \label{sec:RelatedWork}
 109 
 110 \textbf{Other efforts that exist to solve this problem and why are they
 111 less effective than our method}
 112 
 113 %\begin{itemize}
 114 %\item
 115 Resist the urge to point out only flaws in other work. Do your best to point
 116 out both the strengths and weaknesses to provide as well rounded a view of how
 117 your idea relates to other work as possible
 118 
 119 %\item
 120 In a social and political sense, it is {\em very smart} as well as ethical to
 121 say good things, which are true, about other people's work. A major motivation
 122 for this is that editors and program committee members have to get a set of
 123 reviews for your paper. The easiest way for them to decide who should review it
 124 is to look at the set of references to {\em related work} (e.g.,
 125 \cite{Anderson2007,Anderson2009}) to find people who are likely to be competent to
 126 review your paper.  The people whose work you talk about are thus likely to be
 127 reading what you say about {\em their} work while deciding what to say about
 128 {\em your} work.
 129 
 130 %\item
 131 Clear enough? Speak the truth, say what you have to say, but be generous to the
 132 efforts of others.
 133 
 134 %\end{itemize}
 135 
 136 
 137 \textbf{Other efforts that exist to solve related problems that are
 138 relevant, how are they relevant, and why are they less effective than our
 139 solution for this problem}
 140 
 141 %\begin{itemize}
 142 %\item
 143 Many times no one has solved your exact problem before, but others have solved
 144 closely related problems or problems with aspects that are strongly analogous
 145 to aspects of your problem
 146 
 147 %\end{itemize}
 148 
 149 \section{Implementation}
 150 \label{sec:Implementation}
 151 
 152 \textbf{What we (will do $|$ did): {\em Our Solution}}
 153 %\begin{itemize}
 154 %\item
 155 Another way to look at this section is as a paper, within a paper,
 156 describing your implementation. That viewpoint makes this the introduction to
 157 the subordinate paper, which should describe the overall structure of your
 158 implementation and how it is designed to address the problem effectively.
 159 
 160 %\item
 161 Then, describe the structure of the rest of this section, and what each
 162 subsection describes.
 163 
 164 
 165 \textbf{How our solution (will $|$ does) work}
 166 %\begin{itemize}
 167 %\item
 168 This is the body of the subordinate paper describing your solution. It
 169 may be divided into several subsections as required by the nature of your
 170 implementation.
 171 
 172 %\item
 173 The level of detail about how the solution works is determined by what
 174 is appropriate to the type of paper (conference, journal, technical report)
 175 
 176 %\item
 177 This section can be fairly short for conference papers, fairly long for
 178 journal papers, or {\em quite} long in technical reports. It all depends on the
 179 purpose of the paper and the target audience
 180 
 181 %\item
 182 Proposals are necessarily a good deal more vague in this section since
 183 you have to convince someone you know enough to have a good chance of building
 184 a solution, but that you have not {\em already} done so.
 185 
 186 %\end{itemize}
 187 
 188 
 189 \section{Evaluation}
 190 \label{sec:Evaluation}
 191 
 192 \textbf{How we tested our solution}
 193 \begin{itemize}
 194 \item   Performance metrics
 195 \item   Performance parameters
 196 \item   Experimental design
 197 \end{itemize}
 198 
 199 
 200 \textbf{How our solution performed, how its performance compared to
 201 that of other solutions mentioned in related work, and how these results show
 202 that our solution is effective}:
 203 
 204 \begin{itemize}
 205 \item   Presentation and Interpretation
 206 \item   Why, how, and to what degree our solution is better
 207 \item   Why the reader should be impressed with our solution
 208 \item   Comments
 209 
 210 \end{itemize}
 211 
 212 
 213 \textbf{Context and limitations of our solution as required for
 214 summation:} State what the results {\em do} and {\em do not} say.
 215 
 216 
 217 
 218 \section{Conclusions and Future Work}
 219 \label{sec:Conclusion}
 220 
 221 \textbf{The problem we have solved}: The most succinct statement of the problem in the paper. Ideally one
 222 sentence. More realistically two or three. Remember that you simply state it
 223 without argument. If you have written a good paper you are simply reminding the
 224 reader of what they now believe and of how much they agree with you.
 225 
 226 
 227 
 228 \textbf{Our solution to the problem}: again, a succinct statement of the presented solution
 229 Sometimes it works well to leave it at that and not even describe your
 230 solution here. If you do, then again state your solution in one or two
 231 sentences taking the rhetorical stance that this is all obvious. If you have a
 232 good solution and have written an effective paper, then the reader already
 233 agrees with you.
 234 
 235 \textbf{Why our solution is worthwhile in some significant way}:
 236 Again, a succinct restatement in just a few sentences of why your solution is
 237 worthwhile assuming the reader already agrees with you
 238 
 239 \textbf{Why the reader should be impressed and/or pleased to have read the paper}:
 240 A few sentences about why your solution is valuable, and thus why the
 241 reader should be glad to have read the paper and why they should be glad you
 242 did this work.
 243 
 244 
 245 
 246 \textbf{What we will (or could) do next}
 247 
 248 \begin{itemize}
 249 \item   Improve our solution
 250 \item   Apply our solution to harder or more realistic versions of this problem
 251 \item   Apply our solution or a related solution to a related problem
 252 
 253 \end{itemize}
 254 
 255 
 256 \bibliographystyle{IEEETrans}
 257 \bibliography{./my}
 258 
 259 
 260 \end{document}