Added a slide on judging abstraction level

Lectures/L16_MISContinued/MISContinued.tex

@@ -1108,6 +1108,32 @@ $ms$: real
 
 %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
 
+\begin{frame}
+\frametitle{Judging Appropriate Abstraction}
+
+\begin{itemize}
+\item If an MIS is too abstract, it won't capture enough information for someone
+  to do the implementation
+\item In some cases an MIS is not abstract enough
+\bi
+\item This can happen when someone is reverse engineering their spec from
+  exisiting code
+\item Can happen with an operational specification, as opposed to a descriptive
+  specification
+\ei
+\item Judge the abstraction level by
+\bi
+\item If a change in how your code works requires a change in your
+  specification, look for a better abstraction
+\item If writing and maintaining the spec is exceedingly frustrating, the spe
+  could be too concrete
+\ei
+\end{itemize}
+
+\end{frame}
+
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+
 \begin{frame}
 \frametitle{Examples}