Updates to L19

Lectures/Deadlines.tex

@@ -92,8 +92,8 @@ Unit VnV/Implement & Week 12 & Week of Apr 3\\
 \bi
 \item Implementation Present (15 min each)
 \bi
-\item {Mar 26: Reyhaneh, Waqar, Al, Tanya, Atiyeh}
-\item {Apr 2: Nada, Phil, Xinyu, Fasil, Yi-Leng}
+\item \textbf{Mar 26: Reyhaneh, Waqar, Al, Tanya, Atiyeh}
+\item \textbf{Apr 2: Nada, Phil, Xinyu, Fasil, Yi-Leng}
 \item {Apr 5: Gaofeng, Morteza, Valerie, Hunter, Ali}
 \item {Apr 9: Cynthia, Adrian, Yiding, Kim Ying}
 \ei

Lectures/L19_AssuranceCase/AssuranceCase.tex

@@ -104,7 +104,7 @@
 \begin{itemize}
 \item Based on your implementation and testing
 \item You decide what to focus on
-\item If in doubt, Ask
+\item If in doubt, ask
 \item Options
 \begin{itemize}
   \item Demonstration
@@ -151,6 +151,7 @@ requirement and trace it all the way to testing
 \begin{frame}
 \frametitle{Final Documentation}
 \begin{itemize}
+\item Faking a rational design process
 \item Problem Statement revised and improved
 \item Requirements Document revised and improved
 \item Design Documents revised and improved
@@ -177,12 +178,14 @@ requirement and trace it all the way to testing
 
 \item Summarize changes in response to feedback from reviewers,
 instructor, supervisor, users
+\item Include hyperlinks to relevant closed issues
 \item Explain how you arrived at your final design and implementation
 \item Reflect on and justify your design decisions
 \item Ignore questions related to:
 \begin{itemize}
   \item Hazard analysis
   \item Economic considerations
+  \item Feedback on capstone
 \end{itemize}
 \item How did your project management compare to your dev plan
 \begin{itemize}
@@ -222,6 +225,7 @@ instructor, supervisor, users
 \item Use a ``light weight'' VM like docker
 \item Include installation instructions (INSTALL.txt)
 \item Include instructions so that someone else can run your tests cases
+\item Part of the evaluation of each project is to run it
 \ei
 
 \end{frame}
@@ -368,8 +372,8 @@ instructor, supervisor, users
 \item Avoidance of hard-coded constants (other than maybe 0 and 1)
 \item Appropriate modularization
 \bi
-\item Generally follow module guide
-\item Show explicit traceability between MG modules and code files
+\item Follow module guide
+\item Show traceability between MG modules and code files
 \ei
 \item Consistent indentation
 \item Explicit identification of coding standards (see next slide)
@@ -394,10 +398,7 @@ instructor, supervisor, users
 \item \href{https://google.github.io/styleguide/cppguide.html}{C++}
 \item \href{https://google.github.io/styleguide/javaguide.html}{Java}
 \ei
-\item
-  \href{https://developer.mozilla.org/en-US/docs/Mozilla/Developer_guide/Coding_Style}{Mozilla
-    Developer Network}
-\item \href{http://homepages.inf.ed.ac.uk/dts/pm/Papers/nasa-c-style.pdf}{NASA C
+\item \href{https://ntrs.nasa.gov/citations/19950022400}{NASA C
     Style Guide}
 \ei
 %\item Your decisions on style may evolve over the project
@@ -645,7 +646,7 @@ instructor, supervisor, users
 %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
 
 \begin{frame}
-\frametitle{Assurance Cases in Scientific Computing \cite{SmithEtAl2020,SmithEtAl2018_ICSEPoster}}
+\frametitle{Assurance Cases in Scientific Computing \cite{SmithEtAl2018_ICSEPoster,SmithEtAl2020}}
 
 \bi
 \item Assurance cases