Skip to content
Snippets Groups Projects
Commit 613567a5 authored by W. Spencer Smith's avatar W. Spencer Smith
Browse files

Added some additional feedback to the requirements lecture

parent 8bdb4fa9
No related branches found
No related tags found
No related merge requests found
No preview for this file type
......@@ -1150,6 +1150,38 @@ to improve reliability
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\begin{frame}
\frametitle{Feedback From Previous Years}
\begin{itemize}
\item Remember that you are writing the document for someone other than yourself
\item Introduction section gives the name for the software/library
\item Use \texttt{citep} and \texttt{citet} for \texttt{natbib}
\item When the assumptions are listed, traceability is given to where they are
used
\item If assumptions are not used, then they may not be necessary, or they might
be scope decisions
\item For NFRs, specify what you want, not how to achieve it
\item NFRs can point to the VnV plan for details (to make them unambiguous)
\end{itemize}
\end{frame}
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\begin{frame}
\frametitle{Feedback From Previous Years}
\begin{itemize}
\item For reader/user characteristics, give the target course and what level it is taught. (Use a generic name, not a specific course name.)
\item Rationale provided for assumptions, scope decisions and constraints
\item Include a reference to the source of the template you are using
\item Requirements should trace to IMs
\item Define all symbols in table of contents and in Description field
\end{itemize}
\end{frame}
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\begin{frame}[allowframebreaks]
\frametitle{References}
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment